Quantcast

Don’t Think Big. There, I Said It.

By brantcooper, March 15, 2012 5:06 pm

Those who run in #LeanStartup circles know too well the problems encountered with language.  Eric Ries, Steve Blank and others are criticized for choosing terms and phrases — lean, customer development, MVP, fail fast, etc. — which unintentionally lure would be startup entrepreneurs into thinking about things Wrong and then doing them Wrong.  Lean means don’t take money, “don’t you really mean market development, not customer development,” minimum viable product should be minimum desirable product, one doesn’t really want to fail fast, that causes entrepreneurs to screw their investors or not persevere.

While the critics make cogent arguments, there’s an implicit assumption that different words would not be subject to similar critique from a different angle. It’s generally not helpful to remove phrases from their context and critique them standing on their own.  Doesn’t “viable” contain “desirable?”

I tell you all this, however, because I’m about to do the same thing.

Don’t Think Big

“Thinking Big” is used as panacea to the menace of “feature” startups, who are merely “copycat” companies that often embrace the leanstartup “formula” that forces them to have “small ideas” and seek to “flip,” thereby leaving their investors in the lurch.  Thing is, markets determine the size potential of the business and many startup entrepreneurs mistakenly believe “think big” means go for a big market.  Tragically, a small idea attracts a small market no matter how big the market is you go after.  Thinking big doesn’t change a small idea into a big market.

Do you see what I did right there?

Truthfully, people who exclaim “Think Big” mean go for big ideas.  But do you know why the “startup curve” leads with the TechCrunch bump?  Because the founders were “thinking big” regardless of the size of their idea.  Do you know why a few startups survive the bump? The sage Fred Wilson says:

It turns out, like most success stories, the answer [for success] was simplifying the service. Taking features out. Reducing the value proposition to a clear and simple use case. This was not done in a vacuum. This was done by releasing a less than perfect product to the market, finding a few customers who wanted a less than perfect product, and then listening carefully to those customers to get to the ideal product.

That’s right, they succeed by thinking small. Product-market fit happens first in sub-segments. Understanding the core value proposition for hyper-sub-segmented markets is where you’ll find strong market signals.  You can’t go big without winning small first.  It’s impossible.  The top of the funnel is not filled in as quickly as the bottom no matter how fast you pour the water.

Sean Ellis writes: “[S]tart by focusing the majority of your energy trying to create at least one must have use case.”

To understand a “use case” you must properly and even obsessively segment your market.

Think Disruptive

What critics of me-too startups (criticism that I think is unwarranted, btw) really mean is: Think Disruptive.  Don’t be sustaining innovation.  Change the world.  I’m all for that, though all startups have their place in the ecosystem.  (If we grow the bottom of the startup pyramid, we’ll get more disruption at the top.) When you have thousands of new startups, the fact that most founders focus on problems they experience shouldn’t be surprising. What would be surprising is if it were true that if they simply thought a little harder, they’d be able to come up with ideas that are truly disruptive.

Most truly disruptive innovations come out of scientific or engineering disciplines and though they’re not very visible to the startup community, tens of thousands of people are working on them.  If Universities had better lab to market programs (e.g., where they’re taught doing rather than merely writing business plans, or licensing technology to dinosaurs), we would see more disruptive activity.  Investors focusing on hugely promising technology is a good thing, too.

Disruption is often stumbled upon.  Experimentation is a good way to lead to lucrative stumbles.

Like other startup people who hear a lot of pitches, I do tire of hearing similar pitches and the mobile app equivalent of a bridge to nowhere. But hey, if any of them happen to succeed, it will likely be because they nailed the value prop for a market segment that eventually proved big enough.

Post to Twitter

Why UX? Why now?

By brantcooper, December 21, 2011 3:40 pm

When you hear concepts over and over, you often wonder is it because it’s swarming or because your ear is newly attuned to it?  Did you know there’s a lot of people who believe that the #11 has super powers and that’s why when they look at the clock, it’s always 11 after?  Seriously.

UX is hip.  And rightly so.  I thought I’d share a theory why this is so and what impact it might have on your startup.  This despite the fact that I’m relatively new to UX concepts.

The 90s

Painting with a super broad brush, the 90s technology revolution which saw the introduction of PCs and networks into businesses was driven primarily by increases in productivity measured at the business level.  Reduction in support staff, increased internal and inter-business communication had a measurable impact on the business.  While the technology was expensive and the immediate net benefit small, it grew enough in the late 90s to, at the very least, portend benefits to come.

