I’m Salim Virani, an entreprenerd & business advisor. I'm a founder of Leancamp, an open event that combines the best of Lean Startup, Agile, Business Model Generation, Design, and other disciplines – to find market traction faster. I'm also the founder of Founder-centric, a startup peer-support programme.

Blog Posts

Recording the right information to make better strategic decisions. #bmgen #leanstartup

Strategic decisions, even pivots, are messy. The information we collect is messy, and the conclusions are subjective and debatable. In spite of staying focused on data we’ve collected, we weigh in opportunity cost, and also less fashionable but important factors like market trends, competitors, barriers to entry, etc.

Trusted Systems give you back relevant information when you need it.

I’ve learned something useful here from the idea of Trusted Systems, which is from GTD (Getting Things Done) – a time management approach. A Trusted System allows us to input useful things as they come up and trust that the system will bring them back to us when they become relevant. This allows us to stay focused with a clear mind.

For example, you never remember you’re out of milk at the store, but you spot it when you’re at the fridge. A Trusted System allows you to record this at the fridge, and then get on with your day because you know the system will remind you at the store.

The same is true for pivots.  While we’re out collecting information and building our startup, we come across a lot of useful stuff that we don’t record for some reason, but which is useful in the future while deciding whether and how to pivot.  It gives you a place to keep all of the advice you get from mentors and observations from customers that don’t quite fit with your current iteration or goal – so you can stay focused without losing that value.

In terms of iteration speed and failing fast, the confidence that all our information is in one place makes it easier to go into decision-making mode, rather than delay a little longer based on that niggling feeling that a bit more data or time is required to make the decision.

A portfolio of hypotheses

This can be as simple as an Evernote notebook, but I like using the business model canvas for this.

Alex Osterwalder taught me that setting a 3-minute timer to document a business model hypothesis keeps to the tool light-weight and good value-for-time.  Every time there’s an idea, a piece of an idea, or an opportunity from a customer or mentor, I take 3 minutes maximum to record it as a business model hypothesis. (I use Strategyzer now but I used to use a paper canvas and a camera phone.)

This is not a few post-it notes on the current canvas, but a set of separate business models canvases, defining the possibilities.  It doesn’t have to be a whole business model, just the relevant dynamic is useful. When it’s time to analyse our last tests and decide where to go next, all of those ideas are a ready reference. I find the visual aspect of the canvases useful in a few ways:

  1. It’s easy to see how the idea fits with a whole business model.
  2. It’s easier to see how to test that idea as part of the overall business, and the relevant measurement in relation to the whole business.
  3. It allows me to scrutinise my ideas quickly. Rather than keeping “all these great ideas” in my head, when they’re on the canvas in the context of a pivot decision, it’s easy to spot gaps and eliminate them, freeing my headspace for something more useful.

How do you track all the stuff that becomes important when making big decisions like pivots?

Why you don’t need to be a programmer to start a tech startup

A lot of would-be founders with ideas and passion allow themselves to be paralysed, waiting for a tech co-founder. Yet, seasoned tech founders know the hardest parts of startups usually don’t involve tech. That’s why their eyes glaze over when you tell them your idea and ask them about how to build it.

So why is Rob Fitzpatrick telling us to learn to code?

Look at Derek Sivers, the founder of CD Baby, and the man to who we owe the digital music industry. (No, it’s not Steve.) When Derek started CD Baby, he didn’t know how to code and couldn’t afford a programmer. But he could afford a book on PHP, so he made himself to an HTML site with a buy button.  (All the buy button did was send him an email with the buyer’s info, and that was good enough to get him to thousands of customers, profitability, and a whole year of growth.)  Fast forward 10 years. CD Baby has over 100 employees and makes millions per month. But Derek still wrote all the code!

Is this possible for you?

Necessity is a strict teacher, forcing you to focus on clear outcomes.  After interviews and paper prototypes, you have a clear idea of what needs to be built, and why. This gives you a clear learning goal – you’re not learning to program, you’re learning to make this very specific thing.  The gap between your programming ability and what needs to be done helps you really focus.

This way, learning to code is easier than you think, and getting a head-start will allow you to get your business further on your own steam. If all you need is a landing page, you just need to learn Unbounce. The same dynamic is true when you have strong signals pointing to a tech product – you’ll be able to build something functional and usable, because you’ll only need to learn to build that small thing. You focus on closing a small gap, not learning a big thing

Having a clear definition of what truly needs to be built, and why, means you need to learn a lot less than you think to close the gap. Having real customers and viable business as your carrot means you’ll be far more motivated to learn and build.

