• Headlines

  • More Related Stuffs

  • « | Home | »

    By Admin | July 6, 2008

    Product Development 2.0

    While the window on using the “2.0″ suffix is probably closing, I thought it would be worthwhile to explore an especially significant trend in 2006 that will likely see much more widespread uptake in 2007. Specifically, I’m talking about building highly competitive online products by turning over non-essential control to users directly via the Web. For now, I’m calling this online business trend “Product Development 2.0″, a concept that embodies the use of Web 2.0 concepts such as harnessing collective intelligence, users as co-creators, and turning applications into platforms, three of the most powerful techniques in the Web 2.0 arsenal.

    What is Product Development 2.0 exactly? It’s an informal term I’m applying to something that online startups and traditional businesses both are increasingly doing: leveraging of mass user contributions, providing open architectures for others to build on as they like, and even handing control over key product decisions directly to users. The reasoning behind doing this is simple: Satisfied customers have always been essential to having the most successful business, both online and offline. But how best can you ensure that they get exactly what they want from you, as customized and quickly as possible? This is where the scale, new tools, and business models of Web 2.0 have stepped in, giving us the potential to provide our customers with better, rich products, much more quickly, and with more of what they want. Taken as a whole, it’s increasingly clear that there are new business models afoot that are just now being well understood.

    "Product

    Given that any business typically is vastly outnumbered by its customers and potential customers, and that putting a bureaucratic, centralized product development team into the critical path of product creation and ongoing maintenance highlights how little we can actually serve them, especially in an individualized way. And with everyone online, it’s increasingly obvious where the biggest source of talent, engagement, innovation, agility, and worker bandwidth really lies: with your customers. Using the techniques and technologies that have emerged in just the last few years, you can now finally give them the tools and motivation to tweak, tune, refine, and contribute to your products and services. And increasingly, they’ll probably do it. YouTube is still currently one of the best examples of user co-development of a world-class product in its pure form (65,000+ videos uploaded by users per day), but sites like eBay, Slashdot, and many others have been leveraging their users in product development for a long time now. And as it turns out, Product Development 2.0 is not a small topic and starts off at collecting explicit user contributions, leveraging the Database of Intentions, and putting in automated real-time feedback loops to identify the best or most popular new content or capabilities for other users that come along later.

    It’s important to note that it’s a fundamental shift for a business to turn over a large part of its product development to its users, becoming more of a mediator and facilitator than a product creator or owner. This is the shift of control from institutions to individuals that the apparently relentlessly democratizing force of the Web has begun exerting on the business models of organizations of every description around the world. As more organizations figure out how to apply Product Development 2.0 to their individual offerings, they will reap significant competitive advantage over those not harnessing the Web to directly connect to customers and begin a rapid and never-ending innovation cycle. This is another aspect of the perpetual beta concept that reflects the fact that increasingly, products and services online are never finished, and indeed, can’t ever be finished as changes and additions seamlessly pour in over thousands of millions of Internet connections.

    But enough about the possibilities. Let’s talk some examples, both in terms of what older style product development did vs. what this new style is doing. Finally, let’s talk about some companies actually doing this successfully. Note: Incidentally, though I normally write about services in terms of Software as a Service (SaaS) or Web Services, for the purposes of this discussion I’m talking about non-physical business processes for sale, such as car or medical insurance, tax preparation, etc. and not software.

    Like the recently discussed Programming 2.0 concept — a set of software development tools, techniques, and attitudes that is, not incidentally, enabling much of this — and the original Web 2.0 definition, it is examples in lieu of principles that’s one of the best ways to paint a picture of what appears to be happening in the evolution of product development:

    The Move to Product Development 2.0


    Product Development 1.0 Product Development 2.0
    Primary Customer Interaction Channel: Telephone, Mail, Face-to-Face, One Way Media (Print, TV, Radio, etc.), e-mail
    World Wide Web, e-mail, IM
    Source of Innovation: Organizations Customers
    Innovation Cycle: Months, Years
    Minutes, Hours, Days, Weeks
    Content Creators:
    Internal Producers External Producers
    Feedback Mechanisms: Market research, satisfaction surveys, complaints, focus groups Analytics, online requests, user contributed changes
    Customer Engagement Style: Controlled, well-defined process Spontaneous and chaotic
    Product Development Process: Upfront design
    Less upfront, much more emergent
    Product Architecture: Closed, not designed for easy extension or reuse by others; walled garden
    Open, very easy to extend, refine, change and add on to, ecosystem friendly, designed (and legal) for widespread remixing and mashups
    Product Development Culture: Hierarchical, centralized, Not Invented Here, somewhat collaborative, expert-driven Egalitarian, decentralized, remix instead of reinvent, highly collaborative, Wisdom of Crowds
    Product Testing: Internal, dedicated test groups, hand-picked select customers Users as testers
    Customer Support: Customer Service
    User Community
    Product Promotion: One-Way Marketing and Advertising
    Viral propagation, explicit leveraging of network effects, word of mouth, user generated and other two-way advertising
    Business Model: Product Sales, Customer Service and Support Fees, Service Access Charges, Servicing High Demand Products
    Advertising, Subscriptions, Product Sales, Servicing All Product Niches (The Long Tail), Unintended Uses
    Customer Relationship:
    External Buyer (Consumer) Partner and — increasingly remunerated — Supplier (Consumers as Producers )
    Product Ownership: Institution, particularly executive management and shareholders Entire User Community
    Partnering Process: Formal, explicit, infrequent, mediated Ad hoc, thousands of partners online, disintermediated
    Product Development and Integration Tools: Heavyweight, formal, complex, expensive, time-consuming, enterprise-oriented
    Lightweight, informal, simple, free, fast, consumer-oriented
    Competitive Advantage: Superior products, legal barriers to entry (IP protections), brand name advantage, price, popularity, distribution channel agreements #1 or #2 market leader, leveraging crowdsourcing effectively, mass customization, control over hard-to-create data, end-user sense of ownership, popularity, cost-effective customer self-service, audience size, best-of-breed architectures of participation

    It’s worth noting a couple of key points about the table above. One is that the Web makes the shift of control possible by putting every business in direct contact with every one of its customers. No small system can remain unchanged by sustained contact with a much larger system, and this means that any business (which is the small system in this scenario) which embraces its customers over the Web in a two-way fashion will likely undergo a move fairly quickly from the first column to the second. The fact is, if you have loyal customers who like the products and services that you offer online, you’re going to have a hard time avoiding the shift of control and opening up of your product designs and architecture.

    The second is that those that play to the strengths of the Web as platform, instead of trying to fight it, can exploit the most powerful software platform, or indeed, platform of any kind, that has been created to date. Triggering network effects, building an extensible platform out of our product offerings (whether it’s an online software application or if you’re an insurance company, doesn’t matter), and you can see the advantage to be had in the assyemtric model of business on the Web; all of the potential is on the edge of our networks now (where the users are) instead of the middle. And waiting too long to enter the Product Development 2.0 arena potentially means waiting for your competitors to get their ahead of you. And the longer you wait to get the clock started on collected the Database of Intentions (continuously turning 100% of all customer interaction into enriching your product dynamically), the more likely you will face competitive dislocation and even lock-out. Amazon is famous for collecting user contributions to enrich their product database and they are about a decade ahead of potential competitors of in terms of the enriched, hard-to-recreate database they have built.

    Now on to a few examples to highlight what companies are actually doing that has many of the elements of Product Development 2.0. First, the usual preamble about checklists of features; just like Web 2.0, one doesn’t have to implement every one of these in order to deliver better results, just the ones that apply in your situation. So let’s look at a couple of stories of companies — and I have many others I’ll be sharing as soon as I can — that are going part of the way down the Product Development 2.0 path and getting valuable early experience. I selected real-world companies since that’s the majority of companies that have to figure out whether they’re going to play in this space or let others do it for them.

    Product Development 2.0 Examples

    "XMXM Radio is a satellite radio provider that has recently embraced some of the tenets of Product Development 2.0. Compellingly, the Top 20 on 20 channel is one of the most popular channels XM has yet created. Why? Because control of it has been entirely handed over to its users. Says the Wikipedia entry on Top 20 on 20: “The channel plays everything new from rock to rap, with the songs chosen by online votes to the XM website. One can also vote their favorite songs by calling the station number, or text messaging. The channel is completely automated by listener voting with no DJ interruption. [DH- My emphasis] Top 20 on 20 is also one of the most popular music channels on XM. According to XM’s internal research, the channel achieves 1.8 million listeners a week.” And though the channel was relaunched with some changes in December that have proven unpopular to many (less music, live DJs), it presents the cautionary tale of what happens when you assert bureaucratic authority over something that you’ve co-developed with your users; the possibility that you’ll kill the goose that lays the golden eggs of user contribution and engagement.

    "GeneralGeneral Motors conducted its highly innovative Chevy Apprentice campaign early last year and made quite a demonstration of convincing users by the thousands to generate online video commercials for its new Chevy Tahoe SUV. By opening up the contest to anyone on the Web and only screening submissions for truly objectionable content they were able to elicit a stunning 22,000 user generated commercials exhibiting an impressive variety of creativity with both positive and negative messages. From the beginning of the effort, they realized that in a freeform environment created by Web 2.0 tools, that they would only be able to respond to criticism and not control the message. As expected, environmentalists famously picked up the tools to create ads savaging SUVs in general but GM’s Ed Peper understood that only by engaging in conversation instead of censoring dissent could they gain trust and get more information into people’s hands than they could otherwise. Ultimately, GM created its own ads that highlighted the high amount of recycled parts and the best fuel-efficiency in its class of the Tahoe. A brave piece of Product Development 2.0 for sure and one that many traditional business followers probably viewed incredulously as GM truly let their customers and potential customers co-create their advertising campaign with them on the world stage. For the curious: You can see the many Chevy Apprentice commercials still up on YouTube.

    The Potential for Disruption and Opportunity

    The Web is a fundamentally different platform from any platform we’ve seen before. Unlike previous general-purpose platforms, the Web is fundamentally communications-oriented instead of computing-oriented. Sure, computing still happens but what the Web does that’s so important is its ability to connect information and people together. The hyperlink is the intrinsic unit of thought on the Web . So, it’s information connected by links instead of programs that operate on data, that’s the basic difference. But why does this hold the potential to put traditional product development on its head and usher in Product Development 2.0? 1) Because the aforementioned information can now truly be generated by anyone. And 2) because we’re all nearly universally connected to this new medium by the devices on our desktops, in our briefcases, and in our pockets. All of us can now be directly and continuously connected to the products and services which we need, which increasingly, is the rest of us and not a handful of large companies. The very best companies in the future are likely ones that will create innovative new ways to facilitate innovation and collaboration by the hundreds of millions of us that can be reached and embraced by effective architectures of participation. The big winners will enable us and encourage us to take control, contribute, shape, and direct the designs of the products and services that we in turn consume.

    The good news: Only a few industry leaders and early adopters fully appreciate the significance of these trends as yet or even how to fully exploit and monetize them. There’s still enormous opportunity, and for existing businesses with large investments in existing business models, blowing your business model up before someone else does will be the order of the day. This will prove though very hard for most to do successfully. And therein lies the potential for significant industry disruption in the next 5 years as new players with core competency in Product Development 2.0 push older, slow-to-adapt businesses off the stage.

    While this is far-fetched for some, effectively embracing the Web is key to business success today. Why do you think this will or won’t be the ultimate future of how we do business?

    Tips for Building Next Generation Web 2.0 Applications

    "DesignI’ve been spending a good amount of time the last several weeks getting ready for the workshop session I’ll be giving at Web 2.0 Expo next week in San Francisco on building next-generation Web 2.0 applications. What does “next generation” mean compared to what we were doing a couple of years ago with Web 2.0? A good number of things as it turns out.

    "Web We’re currently seeing that newer Web applications are much more federated than in the past, meaning they’re made of distributed parts instead of being just one app on a Web server at one domain and are increasingly leveraging external Web services and APIs. We’re also seeing Web app functionality being bundled up into user distributable components such as widgets, gadgets, badges, and SNS embedded apps. Next generation Web apps are also much more social than in the past with features such as friends lists, activity streams, and aggregation from other social sites as well as using that information to really learn about your customer like Facebook does [Paul Buchheit.] And new Web apps are leveraging powerful new development platforms like Ruby on Rails, grid environments like 3tera , or cloud computing platforms like Amazon’s EC2 and Google App Engine (my comparison of the latter two is here on ZDNet.) And these are just three of the larger aspects of the many new things taking place in on the ‘edge’ of the Web today.

    That’s a lot of things to learn for those who want to build Web applications that offer competitive features and will cost effectively scale as apps get larger, while often using technology that’s still fairly experimental. And that’s one of the big reasons we suggested this workshop to help get a snapshot of the current state of the industry to get up to speed on the latest. So we’re going to spend Tuesday afternoon at Expo going over the details of everything that’s happening in the Web app development space to the fullest extent possible.

    And while I reserve the right to change things right up the very last moment, here’s what I plan on covering next week in San Francisco:

    We’ll start by providing a detailed examination of the best methods for turning a Web application into an open platform to drive growth through the use of open Web APIs with REST, JSON, ATOM. The key success factors for the underpinning business models of open Web platforms including brief case studies will be presented. Designing for consumption in mashups and 3rd party Web apps will also be covered. I’m planning to build a Ruby on Rails REST API during the session based on the positive experiences we had a few weeks ago with Rails 2.0.

    The very latest rich user experience platforms will be explored including Ajax, Adobe’s AIR, Microsoft’s Silverlight, and Sun’s JavaFx with an eye towards how to take advantage of their individual strengths to create new, highly compelling user experiences not previously possible, including for the next generation of mobile devices.

    This session will then look in detail at the latest in Web identity models with a focus on how to use openid and other popular Web single-sign on models to offer users the identity choices they’ll prefer in the near future. The cutting edge of social distribution channels will be explored through the latest field research in OpenSocial and Facebook application models and how best to package and distribute your Web application within popular and high volume social ecosystems and Web widgets.

    The second half of the workshop explores the architectures and cutting edge development models of Web 2.0 era applications circa 2008. The latest techniques for designing applications out of other pre-existing online platforms such as AWS, Google’s APIs, and many others will be given with specific examples for dramatically cutting the cost and time to market of modern Web applications. The latest in emergent architecture techniques, large-scale customer testing approaches, and rapid scalability methods (summary of these three here) will round out the workshop and finish with a informative survey of the latest productivity-oriented development platforms for creating highly effective Web applications including Ruby on Rails 2.0, Cake PHP, Groovy, Grails, and others.

    And while I’ll into more details about these in my session, here are some high level tips for building next generation Web 2.0 applications:

    Tips for Building Next Generation Web 2.0 Applications

    I’ll be at Web 2.0 Expo for most of the week and I’ll be keeping everyone up to date on my Twitter feed , so please follow me if you want to keep up with the very latest.

    What are you most interested in from a Web 2.0 application design perspective? Put your comments below and use wiki markup for links.

    Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
    • Digg
    • del.icio.us
    • Netvouz
    • DZone
    • ThisNext
    • MisterWong
    • Wists

    Topics: Blogroll |

    Comments