Skip to content

Instantly share code, notes, and snippets.

@charlesjohnson
Created December 16, 2014 20:52
Show Gist options
  • Save charlesjohnson/12641906914289fde5f9 to your computer and use it in GitHub Desktop.
Save charlesjohnson/12641906914289fde5f9 to your computer and use it in GitHub Desktop.
Talk about insight

The leaders at IDEO, the world’s preeminent product design firm, have designed products and experiences ranging from the first Apple mouse to a new Red Cross blood donation procedure. They understand the need to prepare their employees — and, more important, their clients — for failure.

Tim Brown, the CEO of IDEO, says that every design process goes through “foggy periods.” One of IDEO’s designers even sketched out a “project mood chart” that predicts how people will feel at different phases of a project. It’s a U-shaped curve with a peak of positive emotion, labeled “hope,” at the beginning, and a second peak of positive emotion, labeled “confidence,” at the end. In between the two peaks is a negative emotional valley labeled “insight.” Brown says that design is “rarely a graceful leap from height to height.” When a team embarks on a new project, team members are filled with hope and optimism. As they start to collect data and observe real people struggling with existing products, they find that new ideas spring forth effortlessly. Then comes the difficult task of integrating all those fresh ideas into a coherent new design. At this “insight” stage, it’s easy to get depressed, because insight doesn’t always strike immediately. The project often feels like a failure in the middle. But if the team persists through this valley of angst and doubt, it eventually emerges with a growing sense of momentum. Team members begin to test out their new designs, and they realize the improvements they’ve made, and they keep tweaking the design to make it better. And they come to realize, we’ve cracked this problem. That’s when the team reaches the peak of confidence.

Notice what team leaders at IDEO are doing with the peaks-and-valley visual: They are creating the expectation of failure. They are telling team members not to trust that initial flush of good feeling at the beginning of the project, because what comes next is hardship and toil and frustration. Yet, strangely enough, when they deliver this warning, it comes across as optimistic.

Heath, Chip; Heath, Dan (2010-02-10). Switch: How to Change Things When Change Is Hard (p. 169). Crown Publishing Group. Kindle Edition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment