Group items tagged

I’ve found that entrepreneurs tend to love talking about the future of higher education, largely because it didn’t work well for them and they want to see something different.

Let me know if something resonates with you or your workplace. I’d love to hear from libraries practicing a similar R&D methodology.

"We assume that telling people things without asking them to actively process them results in learning," Mr. Wieman said. The conference, which also featured demonstrations of innovative approaches to teaching, was the first event in a new Harvard Initiative for Learning and Teaching

Take, for example, the lecture, which came up for frequent shellacking throughout the day. It is designed to transfer information, said Eric Mazur, professor of physics at Harvard. But it does not fully accomplish even this limited task. Lectures set up a dynamic in which students passively receive information that they quickly forget after the test. "They're not confronted with their misconceptions," Mr. Mazur said. "They walk out with a false sense of security."

The traditional lecture also fails at other educational goals: prodding students to make meaning from what they learn, to ask questions, extract knowledge, and apply it in a new context.

Asking students to explain concepts or to teach one another the material they have just learned are also effective.

Writing is often an effective pedagogical tool, too, several speakers said. For his history of psychology course, Mr. Roediger asks his students to send him short essays before each class meets. They respond to the reading. (Others at the conference who use this method said they sometimes ask their students to identify outstanding questions or relevant areas of their reading that have been left unexplored.) Mr. Roediger reads the one-page essays before class and works their thoughts into his comments.

By that point, there were a solid five decades of industrial research that proved, beyond a doubt, that if you wanted to keep your workers bright, healthy, productive, safe and efficient over a sustained stretch of time, you kept them to no more than 40 hours a week and eight hours a day.

After WWII, as the GI Bill sent more workers into white-collar jobs, employers at first assumed that the limits that applied to industrial workers probably didn’t apply to knowledge workers. Everybody knew that eight hours a day was pretty much the limit for a guy swinging a hammer or a shovel; but those grey-flannel guys are just sitting at desks. We’re paying them more; shouldn’t we be able to ask more of them? The short answer is: no. In fact, research shows that knowledge workers actually have fewer good hours in a day than manual laborers do — on average, about six hours, as opposed to eight. It sounds strange, but if you’re a knowledge worker, the truth of this may become clear if you think about your own typical work day. Odds are good that you probably turn out five or six good, productive hours of hard mental work; and then spend the other two or three hours on the job in meetings, answering e-mail, making phone calls and so on. You can stay longer if your boss asks; but after six hours, all he’s really got left is a butt in a chair. Your brain has already clocked out and gone home.

Another is that overtime is only effective over very short sprints. This is because (as Sidney Chapman showed in 1909) daily productivity starts falling off in the second week, and declines rapidly with every successive week as burnout sets in. Without adequate rest, recreation, nutrition and time off to just be, people get dull and stupid. They can’t focus.

The Business Roundtable study found that after just eight 60-hour weeks, the fall-off in productivity is so marked that the average team would have actually gotten just as much done and been better off if they’d just stuck to a 40-hour week all along. And at 70- or 80-hour weeks, the fall-off happens even faster: at 80 hours, the break-even point is reached in just three weeks.

Wise managers who understand this will a) avoid requiring overtime crunches, because they’re acutely aware of the serious longer-term productivity hit that inevitably follows; b) keep the crunches as short as possible when they are necessary; and c) give their teams a few days off — one to two comp days per overtime week worked is about right — at the end of a hard sprint. This downtime enables them recuperate more quickly and completely. It’s much more productive to have them gone for the next week — and then back on the job, rested and ready to work — than have them at their workstations but too fried to get anything useful done for the next month.

The other thing about knowledge workers is that they’re exquisitely sensitive to even minor sleep loss. Research by the US military has shown that losing just one hour of sleep per night for a week will cause a level of cognitive degradation equivalent to a .10 blood alcohol level. Worse: most people who’ve fallen into this state typically have no idea of just how impaired they are. It’s only when you look at the dramatically lower quality of their output that it shows up. Robinson writes: “If they came to work that drunk, we’d fire them — we’d rightly see them as a manifest risk to our enterprise, our data, our capital equipment, us and themselves. But we don’t think twice about making an equivalent level of sleep deprivation a condition of continued employment.”

