<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Johannes Rebane]]></title><description><![CDATA[Thoughts, questions, and a quest for answers]]></description><link>http://johannesrebane.ca/</link><generator>Ghost 0.5</generator><lastBuildDate>Thu, 16 Apr 2026 22:32:01 GMT</lastBuildDate><atom:link href="http://johannesrebane.ca/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Notes from "The Lean Startup"]]></title><description><![CDATA[<p><img src='http://altitudeacquisitions.co.uk/wp-content/uploads/2014/09/Lean-Startup.png'  alt="thumb image-post mask" title="" /></p>

<h1 id="introduction">Introduction</h1>

<h2 id="componentsofthemethod">Components of the Method</h2>

<ol>
<li>Entrepreneurs are everywhere  </li>
<li>Entrepreneurship is management  </li>
<li>Validated learning  </li>
<li>Build-Measure-Learn  </li>
<li>Innovation accounting</li>
</ol>

<h2 id="whystartupsfail">Why Startups Fail</h2>

<ol>
<li>Allure of a good plan, solid strategy, and thorough market strategy.  </li>
<li>Throwing up your hands and saying, "Just Do It"</li>
</ol>

<p>Lesson: *Important to manage the process of management properly to ensure that passion, energy, and vision are not put to waste."</p>

<h2 id="threeprimarypoints">Three Primary Points:</h2>

<h3 id="vision">Vision</h3>

<p>Definition and discipline through validated learning  </p>

<h3 id="steer">Steer</h3>

<p>Being with leap-of-faith assumptions, build minimum viable product to test assumptions and accounting system to evaluated whether you are making progress or if a pivot is necessary.  </p>

<h3 id="accelerate">Accelerate</h3>

<p>Lean manufacturing, org. design, and how to apply those to a startup to accelerate the growth process.</p>

<h1 id="partivision">Part I: Vision</h1>

<ul>
<li>Lean startup asks people to figure out the right thing to build - the thing customers want and will pay for - as quickly as possible</li>
<li>Validated Learning:
<ul><li>What causes demonstrable positive improvements in core metrics?</li>
<li>What <em>are</em> our core metrics?</li>
<li>Effort that does not lead to better learning about what the customer wants can be eliminated (not asking is it just that we <em>can</em> build this product; rather, ask <em>should</em> we?)</li></ul></li>
<li>Experimenting is super important! Make hypotheses and test them.</li>
<li>Experiment is more than just a theoretical enquiry, it is also a first product!
<ul><li>Test <strong>the value hypothesis</strong> - does it really add value to the customers once using it?</li>
<li>Test <strong>the growth hypothesis</strong> how will new customers discover a product or service?</li></ul></li>
<li>Useful often to have a <strong>concierge</strong> customer</li>
</ul>

<h2 id="fourquestionstoanswer">Four Questions to Answer</h2>

<ol>
<li>Do consumers recognize that they have the problem you are trying to solve?  </li>
<li>If there was a solution, would the buy it?  </li>
<li>Would they buy it from us?  </li>
<li>Can we build a solution for that problem?</li>
</ol>

<h1 id="partiisteer">Part II: Steer</h1>

<h2 id="feedbackloop">Feedback Loop</h2>

<ul>
<li>Ideas > Build > Product > Measure > Data > Learn > Ideas > Etc.: Minimize total time through this loop</li>
<li><strong>Minimum Viable Product</strong> version of the product that enables a full turn of the build-measure-learn loop</li>
</ul>

<h2 id="leap">Leap!</h2>

<ul>
<li>As a part of the org's strategy, need to be able to test assumptions systematically and to test without losing sight of the comapny's overall vision:
<ul><li>Core Assumption 1: Value Hypothesis</li>
<li>Core Assumptions 2: Grwoth Hypothesis</li></ul></li>
<li>Various ways to leap:
<ul><li>"Go see for yourself!" - where do we have deep firsthand knowledge?</li>
<li>External customer data</li>
<li>Customer archetype - who are our customers? Can we humanize them?</li></ul></li>
<li>Interesting Concept: <strong>Wizard of Oz Testing</strong></li>
<li>Targeting early adopters as "Testing grounds"</li>
<li>Important to ask: "What if the user doesn’t care about the design in the same way we do?"</li>
</ul>

<h2 id="measureyee">Measure. Yee.</h2>

