GovLoop - Knowledge Network for Government

Design For Yourself, Not For Your Customer?

On August 24, 2011, Steve Jobs resigned as the CEO of Apple Inc. Whether or not you like his products, it’s hard not to be fascinated by the black turtleneck-wearing visionary. Over the course of his career, Jobs has said many insightful and profound statements about technology, PCs, business, the future, and life in general. One interesting perspective he had was around design.

“We think the Mac will sell zillions, but we didn’t build the Mac for anybody else. We built it for ourselves. We were the group of people who were going to judge whether it was great or not. We weren’t going to go out and do market research. We just wanted to build the best thing we could build.” (source here)


“You can’t just ask customers what they want and then try to give that to them. By the time you get it built, they’ll want something new.” (source here)


”It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.” (source here)

As one trained to cater to the customer, I’ve always emphasized the importance of user testing and focus groups. Perhaps a bit too much at times. Naturally, I was a bit surprised to learn of Jobs’ perspective.


But I couldn’t help but be a little inspired, because Jobs is not talking about ignoring your customers; he’s talking about having a certain level of passion and conviction in what you do. I became a little introspective, asking myself questions like:


1) Do I believe in my work?

2) Am I emotionally invested in my work?

3) Do I want to innovate?

4) Do I want the product to look good?

5) Do I want to surprise my customers?

6) Do I take shortcuts?


I think Steve Jobs’ attitude can and should translate to government. It’s about going beyond the minimal requirements and putting out something you’re passionate about. You don’t have to change the world to make a difference. Just put forth your best effort, think outside the box a little, and deliver the best product you can with the resources you have. Don’t just do things for the sake of doing things; do it because you believe it adds value to your customers. 

Views: 114

Tags: 2, acquisition, career, jobs, project management, tech


You need to be a member of GovLoop - Knowledge Network for Government to add comments!

Join GovLoop - Knowledge Network for Government

Comment by Jon Lee on September 11, 2011 at 10:53pm
Thanks, Jay. The plan is to continue... another report going to the web in November.
Comment by Jay Johnson on September 9, 2011 at 6:18pm
The fact that you tried to improve something, followed through with it, and were successful is way more important than finding a word for it. Great job, and don't stop now!
Comment by Jon Lee on September 9, 2011 at 6:00pm
Actually, last year, we moved a traditional white paper like report to the web. You can see it at It was a small, radical change. The move to the web was radical but it wasn't as 2.0 as it could have been. What would you call it? kaizaken?
Comment by Patricia Paul on September 9, 2011 at 5:26pm
We may be defining history here gentlemen!  I'm sure over the weekend, this topic is going to stew in our brains and one of us is going to come up with the next big change to white papers!
Comment by Jay Johnson on September 9, 2011 at 5:16pm

Well said Patricia! In Lean terminology, they are referred to as

  • Kaizen - small continuous change
  • Kaikaku - radical or exponential change

Kaizen would be putting that 75pg doc online instead of printing it out. Kaikaku might start by asking, "Does anyone even read this? Can we get rid of it?" The result could completely alter the report's form or even existence.


Comment by Jon Lee on September 9, 2011 at 4:33pm
Good question, Patricia. How about this for an example: does government need to keep publishing lengthy academic white paper reports that just sits on a shelf? It's something that we're so accustomed to doing, but the rest of the world has moved on. What if you took your 75 page report, took out the superfluous words, and turned it into a website?
Comment by Patricia Paul on September 9, 2011 at 4:16pm

OK-so Ford didn't say that exactly.  However, to use the automotive example to illustrate the difference between adding a few/or many accessories or optional items as compared with changing the whole essence of how people were able to move around and get from point A to point B.  I'm really glad that Henry Ford perservered with his singular vision and that other visionaries saw that it was going to be important to add options and choices and made it possible for me to have a red car if I wanted.  It takes both kinds of visionaries.  My question would be this--would we still be trying to paint horses different colors and add better sound systems to our horses if Henry Ford hadn't risked it all on the Model T.


Some people have ideas that change the very essence and being of a process and some people have the vision to add the "extras" and make sure that everyone can get just what they want.  It takes both kinds to make a great product or service and it takes both visionaries to be really excited about their creations!

Comment by Jon Lee on September 9, 2011 at 3:16pm
Interesting... I don't know enough about automotive history to have an opinion but the article makes a nice distinction between disruptive vs iterative innovation. Yes, there are definite risks to innovation. Many people forget the dark days of Apple when PCs dominated the market. I can't confirm this, but I remember reading that Steve Jobs lost a few billion in a single quarter. And of course, he was fired from Apple in the 80s.
Comment by Jay Johnson on September 9, 2011 at 2:31pm

Hold on, a recent HBR article suggests that Henry Ford never said that quote. It goes on to critize his inflexibility to changing customer demands.


The thing about the Steve Jobs like innovation is that there is a huge risk of failure. Steve knew that, but wouldn't have it any other way. So know what you're getting yourself into. While 90% of the time you'll fail, there's a huge upside if you do succeed. Keep the cost of failure low, and capitalize on the wins when get the chance.

Comment by Jon Lee on September 8, 2011 at 5:06pm
And Peter, I'm definitely borrow that quote for future use. Thanks!

© 2014   Created by GovLoop.

Badges  |  Report an Issue  |  Terms of Service