It was far from smooth-sailing.  The effective lifecycle of a PCs was only 2-3 years.  If you had a network of 100 nodes, you were easily paying 100K/year to hardware and software to keep things running at a pretty basic level.  Some medium sized businesses were seriously thinking of packing it in until costs would come down or larger benefits could be realized.

If there’s one thing that seems to be true in technology, it’s that future benefits are easy to imagine and don’t come quickly enough. In other words, the industry pretty consistently over-promises and under delivers.  Technology in the 90s was mired with buggy (Microsoft) software that bogged down trailing hardware and arguably was maliciously incompatible with (buggy) legacy network software (Netware).

An emphasis on UX was nowhere to be seen.  Of course, that’s not exactly true, Apple had it in spades.  But the extra dollars required for an improved user experience had little impact for the average business user on business productivity. A reasonable argument could be made that this was a short-sighted view, but the view was rational. If you triple the price tag, you must triple the productivity. The Macintosh made headway in businesses at the departmental level, where the impact on productivity was significant; in other words, where specialized graphic-intensive applications were put to use.

The UX experience on the PC was crap and no one wanted to pay to improve it, since you could still reduce the administrative support to principal ratio even with crappy systems.  That it took a IT guy several weeks to implement buggy MS Mail to SMTP gateways and the end-user process to send such an email sucked didn’t matter relative to the time and money savings of sending proposals at the last minute vs sending hard copies via Fed Ex.

The 2000s

As the Internet emerged as a business productivity tool, the primary beneficiary was the department.  The browser as a standardized UI for internal applications reduced IT supports costs and offered some freedom for departments and business units from their dependency on IT.  As SaaS emerged, this independence accelerated.

The early user experience on the browser was horrible and often worse than that of desktop or client/server applications.  But the benefits from a lightweight interface and reduced dependency on IT outweighed the superior UX experience.  Further, technical limitations on the browser thwarted efforts to improve the experience.

Today

While I’m sure there will be a whole new revolution in business and departmental productivity, likely brought on by human-computer interaction technology (think Kinnect), today’s story is about personal productivity.  Applications built for the desktop stand-alone, mobile, browser-based SaaS are all about improving user productivity.  The two primary ways to achieve this are 1) work within existing flows; 2) mimic the offline world.

I chuckle when I see marketing slogans “We’re going to change the way you work!”  Really?  See ya!  Why do dating sites fail? They don’t replicate how human beings meet.

The tricky thing is that you need to improve productivity enough to justify the costs without changing behavior so much as to make the product undesirable.  How do we do this?  With superior UX, of course.  How do you nail such a thing?  It should come as not surprise that my recommendation is deploying Lean UX design principles.  You must understand the it is a delicate, learning process.

“But people are so different!” you rightfully lament. Yep, the one size fits all is dead. While investors and industry pundits hand-wringing about copycats, features-not-products, thinking-too-small, etc., the entrepreneurship world is producing 1000s of startups to figure out how to solve common problems across a wide-diversity of people.

I don’t know what the landscape ends up looking like.  If big businesses swoop up  lean startups who have successfully unlocked one or more beachhead market segments, they can’t kill the innovation or roll it up into bloatware without creating a new startup opportunity.  Similarly, is it possible for one SaaS or mobile product to solve similar productivity problems for a mass of varied segments?

I welcome your thoughts in comments!

 

Post to Twitter

San Diego Startups — ShowUHow

By brantcooper, September 23, 2011 4:49 pm

(52nd in a series introducing San Diego high tech Startups.)

ShowUHow

ShowUHow offers manufacturers and retailers a series of web and mobile video product guides for every stage of the customer lifecycle, including pre-sales, installation, feedback and retention.  Led by Founder and CEO Kim Folsom, ShowUHow has raised $3M from Syncom Venture Partners.

Crunchbase entry.

(Founder of a San Diego-based Startup? Contact me: brant at marketbynumbers.)

Post to Twitter

San Diego Startups — SrvrDJ

By brantcooper, September 23, 2011 3:59 pm

(51st in a series introducing San Diego high tech Startups.)

SrvrDJ

SrvrDJ helps you launch your apps into the cloud quickly, easily, and fault-tolerantly. Founded by Leeward Bound, SrvrDJ is bootstrapped.

(Founder of a San Diego-based Startup? Contact me: brant at marketbynumbers.)

Post to Twitter

Panorama Theme by Themocracy

Twitter links powered by Tweet This v1.8.2, a WordPress plugin for Twitter.