<?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 kerry oconnor on Medium]]></title>
        <description><![CDATA[Stories by kerry oconnor on Medium]]></description>
        <link>https://medium.com/@kerry-oconnor?source=rss-e13574cc505f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*n1YUaQ3MCV75pQlcvbYEqg@2x.jpeg</url>
            <title>Stories by kerry oconnor on Medium</title>
            <link>https://medium.com/@kerry-oconnor?source=rss-e13574cc505f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 15 Nov 2026 14:48:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kerry-oconnor/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[Zig, Then Zag: When to Use Design Thinking and When to Use Lean Startup Approach]]></title>
            <link>https://medium.com/swlh/zig-then-zag-when-to-use-design-thinking-and-when-to-use-lean-startup-approach-ab3d90533ecc?source=rss-e13574cc505f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab3d90533ecc</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[kerry oconnor]]></dc:creator>
            <pubDate>Mon, 30 Nov 2020 17:04:10 GMT</pubDate>
            <atom:updated>2020-12-02T09:39:08.589Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JzdIRMGadCnvuo1SxMTS8w.png" /></figure><p>A sea turtle lays more than 100 eggs each nesting season, but only a handful will successfully hatch and survive the journey into the ocean. Creating a new business is a little bit like being a sea turtle mom — you want to know your environment and create many versions of your offer to increase your odds of success.</p><p>When it comes to making sure those sea turtle babies — I mean, uh, your business ideas — thrive, there are two methods that can help: Design thinking is the approach for discovering which of your eggs has the best chances of survival. Once that baby sea turtle has made it successfully into the ocean, the Lean Startup methodology can improve its chances of successfully reaching adulthood.</p><p>During a recent project, a client asked me about the difference between the two methods. While these techniques have been around for years now, it’s a question I hear a lot — many folks in the world of business think they should know the difference, but in all honesty, I don’t blame them for being confused. The methods are distinct, but they can (and should) be used in tandem. Businesses could benefit from them both.</p><p>Back to the client question — what’s the difference? I started by explaining the difference between the two methods more broadly, laying out what you see in the chart below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2CLg6sMAK_lfqMlJ4ldUxw.png" /></figure><p>Both approaches are about building new concepts and products, learning as much as possible from users, and from what’s happening in the market. And both methodologies employ an iterative approach that consistently seeks feedback and understanding from customers in the market.</p><p>Knowing the difference is one thing — knowing when to use one or the other is just as important.</p><p>Design thinking helps teams come up with many new ideas for new offers they then test before settling on the one that is most desirable, feasible, and viable. When applying design thinking, once we’ve uncovered user needs, we create a slew of options that might solve those needs. Each one is intentionally distinct from the others so we can learn what works best. In visualizing design thinking for our curious client, I sketched something like this (which my colleague Kavya then illustrated for this piece):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGtlSI9U2LtpsNjM5vgT2A.png" /><figcaption>In design thinking, once we’ve uncovered user needs, we create a slew of options that might solve those needs. Each one is intentionally distinct from the others so we can learn what works best. One idea might be a product, another might be an app, and a third might be a service. The point is to create a broad array of ideas that can then be tested.</figcaption></figure><p>On the other hand, the Lean Startup method helps teams drive toward a better version of an existing or new concept. It’s great if you have a product in-market that you want to tweak so it performs better. That end product may vary significantly from the original, but with the Lean Startup approach, you will be able to trace a path from Version A to Version Z. If I were to sketch it, it looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVlufDzU5LkApAfSRuFEzA.png" /><figcaption>The Lean Startup method helps teams drive toward a better version of an existing or new concept. While the end product may vary significantly from the original, there are clear similarities between each iteration because the focus is refinement, not new explorations.</figcaption></figure><p>Now that we have the two distinct methods visualized, we can look at applying them. A hypothetical challenge: Let’s imagine we’ve been asked to create a new concept to upend the fact girls are called on less, given less teacher attention, and given fewer opportunities to speak in mixed-gender science classrooms.</p><p>As design thinkers, our first step would be to talk to girls, boys, and their science teachers. We would talk to psychologists and sociologists. We would explore the mixed-gender education experience in other cultures. After our research, we’d distill our findings into opportunities for improving the classroom experience. For example: How might we immediately reward girls for participating in class? How might we enable teachers to see the disparity?</p><p>Based on those prompts, we would brainstorm a slew of ideas. For example: What if classrooms had a voice monitor that recorded the amount of time that boys spoke versus girls spoke? What if there was an online instructor’s portal with exercises for how to draw out girls in every classroom session? What if there was an app that quizzed students who are girls daily to increase their familiarity and confidence with science material?</p><p>We would then take this array of ideas and create prototypes — rough, inexpensive, tangible expressions of the new concepts — and test them. Based on feedback, the next round of prototypes might look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZHyzmzYQXfluAUcOhKIitw.png" /><figcaption>After an initial round of testing, some ideas get discarded completely while others are broken down so that the parts that resonated can be brought into new forms. Because of the diversity of ideas and prototypes that come from a design thinking approach, there’s no clear throughline from Version A to Version Z.</figcaption></figure><p>Maybe the voice monitor didn’t affect teacher behavior, but it did sufficiently frustrate the girls in the classroom-so much so that the next prototype was a wall-mounted display to show a live tally of student input. Because of the diversity of ideas and prototypes that come from a design thinking approach, there’s no clear throughline from Version A to Version Z.</p><p>Based on knowing that we are now going to build a voice-activated wall display, we would also use design thinking to build and test the accompanying business model and the product’s visual language. We would think about, build, and test options for how the display will get in front of buyers (the distribution channel), who pays for them and how much (the revenue and pricing model), and which entities might help to expedite our success (partnerships). As we explore the most viable business model, we’re still refining the concept.</p><p>Once those designs have been sufficiently evolved, we can plan for a limited launch to test the assumptions behind the products. With a refined concept and business model in hand, we can begin in-market testing.</p><p>This is when you want to lay 100 eggs, because only a very few will meet the bars for user desirability, the company’s ability to implement it, and the crucial feature of being financially lucrative for the business. In general, using a design thinking approach for a limited launch of a new concept will reduce risk, while using the Lean Startup methodology during in-market refinement will improve the chances of success.</p><p>Sometimes, when a team launches a new product but skips the user-centered design process, they find it may be necessary to pivot. That’s a good time for a team to turn to design thinking to explore why the concept isn’t working, and to find new ways to make it meet user needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XSg-dr8RFjUgZNtc5-0AhQ.png" /></figure><p><em>Originally published on November 20, 2020 at </em><a href="https://www.ideo.com/blog/zig-then-zag-when-to-use-design-thinking-vs-the-lean-startup-approach"><em>https://www.ideo.com</em></a><em>. Illustrations by Kavya Singh Barthwal</em> <a href="https://www.kavya-singh.com/"><em>www.kavya-singh.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab3d90533ecc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/zig-then-zag-when-to-use-design-thinking-and-when-to-use-lean-startup-approach-ab3d90533ecc">Zig, Then Zag: When to Use Design Thinking and When to Use Lean Startup Approach</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Ways To Design A Business]]></title>
            <link>https://medium.com/ideo-stories/6-ways-to-design-a-business-de6a12d122de?source=rss-e13574cc505f------2</link>
            <guid isPermaLink="false">https://medium.com/p/de6a12d122de</guid>
            <dc:creator><![CDATA[kerry oconnor]]></dc:creator>
            <pubDate>Tue, 02 Sep 2014 22:14:38 GMT</pubDate>
            <atom:updated>2014-09-03T06:36:07.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9VXOGZ5gI_lPq70hpnFFQ.jpeg" /></figure><p>I asked my students during a class on Business Design at Stanford’s d.school how they might innovate on IKEA’s business. The engineers and scientists’<br>hands rose immediately.</p><p>“Offer interior design services!”<br>“Launch a more premium brand!”<br>“Take back old furniture as a way to discount the price of new purchases!”</p><p>Great ideas, no? I then asked them to talk through generating a business<br>model to support one of those proposals. This time, no hands went up. They turned their eyes down and examined the floor.</p><p>At IDEO there are people who design in pixels or steel, and then there are<br>people like me,who model the systems, cash flows, and structures to sustain<br>such bold innovation.</p><p>Designing a business will never be as sexy as creating a shiny new object.<br>Yet the business system is the foundation upon which those brilliant objects live in the marketplace. And ultimately, the reason they can thrive and change the way we interact with the world.</p><p>For those of you who are interested in this variety of design , I’ve put together a cheat sheet for how to (re)design a business model.</p><h3>1. Break down the problem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bC5bINH931hT4u4uV04JEg.jpeg" /></figure><p>Let’s imagine that IKEA was creating a premium line of furniture conceived by guest designers. What questions might you want to ask about that<br>offering? Well, for starters: who would it serve? How big is the audience these products might appeal to? What kind of premium could IKEA charge for a designer sofa over a Klippan sofa? What extra costs will be incurred for more luxurious fabrics?</p><p>At its essence, a business model needs to define <strong>who</strong> it is serving<br>(customers), <strong>how</strong> the offering gets to that person (channel), <strong>what</strong> unique<br>value is delivered (value proposition), and <strong>how much</strong> that value is worth<br>(pricing).</p><p>I always begin by defining what unique value we can deliver to the market. As a human-centered design firm, IDEO sees the opportunity for innovation in who we are designing for. We focus on what users need — the unique value proposition our designs can offer — and then design the business model around that.</p><h3>2. Create Constraints</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*71b9XkDV_7NIKCfmXukhSQ.jpeg" /></figure><p>OK. Now that you have identified the elements that make up a business<br>model, or business system, it’s time to frame your problem. How? First<br>impose some boundaries that define the problem area. “Constraints are<br>liberating,” says Diego Rodriguez, a partner at IDEO and a mentor of mine. They help you move from blue sky to brass tacks thinking.</p><p>In the case of Bean Pole, a Korean clothing retailer, we started by defining<br>what the brand stood for — delivering high quality, on trend clothing with a<br>British feel. We used that as a foundation to generate ideas for service<br>experiences that would deliver on the implicit and explicit brand values.<br>Without looking at other parts of the business model, we crystalized what was immutable — in this case, the brand attributes — to then inform what was possible in the other parts of the business. Capturing such elements that cannot change are exactly the constraints you’re looking for.</p><h3>3. Look for Inspiration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F3IoWDQS4ZpMimqWZL6pSA.jpeg" /></figure><p>The biggest mistake business design students make is to just copy business<br>models of existing companies, especially those that their innovations seek to supplant. There’s nothing wrong with building a better mouse-trap, but that product will stand out from the pack if it’s supported by a novel business system.</p><p>Take Zipcar, which was, in essence, a car rental service. But the company’s<br>innovative pricing and membership revenue model were wholly different and ultimately disrupted the auto rental industry. Rather than using an existing business model as a template, use it as a starting point. Then, look out to the world for fresh ways that other companies have designed the elements you seek to innovate.</p><p>Likewise, Warby Parker could have introduced eyeglasses the way other<br>designers have — in retail stores with a high markup. Instead, the company<br>took the best practices of e-commerce — offering customers great prices, free shipping, and returns — to drive purchase and change the paradigm for how eyewear is sold.</p><h3>4. Bring in Outsiders</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BEcPbQv6iaxrYuPQYSbObw.jpeg" /></figure><p>My students’ project is around innovating the public school lunch<br>program in San Francisco. One group’s proposal is for the school to charge<br>students for take-home meals, to be eaten at home with family for dinner.<br>That begged the question, how much might people pay for this meal? If it’s<br>seen as equivalent to dinner in a restaurant, they might pay a lot, but what if dinner out is drive-thru fast food? With a few quick phone calls to the families of the public school kids, my students were able to understand how much they could charge for a meal, and therefore if their big idea could work.</p><p>Bringing in outsiders to respond to your ideas is always a good idea. It<br>refocuses the work on true human needs, challenges the designer’s<br>assumptions about audience and capturing value, and allows teams to test<br>and iterate.</p><h3>5. Begin With Ballpark Numbers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NxL5LqtY2k48IRSi8vdMKQ.jpeg" /></figure><p>At IDEO, I led a team that was designing a mobile product for a Korean client. We heard from users that they wanted steep discounts, asking for 40 percent and 50 percent of the retail price through the smartphone app. We also knew from our client’s financial statements that there was no way they could sustain a business if they did so.</p><p>Rather than burying ourselves in a financial model to try to make the numbers work, we mocked up a few simple interactive prototypes to test with target consumers. Once the product was in hand, we discovered that people were surprisingly quite happy with 10–15 percent discounts. The moral: there’s a great gulf between what people say they want and how they actually behave. Knowing this early in our design process saved a lot of time and allowed us to co-design the user experience and discount thresholds over time.</p><h3>6. Remember to Design A System</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGFytndYc9YDh1gnIBIGlw.jpeg" /></figure><p>A business system is a series of “if, then” statements — interdependencies.<br>One design choice influences the next. For example, when Warby Parker<br>decided to sell exclusively through an online channel, it shaped their<br>marketing strategy, requiring them to invest in campaigns that made<br>consumers aware of their offering.</p><p>At each stage of design, think through how your choices generate new<br>assumptions about the interconnected aspects of your business model. Step<br>back and consider how interconnected pieces work together in a system. As<br>designers, we aim to create elegant systems — a whole that fluidly connects<br>the parts.</p><p>As I stand in front of my class at Stanford, I’m certain I’m looking at the future Elon Musks and Marissa Mayers. They are going to innovate in radically new ways. But their brainchildren will only make it to market if they are supported by equally incredible business systems. These product designers will build, breakdown and recreate each product scores of times until they have a form that looks natural and obvious. The business designer too will build, test, tweak and refine until she has an elegant and fluid system in place.</p><p>With this co-creation of product and business we are left with something so well integrated into our lives that we can’t imagine how we ever managed without it. Surely, these students will offer us our next great product – and business –soon.</p><p><em>illustration credits: Tiffany Chin and Feel Hwang</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de6a12d122de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideo-stories/6-ways-to-design-a-business-de6a12d122de">6 Ways To Design A Business</a> was originally published in <a href="https://medium.com/ideo-stories">IDEO Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>