<ul>
<li>Job of startup in measurement is...
<ol><li>Rigorously measure where it is right now, confronting the hard truths.</li>
<li>Devise experiments to learn how to move the real numbers clsoer to the ideal reflected int he business plan (<strong>does this mean we <em>should</em> have a business plan?</strong>)</li></ol></li>
<li><strong>Innovation accounting</strong> is a system to check if we are making progress and actually achieving validated learning. Turning leap-of-faith assumptions into a quantifeied financial model:
<ul><li>Use an MVP to establish real data on where the company is right now</li>
<li>Tune the engine from the baseline toward the ideal</li>
<li>After all changes it can make, decision has to be made: Pivot, or preserve?</li></ul></li>
<li>Think about <strong>cohort analysis</strong> vs. pure chronological performance</li>
</ul>

<h3 id="metrics">Metrics:</h3>

<ul>
<li>Three types of metrics:
<ol><li><strong>Actionable Metrics</strong>: kind we use to judge our business and our learning milestones
<ul><li>Important to have demonstrated <em>cause</em> and <em>effect</em> so that they can be learned from (vs. <em>vanity metrics</em>)</li></ul></li>
<li><strong>Farbs user stories</strong>: Stories that describe feature from POV of customer vs. technical numbers
<ul><li>Balance time spent getting data and getting genuine feedback and stories to guide future actions. Metrics are people too. Everyone should understand reports.</li></ul></li>
<li><strong>Split Test Benefits</strong>: Saves time in long run by eliminating work that doesn't matter to customers.</li></ol></li>
<li>Metrics should also be <strong>auditable</strong>; that is, credible to employees.</li>
</ul>

<h2 id="topivotorpreserve">To Pivot or Preserve?</h2>

<ul>
<li>Pivoting = structured course correction to test new hypothesis</li>
<li>Better to pivpt sooner than later</li>
<li>Learning Milestones force Pivot or Preserve (not meant to make the decision easy)</li>
<li>Runway: How many pivots does a startup have left before it has to take off?</li>
</ul>

<h3 id="typesofpivots">Types of Pivots</h3>

<ul>
<li><strong>Zoom-in pivot</strong>: What preciously was considered a single feature in a product becomes the whole product.</li>
<li><strong>Zoom-out pivot</strong>: What was considered as the whole product becomes a single feature of a much larger product.</li>
<li><strong>Customer segment pivot</strong>: The product hypothesis is partially confirmed, solving the right problem, but for a different customer than originally anticipated.</li>
<li><strong>Customer need pivot</strong>: The product hypothesis is partially confirmed: the target customer has a problem worth solving, just not the one that was originally anticipated. </li>
<li><strong>Platform pivot</strong>: Refers to a change from an application to a platform or vice versa.</li>
<li><strong>Business architecture pivot</strong>: For example when a startup goes from high margin/low volume to mass market or vice versa.</li>
<li><strong>Value capture pivot</strong>: how do companies capture value?</li>
<li><strong>Engine of growth pivot</strong>: A company changes its growth strategy to seek faster or more profitable growth. </li>
<li><strong>Channel pivot</strong>: Is the recognition that the same basic solution could be delivered through a different channel with greater effectiveness.</li>
<li><strong>Technology pivot</strong>: When discovering a technology to achieve the same solution by using a completely different technology. </li>
</ul>

<h1 id="partiiiaccelerate">Part III: Accelerate:</h1>

<ul>
<li>Sustainable growth comes from one of <strong>three engines of growth</strong>:
<ul><li>Paid</li>
<li>Viral</li>
<li>Sticky</li></ul></li>
<li>Depending on the engine of growth that is targeted, there will be different metrics of growth and success and prioritization, etc.</li>
</ul>

<h2 id="batch">Batch!</h2>

<ul>
<li>Small batches help by minimizing expenditure of time, money, and effort that ultimately turn out to have been wasted. Let people discover the truth faster.</li>
<li>You can make changes at the individual customer level - using the <strong>student of one</strong> concept. If the changes work well there, you can expand the change to the rest of the class!</li>
</ul>

<h2 id="grow">Grow</h2>

<ul>
<li>Four primary ways that past customers drive sustainable growth:
<ol><li>Word of mouth</li>
<li>Side effect of products usage</li>
<li>Funded advertising</li>
<li>Repeated purchase or use</li></ol></li>
</ul>

<h2 id="adapt">Adapt</h2>

<ul>
<li>Five whys are useful</li>
<li>Startup's work is never done!</li>
<li>You cannot trade quality for time</li>
<li>Adaptive processes have a natural feedback loop!</li>
</ul>

<h2 id="innovate">Innovate:</h2>

