The Old School Manifesto
Mon, 10/11/08 – 22:08 | 2 Comments

As we saw in the last essay, the 80:20 rule seemingly appears in many circumstances. When I was attending college and working as a programmer during the 80’s, there were some commonly accepted tenets that guided our software development processes and behaviors.

Read the full story »
Management

Methodology

Metrics

Quality

Requirements

Home » Requirements

Aim for Excellence

Submitted by Bill Miller on Tuesday, 1 April 2008 3 Comments

I’ve been reading a few essays on blogs that say the aim should be good enough.  It’s hard for me to get excited about good enough.  It’s not very motivating. Think about it.  Can you get excited to get up every morning and say, “I can’t wait to go to work today and do a good enough job?”  How uninspiring?

Picture this.  You are a member of a new project team that is planning to build a new product that competes with Yahoo, Google, and Microsoft.  The manager calls a project kickoff meeting with the software development team.  To motivate and focus the team, he outlines the strategy to the troops.   He exclaims, “I don’t want you to get carried away with aiming for perfection.  Our goal is to develop a good enough product to begin to win market share away from Yahoo, Google, and Microsoft.”  It’s like some Dilbert cartoon. 

I didn’t get into the software business to build good enough products, and I’m pretty sure most people in this business didn’t either.   Could you picture yourself interviewing with a company, and the interviewer says, “Our software teams aim to build good enough products.”  As you shake hands and begin to exit the interview, you ask yourself, “I wonder how many people they hook with that line?”

Think about it.  Has Apple dominated the MP3 space because they decided to build a good enough product?   Has Apple actually aimed to build anything that you would consider good enough?  Is Google dominating the search market because their search is good enough?  Is the huge demand for the WII game console the result of a good enough product decision? 

Who get’s inspired to buy good enough?  What kind of demographic is that?  If you’re aiming to sell your products in the local five and dime store, good enough is all that’s required.  The commercial software market is extremely competitive.  Good enough won’t cut it for very long.

People who advocate good enough contrast it with perfection, but there is another choice: excellence.  Choose to build an excellent product.  Choose to build the best product. Not only will it be good for the bottom line, you will find that you are attracting the best talent in the industry.  Morale is high when individuals and teams are aiming high.  The best talent doesn’t aim to be good enough; they aim to be the best.  Aim to be good enough, and those who aim for excellence will leave your company and your products in the dust.

Email This Post Email This Post Print This Post Print This Post
Vote This Post DownVote This Post Up (No Ratings Yet)
Loading ... Loading ...

Related Articles:

  • Quality Matters More
  • Agile Content is the Goal
  • Does Agile Solve the Right Problem?
  • Back to the Future
  • Reflection: Weighing the Future

  • 3 Comments »

    • Steve Johnson said:

      Great post. Thanks!

      Companies should strive to create remarkable products and experiences. Those companies–and employees–who do ‘just enough to get by’ will never create products that delight customers. Companies who sweat the details are companies that build great products.

    • Ray Koscinski said:

      We should be careful to not confuse Good Enough releases with Good Enough products. By this I mean that there are windows of opportunity and if you miss your window you miss your market no matter how great the product is. It is in these situations where you need to make ‘good enough’ early releases to get your foot in the door. Then in subsequent releases you strive for the best you can be because if you don’t chances are someone else will be just good enough to beat you.

    • Bill Miller (author) said:

      Hi Ray,

      You make an excellent point, and there are certainly trade-offs that need to be made in the interest of hitting the market timely as you correctly recommend.

      My objection is with the criteria good enough. It’s nebulous, and it doesn’t have enough fidelity to make good product decisions. One person’s good enough is another’s bad, and still another’s excellent. Finally good enough may not be enough to beat your competitor no matter how timely, so we need to frame our criteria in language and objectives that focus on how to win in the marketplace.

      Our behaviors resemble the words we use, and when a team is thinking in words good enough, I believe it morphs into mediocrity and poor products: products nobody gets excited about.

    Leave a comment!

    Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

    Be nice. Keep it clean. Stay on topic. No spam.

    You can use these tags:
    <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

    This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.