<?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[Stories by Alex Cowan on Medium]]></title>
        <description><![CDATA[Stories by Alex Cowan on Medium]]></description>
        <link>https://medium.com/@cowanSF?source=rss-2ee8f7ed9907------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TSme8jcnmiwDJqni.jpeg</url>
            <title>Stories by Alex Cowan on Medium</title>
            <link>https://medium.com/@cowanSF?source=rss-2ee8f7ed9907------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:04:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cowanSF/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Innovating Backwards and Forwards]]></title>
            <link>https://medium.com/@cowanSF/innovating-backwards-and-forwards-93b56b7aa96b?source=rss-2ee8f7ed9907------2</link>
            <guid isPermaLink="false">https://medium.com/p/93b56b7aa96b</guid>
            <dc:creator><![CDATA[Alex Cowan]]></dc:creator>
            <pubDate>Mon, 06 Oct 2014 21:34:34 GMT</pubDate>
            <atom:updated>2014-10-06T21:34:34.084Z</atom:updated>
            <content:encoded><![CDATA[<p>Among other things, I’m an advisor to startup’s and ‘intrapreneurial’ ventures. I’m no sage, so what I can offer them is advice on where to focus and specifics on how to apply best practices.</p><p>I rarely have an advisee where I recommend a change in strategy. Most of them operate in specialty niches they know well and I know poorly or not at all.</p><p>Most of what we spend time on is processes to help them innovate faster. One way to look at those processes is in terms of moving backwards and forwards with regard to the core concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Q9jmJ5SHvFTgeyOw2_kmAA.png" /></figure><h2>Innovating Backwards</h2><p>How do you relate your activities back to advancement of your core value proposition? How do you know that what you’re doing on an hour-by-hour basis actually matters?</p><p>Most of this work has to do with making the core concept itself more explicit and then structuring the work related to its advancement as experiments with explicit assumptions, methods, time periods, and success/failure criteria.</p><p>Let’s say you’re looking to sell something to mom’s through your website. A normal set of things to do might be to update the site and then to run some ad’s to try to generate sales on the site. There’s nothing wrong with that, but how will you know if it’s working or if you should try something else?</p><p>It’s important to have specific assumptions on what you think those changes and those ad’s are going to deliver, and an experimental design with metrics that describes how you’ll know if you’re changes are passing or failing your success criteria.</p><p>I’ll be honest: emotionally, it’s kind of boring to keep track of all your work as experiments. It’s way more interesting to just make the changes, place the ad’s and then hope that this roll of the dice delivers something amazing.</p><p>The issue is that’s just creating output that way is not a reliable or effective way to build a business, product, or even a tactical initiative. The tortoise that plods along with explicit success criteria and new approaches to ‘failed’ experiments will almost always beat the hare that hops around whimsically trying things.</p><h2>Innovating Forwards</h2><p>How have we established the relevance of this idea for our buyer? What is our explicit view of who that buyer (or buyers) really is, what makes them tick, and what problem we’re solving for them? In most cases, we don’t go deep enough.</p><p>More investment in persona development and needfinding is well worth the investment. It can help us focus, eliminate wasteful efforts, and focus and interpret our experiments when we’re innovating ‘backwards’.</p><h2>More?</h2><p>For more on how to do this, please see the <a href="http://www.alexandercowan.com/venture-design/">Venture Design</a> landing page.</p><p>If you’re in the SF Bay Area, I’m teaching a related class at General Assembly staring in October: ‘<a href="https://generalassemb.ly/education/innovating-in-the-enterprise-sf-bay-area/san-francisco/7822">Innovating in the Enterprise</a>‘.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93b56b7aa96b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Things You Can Do To Be More Innovative]]></title>
            <link>https://medium.com/@cowanSF/8-things-you-can-do-to-be-more-innovative-75ab87a95867?source=rss-2ee8f7ed9907------2</link>
            <guid isPermaLink="false">https://medium.com/p/75ab87a95867</guid>
            <dc:creator><![CDATA[Alex Cowan]]></dc:creator>
            <pubDate>Sun, 21 Sep 2014 21:03:43 GMT</pubDate>
            <atom:updated>2014-10-06T21:28:31.404Z</atom:updated>
            <content:encoded><![CDATA[<p>Innovation: everybody wants some! Below are 8 practical tips anyone can apply.</p><p>These ideas are meant to propel the kind of actionable learning the drives innovation.</p><h2>1. Start with the Individual</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*Ucl7xDk17z4eUt3YA5X7Iw.png" /></figure><p>When I hear ‘our market is males 25–35′ I can’t see how that leads to innovation. When I hear that, I think ‘I’m worried for you’. I worry competitors are going to re-segment their market, deliver something more relevant to their sub-segments, and dismantle their business piece by piece.</p><p>Creating prescriptive, actionable learning based on observing the individual has always been central to design research and the practice of needfinding. Product inspiration comes from relatable experiences and those start with the individuals.</p><p>I recommend anchoring your understanding of the customer with personas and then attaching trios of a) problem scenarios b) alternatives and c) value propositions to drive to insights that are vivid, actionable, and testable. For more on that, see the <a href="http://www.alexandercowan.com/tutorial-personas-problem-scenarios-user-stories/">Personas tutorial</a>.</p><h2>2. Anchor to Problems, Not Solutions</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*kEjXvci7Y6-cRoAZPA647A.jpeg" /></figure><p>Like it or not, it’s in our nature to get an idea, fall in love with it, run off and build it, then hope our audience/market loves it. It’s OK- don’t feel bad about it.</p><p>But try not to do it. When we instead spend the time to understand customer problems and test our ideas against that understanding, we’re much more likely to succeed. Problems, whether they’re jobs at a business or the needs of an individual, rarely change. Solutions change all the time- every single one is temporary.</p><p>For more on structuring your ideas against problem scenarios, see the <a href="http://www.alexandercowan.com/tutorial-personas-problem-scenarios-user-stories/#Needfinding_with_Personas">Needfinding section</a> of the Personas tutorial above.</p><h2>3. Become a Better Storyteller</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*UCrT9CxvP3meequFHeubsQ.png" /></figure><p>If you hear innovators like Jack Dorsey (Twitter, Square) talk about their process, you’ll often hear them mention how they’ve become a better storyteller. It turns out this simple skill that we learn as children and then (generally) unlearn in our subsequent education is a great way to propel innovation.</p><p>Storytelling is an effective way to evaluate a hypothetical future where your new idea has achieved relevance in terms that are vivid, actionable and even testable.</p><p>One tool I like is storyboarding. It trains you to be a good storyteller, creating narratives that are sequential and visual. For more on this, I recommend the<a href="http://www.alexandercowan.com/calendar/storyboarding-workshop/">Storyboarding Workshop</a>.</p><h2>4. Circulate Ideas</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*t858N-fiolOC4cH39uFPuA.jpeg" /></figure><p>Even really strong product ideas have something like a 1/20 chance of succeeding, so for consistently successful innovation you need a healthy flow of new ideas. Doing this is harder than it sounds.</p><p>Our emotional wiring makes us want to compel others to our ideas and actions. When others don’t like our ideas we feel hurt, anxious. Back when we were cavemen, I guess that was an adaptive trait. But our mental wiring changes over the millennia while our operating environment changes decade to decade.</p><p>The general rubric of ‘design thinking’ offers tools that help us discipline our emotional nature to be more effective collaborators and hence innovators. For this, I recommend the material here on<a href="http://www.alexandercowan.com/learn/product-design/">Design Thinking</a>.</p><h2>5. Test Early, Test Often</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*x_OZ-ThYhCcTaXXOatveaQ.jpeg" /></figure><p>Innovation is a high risk sport on an idea by idea basis, but you can dramatically increase the quality and reliability of your outcomes in the way you manage new concepts.</p><p>Creating structured ideas and then figuring out creative ways to test them is central to lean and the Lean Startup movement, not to mention the scientific method itself. And it turns out it’s a great way to innovative, even if you’re short on resources.</p><p>For more on this, I recommend the material here in <a href="http://www.alexandercowan.com/creating-a-lean-startup-style-assumption-set/">Lean Startup</a>.</p><h2>6. Learn First, Scale Second</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*XKsNkxgmIY7iX26ZKPXw2Q.jpeg" /></figure><p>It’s hard to find anyone that disagrees with the importance of learning, but it’s also hard to find people that actually put it first, even in a situation where innovation is important. Why? I think there are two main reasons.</p><p>First, how do you feel when you cross something off your to-do list? Awesome, right? Me, too. How would you feel if you had to put it back on that list 5, 6, 7 times? That’s why it’s hard. When you test (well), you’ll likely find you need to revise. That’s the best way to innovate but it’s emotionally daunting.</p><p>Second, most of what we learn about ‘business’ and hold to be the well-established truth is based on scaling existing businesses in relatively static markets. These techniques were good in the 20th century, but bad in the innovative, globalized, hyper-competitive 21st century.</p><p>The <a href="http://www.alexandercowan.com/creating-a-lean-startup-style-assumption-set/">Lean Startup</a> material is a good introduction to this as is the workshop <a href="http://www.alexandercowan.com/workshops/venture-design-ii-iterating-success/">Venture Design II: Iterating to Success</a>.</p><h2>7. Kill Zombie Ideas</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*z-Fs33H2B5qIHbjnYV7n2w.jpeg" /></figure><p>In a successful innovation program, you have a lot of turnover in ideas. The reverse is also true. Lots of typical corporate patterns squelch innovation: getting married to solutions (vs. problems), having solutions looking for problems, the sunk cost fallacy.</p><p>Most ideas fail because either a) they weren’t well anchored in the reality of the customer/user or b) they just weren’t meant to be. Items 1–3 will help you better anchor your ideas and items 4–6 will you separate the wheat from the chaff.</p><h2>8. Get Out There a Lot</h2><p>Innovation is a contact sport. No one learns these skills just be reading material. I recommend finding as many places as you can to practice and see what works where.</p><p>Fun fact: the human eye is completely depending on constant motion and seeing the differences between things. Even if you’re staring at something your eye is probably moving. If you are actually able to still your eye to a single point, your field of vision fades away completely. Innovation’s like that.</p><h2>More?</h2><p>If you’re in the SF Bay Area, in teaching a workshop series, ‘<a href="https://generalassemb.ly/education/innovating-in-the-enterprise-sf-bay-area/san-francisco/7822">Innovating in the Enterprise</a>’ at General Assembly starting this October.</p><p>For general info. on how to get started with some of these things, you may like the <a href="http://www.alexandercowan.com/venture-design/">Venture Design Resource Page</a>.</p><p>IMAGE CREDITS<br><em>Tire Change: By Kabelleger / David Gubler (http://www.bahnbilder.ch) [CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0) or GFDL (http://www.gnu.org/copyleft/fdl.html)], via Wikimedia Commons<br>Recycling Bin: By My Alchemist (Own work) [CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons<br>Scientist: By John Crawford (Photographer) [Public domain or Public domain], via Wikimedia Commons<br>Birdwatchers: By vastateparksstaff [CC-BY-2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons<br>Zombie: By Martin SoulStealer from London, England (Long Time Dead) [CC-BY-2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75ab87a95867" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things Every Product Manager Should Know About Agile]]></title>
            <link>https://medium.com/@cowanSF/3-things-every-product-manager-should-know-about-agile-10fafad20f5d?source=rss-2ee8f7ed9907------2</link>
            <guid isPermaLink="false">https://medium.com/p/10fafad20f5d</guid>
            <dc:creator><![CDATA[Alex Cowan]]></dc:creator>
            <pubDate>Wed, 06 Aug 2014 22:44:33 GMT</pubDate>
            <atom:updated>2014-08-06T22:44:33.302Z</atom:updated>
            <content:encoded><![CDATA[<p>You’re a card-carrying product manager or it’s part of your role because, hey, you’re just that kind of person. You’re interested in seeing things from different perspectives and tying them together to make something awesome.</p><p>Good on you for that, and you’re probably familiar with agile, a set of techniques that take ‘user stories’ as the primary input and produce working software in small, incremental, success-based iterations.</p><p>As much as its contributed to popular frameworks like Lean Startup, much of agile’s actual practice has been ‘captured’ by exactly the kind of orthodoxy and ordained expertise it set out to replace.</p><p>That a pity, but in principle easily fixed. The fundamentals of agile are easy to understand and apply, and they dovetail really well with popular concepts you may already be using like design thinking and Lean Startup. Here are 3 things I think every product manager should know.</p><h2>#1: THE FUNDAMENTALS</h2><p>Fun fact: agile was introduced in 2001 as a set of very simple ideas about how to improve product development. It’s ‘manifesto’ is only 68 words long and the meat of it is that:</p><blockquote><strong>Individual Interactions &gt; </strong>Processes &amp; Tools</blockquote><blockquote><strong>Working Software &gt; </strong>Comprehensive Documentation</blockquote><blockquote><strong>Customer Collaboration &gt; </strong>Contract Negotiation</blockquote><blockquote><strong>Responding to Change &gt; </strong>Following a Plan</blockquote><h2>#2: STORIES ARE NOT SPEC’S</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*p_iyl7os9NpIRIl0uwR-TA.png" /><figcaption>Agile Stories in Brief</figcaption></figure><p>Agile’s primary input is ‘<a href="http://www.alexandercowan.com/best-agile-user-story/">user stories</a>’ which have this syntax:</p><p>As a [persona],</p><p>I want to [do something]</p><p>so that I can [derive a benefit]</p><p>Epic stories, which are more general, have child stories within them for more detail. Against these stories you write test cases to articulate additional points around the story.</p><p>You take these stories and sort them in priority order and work through a set of them in a given iteration (usually 2–4 weeks).</p><p>Here’s the trick: <strong>stories are not meant to be used as a new way to write specifications or designs</strong>, a new format for the same old process of product management handing spec’s to engineering and engineering handing back product. <strong>They’re part of a different process altogether</strong>. The idea is that the author of the stories has frequent, meaningful discussions with the product developer. The stories are just supposed to anchor those discussions.</p><h2>#3: THINGS HAVE CHANGED SINCE 2001</h2><p>Since 2001, product cycles have gotten shorter, software (relatively) easier to build and distribute, and the amount of choice and information available to users has exploded.</p><p>All this has increased the relative importance of figuring out what to build relative to building. As a product person today, it’s extremely important to have an acute understanding of who you’re selling to and what they want <em>before</em> you start building stuff.</p><p>Getting there in a systematic way is the subject of my little box of tricks, called <a href="http://www.alexandercowan.com/venture-design/">Venture Design</a>. The diagrams below summarize this process (forward and reverse), including the role of agile’s ‘user stories’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*2t4Mf3go2-jTGgxsnD_XfA.png" /><figcaption>The Venture Design process- backward</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*n8fdiBqKUViiQGoOApLNOg.png" /><figcaption>The Venture Design process- backward</figcaption></figure><p>As you can see, they fit into a modern approach to product quite nicely. What may not be obvious from the summary is how well they dovetail with today’s best practices and how you can use that to generate easy wins for yourself.</p><p>If that interest you, here are 3 tricks that will enhance your introduction of agile or supercharge your existing practice of it.</p><h2>Trick #1: <strong>Stop Writing “Requirements”</strong></h2><p>The whole notion of requirements invites a formalism and permanence to product development that it doesn’t need or want. Try <a href="http://www.alexandercowan.com/best-agile-user-story/">user stories</a> instead. If you’re obliged to write requirements, try them as a supplemental measure in key places.</p><p>I think what you’ll find is that they do a much better job of helping you think through the experience that you want the user to have and describing that to your collaborators in development.</p><h2>Trick #2: <strong>Use Design Thinking to Write Great User Stories</strong></h2><p>If/when you find yourself writing stories, try linking them back to <a href="http://www.alexandercowan.com/tutorial-personas-problem-scenarios-user-stories/">personas, problem scenarios, and value propositions</a> as you see in the diagram above. The practice of design thinking is about asking yourself if you really understand what makes your user (and/or buyer) tick.</p><p>See also: ‘<a href="http://www.alexandercowan.com/exit-flatsville-using-storyboards-energize-agile-user-stories/">Exit Flatsville: Using Storyboards to Energize Your Agile User Stories</a>’.</p><h2><strong>Trick # 3: Manage Uncertainty with Lean/Startup &amp; Small Batches</strong></h2><p>Have you spent more time that you’d like going back and forth with others about what to build and why? <a href="http://www.alexandercowan.com/creating-a-lean-startup-style-assumption-set/">Lean Startup</a> is a great tool here and builds, plus links to the practice of agile. One of its core tenets is the idea of articulating your key assumptions and then figuring out how you can quickly and inexpensively prove or disprove them.</p><p>Every perspective about what should be done rests on assumptions. Get those on the table, link them to your stories with validation criteria and you’re experimenting vs. arguing. The use of short cycle iterations in agile complements this in that you get your answers quickly.</p><p>Most of these should flow pretty naturally into your regular activities. If you’re an individual contributor, my advice is to try these out in a low profile fashion, proving to yourself and then (probably more gradually) to others that they’re effective.</p><h2>More?</h2><p>If you’re interested in how tools like design thinking, Lean Startup, customer development and the Business Model Canvas fit into best practice development using agile, you might want to check out my ‘<a href="http://www.alexandercowan.com/venture-design/">Venture Design’ page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10fafad20f5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Essential Skills for the Full Stack Product Person]]></title>
            <link>https://medium.com/@cowanSF/7-essential-skills-for-the-full-stack-product-person-dda68fbba5df?source=rss-2ee8f7ed9907------2</link>
            <guid isPermaLink="false">https://medium.com/p/dda68fbba5df</guid>
            <dc:creator><![CDATA[Alex Cowan]]></dc:creator>
            <pubDate>Tue, 27 May 2014 04:35:13 GMT</pubDate>
            <atom:updated>2014-05-27T04:35:13.061Z</atom:updated>
            <content:encoded><![CDATA[<h4>Becoming Super Effective</h4><p>I’m always pushing myself to be the best possible product person I can be, and these days I tend to earn a lot through my work as an instructor. My classes are on the interdisciplinary topics of product design and venture creation, so I get to work with business people wanting to understand the technical side and engineers wanting to learn the business side.</p><p>Often times, students from the business side are thinking of learning to code and students from the engineering side are thinking of going to get an MBA. While both might be advisable in certain situations, I’ve found that there are a few simple foundation skills that drive the interdisciplinary cooperation at the heart of so many successful projects:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdE0MNLCz_tcbskQ6qSu9A.jpeg" /></figure><p>I think that since none of us want to look stupid, we spend too much time trying to out-expert others. Instead, we’d be better off learning how to frame and ask each other the right questions.</p><p>Here are some notes on foundation skills that I think will help you ask those questions and drive the right kind of discussions.</p><h3>Foundation Concepts</h3><h4>1 DESIGN THINKING</h4><pre><strong>Answers the question:</strong> “Who are we doing this for and do we know what makes them tick?”</pre><pre><strong>Good for:</strong> Focusing your efforts on an actionable, testable view of the customer.Creating a robust interdisciplinary tool set you can use across product development and promotion (sales, marketing, etc.).</pre><h4>2 LEAN</h4><pre><strong>Answers the question:</strong> “How do we figure out if this is going to be a hit before we waste a lot of time and money?”</pre><pre><strong>Good for:</strong> Balancing the uncertainty of a new venture with the structure you need to stay focused on the right things. Avoiding waste. Learning quickly.</pre><h4>3 CUSTOMER DISCOVERY</h4><pre><strong>Answers the question:</strong> “How do we create an actionable understanding of our customer, one that we can use to build the right product and promote it efficiently?”</pre><pre><strong>Good for:</strong> Finding out what really makes your customer tick vs. ticking them off.</pre><h4>4 AGILE</h4><pre>Answers the question: “Where’s everyone at and are we progressing to our objective?”</pre><pre>Good for: Creating inputs to product development and promotion that link back to your work in design thinking and customer discovery.</pre><p>In my experience, these tools will help you and your team steer away from distracting tangents and stay focused on what will really help your project succeed. Product and business education is realigning around new practices and ideas, the above being some of the most important. You can see this happening with the emergence of new terms like “growth hacker” and the growth of interdisciplinary programs like a “design MBA.”</p><p>As far as an introduction to these topics, there are a lot of great resources online, but it’s a bit of a “choose your own adventure” situation at the moment. The last section here lists a few resources from this site.</p><p>If you don’t have a coding/technical background, here are three foundation topics that will give you a useful starting point for engaging with technical folks.</p><h3>Technical Literacy</h3><h4>5 Model-View-Controller</h4><pre>Answers the question: “What area of the development program is this, what’s important about it, and how does it fit in with everything else?”</pre><pre>Good for: Decomposing the complexity of software development (into three different areas, anyway) and thinking about the kind of questions that might make sense.</pre><h4>6 APP &amp; PLATFORM INTEGRATION</h4><pre>Answers the question: “What exactly are we building and how does it fit in with the rest of our ecosystem/operating environment?”</pre><pre>Good for: Understanding the different chunks of your extended product and the general implications of different approaches to building your application.</pre><h4>7 ROLES &amp; SYSTEMS IN A TECHNICAL TEAM</h4><pre>Answers the question: “What’s the difference between a UI designer vs. developer vs. QA vs. sysadmin vs. devops?”</pre><pre>Good for: Understanding what everyone does and the different types of talent you need to get where you want to be.</pre><p>I would never discourage anyone from learning to code. Even a few hours invested in learning the basics will earn you perspective and useful skills. That said, there’s a lot of intangible learning and judgement that an experienced developer brings to their work.</p><p>That’s why it’s a good idea to balance an understanding of coding with a general perspective on what your project’s looking to accomplish, framed in a way that lends itself to constructive interdisciplinary discussions.</p><h3>Resources</h3><p>There are a lot of great ways to learn these skills and, generally speaking, more is more — these aren’t exact sciences so the more perspective you can get, the better.</p><h4>General</h4><ul><li>If you’re in the SF Bay Area, I’m doing a free info session at General Assembly- ‘<a href="https://generalassemb.ly/education/the-full-stack-product-person/san-francisco/5714?km_cwe_instance_id=5714&amp;km_metro=san-francisco&amp;utm_campaign=social_guest&amp;utm_content=2014-05-19+full-stack-cowan&amp;utm_medium=ga_blog&amp;utm_source=blog_post">The Full Stack Product Person</a>‘ from 7-9PM on Thursday May 29th</li><li>I teach a ‘<a href="https://generalassemb.ly/education/developing-new-products-creating-new-businesses/san-francisco/5733?km_cwe_instance_id=5733&amp;km_metro=san-francisco&amp;utm_campaign=social_guest&amp;utm_content=2014-05-19+full-stack-cowan&amp;utm_medium=ga_blog&amp;utm_source=blog_post">Venture Design’ class</a> at GA SF</li><li>I offer a <a href="http://www.alexandercowan.com/learn/">Venture Design and product design curriculum</a> online</li></ul><h4>Design Thinking</h4><p>Short &amp; tactical:</p><ul><li><a href="http://www.alexandercowan.com/tutorial-personas-problem-scenarios-user-stories/">Tutorial on the use of personas &amp; problem scenarios</a></li><li><a href="http://www.alexandercowan.com/workshop-storyboarding/">Workshop on storyboarding</a></li><li><a href="http://dschool.stanford.edu/dgift/">‘Virtual Crash Course in Design Thinking’</a> (Stanford d.school)</li><li>‘<a href="https://dschool.stanford.edu/groups/designresources/wiki/4dbb2/The_Wallet_Project.html">Wallet Project’</a> exercise (Stanford d.school)</li></ul><p>Extended &amp; strategic:</p><ul><li>‘<a href="http://www.amazon.com/Design-Everyday-Things-Revised-Expanded-ebook/dp/B00E257T6C/ref=sr_1_1?ie=UTF8&amp;qid=1400268423&amp;sr=8-1&amp;keywords=the+design+of+everyday+things">The Design of Everyday Things</a>’ by Donald Norman</li><li>‘<a href="http://www.amazon.com/Visual-Explanations-Quantities-Evidence-Narrative/dp/0961392126/ref=sr_1_1?ie=UTF8&amp;qid=1400268463&amp;sr=8-1&amp;keywords=visual+explanations">Visual Explanations</a>’ by Edward Tufte</li></ul><h4>Lean/Startup</h4><p>Short &amp; tactical:</p><ul><li>Tutorial: <a href="http://www.alexandercowan.com/creating-a-lean-startup-style-assumption-set/">Your Lean Startup</a></li><li>‘<a href="http://hbr.org/2013/05/why-the-lean-start-up-changes-everything/ar/1">Why the Lean Startup Changes Everything</a>’ (HBR)</li><li>‘<a href="http://www.alexandercowan.com/calendar/lean-startup-circle-san-francisco-b2b-hacks-getting-from-consulting-scalable-products/">B2B Hacks — Getting from Consulting to Scalable Products</a>’</li></ul><p>Extended &amp; strategic:</p><ul><li>‘<a href="http://www.amazon.com/Lean-Startup-Innovation-Successful-Businesses-ebook/dp/B004J4XGN6/ref=sr_1_1?ie=UTF8&amp;qid=1400268892&amp;sr=8-1&amp;keywords=the+lean+startup">The Lean Startup</a>’ by Eric Ries</li></ul><h4>Customer Discovery</h4><p>Short &amp; tactical:</p><ul><li><a href="http://www.alexandercowan.com/online-workshop-day-life-exercise/">Day in the Life Exercise</a></li><li>(see above items from d.school)</li><li><a href="http://www.entrepreneurship.org/en/Founders-School/The-Lean-Approach.aspx">Steve Blank lectures for Kauffman Foundation</a></li></ul><p>Extended &amp; strategic:</p><ul><li>‘<a href="http://www.amazon.com/Startup-Owners-Manual-Step---Step-ebook/dp/B009UMTMKS/ref=sr_1_1?ie=UTF8&amp;qid=1400269137&amp;sr=8-1&amp;keywords=the+startup+owners+manual">The Startup Owner’s Manual</a>’ by Steve Blank and Bob Dorf</li></ul><h4>Agile</h4><p>Short &amp; tactical:</p><ul><li><a href="http://www.alexandercowan.com/best-agile-user-story/">Your Best Agile User Story</a></li></ul><p>Extended &amp; strategic:</p><ul><li>‘<a href="http://www.amazon.com/Agile-Excellence-Product-Managers-Development/dp/160773074X">Agile Excellence for Product Managers</a>’ by Greg Cohen</li></ul><h4>Model-View-Controller</h4><p>Short &amp; tactical:</p><ul><li><a href="http://www.alexandercowan.com/mvc-model-view-controller-overview/">Tutorial: Model-View-Controller</a></li></ul><h4>App. &amp; Platform Integration</h4><p>Extended &amp; strategic:</p><ul><li>Chapter 4 of ‘<a href="http://www.amazon.com/Starting-Tech-Business-Practical-Applications/dp/1118205553">Starting a Tech Business</a>’ by Alex Cowan</li></ul><h4>Roles &amp; Systems in a Technical Team</h4><p>Extended &amp; strategic:</p><ul><li>Chapter 5 of ‘<a href="http://www.amazon.com/Starting-Tech-Business-Practical-Applications/dp/1118205553">Starting a Tech Business</a>’ by Alex Cowan</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dda68fbba5df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exit Flatsville]]></title>
            <link>https://medium.com/@cowanSF/exit-flatsville-8b073ea47d97?source=rss-2ee8f7ed9907------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b073ea47d97</guid>
            <dc:creator><![CDATA[Alex Cowan]]></dc:creator>
            <pubDate>Thu, 22 May 2014 01:43:55 GMT</pubDate>
            <atom:updated>2014-05-22T01:43:55.341Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using Storyboards to Energize Your Agile User Stories</h4><p>If you don’t think through the experience you want customers to have, who will? If you have to make a few guesses along that way, that’s OK. Being right isn’t as important as being explicit and making your ideas testable. Neglect your imaging of the customer experience, and you’re leaving your success to chance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*D0_ILz2rgJh2PzQWjJsrig.png" /><figcaption>anatomy of an agile user story</figcaption></figure><p>Agile user stories are a great solution to this problem. Always popular in software engineering, I’m increasingly seeing companies use them for projects in other areas, like marketing. That said, agile stories are not a silver bullet. They encourage good storytelling but don’t guarantee it. Supplementing your major storyboards will help you avoid arbitrary stories, disconnected from (even hypothetical) customer realities.</p><h3>Quick Review of Agile User Stories</h3><p>(Freely skip this section if you know stories up and down.) First off, agile user stories have this format:<br><em>“As a [persona],</em><br><em>I want to [do something]</em><br><em>so that I can [derive a benefit]“</em></p><p>Second, to help stay organized and coherent, stories are often nested within ‘epic stories’. If you’re new to product development, you’ll probably find yourself writing stories that turn out to be epic stories as you get into their particulars. Finally, ‘test cases’ are a good way to layer additional detail against your stories. (see <a href="http://www.alexandercowan.com/best-agile-user-story/#Example_Agile_User_Stories">agile user story examples</a> for more).</p><p>Storyboard are a great way to humanize and describe epic stories:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a1UueaqQ_xhUKB-QEW8I9Q.png" /></figure><h3>Extracting User Stories out of An Epic</h3><p>The story above an epic story, meaning it had multiple sub-stories within it to flesh out the details. You may find a table helpful for unpacking the detail you’re narrating with your epic storyboard. Here’s an example for the epic story above. This epic assumes Frank and his company have already successfully onboarded with Enable Quiz, using it for screening new recruits.</p><h4>Panel 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*3tAbayOy_HSIGD6BPrw4gw.png" /></figure><p>This epic assumes Frank and his company have already successfully onboarded with Enable Quiz, using it for screening new recruits.Frank’s first goal is to set up a quiz to complete a skills audit for his team. He has the employees he wants and it’s part of his job to help them make time to develop a holistic skill set.This first step covers these two stories:<br>A) “As a functional manager, I want to browse the quiz banks [of available questions] so I can make sure I’m subscribed to all the necessary topics for my skills audit.”B) “As a manager, I want to purchase additional quiz banks so I can add additional technical topics to me quizzes.”</p><h4>Panel 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*XE6cJ-LHBqSpdNRFRDWucw.png" /></figure><p>Frank has some topics specific to their internal products, processes and technologies that he’d like to use for his internal staff. After that, he’s ready to send the quiz. This panels deals with the following two stories:C) “As a manager, I want to create a custom quiz banks so I can add my own questions to the quiz.”</p><p>D) “As a manager, I want to create a quiz so I can use it with my staff.”</p><h4>Panel 3</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*kHcAb_zB2OT1ufQ4wTGMPQ.png" /></figure><p>Now Frank has to get all his staff into the systems so they can get invitations and their individual results tracked. He might want to do this in bulk and/or on a one by one basis.E) “As a manager, I want to create a list of students [employees] from an Excel file so I can invite them to take the quiz.”F) “As a manager I want to create a list of students [employees] online.”</p><p>G) “As a manager, I want to invite a set of students [employees] to take the quiz so I can see their scores.”</p><h4>Panel 4</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*6Tu-YvbE8Ie6ZjLTVsp6xw.png" /></figure><p>Now the employees/students come into play. They need to get a notice that Frank can customize where he communicates what this is about and when he’d like to have them finish the quiz. Suggestions show him how to communicate that the purpose of the quiz is creation of tailored professional development/training vs. micromanagement/big brothering.H) “As a student, I’d like to understand the objectives and content of the quiz as well as when I need to do it by so I can understand and prioritize it.”</p><h4>Panel 5</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*3y5QsqBCkNrzci7Arp-eHg.png" /></figure><p>People get busy, etc. Frank needs to see who’s finished vs. not so he can send automated and/or human reminders to finish up the quiz.I) “As a manager, I want to see which students have completed the quiz and which have not so I can send them a reminder.”</p><h4>Panel 6</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*ZUGsjADvtoPwIlFiatyUNQ.png" /></figure><p>Now he has his result. The objective was to tailor training programs for his team so they’re able to broaden their skill sets in the context of their business schedule.J) “As a manager, I want to see how the students scored on the test so I can put in place a skills improvement program.”</p><h3>Why user stories? Storyboards?</h3><p>Here are a few more reasons I like the user of stories:</p><ol><li>They dovetail with design thinking outputs like <a href="http://www.alexandercowan.com/tutorial-personas-problem-scenarios-user-stories/">personas, problem scenarios and value propositions</a>.</li><li>They are highly consumable by developers, designers, and other creators who are helping you execute, balancing structure and description; specificity and objectives.</li><li>They’re robust and ‘nestable’, scalable even for large, complicated projects.</li></ol><p>Storyboards are a great way to keep agile user stories from mimicking the dull, context-free requirements definitions they were meant to replace. They help avoid myopia, making sure you’ve thought through the whole story. They’re also a great way to engage your audience.</p><p>If you’d like more on storyboards, I have a post here on using them for <a href="http://www.alexandercowan.com/using-storyboards-to-animate-customer-discovery/">Customer Discovery/Development</a> and another on using them for thinking about <a href="http://www.alexandercowan.com/animating-user-acquisition-with-storyboards-in-6-steps/">User Acquisition &amp; Lifecycle</a>.</p><h3>Your Turn</h3><p>What have you tried to improve the quality of your agile user stories? What worked? Didn’t? Have you tried storyboards? Would you? Post a comment, respond on <a href="https://twitter.com/cowanSF">Twitter</a>, drop me a line, post on LinkedIn- we’re in this together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b073ea47d97" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>