I have been running these 1-day workshops for IIM’s Entrepreneur Cell and various offices of ThoughtWorks. We start with a new idea or an existing idea, work through it over the day, focus on one key product to come up with a clear picture of what it will be and an MVP for it. The audience has been folks who came in just with an idea, startups that came with a prototype or startups that have started seeing some customer traction.

Over time a structure has emerged. This is what I am sharing here. And, this is going to be a long one.

My commentary with use startups who have spent sometime on the idea and have a prototype in market as a typical example. However, this approach work for the who spectrum I mentioned above.

Here is what a typical agenda looks like:

Agenda

The day is run over a very tight schedule. So keeping time is important. Also, the aim is breadth-first and cover all rather than depth-first and iron out details.

This allows the attendees to get familiarity with the methods and they can do a do a detailed version on their own.

Our Approach, Objectives and Ground Rules

This is similar to Inception. One thing I always bring out that we will be discussing each idea with the team. Folks attending should be comfortable to share their idea with the group.

I always allow mobile phones. Folks are going to be here all day, typically a Saturday. A few minutes of phone calls related to family and work is not very disruptive.

Product in a Box

At times referred to as Product Box^[1], it is a fun activity in which everyone is asked to imagine if their product came in a box, what would the label of the box look like. I provide this empty sheet to participants:

In order to help them visualize and organise their thoughts, I show them this slide for reference and walk them through each section and give some examples.

Usually people struggle a bit with this. Either they will be lost for words or write too much text and are frozen! Also, this being the first session, folks are bit slow to get started. I suggest to them is to just start writing. Once they do, words follow words and they are able to finish.

Once all are done (15 mins), I request each to read out exactly what they have written and add nothing as an after thought. I then as all if they will be willing to buy/invest in the idea.

The very exercise of having to write out the thoughts, read them aloud, not add in ad hoc manner to it and then hear responses, sets the time for rest of the day. I stress a lot on brevity and simplicity.

Elevator Pitch

We have a very good format for Elevator Pitch^[2] that is part of the Inception Deck. I often reuse that. We give them a printed page which has outline of an Elevator Pitch that they have to complete. Having gone through the Product in a Box exercise earlier, heard the feedback, folks just go swiftly though this and are able to come up with excellent articulation. The format looks like this:

Note: I have reversed the order and done Elevator Pitch first and then the Product in a Box. But in either case, attendees struggle with the first one and then do the next one rather fast and nicely.

Business Model Canvas

We do Business Model Canvas^[3] across two sessions.

Session 1

I first ask them to write down key Value Props. This is followed by writing down the various Customer Segments. They key is to narrow them as much as possible. So using words like ‘All’ are discouraged.

Then I ask them to make a line for each Value Prop to each Customer Segment it serves. Ideally, all Value Props should serve some segment and all segments should have some value prop for them. If none, the customer segment needs to go.

Then I ask them to name a channel for each Value Prop. At least one channel for each stage of Brand Awareness Funnel. That is, Awareness, Consideration, Engagement and then Purchase. In my previous life, my work on Brand Awareness Funnel was converted into a patent by my then organization.

Session 2

In this session we focus on Cost and Revenue. Surprisingly, helping startups that been been around realize their cost is the most a-ha / oh-sh*t moment. Perpetual optimists like Founders rarely internalize the cost of getting things done and this serves as a good eye-opener. Lots of time is spent on revenue side of things.

I usually help them with quick back-of-envelop calculations. Salaries of founders, office rent, internet bills, laptops, furniture, folks for sales, support, development, CA, filings, buying compute power, licenses, fees, etc and soon the estimate balloon.

Session on revenue is smaller. I ask them to write down all possible avenues of revenues and then estimate revenues it can bring in over time and the complexity of making that revenue. This helps them prioritize one avenue over another.

Product Strategy

This session was added after 2-3 such workshops. When asked what all products does your company build, what is your key product, what all components does your product have or what all products are you working on to enable your key product, I used to get very vague answers. Most of them would start talking about their awesome app.

The thing is, that without realising how much effort the company is putting into various products (in house, customer facing, partner facing, admin tools, 3rd part integrations, that 3rd Parties can use, etc), it was often apparent that they were not look at whole picture when prioritising.

So I came with this Product Stack^[4] template:

I ask them to fill this up with all things they are using and have built. The output surprises everyone. Once they have listed them all, I ask them to mark out ones without which they can not proceed as business. This eliminates lots of random / legacy products they have accumulated over time and focus on ones that really matter.

There are two things that also happen while we do this exercise:

1. We force them to think beyond Channels (like Apps, Websites, etc) and think in terms of the whole Platform.

2. Get them into exercise of prioritizing engineering output and not jump into creating apps, websites, etc without creating a roadmap at an strategic level.

Note: In case of new ideas, I ask them to list down things they will need to use and build. They then prioritise based on that.

Product Management Canvas

Once the key product has been reinforced, identified or agreed up, we use the Product Management Canvas^[5] to describe it.

Lots of content flows in from the canvases and work done in previous sessions. That makes filling up this canvas faster. Only thing is that these are not at the level of entire business but at level of this product. This means the slice of whole business canvas that this product addresses.

We recommend they do it for each of they key product. Product Managers can use it for their products. More about Product Management Canvas here.

Identifying MVP

One thing that the Product Management Canvas helps with is identifying a MVP. Here is how I put it:

“Specific Features that deliver extreme value to a specific Customer Segment and helps attain specific Business Value using specific Key Resources measured using related Success and Failure Metrics with right Visual Identity and Go-To-Market support.”

The Product Management Canvas helps identify that MVP that should be rolled out first.

Preparation for the Workshop

As preparation, I printout some canvases. Here is the list and size of paper on which they are printed.

Using A3 gives some real-estate to write down on the Business Model Canvas and the Product Model Canvas.

Never Alone

These sessions were not always done alone. I want to acknowledge these fellow ThougthWorkers for contributing in various sessions I held: Nagarjun Kandukuru, Shaun Jayaraj, Sachin Sapre, Sharath Satish, Suganth Chellamuthu, Kiran M, Prasanna J Vaste and Arjun Dev.

References

[1] Know more about Product in a Box in Innovation Games by Luke Hohmann.
[2] Know more about the Elevator Pitch format on Jonathan’s blog.
[3] Business Model Generation by Alexander Osterwalder, Yves Pigneur (https://strategyzer.com/)
[4] & [5] Created by the Dinker Charak and can be shared under Creative Commons (CC BY-SA 3.0)