Don’t let your inability to code prevent you from starting your business.  

If you start your business, and start a bit of coding now, you’ll be able to close the gap when it matters.

 

Founder-centric workshop notes /by @maxua

Lately, I’ve been doing one-day workshops, based on the Foundation Skills day at Founder-Centric, with different accelerators around Europe. The goal of this day is to teach the principles behind Lean, Lean Startup and Business Model Generation, with a particular focus on practical application and “gotchas” for startups.

Max, founder of DOU, participated at Startup Wiseguys in Estonia, and shared his notes from the day. Thanks Max!

 

From Max’s blog:

Part 1.

  1. do less. more contstraints is better. then you grow with efficiency
  2. you don’t see movement; failed tests allowed us to learn; thats how we succeeded
  3. entrepreneur is NOT an inventor
  4. stealth mode and “coming soon” is wrong
  5. capital efficiency – front-loading the costs
  6. there are no VPs and CxOs in a startup (Blank)
  7. “I wish I knew this sooner!”
  8. you DONT know what will work or not
  9. there different path to get to the goal
  10. customers are full of shit; they lying to you because you ask them to
  11. when you ask “would you buy” you invite them to lie
  12. ask questions in the right way. it really matters.
  13. do 5-10 interviews to know what DOESNT resonate
  14. track actual phrases used by customers, you can use it for copy/ads
  15. ask them about the problem and how they solve it in their context
  16. earlyvangelists.
    • have the problem
    • know they have a problem
    • have budget to solve the problem
    • tried to solve it themselves
  17. choose biz models that are faster to validate, even if it is not the “best”
  18. clay christensen 9/10 fail. “jobs” approach. “You hire Monday to …”
  19. market pull. if there is hesitation – keep looking. that’s the stage you can test. when you start scaling you’re committed
  20. “fail fast” = learn. everything you do must help you to get closer to ultimiate business
  21. what is the fastest way to invalidate my hypothesis?

Part 2.

  1. Choose your customer. You are NOT Evernote yet. Find your very specific niche you can saturate and show traction.
  2. Commitment. It’s a good thing until it’s a bad thing. Have commitment about your vision but allow million variations in terms how you get there.
  3. Vague customer definition.
  4. Multiple customer definitions.
  5. Clear definitions speed progress.
  6. Find early adopters & find specific value prop. Help to communicate and get in front of those people.
  7. “One word” customer segments. Enables you to invalidate your ideas fast.

Part 3. Business model canvas

  1. What do I test? You can’t test everything. Local maxima problem.
  2. Starting point matters.
  3. Being able to see all the different possibilities to choose a starting point (business model).
  4. Really great product is not enough. If you have to build a business model to support the product.
  5. Architect prototype so that they a re not committed to a single idea. There is a infinite number of b.model canvases.
  6. Mckinsey proved funnels is wrong. What matters is timing when asking your customer to pay.
  7. Snapshots and navigating a space.
  8. Four actions framework: remove, reduce, increase, broad.
  9. Take away something you think you need.
  10. 5 rev. streams means 0 rev streams.
  11. Learning is progress. Data is a tool.
  12. We look for data that validates what we believe. “Torture the data long enough and it tell you everything”.
  13. If this problem really crucial, I’ll find 5 people spending money to solve it now.
  14. Customer interview hack: stopwatch. 3 poor interviews is much better than 1 very good one. [because you can learn and adapt your interview approach faster by actually DOING the interviews sooner. - Sal]

Part 4.

  1. What the thing the really worries me? Now what I need to build to test it?
  2. MVP: incremental or piece by piece. Start with a riskiest part.
  3. Growth engines
    • sticky. subscription, marketplace. Are my customers coming back?
    • paid acqusition. transactional biz.
    • viral
  4. MVP. Action is not intent. [test actual customer behaviour, rather than asking customers to state their intentions. - Sal]
  5. Landing page, Paper prototype, customer interviews.
  6. Kickstarter, Dropbox video.
  7. Holistic approach – look at the ultimate number that makes sense for the business as a whole.

It’s interesting to see how things get interpreted. Sometimes what seem like quick points to me really resonated.  I also thought of this as a kind of guide to Lean Startup and related thinking, trying to communicate the context in which a lot of Lean Startup leaders operate, but realise from this that I’m contributing more than just a guide.  Seems that it will be useful to expand on some of the quick points I made that didn’t come from the regular suspects.

If you find this useful, please let me know. And also check out Founder-centric, which I’m running with Rob Fitzpatrick.