<ul>
<li>Three structural attributes to startup:
<ul><li>Scarce but secure resources: Too much is just as bad as too little!</li>
<li>Independent authority to develop business: autonomy to conceive and experiment without getting too many approvals!</li>
<li>Personal stake in the outcome</li></ul></li>
<li><strong>Innovation Sandbox</strong>: Contains impact of innovation but doesn't constrain methods of the startup team.</li>
<li>Less important how fast we can <em>build</em> - more important is how fast we get through <em>the entire loop</em></li>
<li>Lean startup is a <em>framework</em> and not of a set of defined steps!</li>
</ul>]]></description><link>http://johannesrebane.ca/notes-from-the-lean-startup-eric-ries/</link><guid isPermaLink="false">c571d753-0370-44a2-9853-f22d58ba44ba</guid><dc:creator><![CDATA[Johannes Rebane]]></dc:creator><pubDate>Wed, 01 Oct 2014 04:56:15 GMT</pubDate></item><item><title><![CDATA["Am I really good enough for my dream job?"]]></title><description><![CDATA[<p><img src='https://s3.amazonaws.com/StartupStockPhotos/20140808_StartupStockPhotos/72.jpg'  alt="thumb image-post mask" title="" /></p>

<p>A friend of mine wrote me the following question. My response follows, and I believe it applies to anyone thinking about going for their dream job, whatever it may be.</p>

<blockquote>
  <p>Now that I have those second rounds, specifically for McKinsey, the first thing it does it make me doubt myself. The whole question of  — “Am I really good enough for Bain, McKinsey?” Which is weird; I never typically doubt myself (as cocky as that sounds).</p>
  
  <p>Of course, I then ask myself, “are there really any data points to suggest that I wouldn’t be good enough?”</p>
  
  <p>There’s only one that immediately comes to mind — that you have to be stunningly brilliant or exceptional to get it, and that I don’t feel like I’m there. Which is a combination of a hyperbole based on what I’ve heard &amp; my mind making things up, likely.</p>
</blockquote>

<p>When you read that back to yourself, does it make sense?</p>

<p>If I said that about myself, what would your response to me be?</p>

<ol>
<li>No. You just have to be really good.  </li>
<li>Honestly, you are stunningly brilliant and exceptional!</li>
</ol>

<p>I see where you’re coming from. Logically, it doesn’t make sense. Emotionally and irrationally, it’s this weird mental stress that’s in the back of my mind.</p>

<p>And really, your logic is pointing you toward the truth. Here’s what you need to know:</p>

<h1 id="theyrehumantoo">They’re human too</h1>

<p>Everyone at those firms are just people. It’s easy to put them on a pedestal – however, you’ve met Kyle. You’ve met big shots. You know best that they are people who like waffles and who have their own worries and doubts and competencies. It’s important to realize that – and to remember that you’re not meeting the Gods…you’re just meeting a potential employer who may or may not be a good fit for you.</p>

<h1 id="itsultimatelynotyourstodecideeitherway">It’s ultimately not yours to decide either way</h1>

<p>Inevitably, the way that interviews work is:</p>

<ul>
<li>You perform your best</li>
<li>They judge you based on that performance</li>
<li>They either extend or do not extend an offer</li>
</ul>

<p>At no place can you will yourself to get an offer – it’s just not in your control. If you really aren’t meant to be there, then the process will decide that – there’s no reason to disqualify yourself before you get there.</p>

<h1 id="rememberyourmotivation">Remember your motivation</h1>

<p>Remember the reasons that you went into this for – the ability to develop a toolkit to analyze problems. To effect change. To make the incredible happen at a greater level than University clubs can provide. Remember that, if that purpose is still important to you, these steps are really you going through the process of working toward that.</p>

<p>It’s not some sort of great act of judgement at the pearly gates. It’s an opportunity – and you’re going on a second date. If you like the firm, and the firm likes you back, maybe you’ll start going out. If not, you’ll make a decision that’s ultimately right for you.</p>

<p>But, you’ll never know if she likes you back if you don’t go on that second date. And who knows, knowing you, you might be the type to stay friends regardless of the initial outcome!</p>]]></description><link>http://johannesrebane.ca/am-i-really-good-enough-for-bain-or-mckinsey/</link><guid isPermaLink="false">beda78d3-9100-43bf-b22b-ab29d22cc125</guid><dc:creator><![CDATA[Johannes Rebane]]></dc:creator><pubDate>Thu, 11 Sep 2014 09:18:50 GMT</pubDate></item></channel></rss>