And it hurts the country, too. For every four Americans working a 50-hour week, every week, there’s one American who should have a full-time job, but doesn’t. Our rampant unemployment problem would vanish overnight if we simply worked the way we’re supposed to by law.

For these people, work wasn’t just work; it was their life’s passion, and they devoted every waking hour to it, usually to the exclusion of non-work relationships, exercise, sleep, food and sometimes even personal care. The popular stereotype of the geek was born in some real truths about the specific kinds of people who were drawn to tech in those early years.

Companies broadened their working hours, so programmers who came in at noon and worked through till midnight could make their own schedules. Dress codes were loosened; personal eccentricities were celebrated. HP famously brought in breakfast every morning so its engineers would remember to eat.

There were two problems with this. The first is that this “passion” ideal didn’t recognize that the vast majority of people have legitimate physical, emotional and psychological needs — things like sleep, exercise, relaxation and the maintenance of strong family and social support bonds — that these engineers didn’t have to nearly the same degree. The second was that most managers, lacking windows into their workers’ souls, decided to cut corners and measure passion with one easy-to-chart metric: “willingness to spend your entire life at the office.”

The unions — for 150 years, the guardians of the 40-hour week — were falling under a conservative onslaught; and in their place, the new cult of the entrepreneur was ascendant.

“working 90 hours a week and loving it!” (an actual T-shirt worn with pride by the original Macintosh team. (Productivity experts estimate that we’d have probably had the Mac a year sooner if they’d worked half as many hours per week instead.)

Within 15 years, everything America’s managers used to know about sustaining worker productivity was forgotten. Now, 30 years and a few economic meltdowns on, the cafeterias and child-care centers and gyms are mostly gone, along with the stock options and bonuses that were once held out as the potential reward for the long hours. All that remains of those heady, optimistic days is the mandatory 60-hour work-week. And, unless you’re an hourly worker — still entitled to time and a half by law — the only inducement employers currently offer in exchange for submitting yourself to this abuse is that you get to keep your job.

There are now whole industries and entire branches of medicine devoted to handling workplace stress, but the bottom line is that people who have enough time to eat, sleep, play a little, exercise and maintain their relationships don’t have much need of their help. The original short-work movement in 19th-century Britain demanded “eight for work, eight for sleep and eight for what we will.” It’s still a formula that works.

Here’s why. By the eighth hour of the day, people’s best work is usually already behind them (typically turned in between hours 2 and 6). In Hour 9, as fatigue sets in, they’re only going to deliver a fraction of their usual capacity. And with every extra hour beyond that, the workers’ productivity level continues to drop, until at around 10 or 12 hours they hit full exhaustion.

But the bottom line is: For the good of our bodies, our families, our communities, the profitability of American companies, and the future of the country, this insanity has to stop. Working long days and weeks has been incontrovertibly proven to be the stupidest, most expensive way there is to get work done.

Every interview subject conducted some sort of a literature review as part of any research project

Every researcher described some strategies for keeping up with new developments in their area of expertise, all of which involved some scanning of new publications and some personal contact with individuals exploring the same territory.

For most, presenting research at conferences was a common part of bringing their research to completion. For all, writing up results for publication was an important final step, and they seemed acutely aware of the pecking order for publication venues in their field.

(In contrast, undergraduates mostly encounter articles within databases, called up by key words, not as artifacts within a particular journal which carries clout.)

One thing the students all gained through these interviews was an appreciation that research is not a matter of finding answers in other people’s publications. Every scholar interviewed described how they had asked a question that nobody had asked before, a question they couldn’t answer themselves until they had completed the research. It struck me that so much of what undergraduates experience as “research” is very nearly the opposite, a process of uncovering answers others have already arrived at.

I’m also thinking about what these interviews said collectively about how real research is conducted. It makes me a little crazy when students abandon a truly interesting question because they can’t find sources to quote that provide the answer, or when they change their topic based on what they can find easily. Or (shudder) when they say they've written their paper, but need help finding five sources to cite. Clearly, they are not learning how to do research; they aren't even learning what research is.  What I would really, really like is to figure out how to give every student the experience of not worrying so much about getting the right answers, but learning how to ask a really good question. The kind they won't find answered in the library.