<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[CS183C: Blitzscaling Student Collection - Medium]]></title>
        <description><![CDATA[The general submission collection for CS183C. - Medium]]></description>
        <link>https://medium.com/cs183c-blitzscaling-student-collection?source=rss----7104d0e1e98d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CS183C: Blitzscaling Student Collection - Medium</title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection?source=rss----7104d0e1e98d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:15:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/cs183c-blitzscaling-student-collection" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Blitzscaling: A Chemical Reaction]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/blitzscaling-a-chemical-reaction-bf9e318fe903?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf9e318fe903</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cs183c]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Jocelyn Neff]]></dc:creator>
            <pubDate>Sun, 06 Dec 2015 00:41:39 GMT</pubDate>
            <atom:updated>2016-02-01T07:30:50.079Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0yYmr0xcH4QswBmsEiM1Q.png" /></figure><p>This post explores my key takeaways from CS183C. I noticed several similarities chemical reactions and blitzscaling. Enjoy!</p><h3><strong>Hydrogen + Oxygen →Blitzscaling → Water</strong></h3><p>Blitzscaling is like a chemical reaction: it rarely just happens. Hydrogen and oxygen do not just combine to form water. Circumstances have to be just right for them to react and form water. And even when that reaction does take place, there is a definable end when water is produced. Just like chemical reactions, blitzscaling does not occur without the proper setup, and is not a sustainable state for a company. At some point, your ingredients are used up and you reach a stable state like water. You may be able to chain another reaction using the water to produce new results, but each of these steps takes conscious effort to setup the reaction. So how do startups make those reactions take place? When do they know it’s time to blitzscale?</p><h4>Product-Market Fit</h4><p>A startup is not ready to reach a new level of scale unless they have proven product-market fit. Reactions consume a lot of energy, so only sacrifice that energy if you’re sure of good results. Is water really the product you want, or could it be salt? The ingredients are vastly different depending on the results you want.</p><h4>Scalable Leadership</h4><p>Your employees need to scale just as much as your company does. Consider the ingredients your critical leaders need to reach scale. Maybe they need coaching, more responsibility, or a place to fail. More than likely, your company will be looking to form another reaction once you complete your current one. Always consider the results on the right side of the equation that serve as the ingredients for the next reaction. Leadership is a critical component to triggering successful blitzscaling.</p><h4><em>Why This Reaction?</em></h4><p>Reactions are exciting, just as blitzscaling is. Companies dream of reaching the scale Airbnb, Uber, Facebook, Google have. But it’s critical to stop and think: why am I triggering this reaction now? Will producing water from hydrogen and oxyzen really benefit me now, or do I just want to see a reaction take place? Blitzscaling consumes a lot of resources. If the economy isn’t right (as was the case when Minted was young) then you may not have the resources to support a company that has undergone blitzscaling. Timing is critical.</p><h3><strong>Tools of the Trade</strong></h3><p>You’ve decided you like the idea of playing with chemicals to see what you can produce. Now what tools should you use to maximize the chance of producing valuable results?</p><h4><em>Love, not Like</em></h4><p>Paul Graham advised Brian Chesky to get 100 users to love, not like Airbnb. In pursuit of this goal, Brian learned it’s actually quite hard to get 100 users to love your product. Why is it important to love, not like? Users that love your product will be your best missionaries. They will share their love of your product with their best friends that will then give it a try. Soon enough, you’ve triggered a blitzscaling reaction. When users love your product, this also implies you’ve found product-market fit, meaning you found the right ingredients for the reaction.</p><h4><em>Strategic Hiring</em></h4><p>Mariam Naficy, CEO of Minted, shared her opinion on when a company should grow leaders from within, or hire externally. If a company needs a leader in a position related to the company’s secret sauce, then it should grow leaders from within. If, however, a company needs a leader in an area they are looking to move into or is not critical to the core business, hire the best person possible, who will likely be an external candidate. In Minted’s case, Mariam tried to grow leaders from within who understood Minted’s crowdsourcing platform. That platform was uniquely Minted. When they reached a scale where they needed an HR leader, however, they looked externally. A company needs to understand its core competency not only so it can scale that insight, but also so it can work to scale employees for leadership positions. Strategic hiring is a tool by which a company can ensure it has the correct ingredients for the blitzscaling reaction.</p><h4><em>Active, not Passive Culture</em></h4><p>Brian Chesky knew he wanted to make the Airbnb office be remarkable. The meeting rooms are modeled after real residences available on Airbnb. These meeting rooms remind everyone what product and mission they are working for. When a company is a few people, it’s easier for founders to enforce a culture. As a company scales, however, culture will ultimately reside with the employees. It’s the leadership’s responsibility to actively promote the culture they want to scale. Promote your culture by focusing on culture fit in the hiring process, designing your office space to reflect your company, and by hiring leaders who live the culture you want to see grow. You must actively think about culture.</p><p>If you let the culture grow “organically”, you are unlikely to end up with the culture you envisioned.</p><h3><strong>Airbnb: the “do things that don’t scale” Poster Child</strong></h3><p>When you hear Brian Chesky speak about Airbnb’s origin, there is no doubt he is passionate about the product. He did everything in his power to see his baby scale to the amazing product it is today. But some of those ingredients that led to a reaction won’t help the company with its next reaction.</p><h4>Cereal Entrepreneur</h4><p>It may seem odd when you see it as one of Airbnb’s core values, but cereal is the way the cofounders convinced Y-Combinator to accept them in the “nuclear winter”. They founded the company by designing their own “limited edition” cereal (Obama-Ohs and Cap’n McCains) that they sold and raised $30,000. Paul Graham hit the nail on the head when he called the founders cockroaches: they did anything to see Airbnb live to the next day.</p><h4>Personal Touch</h4><p>When you reach the scale and awareness that Airbnb has, it makes sense that users are excited to meet Brian Chesky. Given the company’s scale, however, it’s unlikely that just Brian’s presence will lead to a reaction that takes the company to the next level. When the company is small, however, a cofounder’s presence can serve as the catalyst to help a company scale. Brian personally met all of the early hosts: an exciting event for people that don’t live in Silicon Valley. These users then share their excitement from meeting a cofounder with their friends, who then learn about Airbnb. Before you know it, the product is viral.</p><h4>Boots on the Ground</h4><p>In the early days, NYC was Airbnb’s largest location. The founders flew out to NYC and knocked on each host’s door. They saw the rooms and discovered that the apartments were much nicer in person than they looked on the site. Brian then volunteered to take professional photographs that could be used on the site. Today, it wouldn’t be feasible for anyone, let alone the cofounders, to stay in every Airbnb. But in the early days, these few homes were the only products Airbnb had. Leaving the office and living the product is an important way for founders to gain insight on how to move more uses from liking to loving the product.</p><h3><strong>Why Are You Founding, Let Alone Blitzscaling?</strong></h3><p>We heard a lot of success stories this quarter. For the 16 success stories we heard, there were 144 failed startups that we never heard about. It’s out of the scope of this class to speak about why startups fail (I recommend looking at Noam Wasserman’s and Lindred Greer’s research if you’re interested), but it’s important to acknowledge that a successful reaction is definitely not a sure thing. We heard it from Sam Altman and many others: only start a company if you absolutely cannot think about anything else. If you have any doubts, don’t do it. In this class, we heard from the only story I know of where someone just decided to do a startup without an idea in place: Airbnb. That story worked out, likely because the cofounders obsessed over the product. Are you really ready to spend the next 10 years or more of your life expending all your energy to help your company survive?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf9e318fe903" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/blitzscaling-a-chemical-reaction-bf9e318fe903">Blitzscaling: A Chemical Reaction</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blitzscaling: Abstractions are powerful]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/blitzscaling-the-role-of-abstractions-cb3c0d767cbd?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/cb3c0d767cbd</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cs183c]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Nihit Desai]]></dc:creator>
            <pubDate>Sun, 29 Nov 2015 05:05:29 GMT</pubDate>
            <atom:updated>2016-10-03T21:41:05.763Z</atom:updated>
            <content:encoded><![CDATA[<p>I am taking CS183C (Technology enabled Blitzscaling) this quarter at Stanford. Prompt for this week: Write about how the principles of blitzscaling change as you achieve real scale (e.g. Village, City). Focus on things which: a) resonated the most with you and b) surprised you. Explain how you plan to apply these principles in your own life/business.</p><p>—</p><p>In the past few weeks, we heard from some incredible speakers such as Reed Hastings (Netflix), Patrick Collison (Stripe), Diane Greene (VMWare) and Nirav Tolia (Nextdoor). One difference I noticed when listening to speakers in these past couple of weeks was that the lessons were richer in abstractions about how to think about various problems when building and scaling startups. A hypothesis for why this might be the case is increasing complexity. Complexity of problems such as efficient team communication, pace of innovation, maintaining a strong culture and maintaining hiring standards increases super-linearly in relation to company size. And optimal solutions to these problems seem counter-intuitive or unnatural at first. Therefore, in order to continue to do an effective job as the CEO, it might become necessary to form models or abstractions to understand markets, products and people, and reason from there as opposed to raw intuition. In the rest of this essay, I write about some themes from these talks that I found most insightful:</p><p><strong>Flexibility trumps everything</strong></p><p>In evolutionary biology, it is a well-understood fact that species that are adaptable to environmental conditions are the species that survive in the long run. Related to it is the concept of “generalization” error in Machine Learning. The idea is that when training a model on a given training dataset, we want to make sure the model does not overfit to the data i.e. it is robust enough that it makes accurate predictions on unseen data.</p><p>Something very similar is true in case of startups. They can be chaotic and less than perfect at times. However, every time something goes wrong, if you put a process in place to prevent it from recurring, then as Reed Hastings put it, “After a while, you have people who are just good at following rules but not good at adapting to a new market”. The debates within a company shift from substance to processes. The culture shifts from moonshots to guaranteeing lower bounds. Therefore, it is essential to optimize for flexibility and speed of learning, as opposed to overfitting for a particular market or problem.</p><p><strong>History is underrated</strong></p><p>Patrick Collison’s interview had many great points. Something that really resonated with me was that reading history (of anything really, but particularly, history of technology) is a way to “cheat” and steal good ideas! Startups often ignore all the good ideas that people thought of in another time, that are still very applicable today. Instead they go through this “brownian motion” through the space of all possible solutions when working on a problem, as Patrick put it.</p><p><strong>Building Cars vs Building Roads</strong></p><p>Something else that Patrick talked about was how internet and smartphones have enabled a massive flourishing of products/services that solve utility problems (Uber, Postmates, Doordash), communication problems (Facebook, Whatsapp) or entertainment problems (Netflix, Youtube, Instagram). However, products and services that realize the original “bicycle for the mind” (Software that augments human thinking and makes us smarter) vision of personal computing are surprisingly lacking. This has led to a systemic undervaluing of impact that such a tool can have. Patrick differentiated this by giving the analogy of “building cars” (building the end-product) vs “building roads” (being an enabling force) and that Stripe is one of those companies that is building roads.</p><p><strong>Communication: Less is not more</strong></p><p>Consider these facts — (a) The universe is expanding and the rate at which two given points in space move apart from each other is approximately directly proportional to the distance between them, (b) The “speed of light”, and hence the speed of causality is finite. Using these, we can conclude that there are parts of the universe that are permanently separated from us, i.e. a beam of light that starts from such a part will never reach us. This means, if for some reason, the laws of Physics were to change in that part of the universe, we’d never know since we cannot observe it.</p><p>Something very similar is true of startups — When a company is doubling in size every year, this exponential expansion can quickly outpace the rate at which diffusion of culture can take place via person-to-person interactions. This means, very quickly, individual teams can have separate cultures, separate priorities and goals. This is recipe for disaster and must be prevented. One of the most important things that founders can do during this stage of the company is clear, repeated, transparent and consistent communication. Patrick Collison talked about how it feels unnatural but it is absolutely essential (he also pointed out that in addition to speaking, as the company grows, it makes sense to also communicate in writing. Writing endures, forces communication to be precise, and can be updated).</p><p><strong>Role of the CEO</strong></p><p>“As the company grows, the CEO is the right person to make a decreasing fraction of decisions”. I thought this statement by Patrick was brilliant.</p><p><strong>Org structures might be nearly optimal</strong></p><p>I was surprised to hear Patrick Collison’s view on org structures. He basically said that the current solution that we have (some sort of hierarchy) may not be too far off from a global optimum, given some important empirical facts:</p><p>(i) whatever the shortcomings of the current organizational structures may be, they have been good enough to create the Facebooks, the Googles and the Intels of the world.</p><p>(ii) The timescale of evolution of technology (few generations) is much faster than evolution of people (few thousand generations). This means that solutions to technological problem will be reinvented much more frequently than solutions to “people” problem, such as how can you organize people into teams that work efficiently and towards a goal.</p><p>He also touched upon something important when talking about org structures — it is rarely the case that inventing a completely new way to organize people (versus not) will play a significant role in determining the success or failure of the company. Therefore, it might be a better investment of time to work on problems that matter more.</p><p><strong>Cash flow businesses vs Growth businesses</strong></p><p>I thought this differentiation that Nirav Tolia (and John Lilly) spoke about was very important (and new to me). Conceptually, venture funding makes sense for a startup in order to fund explosive growth to capture a large portion of a market. This may be desirable for a variety of reasons- network effects, economies of scale, outpace regulation etc. But none of these are applicable to cash-flow businesses. Getting venture funding for a cash-flow business is a bad idea, for then you start to think about growth ahead of revenue.</p><p><strong>‘</strong><a href="https://www.youtube.com/watch?v=DLWyP83iU5M"><strong>Competition is for losers</strong></a><strong>’</strong></p><p>For a good part of 8 years or so starting in 2003, Netflix was locked in a competitive battle against Blockbuster. Talking about what the company learned from this, Reed Hastings said, “When attacked, we should have retreated to do our core better, rather than broadening the surface of attack.”. Fast forwarding to today, “When people ask, ‘Are you going to get into news and sports?’ we say No!”. Many people have echoed similar lessons — “Fewer things done better” (Jeff Weiner), “You can’t drive by looking in the rearview mirror to see what others are doing” (Dick Costolo). But the most effective exposition of this idea I found in Peter Thiel’s Zero to One: the secret (or at least one of the secrets) to success in technology is to do something so unique and so differentiated that in effect you don’t have to compete at all. This runs quite contrary to received wisdom, that the way to win (in sports, games, academics etc) is to compete as fiercely as possible!</p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb3c0d767cbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/blitzscaling-the-role-of-abstractions-cb3c0d767cbd">Blitzscaling: Abstractions are powerful</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Kill a Baby Unicorn]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/how-to-kill-a-baby-unicorn-25b7161307ee?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/25b7161307ee</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[blitzscaling]]></category>
            <dc:creator><![CDATA[Dayne Rathbone]]></dc:creator>
            <pubDate>Sun, 29 Nov 2015 05:05:10 GMT</pubDate>
            <atom:updated>2015-11-21T13:18:34.168Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>There are ways to fail at being a 450 person company… there are a lot of failures at this point… so when you look at the current giants they’re not just there because “oh I got the right app and I had the right product market fit and now I just hang on to it and I just do what any smart person does”… there’s a bunch of art in how you build these companies</blockquote><p>That’s <a href="https://www.youtube.com/watch?v=UqHxbVsIkOM">Reid Hoffman talking about the challenges companies face as they operate within the Village stage of Blitzcaling</a>.</p><p>To me this is an uncomfortable truth. My company is a year old, we’ve built a product I’m extremely proud of, and we’re on our way to establishing product market fit — I’d assumed that once we firmly achieved that, the worst would be over.</p><p>But that assumption is dangerously naive — MySpace, Friendster, Orkut, and countless others haunt the graveyard of companies that failed in later stages of scaling. It appears as though getting things right early on just earns you a ticket to the main game.</p><p>And so, invigorated by fear, I’ve paid close attention as Reid, Allen Blue, and Eric Schmidt outline the common pitfalls that companies make as they advance from the family and tribal stages (1 to 10s of employees) into the larger village and city stages (100s and 1000s).</p><h4>Timing is Everything</h4><p>Reid has this to say:</p><blockquote>I wrestled a lot with the term ‘Blitzscale’, and the reason is there are a lot of good and interesting parallels with the term ‘blitzkrieg’… prior to blitzkrieg all war was done through a supply chain… so you had a maximum speed you could advance your front. The essential innovation of blitzkrieg was “to heck with the supply chain — go fast”… once you got to your half way point of your intended battle, if you cross that you win or lose big.<br><strong>If you lose, you lose terribly</strong>.</blockquote><p>Thanks Reid, that’s comforting.</p><p>This begs the question — how do I know when my company is ready to scale? <a href="https://www.youtube.com/watch?v=hcRxFRgNpns">Eric Schmidt offers some advice</a>.</p><blockquote>If you don’t understand the subtlety here you would conclude that the goal here is to grow everything as fast as you possibly can everywhere — let’s just make as many engineers, as many products, as many sales people… and that just doesn’t work. It doesn’t work because ‘no product shall ship before it actually works’… you have to have judgement about when the product is ready to scale against it.</blockquote><p>Eric suggests that a good indicator that your product is ready to scale when people are actually using it — when you’re experiencing consistent user growth over several months.</p><blockquote>Nobody at Google used Wave… how many people do you see walking around Stanford using Google glass?</blockquote><p>I haven’t been to Stanford, but I’m assuming the answer is “not many”.</p><h4>Communication is Also Everything</h4><p>150 people is <a href="https://en.wikipedia.org/wiki/Dunbar%27s_number">Dunbar’s number</a> — a suggested cognitive limit to the number of people with whom one can maintain stable social relationships. Once the number of employees in your company exceeds 150, communication and coordination becomes a problem.</p><p>Reid suggests that companies ask themselves these questions:</p><blockquote>What’s a culture that defines parallel action across a large number of people, and what’s a way of articulating the plan that most people know how to coordinate with one another</blockquote><p>When the company is small it’s not really necessary to formalise communication about these issues, as it’s constantly being discussed and worked out.</p><p>However, in a larger organisation it becomes more difficult to ensure that everyone is working towards the same goals. Allen Blue talks about the importance of focus:</p><blockquote>Almost always there’s a set of critical components you actually have to focus on. You don’t have to focus on everything…. You can’t do everything perfectly, so the question is what are the 2 or 3 things you have to get right.</blockquote><p>For LinkedIn those 3 things were Product, Go to Market, and Engineering, but they should be particular to your company.</p><p>Reid and Allen both advocated the need for clear and concise documentation of the company’s mission, values, and plan. They both had ample praise for the presentation and documentation that Jeff Weiner put together for the company in 2010…</p><p>Allen:</p><blockquote>This is the first time in the company’s history that we had to be executing on multiple threads simultaneously. When you’re a smaller company you’re generally going to do one thing really well… now you need to be able to execute at 3 or 4 things <em>at scale</em> all at once, which is why you need to be able to sum it up like this.</blockquote><p>Reid:</p><blockquote>We knew a bunch of this stuff, but we’d never constructed a document like this ’cause we weren’t trying to figure out how to get 500 people and growing to all be executing on the same plan</blockquote><p>Good managers and executives are constantly reminding their teams what the goals are, and what the mission is. When you know that everyone else is working towards the same goal, you can make reasonable assumptions about what others are doing, and you can behave accordingly.</p><h4>Hiring is Everything Too</h4><p>Eric Schmidt reinforces why hiring is so important</p><blockquote>The way you build great products is you have small teams with strong leaders who obsess over tradeoffs and they push things off and they say “we’ve got to get it done”, and they put a lot of pressure on the team and they work all night and they produce a product that just barely works…</blockquote><p>Hiring in the early stages of a company is easier in some ways — you’re often hiring friends, family, and former colleagues, and you’re selling the opportunity of building a company from the ground up. Reid points out that when you’re hiring in the later stages you have to sell a different vision, more aligned with your company’s grand mission.</p><p>In LinkedIn’s case, they’re offering the opportunity to have a global impact on the lives of professionals — opening them up to more opportunities and allowing them to be more productive.</p><p>Eric Schmidt agrees, going so far as to imply that you don’t want people who don’t quickly understand and believe in the company’s vision:</p><blockquote>There is a way to systematically hire better people than anybody else. What Bob Tailor who I interviewed yesterday… said was “sell the dream”. So here’s how he funded the ARPANET… he called up people and he described what he wanted and they either got it and got incredibly excited, or they didn’t, and if they didn’t he just went to the next person… how hard is that. Well if your idea is pretty good, if the person is sufficiently dull that they don’t get it, then are they going to get it after some persuasion? Probably not. You want somebody quick.</blockquote><p>This really resonated with me — I think largely because <a href="http://www.karma.wiki/">my startup</a> is incredibly divisive, and I’ve spent countless hours trying to get people to see what I see. I’ve recently started to learn that the opportunity cost of these battles of persuasion are very high, and I’m better off ceding the debate and giving myself more time to find the people that immediate love the concept.</p><p>I also think it’s interesting that Eric references a fundraising technique as a way to hire. It’s a reminder that whether you’re hiring, fundraising, or acquiring users — you’re selling.</p><p>Eric also offers this contrarian advice:</p><blockquote>Hire the divas. Traditional management books say they’re a pain in the ass, and they are. But the divas that believe in your vision are the ones that will drive your culture of excellence. Steve Jobs was a diva. They expect a lot, they drive people hard, they’re controversial, and they care passionately… the industry over-values experience, and undervalues strategic and intellectual flexibility, and I feel strongly about that.</blockquote><h4>In Conclusion</h4><p>A baby unicorn is a lot more fragile than you might expect — there are a lot of things that can kill it, and there’s a lot you have to get right to make it grow.</p><p>However, if you scale at just the right time, you’re diligent in your planning and communication, and you hire well, there’s a chance you’ll make it to the next level.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25b7161307ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/how-to-kill-a-baby-unicorn-25b7161307ee">How to Kill a Baby Unicorn</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conviction, Communication, and Coordination at Scale]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/conviction-communication-and-coordination-at-scale-6bc1ddb300b?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/6bc1ddb300b</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Aaron Kalb]]></dc:creator>
            <pubDate>Sun, 29 Nov 2015 05:03:08 GMT</pubDate>
            <atom:updated>2015-11-23T02:08:47.135Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Thoughts on the OS3 and OS4 Sessions in Stanford’s </em><a href="http://reidhoffman.org/cs183c-technology-enabled-blitzscaling-the-visible-secret-of-silicon-valleys-success/"><em>CS183C</em></a><em><br>(recurring themes, and ideas which surprised or resonated with me)</em></p><p>Once companies reach a certain size, there’s a limit to what any one person there—even a top executive—can accomplish alone. Recent speakers really revealed that results at scale are all dependent on the people (who’s recruited and retained) and the principles and processes (how those people are motivated and managed, and how culture and communication are transmitted) in an organization.</p><p>In this essay, I’ll review some salient points about (in reverse order)</p><ul><li>making sure you have (only) the right people,</li><li>getting them all “on the same page”,</li><li>empowering them to make the company better (without telling them what to do),</li><li>and inspiring them to go do so.</li></ul><p>I’ll start with an observation that this last goal—pumping people up about the mission—is achievable (words and deeds can inspire latent passion), but it probably cannot be taught or faked:</p><h3>Conviction and Charisma</h3><p>Patrick Collison spoke proudly about how “most companies build cars, [but Stripe] build[s] roads”—about how they’re empowering people, building Steve Jobs’ “bicycle for the mind,” while most companies are focused on consumption and entertainment. (That totally resonated with me, as someone who grew up as a kid excitedly using Hypercard and Final Cut Pro and other Apple power tools for various creative projects, and then—saddened to watch them shift their focus toward helping people watch TV on different-sized screens—later left Apple to found an enterprise software firm with aspirations to empower analysts).</p><p>But later, Reed Hastings talked with as much pride about his much-beloved consumption platform: <em>“We sell something important, but not necessary. We sell something you want, but don’t need.” </em>And he said it with total conviction, and reminded me about the value of art and entertainment, and how much pleasure I’ve derived from watching Netflix with friends and family (whether on a Macbook or through Apple TV :P).</p><p>And of course, Elizabeth Holmes expounded passionately that preventing early death is the highest calling, probably much more important than helping people watch TV on their iPads or accept payments on their phones.</p><p>Each speaker really engaged the class and has recruited and retained a dedicated and talented team to work on these very different missions. And though they each emphasized and valued different (and even contradictory) things, they shared a genuine conviction which was infectious. As many of the speakers these past couple months have said (and shown): as a leader it may be <strong>more important to be <em>authentic</em> than “right.”</strong></p><p>As Hastings put it (addressing Holmes <em>in absentia</em>?): “don’t try to be someone else. Multiple styles work. Don’t read about Steve Jobs and start wearing turtlenecks.”</p><h3>Delegation, Revisited</h3><h4>Taking it to the next level</h4><p>Prior speakers, like Pahlka of CFA, talked about alignment, and the idea of establishing values, processes, culture, or training to ensure that people make the same decisions when you’re not in the room. Collison took delegation a step further, making a point which struck me as incredibly humble and wise: “I’m the optimal person to make a decreasing fraction of decisions” he said, so “I don’t want [my employees] to do what <em>I</em> would do,” but rather to just make a “Stripe-y” choice.</p><p>Hastings’ advice to “inspire and lead” rather than “micromanage” is embodied in Netflix’s culture as <strong>“Context over Control.” </strong>But Netflix appears do barely even set context when producing original content, as Reed explained: “we evaluate a team, decide to back them, then let them run.” <em>That perfectly mirrors Warren Buffett’s acquisition methodology, referenced earlier by Eric Schmidt as a motivation for the Alphabet reorg.</em></p><p><strong>It’s fascinating to hear that such capable leaders see more value in getting <em>out</em> of the room or out of the way.</strong></p><h4>Many terms; same idea</h4><p>Nirav Tolia adopted a similar view of delegation, arguing that departmental OKRs define ‘What’, the CEO explains ‘Why,’ and everyone else figures out ‘How’, while Shishir Mehotra positioned the act of determining ‘How?’ as one level higher in the management hierarchy than individual execution, and explained how as folks at YouTube were promoted from there, they were subsequently given autonomy to figure out the general solution to a problem, and ultimately to pick which problems to solve. His general advice on management was to to set inspiring goals and coach when needed, <em>not </em>to dictate, micromanage, or even over-empathize.</p><h3>Scaling Communication</h3><p>Asked about the best advice she ever received, Dianne Greene replied: “You can never over-communicate.” [Side-note: Being in enterprise software, it was really great to hear from her about VMWare, in general.]</p><p><strong>How do you communicate in a rapidly growing organization?</strong> Collison and Mehotra both agreed the key is to <strong>write things down.</strong> Written words provide “rigidity and clarity” (in Collison’s words) that oral communication lacks, and it persist through time to be read by later arrivals to a company or conversation. And as Mehotra pointed out, writing helps avoid “game[s] of telephone.”</p><p>Hastings’ culture deck is a powerful and useful example of the principle. And Greene (and Brian Chesky—more on him in the next post) supplement the clarity with consistency and regularity by sending Sunday emails.</p><p><strong>By contrast,</strong> Elizabeth Holmes seemed to suggest that her weekly communications are solely live, using a large cafeteria plus conference calling. Skeptics might claim that the comparative vagueness and ephemerality of such meetings versus something written in stone (or on servers), characterizes Theranos and might partially explain their present predicament. Plus, practically, international offices down the line could make scheduling a time for an All Hands extremely challenging (Google’s tried with their TGIFs and I believe attendance is quite low in parts of the world; thankfully, their culture includes lots of asynchronous written communication as well).</p><p>Big central campuses plus A/V technology (and maybe VR!) all provide cool opportunities to leverage the numerous advantages of oral communication between people at all levels of an organization. But it appears inevitable that at least at a certain size, leaders must write.</p><h3>Dead Wood</h3><p>Everyone likes to talk about hiring A-players. Our speakers were also refreshingly frank and forthright about the converse:</p><ul><li>Greene described an “immune system”—a great group which naturally pushes out less great people. When that fails, she remarked that you never fire people too early</li><li>To prevent waiting too long, Mehotra advised managers to periodically ask, “would I rehire this person?” and to (essentially) fire those for whom the answer is no</li><li>And Hastings takes that idea even farther, asking managers to testify that they’d fight to keep each employee and providing them with an automatic, generous severance offering (and a mandate to use it freely), so that the urge to be nice doesn’t get in the way of a necessary decision. In addition to the practical incentive, he also explained how it’s <em>nicer</em> to those who <em>remain</em> to fire folks who don’t fit, citing an observable productivity <em>increase </em>after laying off a third of the company in 2002 as well as the “joy of excellence” and the synergy that emerges—process-free—from having a “density of talent.”</li></ul><h3>Conclusion</h3><h4>In short…</h4><p>…success at scale requires</p><ul><li>getting the right people (by both hiring and firing wisely),</li><li>clearly transmitting values, inspiration, context, and culture to them (probably through regular writing)</li><li>then getting out of the way, so that your capable and motivated team members—who have the required context and your same passion for the cause—can execute on their initiatives, producing better outcomes than you could have planned.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bc1ddb300b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/conviction-communication-and-coordination-at-scale-6bc1ddb300b">Conviction, Communication, and Coordination at Scale</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Founder’s transition to a Leader]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/founder-s-transition-to-a-leader-56dced0672fc?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/56dced0672fc</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[blitzscaling]]></category>
            <category><![CDATA[cs183c]]></category>
            <dc:creator><![CDATA[Shikhar Shrestha]]></dc:creator>
            <pubDate>Sun, 29 Nov 2015 05:02:36 GMT</pubDate>
            <atom:updated>2015-11-23T22:07:53.585Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The transition of a startup from the “tribe” to “village/city” stage creates an imminent need for the founder to grow into the role of a leader. This essay focuses on all aspects of this transition that I find intriguing and how they relate to the principles of blitzscaling.</em></p><p><em>Read the first two parts of this essay </em><a href="https://medium.com/cs183c-blitzscaling-student-collection/thoughts-on-scaling-when-it-s-too-early-2d31dec00d69#.3fzkuf6yw"><em>here</em></a><em> &amp; </em><a href="https://medium.com/cs183c-blitzscaling-student-collection/so-you-know-what-to-build-now-what-44f74b80adba#.cta20xgky"><em>here</em></a><em>.</em></p><p>The past few weeks of CS183C have been centered around one of the most radical transitions for a founder in the life of a growing company. During the initial stages, the founder has a survivalist mindset where his/her focus is on internal, micro-scale issues that keep the company afloat and help gain significant size. However, as the company scales and approaches the onset of the “village” stage, the focus shifts to more macro-scale issues and decisions are now optimized over a much longer time horizon. The mindset of the founder needs to evolve to that of a strategic leader whose goal is to build a great, lasting organization. This can be incredibly challenging for a founder on a personal level but is critical for the long-term success of the company.</p><p>As a leader, the founder needs to develop clarity of vision and set consistent goals that are clearly communicated to every employee. This helps unify the company, gives perspective to individual contributors on how their pieces fit into the puzzle and provides context for making everyday decisions (<a href="https://en.wikipedia.org/wiki/Ben_Hunt-Davis">will it make the boat go faster?</a>).</p><p>The founder does everything that needs to be done in the early days but now needs to enable others to do their work effectively. In his book ‘Drive’, Daniel Pink talks about the three things that motivate people to do the best work of their lives; mastery, autonomy and purpose. I think this is a very powerful framework and the founder needs to foster an environment that conforms to these attributes. Strong sense of purpose is the most powerful of them all and it’s what empowers people to persevere through moments of lack of confidence.</p><p>Time and again we have noticed that the best companies have a strong culture. In startups, this culture is mostly founder-led and sets the precedent for how people are expected to conduct themselves in different situations. I loved how Reed Hastings at <a href="http://www.slideshare.net/reed2001/culture-1798664">Netflix</a> defined their culture in writing as it leaves no room for misinterpretation and also helps evaluate potential hires for a good fit with a clearly defined framework.</p><p>Another fascinating idea that came out of the conversation between Reed Hastings and Reid Hoffman was that of simultaneously executing while knowing that there is uncertainty. Firm execution is key but it does not mean you compromise on agility. It’s important to keep farming for dissent within the company and gather ideas, but you have to be unequivocal about the path you choose to move forward on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56dced0672fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/founder-s-transition-to-a-leader-56dced0672fc">Founder’s transition to a Leader</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So you know what to build, now what?]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/so-you-know-what-to-build-now-what-44f74b80adba?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/44f74b80adba</guid>
            <category><![CDATA[blitzscaling]]></category>
            <category><![CDATA[cs183c]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Shikhar Shrestha]]></dc:creator>
            <pubDate>Mon, 02 Nov 2015 18:53:39 GMT</pubDate>
            <atom:updated>2015-11-02T18:38:29.710Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Applying the principles of blitzscaling to your company as you hire your very first set of employees, get more users and transition into the “tribe” stage.</em></p><p><em>Read the first part of this essay </em><a href="https://medium.com/cs183c-blitzscaling-student-collection/thoughts-on-scaling-when-it-s-too-early-2d31dec00d69#.nft1di94p"><em>here</em></a><em>.</em></p><p>John Lilly shared Mozilla’s incredible community-driven growth story a few weeks ago in CS 183C and described Microsoft’s position during that period as a combination of <strong>majority</strong> <strong>market share</strong> and <strong>dominant distribution</strong>. That description has been resonating in my head ever since as it fully captures the essence of where you need to get as you scale your company.</p><p>OS-2 or the tribe stage is all about gaining market share by finding your ‘path to scale’. You already have some validation from users and know what the product needs to look like, so it’s time to double down on that path and fully align the startup to its target market.</p><p>First thing you need is a growth hypothesis, which basically outlines your strategy to recruit users and can be one or a combination of techniques like virality (Hotmail), word of mouth/organic (Zappos), growth through value (Slack), leveraging community (Mozilla), seeding (for network dependent value proposition like Linkedin, Twitter) etc. Agility is still of prime importance just like the family stage as you are operating in a dynamic environment and so you keep cycling through the plan-execute-learn-rethink cycle.</p><p>The next part of the puzzle is to understand what you need to execute this growth strategy and hiring people in those images. Your first hires are the most critical and you implicitly define the culture, values and binding principles of your company by picking the right people.</p><blockquote>Industry overvalues experience and strategically undervalues intellectual flexibility. — Eric Schmidt</blockquote><p>Being early hires, most of these people need to be generalists that have the ability to quickly gain competency in new areas and get things done. Look for people that are not generic but special in some way. Eric cited an example of hiring CFOs who have gone through bankruptcy as an example case of a special individual who has been through the wars and will do whatever it takes to not let it happen again. Some of these people need to be ‘divas’ that will drive the culture of excellence, probably be controversial and provocative but care passionately about your mission and the company. The best way to get these people involved is to build aspiration by selling the dream!</p><p>Armed with a formidable team and a strategy to get market share, you now need to frame a set of consistent questions that you keep asking to track your progress along the way. This is what closes the feedback loop and eventually helps you discover what matters the most for your business and why? Selina Tobaccowala and Mariam Naficy both outlined the importance of building dashboards and metrics around your KPIs to gain these insights and use them to correct your hypothesis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44f74b80adba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/so-you-know-what-to-build-now-what-44f74b80adba">So you know what to build, now what?</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Founding Family Values]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/founding-family-values-a88d08416ad?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/a88d08416ad</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Aaron Kalb]]></dc:creator>
            <pubDate>Fri, 23 Oct 2015 14:18:30 GMT</pubDate>
            <atom:updated>2015-10-23T10:12:19.187Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Thoughts after the first four classes of Stanford’s </em><a href="http://reidhoffman.org/cs183c-technology-enabled-blitzscaling-the-visible-secret-of-silicon-valleys-success/"><em>CS183C</em></a><em><br>(ideas which surprised or resonated with me)</em></p><h3><strong>Validate early — any way you can:</strong></h3><h4><strong>make sure you’re building something people love</strong></h4><p>Paul Graham’s discussion of the “Manual” approach to <a href="http://paulgraham.com/ds.html">“do[ing] things that don’t scale”</a>—the “Wizard of Oz” approach in HCI lingo — reminded me of one of <a href="https://en.wikipedia.org/wiki/Siri#Research_and_development">Tom Gruber</a>’s excellent stories from the early days at Siri, pre-acquisition, back when it was a research project becoming a start-up. Early Siri was intended to take requests like “book me a table for two tonight at a romantic Italian restaurant in Palo Alto.” Before actually honing the underlying technology, Tom and team claimed it existed, and — in a hilarious inversion of the Turing test or ELIZA bot — they manually performed the Yelp lookups and OpenTable reservations as fast as they could after IMing “Processing your request…” to unsuspecting interlocutors. By the time Tom came into Apple (where he became my boss), Siri’s destiny as a household name — and perennial SNL topic — was basically secured. It was hard to imagine the early days, when Siri’s success was — as John Lilly described young Firefox or candidate Obama — so fragile and contingent. And it was fascinating to learn about how <em>only</em> through such acts of unsustainable efforts can anything lasting be built. Sam Altman’s story about the AirBNB founders was a testament to that.</p><p>My first attempt at a start-up failed. Like the Siri founders, I’d had what looked like a technological breakthrough in my research on computers and language that could help solve a real-world problem. But I <em>imagined</em> all the utility of the mature product before really validating that a market existed. As I learned about the space with my co-founders, it became evident that there really wasn’t a market for our software.</p><p>With <a href="http://www.alation.com/">Alation</a>, we talked to would-be customers before we even had a product, and found many companies who had spent vast resources trying to internally solve the problem we were targeting (albeit not the exact same way). They were thrilled at the prospect of someone dedicated solely to solving that problem, since they’d looked around and found no solution they could buy. The validation (and ultimately revenue) from those early customers sustained us and helped us grow over the last three years.</p><h3><strong>Diversity and Unity</strong></h3><p>I founded my failed start-up with some of my best friends — extremely dedicated and talented people who happened to be some of the smartest I knew. The catch: selection bias. Geography is destiny and I’d met each of my then co-founders because we lived together (two in Stanford dorms, one on a ship). While we had complementary skills in engineering, linguistics, design, and management, not one of us was over 25. Age doesn’t matter, but experience can. None of us had run a company, executed an enterprise sale, or built a widely-used website. In Silicon Valley, we love to point to the outliers who irrevocably changed the world as college drop-outs with no prior experience, but statistically speaking, that’s not the most likely outcome. (Happy ending: we’re all still good friends, and they’re kicking ass at Facebook, Uber, and MIT, respectively).</p><p>By contrast, I didn’t know my Alation co-founders at all before Alation. But we had each independently developed a contrarian view of the key problem in our space, and we had each independently envisioned a similar approach to solving it. We shared that vision, but differed totally in our backgrounds. Superficially, we came from three different countries and were born in three different decades. More importantly, we had deep and deeply complementary skills in business and sales, Google-scale engineering, and product design. It felt like “Mission: Impossible.” That breadth of skills is hard to find in a single college cohort, even at Stanford.</p><p>Sam Altman described the ideal founding team perfectly: <em>diversity of perspectives is really good. Diversity of vision is a problem.</em></p><h3><strong>A pleasant surprise</strong></h3><p>I came into this course with pretty high hopes. So far, those have been exceeded. I did worry that maybe the content would be a string of generalizations or platitudes. But each instructor and speaker has provided such great examples and strong perspectives, and displayed such wit, compassion, and humor. I’ve left each class feeling energized, inspired, and educated. Looking forward to learning more, especially as we discuss OS2 — of particular relevance to Alation at our present stage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a88d08416ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/founding-family-values-a88d08416ad">Founding Family Values</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(Hiring & [Managing People) & Products]]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/hiring-managing-people-products-710cce10112c?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/710cce10112c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Aaron Kalb]]></dc:creator>
            <pubDate>Fri, 23 Oct 2015 14:18:21 GMT</pubDate>
            <atom:updated>2015-11-17T19:49:57.012Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Thoughts on the OS2 Lectures in Stanford’s </em><a href="http://reidhoffman.org/cs183c-technology-enabled-blitzscaling-the-visible-secret-of-silicon-valleys-success/"><em>CS183C</em></a><em><br>(ideas which surprised or resonated with me)<br></em><strong><em>Part I of </em></strong><a href="https://medium.com/@kalb/perceived-value-52bbfada3753#.jm9hppem9"><strong><em>II</em></strong></a></p><h3><strong>I. Micromanagement vs. the Jeopardy Approach</strong></h3><p>Mariam Naficy observed that if you can’t let people fail, you can’t let them grow. She brought up the notion in the context of capital: when you’re cash strapped you can’t afford mistakes and wind up micromanaging. We’re not in that situation, thankfully, but I could certainly relate to the more emotional reasons for failing to give employees adequate wiggle room. She explained that at first she knew everything going on at the company, but now she doesn’t “which is hard for a person who is detailed-oriented.” I can tend toward perfectionism and worry about how Alation will be seen if things aren’t just right. But I also want Alation to be way bigger than I can personally track with high granularity and getting there will require delegation with high-standards but less oversight. Eric Schmidt offered an excellent strategy for doing so when you’ve got smart people (as we do): early in his talk he described how on arriving at Google he would “just ask questions” (e.g. “what’s the plan for <em>this</em>?”) and later he explained how he got the lawyers to work out the right structure for the Google-to-Alphabet transition by telling them to “solve for <em>x</em>” (specifying the goals / properties of the optimal solution, but not suggesting any methodology). Both quotes strike me as articulations of a <strong><em>Jeopardy Approach to management </em></strong><em>— phrasing your directions in the form of a problem</em>. I love this idea and I’ve seen it work amazingly (including for me sometimes when I’ve had the restraint and humility to execute it correctly and commit to it completely).</p><h3><strong>II. Reconciling (Seemingly) Incongruous Perspectives on Hiring</strong></h3><p>Attracting and retaining talent is top of mind for Alation here in OS2, so I paid extra attention to the speakers’ viewpoints in that regard.</p><p>Eric Schmidt offered support for the Google founders’ belief that the industry generally overvalues experience and undervalues raw intelligence and flexibility. But he also recommended that companies “hire a CFO who’s gone bankrupt.” Taken together, I think the lesson may be that someone really smart can reverse-engineer declarative knowledge, but emotional learning and values can perhaps be gleaned only from experience.</p><p>Meanwhile, Schmidt supported Bob Taylor’s approach of pitching the dream (of ARPANET in Taylor’s case) and not trying to convince anyone who didn’t immediately “get it” to join, while Jennifer Pahlka admired Todd Park’s persistent-persuasion approach which had been compared to “water on stone.” Here too, I think the perspectives are actually compatible: <strong>you can’t talk someone into having a passion, but you can talk them into taking an action.</strong> Jen understood the opportunity right away. But she needed someone to objection handle all the concerns about the job, effect on her family, etc.</p><h3><strong>III. Factoring Firefox feature functions:</strong></h3><p><strong>Palliating palpable pain vs. offering unanticipated experience improvements</strong></p><p>I loved John Lilly’s assessment that early Firefox users came for the popup-blocking and stayed for the tabbed browsing. The first version of Alation’s query tool, Compose, was filled with features that we thought would be game-changers capable of radically improving the lives of data analysts who were using Teradata SQL Assistant. But many of our would-be users did not really perceive themselves to need help (much as IE users in 2004 probably didn’t realize that having one webpage per window was an issue before they’d gone to the other side). Luckily for us, our browser-based tool worked well on Macs, whereas the competing tool offered a really uncomfortable experience for non-PC users. That earned us an initial cohort. Then, for mostly separate reasons, we implemented Offline Execution, which addressed this huge pain point people had of not getting their results for long-running queries when they carried their laptops between WiFi hotspots to get to meetings (thereby dropping the desktop client’s connection to the DB). That led to a huge usage uptick.</p><p>Since then, we’ve tried to always explicitly ensure that everything we release addresses at least one big problem people <em>know </em>they have.</p><p>(Happy Ending: many of the features we thought would help sell the product up front have in fact become sustaining features once users give Compose a try #yaywearentalwaystotallywrong)</p><h3>Appendix</h3><h4>A few moments that totally resonated, with brief reactions in italics.</h4><ul><li>John’s anecdote about being taught to use “let’s take this offline” as a “safe word” at Reactivity:<br><em>Yup, learning to say LTTO totally changed my work life!</em></li><li>Jen’s statement that the user experience with the government need not feel so different than in the consumer realm:<br><em>Here here! The</em> <em>same goes for enterprise software (and not just if you’ve got the split market and bottom-up approach of a Dropbox or Square)</em></li><li>“The problem with communication is the illusion that it has occurred”:<br><em>That’s brilliant! Probably the single biggest lesson we’ve been learning at Alation (and I’ve been learning personally) as we scale is how hard it is to transfer knowledge in a manner that’s not too lossy.</em></li></ul><p>A long tangent down memory lane turned into a post of its own: here’s <a href="https://medium.com/@kalb/perceived-value-52bbfada3753#.mtgg2fxb3">Part II</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=710cce10112c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/hiring-managing-people-products-710cce10112c">(Hiring &amp; [Managing People) &amp; Products]</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Know Thy Phase]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/know-thy-phase-bc7bd213851f?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/bc7bd213851f</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[blitzscaling]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dayne Rathbone]]></dc:creator>
            <pubDate>Fri, 23 Oct 2015 05:39:27 GMT</pubDate>
            <atom:updated>2015-10-23T06:00:10.293Z</atom:updated>
            <content:encoded><![CDATA[<p>In their book “Blitzscaling”, Reid Hoffman and Chris Yea outline 5 key phases of a company’s scaleup maturity: Family, Tribe, Village, City, and Nation.</p><p>A large company may appear to be just a scaled up startup, but Chris and Reid argue that the phases are notably distinct from one another.</p><p>“<em>In the physical sciences, materials often undergo phase changes… ice melts into water; water boils into steam. As a startup scales up, it undergoes a number of such changes. The most obvious, visible, and impactful change to a scaleup is the number of people it employs</em>”</p><p>I had assumed that my small company (<a href="http://www.karma.wiki/">Karma</a>), with just 4 full-time employees was firmly in the Family phase. But as I learnt more about the characteristics of each phase it became apparent that a company can be (and almost certainly is) in multiple different phases at once.</p><p>“<em>It’s also true that the phases of a scaleup don’t move in lockstep… Consider the example of Instagram: When that company was acquired by Facebook for $1 billion, it had reached Phase 5 in User Scale, but was still in Phase 1 in Organizational Scale with just 10 employees, and Phase 1 in Business Scale with no significant revenues</em>”</p><p>As I read what Reid and Chris had to say about hiring in the Tribe stage, it occurred to me that Karma had been facing these challenges since its inception.</p><p>“<em>In the previous [Family] phase, you pretty much hired all your employees through your personal network. At this point, however, you’ve run out of smart people you know who are available… your team may know a ton of great people, but there are so many interesting projects besides yours that most people are already spoken for.</em>”</p><p>When my brother Clyde and I began working on Karma we left behind <a href="https://medium.com/karma-wiki/what-is-the-perfect-startup-team-f30cf647d05d">careers in professional sport and stand up comedy</a>. We’d discovered a problem that we were passionate about solving, but we realised that we needed a co-founder with strong web development experience.</p><p>Half a decade prior I’d been a computer scientist and games programmer, but emigrating and changing careers meant that the number of smart, available, and experienced web developers in our network was precisely zero.</p><p>But hiring in the Tribe stage is tricky business, especially for inexperienced founders like ourselves.</p><p>“<em>One thing that few startups do (unless they have experienced founders) is to have a rigorous hiring process for people they don’t know. You may think you don’t have time to bother with these niceties, but experienced founders know that it’s useful to put in a little bit of time early on to establish a clear and productive process… It’s especially common for startups to underinvest in reference checking… If I had to pick between conducting an interview and conducting a reference check, I’d pick the reference check</em>”</p><p>If I’d read and followed the advice in that paragraph 8 months ago, I’d have saved Karma from <a href="https://medium.com/karma-wiki/the-curious-case-of-e5d837ba5ee5">the biggest mistake in our company’s history</a>. Interestingly, now that Karma has an brilliant tech co-founder and a strong supporting team, our hiring challenges are more consistent with the Family phase.</p><p>Understanding the challenges, principles, and strategies associated with each phase of blitzscaling is important. But what is perhaps equally consequential is knowing which of these phases each part of your company is in, and recognising that these phases are in constant flux.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc7bd213851f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/know-thy-phase-bc7bd213851f">Know Thy Phase</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Letting Demand Pull You Into Scaling: How to Know When To Go From A Family To A Tribe]]></title>
            <link>https://medium.com/cs183c-blitzscaling-student-collection/letting-demand-pull-you-into-scaling-how-to-know-when-to-go-from-a-family-to-a-tribe-562381d76f04?source=rss----7104d0e1e98d---4</link>
            <guid isPermaLink="false">https://medium.com/p/562381d76f04</guid>
            <category><![CDATA[cs183c]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Jon Hearty]]></dc:creator>
            <pubDate>Fri, 23 Oct 2015 05:39:15 GMT</pubDate>
            <atom:updated>2015-10-23T05:39:15.436Z</atom:updated>
            <content:encoded><![CDATA[<p>They say that if you don’t know if you have product-market fit, you don’t have it. Once you know you have it, however, the question at hand becomes “when and how quickly do we scale?”</p><p>When going from a family — roughly 1 to 10 employees — to a tribe — roughly 10 to 100 employees — you are essentially going from one team that does everything to two teams: team #1 focuses on growth and team #2 focuses on helping team #1 do their job.</p><p>Founders start hiring more specialized people to take some work off of their plate. You go from wearing tons of hats to focusing on a few. You bring people onboard that thrive in an environment that is well below <a href="https://en.wikipedia.org/wiki/Dunbar%27s_number">Dunbar’s number</a>, hoping that some of them will quickly evolve into strong team members that can balance out the inevitable external leadership and executives that will soon come, if all goes as planned.</p><p>Instead of core functions like product, engineering and sales, you will start bringing on team members who specialize in finance, HR and customer service. The goal of these teams is to keep the scaling team focused by removing distractions. The same thing happens on a departmental level, also. For example, generalist salespeople go from sourcing their own deals and managing their own accounts to getting handed warm, vetted opportunities by sales development representatives and handing closed deals off to customer success managers.</p><p>This scaling, however, only magnifies the underlying state of affairs, good or bad. The only thing worse than shitty execution is shitty execution scaling at an enormous rate. This rapid growth needs to be carefully calculated. It’s crucial to grow for the right reasons and backup your growth strategy with real data that supports your trajectory. While each scenario is different, one of the best things to closely monitor when deciding how fast to scale is demand.</p><p>Demand can come in many forms. For PayPal, it was a consistent, daily growth in transaction volume that forced them to scale or fold under the pressure of their own success. For B2B SaaS startups, it’s typically lead volume, or what <a href="http://twitter.com/jasonlk">Jason Lemkin</a> refers to as <a href="http://www.saastr.com/why-lead-velocity-rate-lvr-is-the-most-important-metric-in-saas/">lead velocity rate</a>. You want scenarios where demand is <em>pulling</em> you to scale rather than your gut, investors or ambitions pushing you to do so.</p><p>Once you sense the demand, you can’t simply flip the hiring switch and go on a recruiting frenzy. Instead, let the demand be your north star. Do your best to toe the line of hiring slowly and staying ahead of demand, while always reminding yourself that hiring is the means, not the end.</p><p>Picking a number like a million monthly active users or $10 million in annual recurring revenue and basing your hiring and growth strategy off of that is an easy trap to fall into. Take your eye off demand for even a moment or two and you may suddenly find yourself with a large structure being built atop a shaky foundation. As good as it may feel to judge your success on a vanity metric like your employee growth, do the smart thing and let demand pull you into scaling.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=562381d76f04" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cs183c-blitzscaling-student-collection/letting-demand-pull-you-into-scaling-how-to-know-when-to-go-from-a-family-to-a-tribe-562381d76f04">Letting Demand Pull You Into Scaling: How to Know When To Go From A Family To A Tribe</a> was originally published in <a href="https://medium.com/cs183c-blitzscaling-student-collection">CS183C: Blitzscaling Student Collection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>