The best way to implement social tools & practices

If you want to change how large companies work – if you want to eliminate all the waste you know is there while uncovering more commercial opportunities – you can learn a lot from the founder of a Silicon Valley start-up focused on 3D instant messaging.

In most social business efforts, you work on your use cases. You research the technology. You plan everything as best you can leading up to a big launch, and then…you see what happens.

That may teach you something about what works and doesn’t work. But that method of learning costs a lot and takes an awfully long time. And, unfortunately, it’s exactly the approach I’ve been taking.

Until now.

The problem

When it comes to social tools and practices, we simply don’t know the best ways to apply them nor which problems we should try to solve in our firms. In the midst of this uncertainty, we need to try different things – some of which will fail – while we learn.

The problem is that, in most of the companies we’re trying to change – firms with annual budget and performance review cycles – we’re used to planning our way out of uncertainty. And we ask questions at the end.

Why aren’t more users signing up? Why aren’t people using the new features? Why isn’t it working as we’d planned?

Even if you do a brilliant job executing your idea, waiting till the end to learn how effective it will be turns your brilliant execution into a wasteful meander through the possibilities.

Treat your social business effort like a “Lean Startup”

A different and extraordinarily useful approach is described in detail by Eric Ries in “Lean Startup“.  (Ries defines startups as “any human institution designed to create a new product or service under conditions of extreme uncertainty” – a definition that certainly applies to social business efforts.)

Many of the concepts in the book will be familiar, since the approach includes some of the basic methods from the lean manufacturing and quality movements. Examples include using Toyota’s “5 Whys” for root cause analysis and genchi genbutsu for investigating problems in the field.

The big innovation, though, comes from combining these ideas with modern development techniques. Concepts like agile development and user stories. Techniques like building a Minimum Viable Product (one with just those features that allow the product to be deployed and no more). And using cohort analysis (measuring user engagement over time) versus vanity metrics (things like registered users, downloads, and pageviews that don’t necessarily correlate to measures relevant to your business model).

Ries successfully weaves all of these far-ranging ideas into a simple framework you can use whenever you’re trying to “create a new product or service under conditions of extreme uncertainty.”

Build, Measure, Learn

At its core, the framework is a feedback loop focused on quickly learning what you need to do to transform ideas (hypotheses about what will be effective) into products (the minimum thing you need to test the idea) that can generate customer feedback that can then further shape your ideas.

That is, when you have an idea, your first thought shouldn’t be “how will we implement it?” but “what’s a fast, inexpensive way we can test this idea with customers?”

As Ries says, “although we write the feedback loop as Build-Measure-Learn because the activities happen in that order, our planning really works in the reverse order: we figure out what we need to learn and then work backwards to see what product will work as an experiment to get that learning.”

The way forward

As we try to change the way we work, vision and strategy are still important. They’re just not enough.

“Only 5 percent of entrepreneurship is the big idea, the business model, the whiteboard strategizing, and the splitting of the spoils. The other 95 percent is the gritty work that is measured by innovation accounting; product prioritization decisions; deciding which customers to target or listen to, and having the courage to subject a grand visions to constant testing and feedback.”

As we try to understand which problems to solve, which customers to work with, which incentives to use, we can embrace the fact that we don’t know what will be effective.

And then we can get to work, using the Lean Startup approach to turn uncertainty into a set of quick, inexpensive experiments that can guide our learning and help us make the difference we know we can make.


About John Stepper

Helping organizations create a more collaborative culture – and helping individuals access a better career and life – by spreading the practice of Working Out Loud.
This entry was posted in Management, Social Business and tagged , , , , , . Bookmark the permalink.

10 Responses to The best way to implement social tools & practices

  1. brianinroma says:

    Reblogged this on buridansblog and commented:
    The key point is the observation is this:

    As Ries says, “although we write the feedback loop as Build-Measure-Learn because the activities happen in that order, our planning really works in the reverse order: we figure out what we need to learn and then work backwards to see what product will work as an experiment to get that learning.”

  2. Justine Stevenson says:

    Working in internal communication, the notion of User Stories resonates completely. How many times do we implment before really asking ourselves Who, What and Why? All too often we lament that they just don’t get it. If you haven’t articulated in the first place who ‘they’ are, what you expect them to do and why on earth they should – why should you be surprised when you can’t work out if it’s happened…….?

  3. excellent piece. your writing is very important and you should never stop! the great part of ideation is that you don’t know what you don’t know. there’s nothing worse than seeing ideas wither while discovering what you don’t know…

  4. Kelly Adams says:

    John – thanks for this, I just ordered a copy of the book. We humans tend to plan for completeness when completeness – and perfection for that matter, do not exist. Maybe Steve Jobs was a rare exception (I know better; build it and they will come) to this rule but for us mortals learning how live with iterative, collaborative, feedback driven steps can be surprisingly difficult.

    Keep these thoughts coming.

  5. BenH says:

    Great piece John, When is your book coming out?

  6. Great post, John. We’re using Lean Startup methodologies with Spindows and it’s working well.

  7. Pingback: 7 elements of an enterprise collaboration strategy | johnstepper

  8. Pingback: Fieldwork before frameworks | johnstepper

  9. Pingback: Please steal this idea! (How a bill at work can save money & save lives) | johnstepper

  10. Pingback: 5 lessons for driving change from “The Blue Sweater” | johnstepper

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s