BNET Insight

BNET Intercom

News and observations from the BNET staff

Perfectionists Despair: Digital World "Always in Beta"

October 3rd, 2007 @ 12:35 pm

4 Comments

Categories: General, Management, Marketing

Tags: Consumer, Innovation, Beta, Leadership, Strategy, Management, Jessica Stillman

the Digital World “Always in Beta”Today we mentioned that Craigslist CEO, Jim Buckmaster, will be answering questions on the always engaging Freakonomics blog. One of the principles of his management philosophy:

  • Put speed over perfection: “Get something out there. Do it, even if it isn’t perfect.”

Buckmaster is not alone in focusing on getting something out there, even if it’s less than perfect. A panel discussion with Manish Mehta, Dell’s Director of Global eCommerce, and Stan Joosten, an “Innovation Manager” with P&G, on the issue will take place at Forrester’s Consumer Forum in Chicago next week. The idea behind the panel:

“Innovation isn’t limited to R+D rooms anymore. The Web 2.0 movement—powered by scrappy start-ups such as Twitter, Malhalo and even YouTube have proven that innovation often happens in iterations. Build, launch, tweak, measure, and repeat… Digital experiences seem to be “always in beta”—learning and evolving along the way.”

While perfectionists and control freaks twitch in discomfort at the idea, with the pace of business now so fast, speed often trumps the need for a flawless release. Plus, with innovation at a premium, requiring perfection can stifle people’s willingness to play and solve problems creatively.

As David Armano has pointed out in Business Week, consumers are not really consumers anymore. Not only do they consume products, they also want to interact actively with them. The message traffic that used to flow one-way from marketers to consumers, now moves two ways. It’s a conversation which requires companies who want to appear responsive to consumer back chatter to tweak and revamp their products and marketing rapidly. What’s this mean? More and more initiatives are always in beta.

(Image of I Am Beta Sign by matiasjajaja, CC 2.0)

 
Reply to Story

BNET TalkbackShare your ideas and expertise on this topic

Subscribe to this discussion via Email or RSS

  •  
    1

    ema@...

    10/05/07 | Report as spam

    ESTABLISH A TRESHOLD

    Sure, there is need to beat the already out-of-fashion excuse of 'let's get it right' (with resultant bottlenecks) if you are to be relevant in present competitive markets. But, so you don't release substandards there is need to establish specific thresholds (minimum standards allowable). Otherwise, competitors can develop on what you imperfectly released and then snatch the markets.The idea is to blend both - perfection and speed- and strike a balance.

  •  
    2

    TheOpsMgr

    10/05/07 | Report as spam

    RE: Perfectionists Despair: Digital World

    I think that Jakob Neilsen made this point about six years ago (http://www.ibm.com/developerworks/library/it-nielsen3/) but he makes one (crucial) distinction - "mudslinging" doesn't work (http://www.useit.com/alertbox/20000402.html).

    Launch a site with poor usability will alienate the early adopters - the very trend setting people you want to attract to generate "the buzz".

    So Ema (in the early reply) is totally right - you have to set a threshold.

    But more importantly "what is your feedback mechanism?" - unless you have very good mechanisms to gather the feedback from your beta testers, and the ability to react to the feedback fast, you might as well still to traditional development techniques.

  •  
    3

    shubhrakant

    10/08/07 | Report as spam

    Also depends on the category of customer

    My observation says that if the innovation is being rolled out to an existing customer then thresholds are not important because they trust you. But if you talk of new customers then you do need to specify some thresholds.

  •  
    4

    william.chong@...

    10/07/07 | Report as spam

    Even More Dispair in Corporate IT Shops?

    As more consumers/users think "I'm ok with trying this but my feedback must result in +ve change in the product in the very near future", they will start to expect the same of corporate applications.

    But many corporate IT shops (IT PMO, apps etc) are neither geared nor mentally conditioned to handle this mode of operation. To many a PM, change is bad, iterative change a killer and moving targets are a no-no. Then there is the issue of security, compliance etc. All important.

    It seems to me the Internet folks has already accepted the "moving target" notion (as noted in the article above) and is adapting well to it, and users are reciprocating by acception things will never be 100%.

    Is there a need to change the IT project management model? Instead of targeting "100% On Time, On Budget" should it be "90% On Business Outcome"? The notion of "Moving Target" is becoming a reality in business - shouldn't we also adapt to it?

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
advertisement
  • Click Here
  • Click Here
  • Click Here
advertisement