<?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[FutureTight - Medium]]></title>
        <description><![CDATA[FutureTight is an innovation consultancy based in San Francisco, California. Companies that work with FutureTight are mid-sized to large organizations foreseeing disruption and seeking new growth areas. - Medium]]></description>
        <link>https://medium.com/futuretight?source=rss----eb05853cc3ba---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>FutureTight - Medium</title>
            <link>https://medium.com/futuretight?source=rss----eb05853cc3ba---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:08:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/futuretight" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Putting Lean to Work on a Top Secret, Disruptive Product]]></title>
            <link>https://medium.com/futuretight/putting-lean-to-work-on-a-top-secret-disruptive-product-8e6a51d57a0f?source=rss----eb05853cc3ba---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e6a51d57a0f</guid>
            <dc:creator><![CDATA[Andi Plantenberg]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 05:55:12 GMT</pubDate>
            <atom:updated>2014-03-24T19:43:24.256Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fLTUTyR-HgAxmJyBFpl0w.png" /></figure><h4>I’m leading design on a product with grandiose implications for humanity. Kinda like the X-men.</h4><p>I’m leading design on a product with grandiose implications for humanity. Kinda like the X-men. It’s top secret, so I’ll try and paint the picture in metaphor. Okay, think of humanity as ants. Now imagine those ants all have time machines and ray guns! No that’s not quite right. Imagine the world’s brightest minds together in one place engaged in solving the big problems of our age…in real-time! That’s a little better.</p><p>The project is funded. The market is validated. We know there is a huge appetite for what we’re making. We’re also aware of corruption that works against fixing the system. We aim to disrupt that.</p><p>We’re looking to shape future behavior, and not so much looking at the behavior arising from the current broken systems.</p><p>When we think of lean, we think build—measure—learn. We think of validation. Testing assumptions. Getting an MVP in the market. But here we are wanting to enable a quantum leap in behavior and attitude. And it’s under wraps. How do we build—measure—learn in that context? Is it even appropriate to take a lean lens to this?</p><p><strong>The answer is ‘Hell yes’.</strong> In fact it’s more important we do so. Projects that are secluded and funded are more vulnerable to being fatty and ending up way off base. Teams are at higher risk of breathing their own fumes when working in secrecy. And it’s all too easy to add waste by using old, comfortable methods. Historically, the work would go something like this: First there would be the idea. Then there would be a lot of research done by researchers. The designers would then design it. And finally developers would build it. This process is, of course, called <em>waterfall. </em>It’s an expensive and risky way to build products, we now know. A new best practice has emerged.</p><p>We can bring lean methodologies to a project like this. <em>How </em>we build is just as important as <em>what </em>we build and <em>why. </em>Let’s start with the <em>how </em>part.</p><h3><strong>How to Work Lean on Long-Term Projects</strong></h3><p><strong>• Assemble cross-functional teams</strong><br>We build small, cross-functional teams. We have designers and engineers working side by side with the product owner and a domain expert. The act of simply making something together brings about new angles and opportunities that would remain otherwise hidden.</p><p><strong>• Work out loud<br></strong>We keep true to the principles of the project while also testing for feasibility — it’s baked into the day-to-day work. We work together transparently to iterate trials against our blue-sky vision. Adjustment and assessment happens continuously. It takes a lean discipline to maintain a vision that keeps pace with your learnings.</p><p><strong>• Work low-fi<br></strong>It’s important to acknowledge that the starting vision is wrong, wrong, wrong. It will need to change as you’re building. So we work fast, low-fi and towards a common goal. We think aloud as a group, favor white-boarding to wireframes, favor hacking up screenshots rather than maintaining PSD masters. We favor the product over design artifacts and documentation. Get over it. Your product is the documentation.</p><p><strong>• Maintain a shared understanding<br></strong>This is a happy side effect of working out loud. There are no long documents or briefs to be updated and maintained. We are all experts. We all get it. We trust each other and we move as one to build the product.</p><p>Okay, but what about the <em>what </em>and <em>why </em>part? If we are flying under the radar, what external input are we using to correct course? That feedback loop is essential to ‘lean’.</p><h3><strong>How to Build—Measure—Learn on Top Secret Projects</strong></h3><p>This product’s development is more agile than lean. It’s intentionally being well-baked before real people use it in the real world (the reason for doing so is another post entirely). However, lean practices have had an undeniable and enormous impact on the mission, the client, and the product.</p><p>In lean fashion, we de-risk by testing hypotheses and shake out costly assumptions early. We embed lean epicycles of build-measure-learn into the agile development process. Here’s how…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTqM6nR0iWKEcp7P3J5_4g.png" /><figcaption>Test safe people in a secret world</figcaption></figure><p><strong>• If the real world is off-limits, make a secret world</strong><br>We mimic the real-world and test there. If the organization is large, you likely have access to safe people who match prospective customers. Use them for testing.</p><p><strong>• Isolate high-risk assumptions</strong><br>Here’s an example. The client had arrived at the inception armed with two years of upfront research, and felt strongly about building out 3 very specific interaction paradigms. The Neo team members wanted to validate that proposed solution.</p><p><strong>• Listen to customers in your secret world</strong><br>We set up phone interviews with safe subjects who fit nicely into the customer pool. We listened to detailed stories from these people. They’re important foot soldiers in the culture we are hoping to affect. If the solution doesn’t work for them, then it won’t succeed in the broader, global context.</p><p>They detailed their pains to us. They ranked them for us. We learned what motivates them to do their work. At the end we had a nice set of data points, and validated specific problems.</p><p>• <strong>Test hypotheses in your secret world</strong><br>Next, we wanted to see if the same paradigms would rise to the top if we considered interaction models from scratch. So we set out on a time-boxed, blue-sky design exercise.</p><p>After quick internal iteration, we had a set of comps with which to test. From testing sessions, we arrived at interaction models that were in some ways similar, and in other ways different than what the client originally envisioned. What rose to the top were the aspects of those initial paradigms that were of highest value to the customer.</p><p>So that’s it. We create hypotheses from assumptions. We build tests (comps and quick prototypes), and we learn from testing them. Then we feed the learnings back into the product we’re building. As the broader team sees the benefits, they feel comfortable referring more customers for testing, thus growing our secret world to better match the real world with it’s varied, global actors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e6a51d57a0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/futuretight/putting-lean-to-work-on-a-top-secret-disruptive-product-8e6a51d57a0f">Putting Lean to Work on a Top Secret, Disruptive Product</a> was originally published in <a href="https://medium.com/futuretight">FutureTight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Branding for Startups]]></title>
            <link>https://medium.com/futuretight/branding-for-startups-3db0cb9721c7?source=rss----eb05853cc3ba---4</link>
            <guid isPermaLink="false">https://medium.com/p/3db0cb9721c7</guid>
            <dc:creator><![CDATA[Andi Plantenberg]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 05:47:27 GMT</pubDate>
            <atom:updated>2018-09-01T05:47:34.703Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uTkEE17J7JuNCGnsy9wTtg.jpeg" /></figure><h3>CRUSH your brand where it matters. Forget the rest.</h3><p>It’s easy for new companies to burn resources on branding and miss the mark all together. There’s a lot of outdated advice out there and outdated people to give it. I’d like to show you the old, inefficient way, and a new, emerging practice, so you may navigate this shifting territory.</p><h3>Brand is a weird thing.<br>Let’s break it down.</h3><p>Brand is not a logo. It’s not a name. Branding is a big fat complicated thing because of how our brains work. A brand is nothing less than the space your company occupies in someone’s brain. The look, feel, voice, smell, sound. So much of what a brand is is qualitative.</p><p>Consider this analogy. If a company is a person, the brand is what they wear, how they sound, how they behave, whether or not they look like they belong at the party. For instance, if someone appears well-to-do, yet they always turn the conversation to the topic of their success, they come off as desperate. If someone stands too close to you in an elevator, you notice it and you think less of them for it. <strong><em>Admit it!</em></strong></p><p>The same social factors I just described are at play when we deal with brands. That explains why traditionally it’s been a long, thoughtful process to cook up a brand from scratch.</p><p>There are a few brand components (logo, voice, vibe, mood, color, and typography) that can be expressed across a huge multi-verse of potential experiences. But for new companies and products looking to establish a brand, not all of those experiences are important to consider right now. This runs counter to aging best practices.</p><h3>First, let’s look at the old way: The Big Agency Branding Exercise</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k6BJOw5WXbAiUYeGeXeCrA.jpeg" /><figcaption>A day in the life of a typical digital agency. For more on this topic see “<a href="http://bit.ly/1tmDZpV">Is it too late for big agencies?</a>”</figcaption></figure><p>Agency branding exercises are designed to make brands that scale — to cover off on <strong><em>the entire universe of brand experience</em></strong>, however large it may grow in the future.</p><p><strong>Here is a typical brand ecosystem that an agency might cover:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SHKAUUGTWXTNkpcLUoNZpA.jpeg" /></figure><p>It’s not unusual for this to cost hundreds of thousands of dollars. The exercise is politically charged because of all the money being spent. The process becomes about <strong><em>stakeholder consensus building </em></strong>more than anything else.</p><p>When launching a product or company, we know that it must appear legit, polished and consistent if anyone is to give it the time of day. In short, you need a solid brand experience. But how can you invest so much capital into something you aren’t sure will survive? What’s a startup to do? Here’s what…</p><h3>There is a new, better way to do branding.</h3><p>There is a slice of the larger brand experience that you <strong><em>must crush.</em></strong></p><h4>Narrow your effort to your most important points of contact.</h4><p>Isolate the slice of the larger branding ecosystem that your venture really needs. Then CRUSH THAT SLICE. Articulating this slice is the mechanism through which you control your branding timeline and cost.</p><p>Here’s how you determine your slice. All ventures need to have the following to be minimally viable: <strong>Acquisitions, Activations, Retentions, Referrals, Revenue.</strong> For our purposes we will consider the first four.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNwt1KuHCKr1Ugx9t5DgAg.jpeg" /><figcaption>For more info, see David Bland’s “<a href="http://slidesha.re/1wCHqif">How to build products that matter with innovation accounting</a>”</figcaption></figure><p>These four stages have brand artifacts your customer will interact with. For instance, Acquisitions might happen with Google Adwords and a landing page. Activation with the landing page, sign up flow and a thank you email. Retention with exceeding your brand promise. You’re only concerned with certain customer touch-points early in the game.</p><p><strong>Here are the brand components we mentioned earlier:<br></strong>The things that apply to all points of customer / brand contact; logo, voice, vibe, mood, color, and typography.<br>(<em>The stickies with </em><strong><em>blue underlines</em></strong>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-hdg3kjkzRfcWTBpqth0Lw.jpeg" /></figure><p><strong>Here are some likely acquisition points for a startup or validation team:<br></strong>(<em>The stickies with </em><strong><em>pink dots</em></strong>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1-y2QJnaA4VOicBcogNsKA.jpeg" /></figure><p>You will be expressing your brand (logo, color, mood, vibe etc) in the context of a few key areas (landing page, website, SEM, biz dev etc).</p><h4>Find the Right Touch-Points for Your Early Brand</h4><p>Become familiar with<strong> </strong><a href="http://slidesha.re/1wCHqif"><strong><em>Innovation Accounting</em></strong></a><em> </em>to find the necessary touch-points in your acquisition channel. <em>THAT is where you should focus your brand expression. </em>Then turn your focus on Activation, Retention and Referral touch-points.</p><p><strong>There are many places on which you risk wasting your precious resources. </strong>Anything that is not a completely necessary point of customer contact for your near term goals is a <em>waste of resources</em>.<br>(<em>The stickies with </em><strong><em>red Xs)</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1bdA4g11nOJ2I9mlPqisHA.jpeg" /></figure><blockquote><em>Don’t let anyone freak you out about your brand not scaling. They are parroting best practices from a bygone era.</em> (← <a href="http://ctt.ec/cGXLi">tweet it</a>.)</blockquote><p>You want your brand to scale only in your key touch-points and be flexible enough to allow you to reach your near-term goals.</p><p>Now, once you’ve found your slice, <strong><em>you still need to crush it</em></strong>. You’ll need seasoned creatives who can bring their talents and instincts to bear on the problem. Like I said, brand is qualitative and complex. It’s like a relationship with a person. That’s why we must narrow the scope to interactions that matter most. If your company is like a person, then be mindful of who your chatting with at the party. Don’t blow your immediated interaction by being distracted by future interactions that may or may not happen.</p><p>There are teams that have a solid understanding of these emerging best practices. <a href="http://bit.ly/1vW6JYC">Talk to them for help</a>.</p><p>The resources you save in <em>not considering</em> a full scale brand can be applied to getting your entire team focused on your customers’ needs and your near-term goals.</p><p><a href="http://youtu.be/3sF9URmpxyY">Now go CRUSH IT!</a></p><p>Love,<br>Andi</p><blockquote><strong><em>More about Andi:<br></em></strong><em>Andi Plantenberg is an innovation consultant who builds entrepreneurial capabilities in the enterprise. She&#39;s also a long-time mentor for startups in the Bay Area (500 startups, IndieBio, Singularity University).</em></blockquote><blockquote><em>The large companies that work with Andi are foreseeing disruption. They are looking to stand up innovation in their org to prepare for it. The smaller companies are seeking product / market fit through experimentation and validated learning.</em></blockquote><blockquote><em>Prior, Andi co-founded Singlebound Creative in 2000. The Product Studio / Digital Agency had an eleven year run and served Fortune 500 clients and visionary startups. In its later years, Singlebound partnered with VC firms to spin up new pilot ventures.</em></blockquote><blockquote><em>(</em><a href="http://twitter.com/andisf"><em>@andisf on twitter</em></a><em>)</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3db0cb9721c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/futuretight/branding-for-startups-3db0cb9721c7">Branding for Startups</a> was originally published in <a href="https://medium.com/futuretight">FutureTight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Approaches To Innovation That Fail]]></title>
            <link>https://medium.com/futuretight/3-approaches-to-innovation-that-fail-120c608b9574?source=rss----eb05853cc3ba---4</link>
            <guid isPermaLink="false">https://medium.com/p/120c608b9574</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[innovation-management]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[innovation-lab]]></category>
            <dc:creator><![CDATA[Andi Plantenberg]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 05:45:13 GMT</pubDate>
            <atom:updated>2018-02-07T05:43:01.712Z</atom:updated>
            <content:encoded><![CDATA[<p>Big companies all over the world are trying hard to act more like startups and often failing. I’ll share 3 common approaches that fall down. And then present what<strong><em> has</em></strong> been working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uoMnKr1VSjWQnd7GbhVCCg.png" /></figure><h3>1) The Acqui-hire</h3><p>The big company acquires a startup for their DNA. They hope the DNA will spread in their organization giving them an edge over the competition.</p><h4><strong>How it fails:</strong></h4><p>The special DNA that made the startup successful withers and dies as the team gets pulled into the org. Senior staff leave as soon as they vest.</p><h4><strong>Why?</strong></h4><p><em>Startups and big companies have a fundamental difference in their structures.</em></p><p><strong><em>Startups have a structure that supports adaptation and learning.</em></strong> Small groups of people with different expertise all work together—in areas of high uncertainty—toward an outcome. They can try lots of small things, learn what does and does not work before committing company resources. They take many shots at the same goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*iVV00QG3tWDRaeweEpSq5g.png" /><figcaption>Startup Team Structure</figcaption></figure><p><strong><em>Conversely, big companies are structured to deliver a well-known solution to a well-understood market. At scale. </em></strong>Their structure reflects that. They organize people in functional silos. People work with an eye towards fulfilling requirements. Gate-keepers ensure that everything goes according to plan.</p><p>When the startup team is pulled into the org, the the team is broken up. Everyone’s moved to the department that corresponds to their discipline .<strong><em>It’s not just the people that make innovation happen, it’s also a startup team structure. And that was dismantled in the acqui-hire.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*V6YtV7TxVY6oNVbGWQVv9g.png" /><figcaption>The Acqui-hire: Startup DNA dies when the startup team moves into the org</figcaption></figure><h3>2) The Innovation Lab</h3><p>The Innovation Lab runs outside the business structure. The lab is supposed to benefit from all the assets of the parent company — brand cachet, access to customers, marketing reach, etc. — but be protected from the bureaucracy.</p><h4><strong>How it fails:</strong></h4><p>The learning slows to a crawl. After a year the Innovation Lab is dismantled. Or the head of innovation is removed.</p><h4>Why?</h4><p>As soon as this innovation team needs to interface with the org, the learning stops. They hit a brick wall when they need brand approval, access to customers, or to schedule an email campaign.</p><p>For instance, imagine this lab team trying to put a super early version of a product in the hands of just 10 customers, so the team can learn. They will be routed to legal and compliance, raising all sorts of red flags. They will need to justify to many parties that they are only working with 10 people to learn early. But the parent org is optimized for delivery at scale, so the notion for doing anything for just 10 customers does not compute. If the lab team doesn’t have a sponsor or a business owner to intervene, they are stuck.</p><p>The upshot is this: <a href="https://medium.com/@andisf/the-role-of-the-executive-sponsor-in-enterprise-innovation-810396c345e4">the team is not able to learn without the support of the org</a>, so they end up with the same barriers as before. Only this time with impossible expectations.</p><p>Colleagues perceive the innovation lab as a <a href="https://medium.com/@andisf/the-role-of-the-executive-sponsor-in-enterprise-innovation-810396c345e4">special playground with lackadaisical standards</a>. This resentment hampers cooperation as the startup team goes outside normal processes. Colleagues see them as trying to take short-cuts, cut corners, or as ‘not-getting it’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Z7e7_rmXQo9acuNRReZ4g.png" /><figcaption>The Innovation Lab: Learning Stops</figcaption></figure><p>If people in the org <strong><em>do</em></strong> cooperate, the relative pace of the parent company is slow. So the team gets very few shots on goal.</p><p>And since they only get one shot, they end up doing and making complex things when they ought to be running quick experiments. They juice their predictions about their product idea to gain the support they need.<strong><em> Out of survival, they’ve aligned themselves to the pace and processes of the org.</em></strong></p><h3>3) The Startup-in-a-Box</h3><p>Some companies go to an outside firm that specializes in being a ‘Startup-in-a-Box’. Or they build their own team and put them completely off site with their own P&amp;L.</p><p>These teams are in the same situation as the the Innovation Lab. They can’t move fast <strong><em>and</em></strong> work with the org. The Startup-in-a-Box will run experiments entirely off-brand to get around this issue.</p><h4>How it fails:</h4><p>If they do find product-market fit (hooray!), the new business is destined to die once it’s taken over by the parent org (sigh).</p><h4>Why?</h4><p>The team may have found product-market fit. But moving the product into the ‘delivery-at-scale’ structure doesn’t work. It’s not yet a well-known solution being delivered to a well-understood market. Learning is still important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*vpkwjXFK1N4X5GG_Ey48ug.png" /><figcaption>Startup-in-a-Box: Successful products die in the org</figcaption></figure><h3>An Approach That Has Worked</h3><p><em>The good news:</em> There are big companies doing innovation work and growing an entrepreneurial capacity in their teams. <em>The bad news:</em> It’s not a turn-key solution, and it’s hard. It touches every function to build an entrepreneurial capability in a company.</p><p>But if you’re ready to give it a shot, this is how you begin. Start small and get some wins. That will lay the foundation for other structural changes down the road. Wins include unlocking new revenue streams. Wins also include killing of bad projects that will deliver no value to the company. This saves significant time, talent and money.</p><h4>Do these things:</h4><p><strong>A) Name your mission and create one startup team to follow it.<br></strong>You need a mission or an outcome that is meaningful for the business. Then assemble a team of 3 to 5 people from different departments, who all have a stake in that mission. The mission can be anything from “Speed up X internal process by 50%” to “Find a new revenue stream for connected kitchen appliances with millennials in China.”</p><p><strong>B) Let the startup team work together in the same physical space. Full time.<br></strong>Companies have a bad habit of creating part-time committees to do the work of a startup team. That’s a great way to have a plethora of meetings and email threads with no meaningful outcomes. This startup team needs permission to more or less work full time on a single mission.</p><p><strong>C) Train them to design and run good experiments.</strong> <a href="https://en.wikipedia.org/wiki/Validated_learning">Validated learning</a> is not rocket science. But for this to work, teach teams the basics of good experiment design. <a href="http://andiplantenberg.com/">A workshop or a few hours with a coach</a> will set them up to succeed.</p><p><strong>D) Limit funding and tie increases to learning goals.</strong> No entitlement funding of zombie projects. Give the team a small, secure budget. As the product and business ideas are validated, those ideas get additional funds. ‘Validation’ means an increased likelihood of success. Increased because we’ve been learning with a real (albeit small) set of customers.</p><p><strong>E) Keep the team safe.</strong> Keep the team but fire bad projects. If the team is exploring a product / business that we learn isn’t viable, pivot to a new one. If you are not clear about this up front, you will unwittingly plant bad incentives.</p><blockquote>I can’t stress this point enough. Teams will feel that in order to survive they must prove their ideas and plans are correct. This defeats the whole purpose.</blockquote><p>Validated learning can only happen if you dive headlong into discovering <strong><em>where</em></strong> your ideas and plans are wrong. And the team can’t do so if they fear losing their reputation or job.</p><p><strong>F) Provide executive air cover.</strong> Since the team will be working outside of normal business processes, they will need <a href="https://medium.com/@andisf/the-role-of-the-executive-sponsor-in-enterprise-innovation-810396c345e4">an executive sponsor.</a> This person creates exceptions for the team (air cover). The sponsor clears roadblocks when the learnings to be had exceed the risk of going outside normal process.</p><p>Socializing the wins will create excitement in other parts of the company and allow other small teams to ramp up. Learning how to do these things in your own company culture is the best way to get traction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=120c608b9574" width="1" height="1" alt=""><hr><p><a href="https://medium.com/futuretight/3-approaches-to-innovation-that-fail-120c608b9574">3 Approaches To Innovation That Fail</a> was originally published in <a href="https://medium.com/futuretight">FutureTight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimum & Viable not “Rough”]]></title>
            <link>https://medium.com/futuretight/minimum-viable-not-rough-52e4619092dc?source=rss----eb05853cc3ba---4</link>
            <guid isPermaLink="false">https://medium.com/p/52e4619092dc</guid>
            <dc:creator><![CDATA[Andi Plantenberg]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 05:44:01 GMT</pubDate>
            <atom:updated>2015-04-01T04:25:15.959Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlFKKQ9JJlVTtl87cjkUFQ.png" /></figure><h4><strong>What follows are the misconceptions I’ve encountered that have cost some colleagues dearly.</strong></h4><p><em>(Originally posted on </em><a href="http://bit.ly/18yo2Ks"><em>Neo.com</em></a><em>.)</em></p><p>I know CEOs, CMOs and Product VPs who’ve shied away from the idea of a Minimally Viable Product for fear they must sacrifice quality.</p><p>There is a misconception that Minimum Viable Product means un-polished, unfinished or generally half-assed. I’d like to clear this up. Too many focus on “Minimal”. Its “Viable” that’s the most essential in this pithy acronym.</p><blockquote>Sexism disclaimer: The people I’m about to talk about are real, and are all men (white ones). That’s simply a byproduct of the severely lopsided industry demographics.</blockquote><p>The CEO I refer to above — let’s call him Jay — had a solid track record in the tail end of the 1.0 bubble. Jay knew todays products must offer something new AND feel crazy good to use if it’s to differentiate. <em>“You can’t have a minimal approach to designing something that feels amazing.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VX69Wy3dezkLs4TT9N2XRQ.jpeg" /><figcaption>Artwork by @wakeupmrkim</figcaption></figure><p>Let’s call the CMO I mentioned Steve. Steve was afraid he’d end up with something that technically worked, but looked off. He knew compromising the brand in order to learn early was ill-advised. Falling short of a certain quality and flavor would not play with the prospective customer.<em> “An MVP will just look bad. I don’t buy the hype. We need to do this right.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6AVqAqc-yFhsMugWS2S9dQ.jpeg" /><figcaption>Artwork by @wakeupmrkim</figcaption></figure><p>The Product VP — let’s call him Albert — had a high level of confidence in his intuition about what users really need. He was in a startup, but his history lay in corporate, waterfall settings. Eager for a big win in his new role, he was focused on wowing his colleagues. He guessed at problems / solutions based solely on his own experience. And he conducted brainstorm sessions with his product team — nervous to show any work in progress or test assumptions in the real world. <em>“We don’t want the devs involved now, they’ve got no vision. We know what’s best.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CwKUbjEXCk0bfCc65uHVdA.jpeg" /><figcaption>Artwork by @wakeupmrkim</figcaption></figure><h3>Here’s what these guys were missing:</h3><h3>1) There is huge unseen risk</h3><h3>2) That can be fixed.</h3><h4><strong>1) Unseen Risk:</strong></h4><p>When you’re making anything of a certain complexity, there is a huge risk just getting it built on time within the budget you have. In fact, I’ve yet to see this ever done in my 20 yrs in the industry.</p><p><strong>Here’s what happened to Jay, the CEO. </strong>He had strong funding connections, industry cred, and a killer idea. He was sure the market wanted his product. He had a strong design esthetic and ‘quality is king’ perspective. Jay’s company built something slick, albeit incomplete, for pitching his investors. Jay closed funding to get something to the market. That ‘something’ was too big of a job for the cash on hand, so the scope was limited for him when money and time ran out. Jay put more pressure on the development team and they began leaving. He bit off more than could be delivered. Despite a nice PR splash and good write-ups, his product is now languishing because it’s weird and hard to use.</p><p><strong>Our CMO, Steve,</strong> was looking for product market fit. His risk was much lower. As a seasoned marketer, Steve was doing a <a href="http://www.allbusiness.com/barrons_dictionary/dictionary-dry-testing-4966246-1.html">dry test</a>. He measured reactions to a value proposition, which is great. But he’s not learning what the right solution is. Or what it will take to make it real.</p><p><strong>Albert, the Product VP,</strong> was at enormous risk. He invested in building out a solution to a problem he did not validate. The release date was delayed for reasons most build product releases are delayed. The devil’s in the details, and scope increases as you learn what’s really involved. When the product was released, it was less than anyone had hoped for and was out in the wild for a few months only. The investors lost faith in the company soon after.</p><h4>2) The Fix: Make something small first</h4><p>Minimum Viability is a way to get something <em>small </em>into the market to measure so the team may <em>learn before more time and money is invested</em>. It is a way to <strong>build smartly (</strong><a href="https://medium.com/design-process/branding-for-startups-3db0cb9721c7"><strong>and beautifully</strong></a><strong>), and de-risk as you move forward.</strong> Risk accumulates over time. Real world feedback is the mechanism to re-set this risk accumulation. That is why this is considered a best practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MyGIPH6_NzIk_o58uc-3Sg.jpeg" /><figcaption>Risk accumulates over time. Real world feedback is the mechanism to re-set this risk accumulation.</figcaption></figure><h4><strong>Viable = Valuable, Usable, Feasible</strong></h4><p>The “something small” you make must be your best shot at <em>Valuable, Usable and Feasible. </em><strong><em>Otherwise it is not viable. </em></strong>You’ve probably seen this handy venn diagram for making successful products…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iddMh1oe-jPtqXIj0o3rwg.jpeg" /></figure><p><strong><em>Valuable</em></strong>: Is this something people want? Are you solving a real problem?<br><strong><em>Usable: </em></strong>Can customers reach their goal? Does it feel lovely?<br><strong><em>Feasible: </em></strong>Can this be created with the time and money available?</p><p>You may not skimp on any of these. This means you need to nail what you bite off in all three categories to the best of your ability. <strong><em>But nail them for something small. </em></strong>Demonstrate each of these with real customers, before you build much at all. Having something that technically works but feels off-brand is not viable. Having something crazy valuable that feels amazing is not viable if it can’t be build on time and on budget.</p><p>Right off the bat, you need to demonstrate <strong><em>Value </em></strong>(or lack of it). This can be done quickly and easily without touching your brand <strong><em>(</em></strong><em>See Giff Constable’s </em><a href="http://www.talkingtohumans.com/">http://www.talkingtohumans.com/</a>).</p><p>Once you’ve demonstrated that your idea has value to others, ask yourself, “<em>What is the smallest possible thing I could make?</em>” You should be focused on reducing risk <em>without</em> compromising your brand values and your tenets. This is where <strong><em>Usable</em> </strong>and <strong><em>Feasible</em></strong> come together. You must demonstrate both early. Doing so requires working transparently in balanced, multi-disciplinary teams. Designers need feasibility input from developers. Developers need to understand the constraints. Both need mind share on the desired outcomes from the product owner.</p><h4>Outcomes &amp; Measures</h4><p>To de-risk as you move forward, you need to understand what <strong>outcomes</strong> you are looking for (<a href="http://igniteshow.com/videos/startup-metrics-pirates-aarrr">See Dave McClure’s Startup Metrics for Pirates</a>). Craft experiments so you may learn as quickly as possible how your product fairs in this lens. Now you are free to <strong>go make that small thing awesomely</strong>, and measure its use. And <em>then</em> build more<strong>.</strong></p><p>The three colleagues I mentioned at the outset would have had wildly different outcomes had they focused early on value, worked with a balanced team to devise an MVP, and then measured how outcomes are being achieved. Don’t be those guys. Be this person:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GuJBhKoFe2U-kB-XeomASQ.jpeg" /></figure><p><strong>Resources:</strong></p><p>Dave McClure: <a href="http://igniteshow.com/videos/startup-metrics-pirates-aarrr">Startup Metrics for Pirates: AARRR!</a><br>Giff Constable: <a href="http://www.talkingtohumans.com/">Talking to Humans</a><br>Jonathan Irwin: <a href="http://neo.com/2015/03/03/the-opportunity-sprint">Opportunity Sprints</a><br>Andi Plantenberg: <a href="http://neo.com/2014/07/25/rapid-design-for-personality-and-impact">Rapid Design for Personality and Impact</a><br>Andi Plantenberg: <a href="https://medium.com/design-process/branding-for-startups-3db0cb9721c7">Branding for startups</a></p><blockquote><strong>More about Andi: </strong>Andi has been working with fortune brands and visionary startups since the mid 1990&#39;s. In 2000 she co-founded a digital agency in San Francisco. It was in that 11-year role as chief creative where she realized small, interdisciplinary teams are able to create superior products in a fraction of the time. She continues that vision at <a href="http://www.neo.com/">Neo</a> as a Lead Product Designer.<br>(<a href="http://twitter.com/andisf">@andisf on twitter</a>)</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52e4619092dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/futuretight/minimum-viable-not-rough-52e4619092dc">Minimum &amp; Viable not “Rough”</a> was originally published in <a href="https://medium.com/futuretight">FutureTight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role of the Executive Sponsor in Enterprise Innovation]]></title>
            <link>https://medium.com/futuretight/the-role-of-the-executive-sponsor-in-enterprise-innovation-810396c345e4?source=rss----eb05853cc3ba---4</link>
            <guid isPermaLink="false">https://medium.com/p/810396c345e4</guid>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[executives]]></category>
            <category><![CDATA[lean-enterprise]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Andi Plantenberg]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 05:42:46 GMT</pubDate>
            <atom:updated>2018-09-01T05:41:07.852Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“If you’re part of a big organization’s innovation team, the Executive Sponsor is your fairy godmother.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LpNoZhppqZuM9txJYby0SA.jpeg" /><figcaption>Photo by <a href="https://www.flickr.com/people/dams999/">Dams999</a></figcaption></figure><p>Organizations across industries are setting up startup teams. They’re sometimes called innovation teams or skunkworks projects. Many of these teams are missing a critical piece of the puzzle: The Executive Sponsor.</p><p>If you’re part of a big organization’s innovation team, the Executive Sponsor is your fairy godmother. Most teams need to either find one, or train up the one they have. Here’s what they do, in a nutshell:</p><ol><li>Provide executive air cover</li><li>Hold the team accountable to learn what’s most important to learn</li></ol><h4>1) Executive Air Cover. It’s not about funding and aligning all the roadmaps.</h4><p>First, let’s talk about<strong><em> executive air cover</em></strong>. Think of this as helping make exceptions for your team’s unorthodox requests.</p><p>Companies over 20yrs old are set up to execute well at scale. The structures and processes within big companies hinder the pace of learning for startup teams. Your sponsor is there to help you. <strong>For instance, consider this scenario (based on true stories)…</strong></p><blockquote>A startup team within a durable goods company has a new product idea: A refrigerator that knows when your food is going to go bad, and then suggests new food items for your family. The team is charged with determining if this product idea is worth investing in. To do so, they need to learn a few things. Things like:</blockquote><blockquote>• Does anyone have pain around food going bad, or what to buy next?<br>• Are there enough people with this pain to sustain a business?<br>• Does our product idea actually solve that pain well enough?<br>• Can we get the distribution partners we need at the price point that works?</blockquote><p>To find out the answers to these questions, the startup team needs to work outside of normal channels and processes. The normal channels are designed for execution at scale, and are much too slow for answering questions like this. They’re optimized for throughput and focus on aspects other than what the startup team needs to learn. It’s the wrong tool for the job.<strong> Here is how that scenario is likely to play out (based on true stories)…</strong></p><blockquote>This startup team wants to see if people have a problem with food going bad and what food to buy next. If they can talk to a handful of prospective customers, they expect to see many of them have this problem. And if very few actually do have the problem, they will know right away not to invest in the idea as it is today. They feel 10 people will be enough for this important gut check.</blockquote><blockquote>Someone on the team recalls a focus group last month with people who would be great prospects. So the team reaches out to the marketing department to see if they can get some some names from last month’s focus group.</blockquote><blockquote>The marketing department sends them to the contact person for this sort of thing. And she promptly sends the team the form for setting up focus groups. After explaining to 3 people to no avail that they simply need 10 names, the team realizes it might actually be faster just to set up a new focus group!</blockquote><blockquote>So they begin the paperwork, and quickly discover that in order to set up a focus group, the team needs to have a product charter. To have a product charter, they need an approved idea that’s been vetted on certain success criteria (IP, price, performance, weight specifications). The team is now stuck after spending the better part of a week trying to get a handful of names!</blockquote><p>It’s easy to see how our startup teams can spend significant time explaining themselves. Explaining why you’re not crazy is the primary activity of teams attempting to innovate in enterprise. And this is exactly how many teams are undone. They are perceived as trying to take short-cuts, cut corners, or as just ‘not-getting it’. They are turning heads… and not in a good way.</p><blockquote>“Explaining why you’re not crazy is the primary activity of teams attempting to innovate in enterprise. And this is exactly how many teams are undone.”</blockquote><p><strong>Imagine if it played out this way instead (also based on true stories)…</strong></p><blockquote>When the startup team sees they’re expected to request a new focus group, they reach out to their Executive Sponsor right away.</blockquote><blockquote>The Executive Sponsor — well aware of the normal charter process — immediately sees the problem here. She picks up the phone and talks with the marketing manager to see if there’s any <strong>real</strong> problem with grabbing 10 names off of last month’s focus group list.</blockquote><blockquote>She explains “It’s not the way we normally do things, but we need to make an exception here to check our gut before going further.” And the marketing manager forwards a list of contacts to the team. They are on their way to learning something crucial about their product idea!</blockquote><p>Working by exception is a great way to start growing entrepreneurial capabilities within the org. Eventually, companies will need to support startup teams as a norm and not as an exception.</p><h4>2) Accountability. It’s not about making sure the product succeeds.</h4><p>Now let’s talk about <strong><em>accountability</em></strong>. Startup teams are charged with determining if a product or business idea is worth investing in. To accomplish that goal, they need to systematically learn what it will take for that product or business to succeed. This is called validated learning.</p><p>When startups refer to ‘running experiments’ they are talking about validated learning. Validated learning is the practice of gaining insights based on real evidence. Startups put an early product (MVP) in front of the customer and measure their actions in response to it. And then use that feedback to direct their product plans. That’s it. To be sure, many times the product plan becomes, “<em>Whoa, let’s not do this product at all.</em>” In fact, it’s essential to have a healthy kill-rate on your ideas.</p><p>Executive Sponsors need to be in the loop on what is most important to learn right now. And they absolutely need to hold teams accountable to learning those things. Sponsors and teams meet briefly and as often as needed to make pivot-or-persevere decisions based on validated learning.</p><p>Be aware of this common misconception: <br>Validated learning is <strong><em>not</em> </strong>about uncovering <strong><em>how </em></strong>to make the product succeed in the market. Because you can’t actually do that. As <a href="https://medium.com/@mulegirl">Erika Hall</a> tells us, “you don’t get to determine under which circumstances your product will succeed”. Rather, validated learning is about discovering <strong><em>if it can</em></strong> succeed under the existing market conditions. This is a simple but critical distinction.</p><blockquote>“You don’t get to determine under which circumstances your product will succeed” -<a href="https://medium.com/@mulegirl">Erika Hall</a></blockquote><p>The Executive Sponsor helps the startup team learn fast by providing executive air cover. And then holds them accountable to what they’ve learned. That’s how teams truly discover whether the product or business idea is worth investing in.</p><h4>Here’s what you need in an Executive Sponsor:</h4><ul><li>The Executive Sponsor is someone senior enough to clear roadblocks (and has the moral authority to do so), but not so senior that they cannot meet with the team.</li><li>The Executive Sponsor is someone who is in in touch with the mission of the team. That mission is something they care about and is linked to their business unit (hence the moral authority comment).</li><li>The Executive Sponsor must be willing gain a basic understanding of how validated learning works. Validated learning is simply making product and business decisions based on evidence.</li></ul><p>There are plenty of startup teams in large companies doing the work without an Executive Sponsor, and they are feeling the pain. These teams are doing very noble (and largely thankless) work. They do it because they believe in the company. And they want to get to value faster with less waste.</p><p>To those teams I say this: If there is someone in your organization that fits the above criteria, talk to them about working with you. <a href="https://twitter.com/andisf">And shoot me a note</a>. I’d like to help you find your fairy godmother.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=810396c345e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/futuretight/the-role-of-the-executive-sponsor-in-enterprise-innovation-810396c345e4">The Role of the Executive Sponsor in Enterprise Innovation</a> was originally published in <a href="https://medium.com/futuretight">FutureTight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>