Hasn't That Been Done Before?
Comments [0]
Comments [0]
The beta tag is one of Google’s brilliant hallmarks.
The beta phase (it can actually last forever) solves one of the key challenges in software product development. The first challenge (unsolved by the beta phase) is to build software that solves a serious consumer or business problem, which is no small task. But the second challenge (once your software solve a serious customer problem) is that you can never figure out how human beings will actually use your software once they get their hands on it. That is, unless you have a strong beta program and you watch a large number of your users in action, and you learn from them.
Google is the master of using emergent data. Don’t design Gmail. Let your beta testers play with your new email system until the right patterns emerge, and let them design Gmail for you. Same with Twitter. Let the right features emerge, don't airdrop them in from corporate HQ.
Having a strong beta culture is all about knowing when to stop inserting your own preferences and opinions into things, and letting the end users tell you how the product should be designed. That’s when the software gets designed right.
Comments [0]
For the last 42 days, there has been a YouTube video of an awesome presentation about trends in high tech by my hero Geoffrey Moore (below). Over the last 42 days this video has been viewed a grand total of 617 times, according to the YouTube statistics. Anyone who wants to gain a better understanding of cloud-computing, and how consumer software is entering the enterprise world, would be interested in watching this.
Comments [1]
Sometimes it’s a good idea to put all your eggs in one basket. This is one of the key lessons of the startup bible, Crossing the Chasm, which I’m re-reading right now.
The Chasm is the place where many high-tech startups die. It’s the gap between the early market of innovators (people who are enthusiastic about buying a groundbreaking product that is only 80 percent complete) and the pragmatists (the people who look at a product that is 80 percent complete and say, Where’s the other 20 percent?).
In order to leap across the Chasm, you need to commit to building the “whole product” for at least one target customer. Rather than making the common mistake of building a product that’s got something for all your potential target customers, you need to give just one target customer everything. If you do that, you’ll get your first round of pragmatist customers, who will be your reference base as you seek to get more pragmatist customers. (Don’t forget: there are a lot more pragmatists than there are innovators, so you’ll want your reference base to be full of pragmatists so they can tell their friends.)
I regularly recommend Geoffrey Moore’s book Crossing the Chasm to other people who work at startups. For now, this book, along with the sequel, Inside the Tornado and Guy Kawasaki’s Art of the Start, stands alone as required reading for entrepreneurs, in my opinion. If anyone has suggestions for books that they would recommend to entrepreneurs, please let me know at will@alumnifidelity.com, or @willmarlow, or in comments below, or let me know when you run into me on the street :)
Comments [0]
I attended a good panel this morning organized by the people at Ogilvy PR in DC. The topic was innovation in organizations, and there were some great panelists.
We ran out of time, but I would have loved to discuss the dynamic between the outward-facing guys and inward-facing guys within companies. My own attitude has been that a company should do its best to create tension between the outward-facing team (maybe led by the CEO), and the inward-facing team (led by the COO). Both teams are essential to stimulating innovation. The trick is, even though you want to foster tension between the outward and inward forces, you need the outward force to win often enough to keep people very busy.
Comments [0]
Comments [1]