<?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 Ryan Seamons on Medium]]></title>
        <description><![CDATA[Stories by Ryan Seamons on Medium]]></description>
        <link>https://medium.com/@ryanseamons?source=rss-77e77abb3d41------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*en2xlmy9pJMG69HtZu2yLw.jpeg</url>
            <title>Stories by Ryan Seamons on Medium</title>
            <link>https://medium.com/@ryanseamons?source=rss-77e77abb3d41------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:41:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ryanseamons/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[A Lesson from Medieval City Centers about How to Gain Career Fulfillment]]></title>
            <link>https://ryanseamons.medium.com/a-lesson-from-medieval-city-centers-about-how-to-gain-career-fulfillment-8a7d623e0e13?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a7d623e0e13</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[fulfillment]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Tue, 19 Jan 2021 18:19:37 GMT</pubDate>
            <atom:updated>2021-01-19T18:19:37.089Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s an important lesson about career fulfillment to learn from the shift over the past millennium in how we build our cities.</p><blockquote>“People 1,000 years ago walked among squares with marble sculptures, domes, stone arcades, and past village churches with gardens kept by the clergy that lived there. As a matter of life, some walked through what constituted art on the scale that people today, even very rich people, may never experience.”</blockquote><blockquote>“Almost no new cities match the beauty of the few remaining medieval city centers, which themselves are so cherished that people will spend thousands to fly there, just to see them in person for a few days. But tourists fly home, and never think of creating a new place, of creating something that constitutes an artistic endeavor beyond themselves. Rather they will leave building to builders and zoning codes, who will plan the next warehouses for humans, for <strong>rarely today can people verbalize their values in any other terms than the economic</strong>… though we often know something is wrong or even deeply troubling with the aesthetics of a place or situation, do not even have the vocabulary to dissent”</blockquote><blockquote><a href="https://simonsarris.substack.com/p/in-praise-of-the-gods">In Praise of the Gods</a> by Simon Sarris.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ILeiWIaAksQgzPPw.jpg" /></figure><p>What we value shows in what we optimize for and surround ourselves with. That’s changed over time for cities and it applies to our careers as well.</p><h3>Non-economic Value</h3><p><strong>“Rarely today can people verbalize their values in any other terms than the economic.”</strong> Reading this hit me like a ton of bricks.</p><blockquote><strong>Knowing what you value and how that matches up with the culture of a new potential company/job is critical to career fulfillment.</strong></blockquote><p>Nowhere is this more true than in a career. We instinctively use raw economic terms to consider and compare career options. Concepts like base salary, bonus, health insurance, and other perks come up most often. Why? Because it’s easy. It’s simple to quantify. It’s obvious to compare.</p><p>As an occasional career coach and mentor, one consistency I find (especially in younger job seekers) is a fixation about base salary. Much of my coaching centers on helping job seekers consider more possibilities about what matters. This includes not only the economic possibilities they should negotiate for beyond base salary (like benefits, time off, equity, compensation conversations, learning budget, etc.) but also other intangible parts of a job (values like flexibility, respect, trust, adventure, autonomy, and courage). Those intangibles tend to end up having more impact on our happiness than economics.</p><p><strong>Knowing what you value and how that matches up with the culture of a new potential company/job is critical to career fulfillment.</strong></p><h3>Economics still matter, but they are a piece of a much bigger career fulfillment puzzle</h3><p>Now, economic means aren’t unimportant to your career. But money is a hygiene factor. You notice when it isn’t right, but after a certain level, it is no longer an influential motivator.</p><p>It’s why studies show that <a href="https://www.cnbc.com/2017/11/20/how-much-money-you-need-to-be-happy-according-to-wealth-experts.html">after $75,000 your happiness doesn’t increase</a>.</p><p>One of my career decisions was almost made completely on the basis of money.</p><p>I was deciding which MBA program to pick. My plan was to go to one of the prestigious schools on the East coast. I worked hard and got the test score I would need. As I was filling out applications, it was difficult for me to think beyond the raw base salary expectations. One school’s average salary upon graduation was <strong>over $50k higher</strong> than another school I was considering! I kept coming back to the difference that money could make for my family.</p><p>I assumed that the prestige of the school alone was adding more money. As I explored more about the disparity, it ended up that industry and location was the main driver of the difference. Investment bankers in New York make a lot more money than most other MBA graduates.</p><p>Some of my friends chose this route. There’s nothing wrong with being an investment banker in New York City. But given that I had 3 young children at the time, <a href="https://www.investopedia.com/articles/professionals/111715/day-life-investment-banker.asp">working 80 hours a week</a> wasn’t my first desire.</p><p>You have to consider the whole package, especially beyond the money.</p><p>One of my mentors shared this personal observation — MBA students tend to flock to the large companies right out of school. Large salaries attract them. But after a few years, many come back to small businesses. They have learned that it’s ok to take a lower salary smaller companies can offer in exchange for the autonomy and influence often lacking at large corporations.</p><p>This is a broad generalization, but what I like about this perspective is the change that happens for some people.</p><h3>How you can optimize your career around real values</h3><p>Instead of only looking at the economics, you should take time to develop your own perspective about what you value at work. Here’s a process I’ve seen help hundreds of people decide what matters and take meaningful action in their career:</p><p>1. <strong>Carve out time to answer the question, “What matters most in my career?”</strong> I’ve found the most important part of this is just taking the time. Put technology down. Journaling can help some people. A card sort is the best mechanism I’ve seen consistently help people sort through potential thoughts.</p><p>Another approach that can be helpful is to think about experiences you’ve had in your career. What brought you the most joy and fulfillment. When were you at your best? What boss/job/project/team filled your bucket? Why?</p><p>2. <strong>Speak with a mentor about why these things matter</strong>. A simple framework for a good mentoring session about career is to talk about the past, the future, and the present.</p><p>Sit down with someone you trust — a mentor, spouse, friend, or even your boss. You talk about what matters most. It’s a conversation many people say they’ve kind of had, but it’s rare to dedicate time to have it. This approach is aligned with <a href="https://firstround.com/review/three-powerful-conversations-managers-must-have-to-develop-their-people/">a framework Russ Laraway suggests</a> from his time at Google. He got a 10-point bump in engagement scores on his teams by using this conversation approach!</p><p>3. <strong>Commit to a plan</strong>. Figure out what you’re going to do next, ideally with a prioritized list of career experiments vs a linear plan that is bound to change. Too many people jump head-long into a big career change without actually validating that it’s what they want. Often the path one person told them about is what ends up guiding most of someone’s decisions.</p><p>I’m a big fan of <a href="https://ryanseamons.com/product-roadmap/">one-pagers for product roadmaps</a>. Applying this methodology to careers can give you a simple living document that can give you guidance while being adaptable.</p><p>Being able to verbalize your values in non-economic terms is a valuable practice. It’s difficult to make something happen if you can’t talk about it.</p><p>If you find yourself nodding along in agreement with this, you’ll love the <a href="https://meetgroove.com/career-clarity/">Career Clarity Toolkit</a> we created. Its proven, step-by-step method uses design thinking, guided reflection, and career experiments to help you gain clarity and confidence to get more of what you want out of your career, even in your current job. We’ve inspired hundreds of people to make changes big and small to find more career fulfillment.</p><p>I came across the original quote from Simon Sarris in Trevor McKendrick’s wonderful newsletter <a href="https://www.trevormckendrick.com/newsletter?rh_ref=3fad8aa7">How It Actually Works</a></p><p>Originally published at <a href="https://meetgroove.com/career-fulfillment/">meetgroove.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a7d623e0e13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Lessons Product Managers Need to Learn From Clayton Christensen]]></title>
            <link>https://ryanseamons.medium.com/8-lessons-product-managers-need-to-learn-from-clayton-christensen-33ac7302fe95?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/33ac7302fe95</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Thu, 30 Jan 2020 00:35:22 GMT</pubDate>
            <atom:updated>2020-01-30T19:19:20.371Z</atom:updated>
            <content:encoded><![CDATA[<p>Clayton Christensen is one of the greatest business minds of our time. His recent passing caused me to reflect on all I learned from him. His life was dedicated to his family, his faith, and the theories he taught. He personified servant leadership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/0*DrLoudUs1TlgJ3qh.jpg" /></figure><p>Almost every single topic he taught is relevant to the work of product management. Here I share 8 key lessons I’ve learned from his work that have helped me be a better product manager, leader, entrepreneur, husband and father.</p><ol><li>The Theory of Disruptive Innovation</li><li>Jobs to be Done</li><li>Don’t Outsource Core Capabilities</li><li>The Pitfalls of Best Practices</li><li>How You Measure Success Matters</li><li>Relationships Matter</li><li>The Importance of Strategy</li><li>Success Beyond Work</li></ol><h3>1. The theory of disruptive innovation</h3><p>Clay’s seminal work deals with this question:</p><p><strong>Why do big companies with lots of resources miss out on innovative solutions?</strong></p><p><a href="https://www.youtube.com/watch?v=mbPiAzzGap0">Disruptive innovation</a> is the theory that explains the answer. I encourage every PM to <a href="https://www.amazon.com/Innovators-Dilemma-Technologies-Management-Innovation/dp/1633691780/">read the book</a> and read some of his best articles. Here are 3 I recommend:</p><ul><li><a href="https://hbr.org/1995/01/disruptive-technologies-catching-the-wave">Disruptive Technologies: Catching the Wave</a> — the original</li><li><a href="https://hbr.org/2015/12/what-is-disruptive-innovation">What is Disruptive Innovation</a> — this one is a good clarifier</li><li><a href="https://hbr.org/2012/12/surviving-disruption">Surviving Disruption</a> — about long-term disruption</li></ul><p>The theory of disruptive innovation is nuanced and often misapplied. His theory doesn’t describe all “innovation”.</p><p>The key lesson from disruptive innovation is that what ends up being disruptive technology starts by looking inferior. They are cheaper solutions that usually appeal to another segment of the market. The technology that makes them disruptive is unappealing to the current leaders at first.</p><p>Blockbuster vs Netflix. Hotels vs Airbnb. Taxis vs Uber.</p><p>The new solutions seemed a lot worse at first, but the technology and improvement over time made them much more successful over time.</p><p><strong>So what do you need to do?</strong></p><blockquote><em>“Managers must beware of ignoring new technologies that don’t initially meet the needs of their mainstream customers.”</em></blockquote><p>Question who your customer is and realize that unmet needs in new segments can represent massive opportunities.</p><p>At its core, the concept that future growth and potential are worth more than current status. It’s an incredibly powerful idea about how the world works. Used well this theory governs not just the rise and fall of companies, but also how we need to think about potential in all domains.</p><blockquote><em>“It’s </em><strong><em>important</em></strong><em> to remember that disruption is a positive force. </em><strong><em>Disruptive innovations</em></strong><em> are not breakthrough technologies that make good products better; rather they are </em><strong><em>innovations</em></strong><em> that make products and services more accessible and affordable, thereby making them available to a much larger population.” </em><a href="https://www.christenseninstitute.org/key-concepts/disruptive-innovation-2/"><em>source</em></a></blockquote><p>Existing businesses you need to invest in more than ideas that have obvious, immediate returns. Disrupt yourself by developing low-cost ways to serve customers that seem to cannibalize your existing market.</p><h3>2. Jobs to be done</h3><p><a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">The Jobs to be Done</a> concept is similar to user stories or <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27">job stories</a>, but with some important distinctions. It’s more effective to answer the question “What job are you hiring this product to do?” compared to the plug and chug user stories or job stories alone encourage.</p><p><a href="https://hbr.org/podcast/2016/12/the-jobs-to-be-done-theory-of-innovation">The example of the milkshakes</a> is one of my favorite examples to share. It’s common for non-product people to think that gathering user insight can be done by running a survey and adjusting the product according to the overall results. But in-person observation and interviewing find distinct use-cases that could then be optimized to serve those customers.</p><blockquote><em>Many organizations have unwittingly designed innovation processes that produce inconsistent and disappointing outcomes. But firms don’t have to continue down that path. Innovation can be far more predictable-and far more profitable-if you start by identifying jobs that customers are struggling to get done. Without that lens, you’re doomed to hit-or-miss innovation. </em><a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done"><em>source</em></a></blockquote><p>One of the first rules of product management is to <a href="https://twitter.com/hnshah/status/1107871918433026048">be obsessed with your customers</a> (thank you Hiten Shah). In a world that supports in-person relationships less and less, Clay was an advocate for getting out of the room and being with the people.</p><p>Key questions you can ask to apply the theory to your product include:</p><ul><li><strong>Who is hiring this product?</strong></li><li><strong>What are they hiring this product to do?</strong></li></ul><p>This simple reframe and examples from Clay help product managers as they seek to become not just a delivery team or a feature team, but a real product team solving real problems for users.</p><h3>3. Don’t outsource core capabilities</h3><p>This principle is applicable to product managers from a talent standpoint, both for your own company’s abilities as well as your own personal skills.</p><p>It’s the classic tale of middle managers who no longer know how to do anything real. It’s easy to build a habit of always passing the grunt work along. While delegation is critical to leadership and potentially the biggest blocker to company growth, so outsourcing everything is a path towards skills irrelevance.</p><p>One of the surest ways to rise in a company is to find something that no one else understands and do it better than anyone else. This is how <a href="https://www.wired.com/story/jeff-weiner-on-how-technology-accentuates-tribalism/">Jeff Weiner</a> got his rise through the ranks of Warner Brothers. It’s also how <a href="https://blogmaverick.com/2011/04/07/shark-tank-success-motivation/">Mark Cuban</a> put himself in a prime position to build a company and trade tech stocks to make his billions.</p><p>Doing the hard work no one else wants to do is a path to success. Clay found over and over again companies that failed to do so, outsourcing the “boring” or “mundane” work which eventually led them into irrelevance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/0*JvIplKmo27mqlDTt.jpg" /></figure><h3>4. Following best practices doesn’t always work</h3><p>Just because something looks like it should work doesn’t mean you understand the underlying principles and mechanisms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*3eZw_6XX1vfZ5h0h.jpg" /></figure><p>Consider how our ancestors thought about approaching flight. They believed that feathers and flapping wings were the answer to how we would fly. The solutions that ended up actually working (based on the principles of flight vs just the outer look of birds) are very different than they expected.</p><blockquote><em>“[Using] robust theory to predict what will happen has a much greater chance of success.”</em></blockquote><p>For product managers, this is a clear invitation to avoid relying only on what the competition does or what customers say as fuel for your product concepts. Understanding the theory underneath problems (the <strong>why</strong>) is powerful.</p><blockquote><em>“That’s a hallmark of good theory: it dispenses its advice in “if-then” statements.”</em></blockquote><h3>5. How you measure success matters (resource allocation)</h3><p>You get what you reward for.</p><p>SonoSite had developed a new portable ultrasound machine. The CEO tagged along with a sales meeting. The sales rep wouldn’t pull the machine out of his bag and was laser-focused on selling the current, larger solution. The CEO later realized that the rep’s incentive plan wasn’t aligned with an important future shift for the company.</p><p>Another example of this is the story of an archaeological discovery in the 1940&#39;s:</p><blockquote><em>… a team led by Ralph von Koenigswald had found another group of early humans which became known as the Solo People, from the site of their discovery on the Solo River at Ngandong. Koenigswald’s discoveries might have been more impressive still but for a tactical error that was realized too late. He had offered locals 10 cents for every piece of hominid bone they could come up with, then discovered to his horror that they had been enthusiastically smashing large pieces into small ones to maximize their income.</em></blockquote><p><a href="https://www.ncbi.nlm.nih.gov/pubmed?cmd=Retrieve&amp;dopt=Abstract&amp;list_uids=17502168">Unintended consequences</a> happen come with rewards. What you reward (both consciously and unconsciously) has incredible influence on the work.</p><blockquote><em>“The only way a strategy can get implemented is if we dedicate resources to it.”</em></blockquote><h3>6. Relationships matter, especially on product teams</h3><p>This is especially critical for product managers because of a trend to be arrogant. Product managers need to be very intelligent. It’s one of the hardest and most critical roles in a company. It requires an incredibly broad skill set to manage a product. A PM helps the team figure out the right problems to solve and decide which bets to place.</p><p>But PM is a role that can’t be done on an island. Without a team willing to follow, nothing happens. Investing in relationships is key.</p><p>PMs can be attracted to the field because they believe the old myth that the PM is the CEO of the product. I have actually heard aspiring PMs say they are pursuing the role because “I want to be able to make all the decisions” or “I want to call the shots”. If you think you’re in charge, you have a long road ahead of you. Even at companies where the PM role is well respected and giving generous authority, you will find much more success by inspiring and working together with those around you vs telling everyone the “right answer”.</p><p>The impact to both the work and the team is powerful when we take Clay’s advice:</p><blockquote><em>“If you want to help other people, be a manager. If done well, management is among the most noble of professions.”</em></blockquote><p>Help others. Don’t just try to look like the smartest person around.</p><h3>7. The importance of figuring out and communicating the strategy</h3><p>Getting aligned and staying aligned as a team is difficult. Too many product teams waste time and money because they lose sight of why they are building something and fall into the trap of becoming a feature factory.</p><figure><a href="https://blog.sprintwell.com/team-velocity/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c2K9dGhVSKTDKLe_.jpg" /></a></figure><p><a href="https://blog.sprintwell.com/team-velocity/">Activity ≠ Progress</a></p><p>Figuring out which bets are worth making, which experiments should be run, and how to optimize for fast learning isn’t always straight forward.</p><p>Clay warns:</p><blockquote><em>“93 percent of all companies that ultimately become successful had to abandon their original strategy”</em></blockquote><blockquote><em>“[Successful] senior executives need to spend a lot of time articulating clear, consistent priorities that are broadly understood throughout the organization.”</em></blockquote><h3>8. Don’t let personal work success become the driving force in your life.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*qJB0rR8-xm-BVoDN.jpg" /></figure><p>I’ll let <a href="https://hbr.org/2010/07/how-will-you-measure-your-life">Clay’s words</a> speak for themselves:</p><blockquote><em>“Work can bring you a sense of fulfillment-but it pales in comparison to the enduring happiness you can find in the intimate relationships that you cultivate with your family and close friends.”</em></blockquote><blockquote><em>“Don’t worry about the level of individual prominence you have achieved; worry about the individuals you have helped become better people.”</em></blockquote><blockquote><em>“I have a pretty clear idea of how my ideas have generated enormous revenue for companies that have used my research; I know I’ve had a substantial impact. But as I’ve confronted this disease, it’s been interesting to see how unimportant that impact is to me now. I’ve concluded that the metric by which God will assess my life isn’t dollars but the individual people whose lives I’ve touched.”</em></blockquote><p>If you haven’t taken time to carefully study his theories, I encourage you to do so. I’ve included links throughout this article as a reference point for those wanting to read his thinking for the first time and for those wanting to review them again.</p><p>If I could summarize the lesson Clayton Christensen has for every product manager, it is this:</p><p><strong>The way you architect your work and your life make a meaningful long-term difference, for success or failure. Success isn’t always gained by pursuing what is immediately obvious.</strong></p><p>Thank you, Clayton.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/0*oTGUGYRZJskFmxtr.jpg" /></figure><p><em>*Any quotes not sourced in the copy come from Clayton’s book </em><a href="https://www.amazon.com/How-Will-Measure-Your-Life/dp/0062102419/"><em>How Will You Measure Your Life</em></a><em>. If you haven’t read it you really should.</em></p><p><em>Each Sunday I send out the free </em><a href="https://ryanseamons.substack.com/"><em>“What do you really want?” Newsletter</em></a><em>. I share ideas that equip readers to help themselves and others clearly answer the question: What do you really want? and concisely communicate that answer to others.</em></p><p><em>Originally published at </em><a href="https://ryanseamons.com/christensen-product"><em>https://ryanseamons.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33ac7302fe95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why my boss telling me I couldn’t do something was the best thing that ever happened to me]]></title>
            <link>https://ryanseamons.medium.com/why-my-boss-telling-me-i-couldnt-do-something-was-the-best-thing-that-ever-happened-to-me-7129442a3ece?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/7129442a3ece</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 14:21:01 GMT</pubDate>
            <atom:updated>2019-09-11T14:21:01.169Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jDEbn-VJIZcyUtgg.png" /></figure><p>“You just don’t have the skills to do this. Some people work for years to do this and I just don’t think you have what it takes.”</p><p>Not exactly what you want to hear from your boss.</p><p>I was early in my pursuit of a career in product management. Looking back, I really didn’t have much of a clue what I was doing. But I wasn’t being equipped and enabled — instead I was told I wasn’t enough.</p><p>I walked out of that 1:1 furious.</p><p>That experience could have been crushing except for the reframe I decided to take.</p><p>I decided to ask myself, <strong>“What can I learn from this?”</strong></p><p>I vowed to never limit someone’s potential in my mind. I would take seriously the responsibility of managing others. I also committed to double down on building pm skills so that I could accomplish my future goals.</p><p>Reframing can change a miserable experience into something desirable. My friend, Rob Callan, <a href="https://www.linkedin.com/posts/robcallan_perspective-change-vision-activity-6556524001458470912-JWiQ/">shared his thoughts on LinkedIn</a> about reframing.</p><blockquote><em>How we frame situations matters, especially when we’re doing hard things.</em></blockquote><blockquote><em>If you’re on a team and you feel enthusiasm stalling for a new project, try focusing instead on what people can learn, achieve, and become — that’s a lot more compelling than focusing exclusively on the tasks themselves.</em></blockquote><p>Many years later I am grateful I took the attitude I did. I’ve been a successful product manager at multiple hyper-growth companies. I run a <a href="https://ryanseamons.substack.com/">weekly newsletter</a> about being a great product leader. And now I enjoy teaching product management as part of what we do with clients at <a href="https://www.sprintwell.com/">Sprintwell</a>.</p><p>The biggest piece of advice I give to recent college graduates is to optimize your career for learning. Choose a job where you will learn the most.</p><p>For a tough situation at work or in personal relationships, my invitation is to ask, <strong>“What can I learn from this?”</strong></p><figure><a href="https://ryanseamons.substack.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yiFgiM1SIAyjgbfNbSkiw.png" /></a></figure><p><strong>Check out other articles I’ve written:</strong></p><ul><li><a href="https://medium.com/@ryanseamons/the-best-way-to-build-an-effective-product-roadmap-sprintwell-e55b01b489a">The Best Way to Build an Effective Product Roadmap — Sprintwell</a></li><li><a href="https://medium.com/@ryanseamons/3-leadership-lessons-from-a-legendary-football-coach-that-have-nothing-to-do-with-football-19aee7c3dac2">3 leadership lessons from a legendary football coach (that have nothing to do with football)</a></li><li><a href="https://medium.com/hackernoon/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c">9 lessons product teams can learn from Formula 1 pit stops</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7129442a3ece" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 leadership lessons from a legendary football coach (that have nothing to do with football)]]></title>
            <link>https://ryanseamons.medium.com/3-leadership-lessons-from-a-legendary-football-coach-that-have-nothing-to-do-with-football-19aee7c3dac2?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/19aee7c3dac2</guid>
            <category><![CDATA[parenting]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[sports]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 14:41:18 GMT</pubDate>
            <atom:updated>2019-09-10T14:41:18.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*26VTr9xAl802O8St-NDUCw.jpeg" /><figcaption><a href="https://unsplash.com/photos/ZSunLS878Yk">https://unsplash.com/photos/ZSunLS878Yk</a></figcaption></figure><h4>True leadership isn’t just about winning. Secrets from Legendary BYU College Football Coach, LaVell Edwards</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*PalFOrCbaNNwHD6_OQ9UMQ.jpeg" /></figure><p>LaVell Edwards, former football coach at Brigham Young University, died at the end of 2016 and is one of the greatest coaches of all time. He took a relatively unknown team and built a top football program. Even with all his success on the field,<strong> his greatest legacy is seen in the lives of his former players.</strong> Here are 3 lessons on leadership, as told by his former players:</p><figure><a href="https://ryanseamons.substack.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yiFgiM1SIAyjgbfNbSkiw.png" /></a></figure><h3>1. Care about Those You Lead</h3><p>Hear what former players had to say about LaVell:</p><blockquote>“The №1 quality that Coach had was a gift to see things that you didn’t see, to see potential in you that you didn’t know about … He was like the Johnny Appleseed, just spreading seeds of goodwill and positivity”</blockquote><blockquote>— Steve Young</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2G7J6BY4HqY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2G7J6BY4HqY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2G7J6BY4HqY%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1ec1504ffcc22c326dbb0defdeea3eb1/href">https://medium.com/media/1ec1504ffcc22c326dbb0defdeea3eb1/href</a></iframe><blockquote>“He made [his team] better players …, but more than that, he made them better husbands, better fathers, better men. That’s the trophy—that’s the legacy of LaVell Edwards”</blockquote><blockquote>— Trevor Matich (ESPN interview)</blockquote><p>Lavell was personal and compassionate. He could see potential in others and he used that gift to lift others.</p><p>Many leaders have the gift of vision. They see into the future. What impact could we have on our employees, businesses, communities, etc. if more leaders used those skills of vision to genuinely help individuals (not just to make money)? This is one of those skills that I know has a positive impact on the bottom line, even though it’s hard to measure.</p><h3>2. Remember that Leadership Impacts Families</h3><blockquote>“The legacy of LaVell Edwards is not that trophy inside the case. It’s that father standing outside the case.”</blockquote><blockquote>—Trevor Matich (ESPN)</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDDoSiPjeheI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDDoSiPjeheI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDDoSiPjeheI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0651c0d98a9abea27ae0ee077ba37563/href">https://medium.com/media/0651c0d98a9abea27ae0ee077ba37563/href</a></iframe><p>Building Mothers and Fathers is the greatest form of leadership. Parents are the real impact in this world. That is where change truly happens—building Mothers and Fathers who can teach patterns of happiness and success to their children.</p><p>This past year, I was at an education summit in Washington D.C. The summit brought college deans, educational policy makers, and education tech. entrepreneurs together to talk about improving education. Through dozens of presentations, one factor remained unmentioned: Parents.</p><p>After a full day of intellectuals discussing ways to improve education, I was troubled that parents hadn’t even come up. Granted, it’s easier to talk about new technology or additional funding. Those are quick, external fixes. Changing families is hard. That’s what makes LaVell Edward’s legacy that much more powerful.</p><p>Leaders would do well to consider their impact not just on work or sports, but in the lives of those they lead and their families.</p><h3>3. Winning isn’t the Goal</h3><blockquote>“LaVell had a pure heart. He was the dream coach of every parent. His example will forever be with me, and I will strive to live a life of love as he always did.”</blockquote><blockquote>— Tom Holmoe</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7-1f9cJQkTZnqIfbk3G7Rw.jpeg" /></figure><p>Was he tough? Absolutely. But he was tough for a reason, and that reason wasn’t just winning. Winning in sports or business is a by-product of great leadership, but it isn’t the ultimate goal. Relationships and serving others brings true happiness. That’s why one of the <a href="http://www.bronnieware.com/blog/regrets-of-the-dying">top regrets</a> of the dying is spending too much time on work. LaVell obviously cared about more than just winning football games.</p><p>Some might say that it’s cute to talk about caring about people and not focusing on winning, but that reality is different. It’s easy to talk about this stuff when you are winning. It’s true, if he hadn’t been a great football coach, he wouldn’t have stayed a coach long enough to have this kind of impact on people.</p><p>I’m not saying that this aspect of leadership excuses excellence and hard work. But I have personally seen the emptiness that comes from winning at the expense of relationships. That optimizes the short term at the expense of the future.</p><blockquote>“… all that has happened to me in my chosen profession is a mere drop in the bucket compared to the truly important things in my life.”</blockquote><blockquote>— LaVell Edwards</blockquote><h3>Conclusion</h3><p>We often talk about qualities of leadership that, while important, distance leaders from those they lead. The greatest legacies are built by those who can see beyond the bottom line. I challenge current leaders to ask themselves:</p><ul><li>How do I show those I lead that I care for them? Do I show them often?</li><li>What is my ultimate goal as a leader? Do those I lead know that goal?</li><li>Am I compassionate towards those I work with, remembering that I can impact how they contribute to their family?</li></ul><p>May we lead in a way that builds people (which in turn builds truly great businesses, departments, products, and football teams).</p><p>Want to go from unsure to unstoppable as a leader? <a href="https://ryanseamons.substack.com/">Join my weekly newsletter</a> to learn about leading teams, building products, and finding joy.</p><figure><a href="https://ryanseamons.substack.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yiFgiM1SIAyjgbfNbSkiw.png" /></a></figure><h4><strong>Additional Reading</strong></h4><ul><li>RIP to BYU’s LaVell Edwards, who built college football’s unlikeliest champion (<a href="http://www.sbnation.com/college-football/2016/12/29/14116042/lavell-edwards-byu-football-coach">http://www.sbnation.com/college-football/2016/12/29/14116042/lavell-edwards-byu-football-coach</a>)</li><li>Prepare for a Mission (speech by LaVell, <a href="https://www.lds.org/general-conference/1984/10/prepare-for-a-mission?lang=eng&amp;_r=1">https://www.lds.org/general-conference/1984/10/prepare-for-a-mission</a>)</li><li>Manage Compassionately (Jeff Weiner, <a href="https://www.linkedin.com/pulse/20121015034012-22330283-managing-compassionately">https://www.linkedin.com/pulse/20121015034012-22330283-managing-compassionately</a>)</li><li>The Art of Conscious Leadership (Jeff Weiner, Wisdom 2.0, 42 minutes, <a href="https://www.youtube.com/watch?v=2x0fOLqj2Zw">https://www.youtube.com/watch?v=2x0fOLqj2Zw</a>)</li></ul><p><strong>Check out my other articles</strong></p><ul><li><a href="https://medium.com/@ryanseamons/why-you-need-to-focus-on-more-than-speed-to-get-results-4db6e11ab46a">Why You Need to Focus on More Than Speed to Get Results</a></li><li><a href="https://medium.com/@ryanseamons/the-best-way-to-build-an-effective-product-roadmap-sprintwell-e55b01b489a">The Best Way to Build an Effective Product Roadmap — Sprintwell</a></li><li><a href="https://medium.com/@ryanseamons/how-my-9-year-old-daughter-prototyped-a-food-truck-concept-7845799724b9">How My 9-Year-Old Daughter Prototyped a Food Truck Concept</a></li><li><a href="https://medium.com/@ryanseamons/the-costanza-effect-rock-your-next-interview-with-this-insider-tip-from-the-audition-for-george-b7b8ae521508">The Costanza Effect - Rock your next interview with this insider-tip from the audition for George…</a></li><li><a href="https://medium.com/hackernoon/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c">9 lessons product teams can learn from Formula 1 pit stops</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19aee7c3dac2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Need to Focus on More Than Speed to Get Results]]></title>
            <link>https://ryanseamons.medium.com/why-you-need-to-focus-on-more-than-speed-to-get-results-4db6e11ab46a?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/4db6e11ab46a</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 18:19:01 GMT</pubDate>
            <atom:updated>2019-08-23T16:29:03.337Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/868/0*uE-2qPWQW-aBS9qL.jpeg" /></figure><p>If you’re feeling burnt out by your team’s lack of progress, you’re not alone. We know from our own experience how frustrating it can be to feel stuck in one of two worlds:</p><ul><li>Struggling to gain speed with slow decision making or productivity</li><li>Trying to stay focused when everything is a priority</li></ul><p>Whether you experience one or both of these issues, they can block you and your team from high performance.</p><p>While identifying the source of friction is important, it’s only half the battle. Knowing what to do about it and how to get started are key to accelerating high performance in your team.</p><p>From experience building and running teams at LinkedIn, Degreed, and Sprintwell, I’ve made plenty of mistakes on my road to finding patterns that work. To help you understand the best way to get comprehensive results, I’ll cover:</p><ul><li>The negative practices that hold teams back from success</li><li>What you need to focus on instead to get results</li><li>What steps you can take to make meaningful progress</li><li>How to get started now</li></ul><h3>What’s Blocking You from High Performance?</h3><p>The challenges listed above are frustrating, but they are not the real problems. Slow decision making, burnout, and competing priorities are the <em>symptoms</em>. What really blocks teams from high performance is either:</p><ul><li>Lack of alignment</li><li>Lack of speed</li></ul><p><strong>Lack of alignment</strong> comes from people issues (this is the most common), an incoherent strategy, or a strategy that has not been committed to and written down. Usually, this becomes evident when team members do not know what to align on or someone goes against the grain.</p><p><strong>Lack of speed </strong>comes from poor habits and systems, lack of skills, lack of empowerment, and lack of motivation or engagement.</p><p>But when teams get this right (alignment + speed), their progress is fast, meaningful, and focused.</p><p>We call this <strong>team velocity</strong>, and it’s essential to high performance.</p><p><em>Side note: Team velocity is different than velocity in scrum. Velocity in scrum is a measure of the amount of work a team is capable of completing. It’s usually measured in story points.</em></p><p><em>Velocity in scrum can be helpful in providing a visual for teams as they think about how much work to commit to and if they are improving throughput as a team. But this can also be destructive as it’s easy to manipulate points and focus on output over outcome.</em></p><p><em>This highlights two ways we see teams fail to achieve velocity-focusing on speed and outputs as the only indicators of progress.</em></p><h3>Why Team Velocity is More Important than Speed</h3><p>Business team velocity is about the real progress your team makes.</p><p><strong>Velocity = Speed + Focused Direction</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NEgAYBdJvlhnnPbr.png" /><figcaption>Shout out to <a href="https://fs.blog/2018/03/speed-velocity/">Shane Parrish</a> for the idea of this way to visualize speed vs velocity</figcaption></figure><p>It’s about delivering value and impact, not just output.</p><p>When a team’s performance is measured by speed or outputs (or both), they rarely get the end result they want. This is because neither one delivers value by itself. You can go fast around a track but make zero progress. You can ship plenty of features for your product, but not deliver anything of value.</p><p>Yet teams need to have speed <em>and</em> focused direction.</p><p>A team making a high impact on the business has high velocity. A team not making any progress (or worse, creating additional rework for other teams) is operating with low velocity.</p><p>And while struggling to move quickly is certainly a serious issue for many teams, we’ve found that lacking <em>focused direction</em> is where most teams struggle when it comes to high performance.</p><p><strong><em>Do you know your team’s velocity? </em></strong><a href="https://www.sprintwell.com/velocity-quiz"><strong><em>Take our free quiz →</em></strong></a></p><h3>Aligning your team on a focused direction</h3><p>As <a href="https://fs.blog/2018/03/speed-velocity/">Shane Parrish articulates so well</a> about individuals, direction has a lot to do with what you say ‘no’ to. A good strategy is as much about what a team <em>won’t</em> do as what they will do.</p><p>Always saying ‘yes’ is the path to mediocrity.</p><blockquote><em>“People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. I’m actually as proud of the things we haven’t done as the things I have done. Innovation is saying ‘no’ to 1,000 things.”</em></blockquote><blockquote><em>Steve Jobs</em></blockquote><p>This is what makes alignment on your strategy so powerful (and necessary).</p><p>It gives you the clarity you need to make decisions quickly and cut through the noise of tasks and projects competing for your attention.</p><p>Yet even once you’ve crafted a focused strategy, it’s easy to assume your whole team is aligned when they aren’t. And even after you have gotten initial alignment, you have to work really hard to stay aligned.</p><p>When I worked at LinkedIn, the CEO (Jeff Weiner) had a practice that worked magic for keeping teams aligned.</p><p>Every two weeks we had a company all-hands meeting. I usually attended in-person, but everyone around the world could join by video. Without fail, he would cover the same points each week:</p><ul><li>People</li><li>Product</li><li>Monetization</li></ul><p>He was religiously consistent about touching on these priorities, usually sharing the same metrics week over week. Because I was involved in upskilling leaders on the people development team, I heard Jeff train dozens of times about management lessons he’d learned.</p><p>One of my favorites was that by the time you are sick of saying something, your followers are just beginning to understand.</p><blockquote><em>“As organizations mature, the job of any senior executive is about coaching and strategy.”</em></blockquote><blockquote><em>Jeff Weiner</em></blockquote><p>Getting aligned and staying aligned are the main jobs of a leader.</p><p>In the same way, being married doesn’t automatically mean you always love each other, so being aligned with your team at one point doesn’t guarantee perpetual alignment. With relationships, you need to invest time and energy to stay in love. Lasting love isn’t a result of happenstance.</p><p>Likewise, strategic alignment doesn’t just happen. You have to invest time and energy in re-clarifying and re-communicating often.</p><p>Here are four practices we use in our <a href="https://sprintwell.com/">Strategy Sprints</a> to help our clients find and keep alignment.</p><h4>1. Setting up shared norms</h4><p>Any experienced sprint facilitator understands the power of shared norms.</p><p>A sprint is like a game. It’s a step out of your normal day-to-day activities and environment. Setting up clear ground rules for how the team will interact is a must-have for getting the results you want.</p><p>These include decisions about who acts in what role (decider, facilitator, team member) as well as behavior during the day. Some of our norms for sprints include:</p><ol><li>No distracting technology</li><li>Give constructive feedback using “I like …, I wish …, I wonder.”</li><li>No silent detractors</li><li>No armchair sprinters</li></ol><h4>2. Setting aside time</h4><p>When we work with teams, we often hear someone say, “Wow, I can’t believe we haven’t taken time to talk about these things.” It’s easy to get caught in the daily work that consumes your attention. Pulling up to talk about important but non-urgent things is hard.</p><p>It requires intentionally setting aside time to discuss what’s going well, what desired outcomes matter most to your team, problems that are most pressing, or what principles you believe should guide the team.</p><p>This is one reason for doing a burst of focused activity in a sprint is beneficial. Sprints give you permission to take a step back and answer these questions. They allow you to decide on a focused direction and get everyone aligned.</p><h4>3. Creating space for dialogue</h4><p>Conversation is important. It fosters shared understanding and encourages all members to contribute.</p><p>But it’s easy to only allow for monologue.</p><p>Monologue happens when you rely on robust documentation and don’t have safe forums for discussion. When you allow the loudest people in the room to dominate the conversation. And when decisions are made by those at the top with little or no input from those on the front lines.</p><p>Alternatively, sprints are sanctuaries for true dialogue. And I’m not talking about endless group discussion here. Ironically, the constraints during sprints around who talks and when actually encourages richer dialogue.</p><p>This is similar to the forcing function of <a href="https://www.linkedin.com/pulse/beauty-amazons-6-pager-brad-porter/">Amazon’s 6-pager approach</a> to meetings. Taking time to write a document before meetings and then taking time to read it at the beginning of meetings makes for richer meetings.</p><h4>4. Encouraging “Both + And” thinking, not “Either + Or”</h4><p>All too often we think of a decision as a dichotomy. You either have to choose one or the other. If you’re right, that means I have to be wrong. While this does describe some situations, far more often we can use Both + And thinking.</p><p>Instead of saying “No” or “But,” you add to what’s good about what someone has said. Example: I like what you’re saying, <em>and</em> I think we can make it better!</p><p>These practices give you space (time + environment) to align. Too often we are rushed, do not include the right people in a productive way, and cut down input that harms both the quality of the work and the motivation of the team.</p><h3>Speed still matters</h3><p>With all this said on the importance of focused direction, <strong>speed still matters</strong>.</p><p>Hiten Shah <a href="https://producthabits.com/my-billion-dollar-mistake/">missed a billion-dollar opportunity</a> because, after initial success with KISSmetrics, they moved too slowly.</p><blockquote><strong>Speed really does matter.</strong></blockquote><blockquote><em>“You can’t just capture the market once and expect to keep it. You have to do it over and over again and faster than everyone else if you want to keep distance from competitors coming up behind you and disrupting you. That’s how you get ahead of the market.”</em></blockquote><blockquote>Hiten Shah</blockquote><p>When you sprint (whether a 4-day design sprint, a 3-hour brand sprint, a 2-day strategy sprint, or a weekly agile cadence), speed matters.</p><p>But we humans aren’t naturally very time aware. This explains why one <a href="https://www.ics.uci.edu/~gmark/chi08-mark.pdf">UC Irvine study</a> found that it took an average of 23 minutes to return to a task when you get distracted. Setting a timer and having a facilitator help.</p><h4>Setting a timer</h4><p>Time-boxing is one way we encourage speed.</p><p>We will naturally take an allotted time and fill it with work. That’s why when given an hour meeting, it’s typical to take the full hour. A good way to speed up work is to break it up into smaller chunks and time-box getting those chunks done.</p><p>When I need to go fast on personal projects, I use the Pomodoro technique. It’s one of my favorites for personal productivity. If you aren’t familiar, I encourage you to learn about it. You pick one task, set a timer for 25 minutes, and focus on that task. When the timer rings, you get a 5-minute break. Then you repeat. Take a longer break after four Pomodoros.</p><p>A sprint is similar. You break tasks down and time-box each one. It’s amazing what you can do with a series of 15–60 minute activities. The time-boxed nature keeps everyone mindful about the clock and discourages irrelevant tangents. It helps create the urgency you want.</p><p>To help keep a group aligned on time, we use a <a href="https://www.timetimer.com/">time-timer</a> in sprints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wLVeh5evCSxEktyd.png" /></figure><h4>Designating a Facilitator</h4><p>A facilitator helps a group move quickly. This is one way we work with companies-through facilitating sprints. Product management done well is a lot of facilitation. PMs keep track of the necessary moving parts, help everyone know where everything is at, and encourage people to participate or pipe down at the right times in the product development process.</p><p>One way to think about this role is that they are the driver. It doesn’t mean they are calling all the shots, but they are responsible for forward movement. They have their hands on the wheel.</p><p>Having a single, identified driver is a critical element of speed. Group driving usually ends in a mess and happens often when roles are not well defined.</p><p>Here are some practical steps you can take to increase your team velocity immediately.</p><h3>Identify sources of friction</h3><p>When you’re feeling burnt out and frustrated, it can be difficult to identify exactly what’s causing the most trouble.</p><p>Set aside time to think through your team’s speed and direction. Where are your biggest challenges? What have you tried to fix it already?</p><p>If you’re not sure where to begin (or don’t have enough downtime because you’re too busy putting out fires!🔥), try taking our <a href="https://www.sprintwell.com/velocity-quiz">free Velocity Quiz</a>. It’s an effective tool for quickly identifying blockers, and we send you a custom report when you’re done.</p><h3>Get alignment on what matters most</h3><p>We’ve already laid out why alignment is so important for your team. A quick way to get started and check the alignment in your team is to go to 5 different front-line employees. Ask them to articulate their understanding of the current strategy.</p><p>“Why are we doing this project?”<br>“Why does this team exist?”<br>“What are we trying to accomplish?”</p><p>The answers are a quick but important data point to show you if you are aligned. If the answers are different (which they all too often are), you need to create and evangelize your strategy better.</p><p>We run 2-day strategy sprints to help executive teams align on strategy. They walk out with a clear, one-page living document that guides their teams. This <a href="https://blog.sprintwell.com/product-roadmap/">strategic roadmap</a> is a communication tool you need to use at every team meeting. Make it visible in a place that every employee can find in under 30 seconds.</p><h3>Know that agile is about mindset + mechanics</h3><p>Most botched agile implementations fail because teams adopt the mechanics of scrum without understanding the mindset of agile. This happens because teams lack experience using agile and/or the company culture is at odds with agile values.</p><p>Read through the <a href="https://www.agilealliance.org/8-reasons-why-agile-projects-fail/">survey results</a> Agile Alliance gathered about failed implementations.</p><p>Leaders need to realize that agile is going to be more of a change for them (especially when it comes to mindset) than it is for their teams.</p><p>If you haven’t read the <a href="https://agilemanifesto.org/">agile manifesto</a>, that’s a good place to start. It’s also helpful to talk to those who have built and run successful agile teams-not just as coaches but as product leaders who have shipped successful products.</p><p>You’ll know you have velocity when your team can clearly answer questions such as:</p><ul><li>Which priorities drive the most value for the business?</li><li>What results are we measuring to positively reinforce our goals?</li><li>How can I make the biggest impact today?</li></ul><p>Teams with velocity don’t just create more impact, they are fun to work on. High-velocity teams happen when each employee is closer to <a href="https://en.wikipedia.org/wiki/Flow_(psychology)">flow</a>.</p><p>If you’re interested in learning more about how you can become a high-velocity team, I strongly recommend <a href="https://www.sprintwell.com/velocity-quiz">taking our Velocity Quiz</a>.</p><p>After identifying key points of friction for your team, we will send you a customized report with action steps you can start taking today. We will also send you the frameworks and tools that we use for ourselves and clients to unlock higher performance and results.</p><p>Did this spark ideas and questions for you? I’d love to hear about them. Reach out to me anytime at <a href="/service/mailto:ryan@sprintwell.com">ryan@sprintwell.com</a>.</p><p><em>Originally published at </em><a href="https://blog.sprintwell.com/team-velocity/"><em>https://blog.sprintwell.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4db6e11ab46a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Way to Build an Effective Product Roadmap — Sprintwell]]></title>
            <link>https://ryanseamons.medium.com/the-best-way-to-build-an-effective-product-roadmap-sprintwell-e55b01b489a?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/e55b01b489a</guid>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-roadmap]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Thu, 25 Jul 2019 07:39:07 GMT</pubDate>
            <atom:updated>2019-08-23T16:30:40.072Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Best Way to Build an Effective Product Roadmap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/0*0WqNTaRPsz8ljql_.jpg" /></figure><p>When working with clients, one topic that comes up frequently is product roadmaps. As a product manager at LinkedIn and director of product at Degreed, I kept the best practices and tips based on what worked for me and the hard lessons I learned.</p><p>But people rarely ask, “How do I build a product roadmap?”</p><p>Instead I hear questions like:</p><ul><li>How do I move this project forward?</li><li>How do I get everyone on the same page?</li><li>How do we get the team moving quickly?</li></ul><p>The answers to these questions start with building an effective product roadmap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qonBWZ8HQcpg8YET.jpg" /></figure><h3>Why You Need a Product Roadmap</h3><p>Before we go into details on <em>how</em> to build an effective roadmap, let’s start with <em>why</em> you need one.</p><p>Done well, a solid product roadmap helps you focus on what is most important. This starts with customer obsession.</p><blockquote><em>“Product roadmaps should come from this idea that you’re actually obsessed with the customer, that you’re looking to solve the problems that your product is supposed to solve for them in a way that’s better than any other business or product or solution or alternative in the market.”</em></blockquote><blockquote><em>- </em><a href="https://www.freshworks.com/saas/uncomplicate-how-to-build-a-product-roadmap-blog/"><em>Hiten Shah</em></a></blockquote><p>This is where product managers come in.</p><p>As you focus on the customer, what problem you solve for them, what pain you alleviate, you need to bring others along.</p><p>Product managers balance relationships with executives, their team, customers, and more. They are asked to lead, make decisions, and communicate across teams.</p><p>With this environment, a product roadmap achieves three key results for you and your organization:</p><p>ProdPad describes a <a href="https://www.prodpad.com/resources/guides/product-management-process/roadmapping/">good product roadmap</a> as “visual, clear and accessible enough for everyone involved to understand.”</p><p>This is critical because of the complex nature of products. Products have many teams involved, a high degree of uncertainty, and the potential for high costs. Communicating simply and clearly in this environment is a must.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8B0k3_uOK9HD0InH" /></figure><p>Kris Gale, VP of Engineering at Yammer, <a href="https://firstround.com/review/The-one-cost-engineers-and-product-managers-dont-consider/">wrote about the high cost of complexity</a> and its challenges.</p><blockquote><em>“Among the most dangerously unconsidered costs is what I’ve been calling complexity cost. Complexity cost is the debt you accrue by complicating features or technology in order to solve problems.”</em></blockquote><p>This is why the best product roadmaps have two key characteristics.</p><p>They are used as <em>strategic communication documents</em>.They help teams make decisions about what they will and won’t do sooner (before committing to costly solutions).</p><p>Second, they are <em>living</em>. This means they are updated often to reflect a current state of the product direction. It also means everyone who views the roadmap understands it is subject to change.</p><p><strong>A living roadmap used as a strategic communication tool enables your team to stay aligned and make better decisions</strong>.</p><p>Unfortunately many roadmaps are too detailed, confusing, or outdated. They function as tactical release plans, and teams get lost.</p><p>I like what Melissa Perri has to say on <a href="https://melissaperri.com/blog/2016/07/14/what-is-good-product-strategy">product strategy</a>:</p><blockquote><em>“Most companies fall into the trap of thinking about Product Strategy as a plan to build certain features and capabilities… The problem is that when we treat a product strategy like a plan, it will almost always fail.”</em></blockquote><p>A product strategy that is only a release plan will fail.</p><p>To avoid this, here’s how to make a clear, concise roadmap that guides you and your team effectively.</p><h3>What Every Product Roadmap Needs</h3><p>So how do you actually build a roadmap that is clear, simple, and effective? I teach managers (yes, this goes beyond just product managers) they only need three sections: why, what, and how.</p><p><a href="https://paper.dropbox.com/doc/Strategic-Product-Roadmap-Template--AhmaP0W5EcU3kpnMSrVQTwU_Ag-oYb5ZVfdjLbI7ml4eJ0iH">Download Our Free Product Roadmap Template</a></p><h3>Section 1: Why</h3><p>This section answers the question, “Why are we building this product?” This is the big vision, the mission, and/or the purpose (those are different things, to be discussed in a future article).</p><p>You want to find a balance between being very aspirational (e.g. solving world hunger) and overly tactical (e.g. “The CEO told us to do this”).</p><p>Unfortunately, many people skip this step, or lose sight of it. They include so many details that everyone forgets <em>why</em> they’re making it. I encourage teams to simplify this into a single customer-focused sentence, and then add some context if needed.</p><p>A <a href="https://medium.com/@charbel/create-compelling-content-for-employees-in-9-words-the-3x3-walkthrough-257b29086bfd">3×3 walkthrough</a> is one approach we advocate.</p><p>This one sentence is powerful. Everyone can understand it, buy into it, and talk about it in a way that is clear and compelling.</p><h3>Section 2: What</h3><p>Product roadmaps are out <em>come</em>-driven. Backlogs and release plans are out <em>put</em>-driven.</p><p>The “what” section of your roadmap answers questions such as, “What outcomes do we hope to drive because of this product?” and “What do we hope changes because of this?”</p><p>These are the business objectives that your product will help accomplish.<br>I recommend including both quantitative and qualitative data to inform this section. For example:</p><ul><li>What do you want users to <em>do?</em></li><li>What do you want users to <em>feel</em>?</li><li>What do you want them to <em>think</em>?</li><li>What do you want them to <em>say</em>?</li></ul><p>When defining “what,” most people focus on outputs (or features) way too fast. Instead, <strong>define the real business value you want your product to drive</strong>. This allows your teams to understand the strategy more clearly and better involves partner teams like sales and marketing in your product’s long term success.</p><h3>Section 3: How</h3><p>The last section is <em>how</em>, which breaks down into <em>themes</em> and <em>timelines</em>.</p><p>I have found the best number of themes is 4–6. These categories simplify the different pieces involved and help your team understand them. They also help guide your priorities and backlog.</p><p>Examples of themes can include:</p><p>Once you have your themes, you want to decide on a high-level timeline. Three categories I recommend starting with include <em>current</em>, <em>near term</em>, and <em>long term</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kqdSx6NPxRnMluKm.png" /></figure><p>While months or quarters seem ideal, they can trap you in commitments to release that you aren’t ready to make. It is better to use more generic terms and talk through the current desired timeline-with the caveat that timing is subject to change. This is a balancing act that depends on your needs, company culture, and other factors.</p><p>As an example, if “search” is a theme and our product doesn’t have this functionality, we could break the timeline down like this:</p><ul><li><strong>Current goal</strong>: Add basic search -or- Enable users to search articles</li><li><strong>Near term goal:</strong> Enable users with basic filtering</li><li><strong>Long term goal: </strong>Enable advanced filtering</li></ul><p>This helps <em>all</em> teams know which features are coming at the highest level and when.</p><p>For example, when your salespeople talk with customers, or support teams check in with developers, this simplified timeline becomes invaluable.</p><p><em>: A disclaimer at the bottom of this section is critical, so that those consuming and using the roadmap realize this isn’t set in stone-it reflects the current direction of the team. This is also why current, near term, long term are good timeline categories, rather than exact dates or quarters. It helps communicate the ever-adjusting nature of the themes and timelines.</em> <a href="https://paper.dropbox.com/doc/Strategic-Product-Roadmap-Template--AhmaP0W5EcU3kpnMSrVQTwU_Ag-oYb5ZVfdjLbI7ml4eJ0iH">Download Our Free Product Roadmap Template</a></p><h3>Why this Model is Effective</h3><p>As mentioned above, some main challenges with products are:</p><p>It’s easy to jump to a solution too soon or overwhelm people with too much information. But building a product roadmap is more than categorizing information.</p><p>The model we’ve laid out for you also <strong>improves communication, sets clear expectations, and enhances productivity</strong>.</p><p>People from all teams can wrap their heads around the product. The summaries make it easy to digest. Regular updates keep it current. All teams and executives have clear expectations about the general timeline. Developers and designers know what is expected of them and can identify which pieces are missing.</p><p>With a visible strategy, it can be questioned by everyone in the process (executives, designers, developers, partner teams) and improved from the ensuing conversation.</p><p>And most importantly, <strong>using a product roadmap as a strategic tool empowers your team to become truly agile</strong> (in mindset <em>and</em> mechanics). People can ask critical questions, shift their focus, and make better decisions on where to spend their time.</p><h3>3 Mistakes to Avoid</h3><p>With all that said, knowing what <em>not</em> to do is just as important as knowing what to do. Here are the three most common mistakes I see people make when creating a product roadmap.</p><h3>Mistake #1: Including too much detail</h3><p>The main problem here is the product roadmap becomes too complex. There are so many details that teams can’t get through it quickly. Sometimes the roadmap is a 40-page slide deck, and no one can concisely relay the purpose of the product.</p><p>This is how I know teams have strayed away from a useful roadmap and created either a run-on sentence of a roadmap or a release plan. They have skipped one of the most important parts-simplicity-and their people can’t digest the information.</p><p>This usually happens because teams don’t have the discipline to say no (which causes run-on product docs), or they center their thinking around solutions too early in the process (and end up with a release plan).</p><h3>Mistake #2: Not defining clear priorities</h3><p>Another mistake I often see is not including clear priorities. The themes and timelines are not well-defined, and communication is poor. People have unrealistic expectations on what can get delivered and when.</p><p>I often seen vision decks that include dozens of priorities. When asked, “Which of these is most important?” the answer is typically, “Well, they are all important.”</p><p>If everything is important, <em>nothing</em> is important.</p><p><strong>This is why I recommend a 1–2 page document with clear, useful themes and timelines.</strong></p><p>These let everyone know what’s currently being working on and sets expectations for the future.</p><h3>Mistake #3: Focusing on solutions instead of problems</h3><p>A final mistake I see often is focusing on solutions instead of problems. We can get married to solutions way too early and focus on shipping features fast.<br>But teams should <em>always</em> start with problems to solve.</p><p>If you become obsessed with a problem vs. a solution, you can say, “Look, I don’t care how we solve it. I just want to solve the problem our users have.” It’s a much better place to be in, and it opens teams up to greater learning and openness to new possibilities.</p><p>As a product manager, this also empowers you to defend your product roadmap-your why, what, and how. It enables you to get people excited and bought-in. You can iterate on solving the right problem and create value for customers and the business.</p><h3>Setting Your Roadmap Up for Success</h3><p>Even if you follow all the steps above, you still need a strong foundation. A critical component to your product roadmap is the data that informs it.</p><p>Without data, it will be hard to make good decisions and get buy-in from everyone involved.</p><p>Here are five steps you can take to make sure you have the strongest foundation possible for your product.</p><h3>1. Talk to Your Users</h3><p>Product managers are champions for solving <em>valuable</em> problems for <em>real</em> users. It’s not always the easiest or most exciting problem, but it should be the most impactful. People pay for products that solve real problems, so this step is critical.</p><p><a href="https://blog.sprintwell.com/design-sprints/">Design sprints</a> (originally developed at Google Ventures) are one way you can test this up front and avoid wasting time and energy on the wrong problem or solution.</p><p>But in order to do this, you must talk to your customers. Learn how they use your product and understand what they want. Join sales and support calls. Keep yourself updated and build a regular habit of learning from them.</p><p>It’s easy to get out of this habit when you are busy with meetings and conversations with stakeholders. But fostering these relationships with users on a regular basis is one of the most important responsibilities you have and will serve you well in the long term.</p><h3>2. Gather Data</h3><p>Next, consider what data you already have. What information from market research, historical sales data, or customer behavior is available?</p><p>As you continue chatting with users, track this information. Gather relevant data, conversations, and other metrics.</p><p>Talk with your executives and learn how they make decisions. Get their input and understand their goals, objectives, and insights. Many of them interact with customers every day and have a unique perspective.</p><p>Gathering this information will empower you to make critical strategic decisions. You will be equipped with more than your intuition, and you won’t be subject to the opinions and whims of everyone involved.</p><h3>3. Align Key Stakeholders</h3><p>Equipped with data, you can start capturing it and reflecting it back to key stakeholders. This allows you start aligning your goals and get buy-in.</p><p>For example, after you write down your one-sentence vision for the product, go to the CEO or head of product. Ask them, “Is this accurate?” Share your conversations with customers and why you think you’re building the product. Give additional context, metrics, and what outcomes you hope to drive.</p><p>Because you have written it down and gathered data first, it will be easier for them to react. They can offer feedback, ask questions, and have a specific conversation with you. You can identify key areas where you are not yet aligned and address them.</p><p>Then, when it’s time to get alignment on the full product roadmap, you have already resolved most concerns. You can confidently say, “Here is the roadmap, and I think we’ve all agreed on it. What questions do you still have?”</p><p>But whether or not you use a sprint to get this initial alignment, roadmaps still require ongoing work. It should be adjusted and updated continually-and that requires continually making sure people are aligned.</p><h3>4. Tie Your Backlog to the Strategic Roadmap</h3><p>Now that you have articulated why your product exists and aligned your teams on the roadmap, it is important to make sure your backlog reflects this.</p><p>There is a lot I could talk about here with how to prioritize your backlog and incorporate user stories. It is a complex process, and everyone has a different ways of doing it.</p><p>But one tip that really helps me is this — <strong>use the priorities in your roadmap as a guide for your backlog</strong>.</p><p>For example, breaking down the stories for the <em>current </em>prototype or sprint will be much more helpful than getting into details further down your backlog.</p><p>If you start breaking down the stories you plan on using later, you end up wasting a lot of time and energy. Realistically, when you are ready to address those features, everything will have changed. Your priorities may be different because you will have learned and adjusted through the process.</p><p>One solution is to group stories based on your themes. You can then add some sub-themes and plan to break them out later.</p><p>This method helps keep me sane, especially when product groups have a backlog that increases from 10 to 20 to 50 to 100 items. I have personally “managed” a backlog with <em>600 items</em> in it.</p><p>But no one can realistically manage that, and it becomes useless.</p><p>Tying the backlog to the main priorities in the roadmap helps alleviate this waste and allows for more flexibility.</p><h3>5. Communicate Well (and Often)</h3><p><strong>Lastly, your product roadmap will only be successful if you communicate well and often</strong>. Agile teams are autonomous, self-organizing, and engaged-meaning they can’t rely on one person to tell everyone else what to do.</p><p>So great product roadmaps and product managers enable all teams-including designers and developers-to contribute what they have to the product in the best way. They empower every person involved at detailed levels to understand the vision and make informed decisions.</p><p>The simplest way to know if you’ve communicated it well is to ask someone what they think the strategy is. Their response will tell you everything you need to know about how well your team is centered strategy-wise.</p><p>Strategy isn’t just what you have written down somewhere. It’s what everyone remembers and uses to make daily decisions.</p><p>In the end, <strong>a product roadmap done well enables agile behavior</strong>. This is because it’s not a release plan-it’s a strategic communication document.</p><p>Knowing how to create a roadmap, you’re ready to get alignment across your organization and empower your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c970kQk5TL0x7hw6.jpg" /></figure><p>Join <a href="https://ryanseamons.com/">my monthly newsletter</a> where I share practical links and advice from what I learn about product and parenting. Reach out to me on <a href="https://linkedin.com/in/ryanseamons">LinkedIn</a> or <a href="https://twitter.com/ryanseamons">twitter</a> and let me know how building roadmaps works for you.</p><p><em>Other great resources you might enjoy:</em></p><ul><li>“<a href="https://www.prodpad.com/resources/guides/product-management-process/roadmapping/">What is a product roadmap?</a>” by ProdPad</li><li>“<a href="https://medium.com/@stewart/we-dont-sell-saddles-here-4c59524d650d">We don’t sell saddles here</a>” by Stewart Butterfield</li><li><a href="https://www.amazon.com/Product-Roadmaps-Relaunched-Direction-Uncertainty/dp/149197172X/">Product Roadmaps Relaunched</a>, the best book on product roadmapping, which has helped me better create and use roadmaps.</li></ul><p><em>Originally published at </em><a href="https://blog.sprintwell.com/product-roadmap/"><em>https://blog.sprintwell.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e55b01b489a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How My 9-Year-Old Daughter Prototyped a Food Truck Concept]]></title>
            <link>https://ryanseamons.medium.com/how-my-9-year-old-daughter-prototyped-a-food-truck-concept-7845799724b9?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/7845799724b9</guid>
            <category><![CDATA[food]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Thu, 30 Aug 2018 21:21:45 GMT</pubDate>
            <atom:updated>2019-07-26T18:35:15.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VqL0A_1DZb-MZTOVXXHlw.png" /></figure><p>Have you ever had an idea that you just keep thinking about? Something that should exist in the world? Ever since living in Thailand, one of those ideas for me is a Bangkok street food experience created as a Thai restaurant.</p><p>Whatever your idea is, <a href="https://blog.sprintwell.com/decision-making-deadlock/">knowing how to move forward</a> can be tricky. Many people, including myself, often end up choosing to do nothing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*a0chlcJUZre6cRDx.gif" /><figcaption><a href="http://wondermark.com/541/">http://wondermark.com/541/</a></figcaption></figure><p>Prototyping is a real way to move forward. Building a prototype and testing it with users is the pinnacle of the <a href="https://blog.sprintwell.com/design-sprints/">Design Sprint</a> experience. But how do you prototype an idea? Especially one that isn’t just some digital app you can get a designer to whip up?</p><h4>Background</h4><p>12 years ago I lived in Thailand for 2 years as a missionary. I lived with Thai people, learned to speak Thai, and ate lots of yummy Thai food. I also learned how to cook a few Thai dishes.</p><p>Once I was back in the states, I made Thai food every few months as a fun experience to share with family and friends. And I had the first seed of an idea for a Thai restaurant that would be fun and unique.</p><p>Fast forward a few years and I rarely made Thai food. We realized while I loved cooking and eating Thai food, we didn’t make it often because it took some unique ingredients and was always hard to remember the details of how to cook the dishes, since it was so infrequent.</p><p>My wife and I wanted to change that. We decided to start making Thai food every Sunday as a family. 5 years later, I have cooked hundreds of Thai meals. This tradition creates opportunities to help my children experience a different culture and share something that’s important to me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E43eYYQxKVTQ3if2.JPG" /></figure><p><em>*Our favorites are Thai fried pork, massaman curry, cashew chicken, pad thai, pad mamas, pad gra praw, waterfall beef, and(my favorite desert in the world) mango and sticky rice. Always with Jasmine rice and sticky rice.</em></p><h4>Concept</h4><p>I noodled on the concept of a Thai restaurant for years. I shared it with some family members. Adjusted it a bit as I saw new inspiration. But always knew this was a some-day idea. And, like any parent, I’ve projected my desires onto my children. My oldest daughter, Kamryn, loves Thai food just like me.</p><p>I had a theory that Bangkok street food (อาหารตามสั่ง) would do very well as a restaurant in the US. Similar to Cafe Rio (popular local favorite in Utah), but Thai. Fresh ingredients, cooked in front of you, into a stir fry dish, for an experience that mimics the magic of a Thai market.</p><p>My daughter was thinking about what to sell at the upcoming <a href="http://www.childrensentrepreneurmarket.com/">Children’s Entrepreneurship Market</a>. I suggested people might enjoy Thai food. The past markets had little or no real food. And in Utah, kids don’t need food permits (thank you <a href="https://libertasutah.org/">Libertas</a>). This became the perfect prototype for a Thai Restaurant.</p><p>KamThai was born.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*aUQSGj9BRRcPzso2.png" /></figure><h4>Why Prototype</h4><p>Prototyping is all about creating enough to test.</p><p>A prototype is powerful when you watch users interact with it. It just take 5 users to get solid feedback. A prototype can help you check and question assumptions, get a feel for real user willingness to pay, and give you confidence that something will work.</p><p>It also worked perfectly for this Thai restaurant concept, since I don’t want a restaurant to be my main income (for that, I’ve co-founded Sprintwell, design sprints as a service). But I’ve thought about this concept for years. And I finally got a chance to test the concept out.</p><h4>Preparation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QZRsy-XjuySOib15.jpg" /></figure><p>I wasn’t in charge of the execution, since it was Kamryn’s Children’s Entrepreneurship Market shop. This was actually perfect since, given no constraints, I probably would have taken far more time worrying about unimportant details. We had a deadline and that pushed us to make decisions.</p><p>This worked as a great prototype because we didn’t have to worry about some larger pieces (getting a food truck or restaurant space, getting through the legal requirements to actually set up a restaurant, big marketing pushes, a website …). It let us see how people would react to Thai food being cooked in front of them. Would they actually pay? What questions would they ask?</p><p>We decided on a name (KamThai กมไทย — Kamryn + Thai). We decided on a menu (massaman curry with jasmine rice, Thai fried pork with sticky rice). We got a list of ingredients and other supplies.</p><p>The day before we did a lot of prep work. We decided on pricing ($5 for a bowl of massaman curry and $5 for 3 pork skewers and a bag of sticky rice). We also bought the ingredients and borrowed supplies.</p><p>Then we stayed up until midnight the night before getting the pork cut for marinating. We were really excited to see how it would go. I kept telling my daughter that I could finish cutting the pork and she could go to sleep, but she kept saying “No, I want to finish this!”<br>Working on real things brings excitement.</p><h4>Results</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5l7axrjGQ993Cmz3.JPG" /></figure><p>The results were fantastic.</p><p>My daughter grossed $260 from 3 hours of selling (with $90 of supplies). She sold out of Thai pork and sticky rice about halfway through and we had a line of 12 more people wanting to buy (if you want to make people angry, just tell them the meat on a stick is sold out). We had just a bit of massaman curry left at the end.</p><p>Some of our favorite questions/comments:</p><ul><li>“Do you have a restaurant?”</li><li>“This would make for an <em>awesome</em> restaurant”</li><li>“Wait, <em>you</em> made this?”</li><li>“Ooh. This smells so good.”</li><li>“I love seeing you cook!”</li><li>“Can we get 7 more?”</li><li>“This is amazing!”</li></ul><p>Some comments we’re going to adjust for next time:</p><ul><li>“If you had chicken skewers, I would buy 10.”</li><li>“The massaman curry veggies aren’t cooked enough”</li><li>“Can you cook this pork a little more.”</li><li>“Is there a vegetarian option?”</li><li>“You’re all out?”</li></ul><p>Cooking food in front of people brought attention and excitement. And, of course, people love meat on a stick.</p><p>While this was a success for us, good principle to remember is that it’s ok (and common) for prototypes to fail. A prototype is meant to learn from, not succeed from. It’s a small test so that you can take the failure.</p><p>For my daughter, I told her that if the idea tanked, I would cover her costs, helping her handle the risk. Always good to get cover from you leaders so that failure isn’t devastating. Learning from failure is a key part of psychological safety that is so key to high performing teams.</p><h4>Adjustments</h4><p>For the next test, we’re changing some things based on customer feedback and parts we found cumbersome.</p><ul><li>In addition to pork skewers, we’re going to cook chicken and veggie skewers</li><li>We’re going to use a propane griddle instead of an electric one</li><li>We’re not going to serve massaman curry (which means we don’t need electricity and we only need sticky rice).</li><li>We’re going to have a better system to timing how long skewers need to cook and then use a part of the griddle just for warming.</li></ul><h4>Takeaways</h4><p>What can you do to prototype your next idea, especially if you aren’t a designer by trade or the concept isn’t digital?</p><ul><li><strong>Just move forward</strong>. Doing something is better than nothing. I’d talked about the concept of a Thai restaurant for a long time. This was a concrete way to do something.</li><li><strong>Build a small piece</strong>. Think about how you could do something small that would give users a taste of the real experience. A 3 hour market is much smaller than buying a food truck. We originally wanted to make more dishes, but settled on just 2.</li><li><strong>Think about the job to be done and use a prototype to check</strong>. Clayton Christensen’s <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">job to be done model</a> is one of my favorites. Make sure you write down what you think the job is that customers will hire your product for. Create a prototype to test that thought. We thought meat on a stick and Thai curry was perfect for what people wanted at dinner time. We also thought that seeing food cooked in front of you would attract interest (something else people are looking for at a market).</li><li><strong>Don’t worry about being perfect</strong>. Done is better than perfect. We did some things we weren’t sure would work. We’d never used an electric generator before. But we researched what we could, then pressed forward.</li><li><strong>Seek mentors and experts</strong>. My daughter leaned on me throughout the process. So many successful entrepreneurs talk about how others helped them through parts of their journey. Also use articles, videos, and books to tap into experts you couldn’t normally talk to. Kamryn and I found a <a href="https://www.youtube.com/watch?v=vz5lsC6uhfc">youtube video</a> about authentic Thai Pork to check if we’d been making it right. It helped us make some small adjustments to the recipe.</li><li><strong>Have fun</strong>. One of the best indicators about your ability to continue forward with a concept is excitement. You’ll need some excitement to get through the hard parts. Every idea will have some grind when it comes to real execution. Most jobs aren’t as glamorous as they seem. Seeing if you maintain excitement at times during your prototype is key to checking if this could become something you put even more time into. This is a lesson I’ve written about before from <a href="https://medium.com/@ryanseamons/the-costanza-effect-rock-your-next-interview-with-this-insider-tip-from-the-audition-for-george-b7b8ae521508">Jason Alexander and the audition for George Costanza</a> — just having fun is a great way to actually perform at your best.</li></ul><p>I’m excited to see KamThai launch as a full food truck and/or casual dining restaurant in the future. In the mean time, we’re going to run our next test in about a month and continue to enjoy the making journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*pjNoGwIMz3_64uJz.png" /></figure><p>Join <a href="https://ryanseamons.com/">my newsletter</a> where I share practical links and advice from what I learn about product and parenting. Also reach out to me on <a href="https://linkedin.com/in/ryanseamons">LinkedIn</a> or <a href="https://twitter.com/ryanseamons">Twitter</a> to say hello.</p><p><strong><em>→ LIKED THIS? You can help others find it as well:</em></strong> Please, feel free to share this post <strong>and to clap it</strong> <em>(up to 50 times)</em> if you found this helpful.</p><p>FYI: <a href="https://blog.sprintwell.com/food-truck-prototype/">this article originally appeared on Sprintwell</a></p><p>Other articles you may like …</p><ul><li><a href="https://medium.com/@ryanseamons/the-costanza-effect-rock-your-next-interview-with-this-insider-tip-from-the-audition-for-george-b7b8ae521508">The Costanza Effect - Rock your next interview with this insider-tip from the audition for George…</a></li><li><a href="https://medium.com/@ryanseamons/the-best-productivity-tip-i-know-has-nothing-to-do-with-todo-lists-or-calendars-bf263fdc631a">The best productivity tip I know has nothing to do with todo lists or calendars</a></li><li><a href="https://hackernoon.com/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c">9 lessons product teams can learn from Formula 1 pit stops</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7845799724b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The best productivity tip I know has nothing to do with todo lists or calendars]]></title>
            <link>https://ryanseamons.medium.com/the-best-productivity-tip-i-know-has-nothing-to-do-with-todo-lists-or-calendars-bf263fdc631a?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf263fdc631a</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[hacks]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 16:18:48 GMT</pubDate>
            <atom:updated>2019-07-26T18:36:46.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2WTEqyRQxaxCzla7" /><figcaption>Photo by <a href="https://unsplash.com/@anohin?utm_source=medium&amp;utm_medium=referral">VITALIY ANOKHIN</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’m writing this because multiple people have told me they’ve loved this tip after I told them about it. It’s the best kept secret to productivity for the productive-impaired. This can help you even if you don’t use a todo list well (which, let’s be honest, most of us don’t).</p><p>The best todo lists are in calendars. Why? Because you already carve space for them.</p><p>But many ‘todos’ are more nebulous and are tasks only the super productivity geeks would really write down and follow through. Generic research, for instance. “Look into this thing” type stuff. You could write down “research task x for 25 minutes”, but reality is most people aren’t that organized. So instead of organizing your life like David Allen, here’s an extension that makes for a cleaner daily workspace and timely reminders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/311/0*9glwVK6haGf9atSp.png" /></figure><p><a href="http://www.tabsnooze.com/">Tab Snooze</a> is my most actively used extension (which is saying a lot, since I have 78 extension I currently use in Chrome).</p><p>Tab Snooze lets you snooze any tab so that it comes back at a later date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/335/1*y9TTCByF36jZPw3yDkF9kA.png" /></figure><p>And you can see what tabs you have snoozed for when.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*j6hhD0XbeCjq37_3hGEZwg.png" /></figure><p>Here’s what I use <a href="http://www.tabsnooze.com/">Tab Snooze</a> for:</p><p><strong>Reminders</strong></p><ul><li>Bring my yearly goals up each day. Every morning I have a tab that lists my goals. Some days I close it. More often than not, I read through them. That type of reminder is powerful.</li><li>Monthly expenses that I cannot automate or want to check on each month</li><li>Articles or sites I want to talk to about with a specific person next time I see them. (Snooze until I’m in the office, snooze until right before my 1:1)</li><li>Reminder to check on social media at a certain time (LinkedIn, Twitter, Facebook)</li></ul><p><strong>Learning</strong></p><ul><li>Sites I want to use every so often (learning, book review, lynda.com, the Seth Godin course on value that I bought from Udemy)</li><li>Articles I can’t read right now but want to read shortly</li><li>For learning follow up. When I finish a book, I write down key takeaways in a doc, then snooze it for a month. A month later, I have a 1 minute read through to remember what I learned.</li></ul><p><strong>Todos</strong></p><ul><li>Todos on the web I want to deal with tomorrow. I don’t want to write down what it is. That takes a number of steps.</li><li>Ideas/articles/todos for my weekend. I don’t need a Saturday todo list. I just need to snooze a tab until Saturday. It comes up and I deal with it when I open my computer on Saturday.</li></ul><p>This works well if you’re someone who, like me, opens your computer often. I have a home office and do my work and hobbies on a computer, so I’m on it multiple hours a day. Having those tabs come up when needed is great.</p><p>Between <a href="http://www.tabsnooze.com/">Tab Snooze</a> and <a href="https://getpocket.com/">Pocket</a>, I can keep my tabs semi-clean and my time focused.</p><ul><li>This is not some sort of paid plug. I just really like TabSnooze.</li></ul><p>Join <a href="https://ryanseamons.com/">my newsletter</a> where I share practical links and advice from what I learn about product and parenting. Also reach out to me on <a href="https://linkedin.com/in/ryanseamons">LinkedIn</a> or <a href="https://twitter.com/ryanseamons">Twitter</a> to say hello.</p><p><strong><em>→ LIKED THIS? You can help others find it as well:</em></strong> Please, feel free <strong>clap it</strong> <em>(up to 50 times)</em> if you found this helpful.</p><p>Other articles you may like …</p><ul><li><a href="https://medium.com/@ryanseamons/the-costanza-effect-rock-your-next-interview-with-this-insider-tip-from-the-audition-for-george-b7b8ae521508">The Costanza Effect - Rock your next interview with this insider-tip from the audition for George…</a></li><li><a href="https://hackernoon.com/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c">9 lessons product teams can learn from Formula 1 pit stops</a></li><li><a href="https://blog.usejournal.com/how-i-turned-down-google-and-quit-my-job-dcb8e3bdda49">How I turned down Google and quit my job</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf263fdc631a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Costanza Effect - Rock your next interview with this insider-tip from the audition for George…]]></title>
            <link>https://ryanseamons.medium.com/the-costanza-effect-rock-your-next-interview-with-this-insider-tip-from-the-audition-for-george-b7b8ae521508?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7b8ae521508</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Wed, 25 Jul 2018 12:36:59 GMT</pubDate>
            <atom:updated>2019-07-26T18:37:18.848Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*SnkinzZRLxAWSLB08_Qf1Q.jpeg" /></figure><h3>The Costanza Effect — Rock your next interview with this insider-tip from the audition for George Costanza</h3><p>Did you know the role of George Costanza (from the iconic sitcom Seinfeld) wasn’t supposed to be filled by Jason Alexander? Not only was Alexander not supposed to get the part, but he may have gotten the role <em>because</em> he thought he didn’t have a chance. What he did teaches any interviewee how to show well when it comes to interviews.</p><p>Alexander made his audition a joke. He knew he wasn’t going to get the part — he was up against Jerry Seinfeld’s <em>best friend</em>. Alexander was there so casting could say they looked at someone else.</p><p>Yet that attitude is what landed him the role.</p><p>After entering his audition (which he knew wouldn’t land him the part) and noting only 30 people in the room, he quipped that he didn’t perform for less than 50 people and left the room to recruit others from the hall. Ad-libbing and not taking it too seriously ended up being what made his audition so great.</p><blockquote>“I was as loose as a goose, because I know I’m not getting this.”</blockquote><p>And he got the job.</p><p>Being relaxed is key to elite performance. That’s why <a href="https://www.levo.com/posts/6-successful-athletes-share-their-relaxation-techniques">Olympians have relaxation routines</a>.</p><p>(<a href="https://www.heraldextra.com/entertainment/arts-and-theatre/alexander-the-great-former-seinfeld-star-entertains-at-uvu/article_ba4b86d4-5796-56dc-8e88-00e8fe50efbc.html">Read</a>, <a href="https://www.accesshollywood.com/videos/jason-alexander-dishes-on-his-seinfeld-audition-2004-35631/">watch</a>, or <a href="https://soundcloud.com/howardstern/jasonalexander_audition">listen</a> to Alexander talk more about his story)</p><h3>Don’t Take Yourself Too Seriously</h3><p>The irony is when you really want something, and figuratively tighten your grip, you’re less likely to get what you want. The key is not to rush or panic. Don’t make it too intense. Loosen up. Relax. Just roll with it. Smile. Do all you can not to make it a must-win situation.</p><p>Since you know the outcome (you won’t get the job), why not have some fun? You have a higher chance of getting into flow. You aren’t worried.</p><p>Being relaxed in an interview has helped me in a few job interviews. I didn’t go get more people to come in the room, or get up on a table to read lines, but I was more relaxed.</p><p>I was a sophomore at Brigham Young University and I landed an interview at ARUP Laboratories for a summer internship spot as a bioinformatics consultant. Now, I didn’t know squat. I was barely through my intro programming classes, mostly just taking generals. But I was majoring in bioinformatics and had been very excited to get the interview.</p><p>I checked in at the front desk and sat down in a room with the head of their genetics department. “Ok,” I told myself. “You can do this!” My initial excitement left when, one-by-one, three other interviewers entered the room (another medical director, the head of bioinformatics, and the head of the R&amp;D department). My positive self-talk was gone. I was just waiting for the moment they found out I was a student who didn’t know anything.</p><p>We started talking, and the questions weren’t too bad. They asked me what my definition of bioinformatics was (for those still wondering it’s when you smush biology and computer science together). I gave some basic answer. They asked about what jobs I’d had before. They asked me about the new bioinformatics program at BYU.</p><p>This isn’t going too bad, I thought. I could answer all these questions. But I was still waiting for the hard questions. Then, after a few more minutes of conversation, someone said “Well, if you would be willing to come work for us this summer, here’s what we think would be great about having bioinformatics students in our department.”</p><p>“Are they selling me on coming?” Ends up, they were. I’ve since learned how awesome internships are for companies and students. I loved working with university recruiting at LinkedIn and at <a href="https://sprintwell.com/">Sprintwell</a> we wanted to have a summer intern working with us from the start. With my sudden realization, I relaxed. I was just talking, getting excited, asking questions.</p><p><strong>I’m convinced that had they put pressure on me from the very start of the interview, I wouldn’t have gotten the job.</strong> Thankfully, they helped me feel at ease, and I settled in, landed the job, and ended up having a fantastic summer and continued working with their team through the rest of my undergrad.</p><p>While most interviews won’t go exactly like that, getting in a relaxed mindset is something you can control. Taking off the pressure allows for <a href="https://en.wikipedia.org/wiki/Flow_(psychology)">flow</a>.</p><h3>How this can help in all pursuits (and how I got my daughter to beg me to get her on Khan academy and teach her how to write a book report).</h3><p>A personal example where taking a relaxed approached worked for me.</p><p>My wife and I homeschool our 5 kids. And as we’ve talked about how and what we should teach, we’ve settled on a more relaxed approach. Our main goals are that our kids 1. love learning and 2. learn how to learn. Pretty simple. But this immediately rules out any sort of command and control approach. We can’t force our kids into loving to learn. We have to set up the right environment. We create opportunities.</p><p>When my daughter was entering first grade, we had a decision to make: how do we teach her math? We decided not to push it at all. I want all my kids to learn math and grow in analytical skill. But so many people hate math because it was forced on them. So I simply pulled up Khan academy and said “Hey, let me show this to you.” She watched for a bit, mumbled something, and walked off. I mentioned it a couple more times, but she didn’t really have much interest. So we didn’t make her do match at all that year or the next.</p><p>Fast forward a year and a half. Mid-way through her second grade year she comes into my office and says, “Hey dad. You remember that Khan Academy thing you talked about?”</p><p>“Yeah”</p><p>“Could I do that sometime?”</p><p>(trying not to show too much excitement) “Sure, I’ll get back into your account and we can try it out tomorrow.”</p><p>She ended up spending HOURS watching videos and doing exercises. Over the next few weeks, she easily passed the knowledge she ‘should’ have for her grade level. And she LOVED doing it. She was having fun.</p><p>And it just keeps coming. When my daughter was in 3rd grade, she comes to me again, ‘Dad, I want to write a book report.’</p><p>‘A book report?’</p><p>‘Yeah. I’ve been reading books and haven’t written about them. And my friend says she wrote a book report. So I want to write one.’</p><p>‘Ok. Let’s find an outline and you can write a book report.’ (as I do a happy dance)</p><h3>Why this works</h3><p>Relaxing when it comes to achievement works because you aren’t hand-cuffing mental performance. Without the pressure, you can breathe. You can think. You aren’t feeling that fight or flight stress, which naturally lets you put more energy into the performance instead of fighting against your own physiology.</p><p>Trying to have a date under pressure. Trying to learn under pressure. Trying to interview under pressure. None of those goes as well under pressure as when you’re calmly testing things out.</p><p>You need to be patient. Wait. Relax. Listen. Then move.</p><p>Chris Voss describes multiple examples of this in his book <a href="https://www.amazon.com/Never-Split-Difference-Negotiating-Depended/dp/0062407805/">Never Split the Difference</a> (which I highly recommend).</p><blockquote><em>Voss tells a story of coaching a man in the Philippines through a negotiation with a kidnapper, to save his brother’s life — a high-stress situation if ever there were one. He says, this man “knew his brother might not come out alive and it could well be beyond his control. He simply recognized that was a possibility — and he performed like a star. He saved his brother’s life. Not knowing at the time how he had been able to perform so well under pressure, I asked him about it later. He told me, ‘I just said to myself, That’s a possibility, when I got scared that my brother might not come back to us. It calmed me down.’ ”</em></blockquote><p>Another reason this works is by enabling better <a href="https://en.wikipedia.org/wiki/OODA_loop">OODA Loops</a> (Observe — Orient — Decide — Act). OODA Loops are a concept originating from the <a href="https://www.artofmanliness.com/articles/ooda-loop/">military and fighter jets</a>. It’s the model for how jet fighters win dog fights. Not by being bigger or faster, but by being able to be more agile than their opponent. Do that faster than your competition (or your kids, or your date) and you’ll get what you want.</p><p>Relaxing allows you to more fully engage in OODA loops. Observation is key. Too often we get wrapped up in deciding and acting over and over again. This is what happens when you formulate your answer as the other person is talking. That isn’t listening. It’s deciding and and then impatiently waiting to share your ‘brilliant’ insight.</p><p>So next time you have an interview, realize you might not get it and that’s ok. Take a breath, smile, and enjoy. You’re far more likely to actually land the job (or part).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*K7XBg9uTAMt4tZx3md4dtA.jpeg" /></figure><p>Join <a href="https://ryanseamons.com/">my newsletter</a> where I share practical links and advice from what I learn about product and parenting. Also reach out to me on <a href="https://linkedin.com/in/ryanseamons">LinkedIn</a> or <a href="https://twitter.com/ryanseamons">Twitter</a> to say hello.</p><p><strong><em>→ LIKED THIS? You can help others find it as well:</em></strong> Please, feel free to share this post <strong>and to clap it</strong> <em>(up to 50 times)</em> if you found this helpful.</p><p>Other articles you may like …</p><ul><li><a href="https://medium.com/@ryanseamons/the-best-productivity-tip-i-know-has-nothing-to-do-with-todo-lists-or-calendars-bf263fdc631a">The best productivity tip I know has nothing to do with todo lists or calendars</a></li><li><a href="https://hackernoon.com/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c">9 lessons product teams can learn from Formula 1 pit stops</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7b8ae521508" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 lessons product teams can learn from Formula 1 pit stops]]></title>
            <link>https://medium.com/hackernoon/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c?source=rss-77e77abb3d41------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2e23e22f9c</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ryan Seamons]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 17:17:02 GMT</pubDate>
            <atom:updated>2019-09-10T15:20:25.131Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*TrBxA8HW9w8h5A-sqU-K2Q.gif" /><figcaption>Ferrari F1 Pitstop <a href="https://youtu.be/aHSUp7msCIE?t=30s">https://youtu.be/aHSUp7msCIE?t=30s</a></figcaption></figure><p>Want your product teams to function with the focus of Formula 1 pit crews? It’s magical when you stop wasted time, avoid wasted decisions, and perform at elite levels as a product team.</p><figure><a href="https://ryanseamons.substack.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yiFgiM1SIAyjgbfNbSkiw.png" /></a></figure><p>First, here’s what a great F1 pit stop looks like (23 people changing 4 tires in 2 seconds)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FaHSUp7msCIE%3Fstart%3D30%26feature%3Doembed%26start%3D30%26showinfo%3D0%26rel%3D0&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DaHSUp7msCIE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FaHSUp7msCIE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/43562698adfc645bd548d4112a35013e/href">https://medium.com/media/43562698adfc645bd548d4112a35013e/href</a></iframe><p>Mesmerizing. While product teams have a lot more variability in most of their work, I’ve learned key lessons for product teams from studying formula 1 pit stops. These lessons illustrate why <a href="https://blog.sprintwell.com/design-sprints/">sprints</a> help product teams perform at elite levels.</p><h3>1. Everyone knows their role</h3><p>All team members know their role, what is within their control, and what others depend on them for. No one is standing around wondering what’s going on or how they can contribute.</p><p>Key question: Can you describe your role? What are you accountable for?</p><h3>2. Flow is important</h3><p>Knowing the goal, knowing the process. These are important to get and stay in a state of flow. The perfect pit stop is fluid compared what most of us experience when we need to change a tire — lots of awkwardness, pausing and wondering, obvious that we don’t do this often, etc.</p><p><em>Key question: Where aren’t you fluid? What could you do to better get into flow?</em></p><h3>3. The driver isn’t the star</h3><p>This is about a team functioning as a single unit. Support is critical. HR, IT, marketing … all support functions are critical to building great products. If a pm or dev has to take half a day to fix some benefits issue or has a computer issue that IT can’t get to because they are backlogged, that impacts the team. Just because someone is the driver doesn’t mean others aren’t critical to making sure everything runs smoothly.</p><p><em>Key question: Do you support your support team?</em></p><h3>4. Focus on the right thing at the right time</h3><p>Practice is critical. Everyone knows their job and knows what needs to happen. <a href="https://blog.sprintwell.com/design-sprints/">Sprints</a> give you stability and clear process so that you can focus on the unknown.</p><p>i.e. If you spend hours doing releases, you’re wasting time. There’s a better way (please read any post/<a href="https://hackernoon.com/tagged/book">book</a> on devops). It’s like you’re a pit crew from the 50’s (see the video below).</p><p><em>Key question: Are you wasting time on a process that happens weekly or monthly?</em></p><h3>5. Prioritize</h3><p>“Fewer things, done better” was our mantra at LinkedIn. Easy to say and very hard to do. One key ingredient of great pit stops is only doing a few things. Limit what you’re doing to increase speed and accomplish the goal (get back out on the track). They used to refuel, but no longer do. Removing that step was a major piece of getting to the 2-second pit stops of today.</p><p><em>Key question: What can you stop doing?</em></p><h3>6. Preparation</h3><blockquote><em>A woodsman was once asked, “What would you do if you had just five minutes to chop down a tree?” He answered, “I would spend the first two and a half minutes sharpening my axe.” Let us take a few minutes to sharpen our perspective.</em></blockquote><blockquote><em>— Anonymous Woodsman (not Abraham Lincoln) (</em><a href="https://quoteinvestigator.com/2014/03/29/sharp-axe/"><em>source</em></a><em>)</em></blockquote><p>Toyota made its system great by working on the system. Spending more time on infrastructure is key. That’s what formula 1 pit crews have done exceedingly well. They have the right tools, right training, right communication, etc. Everything has been planned and tweaked. And if someone said “hey, I think I know a way we could do this better,” I am sure everyone would take a second to listen.</p><blockquote><em>“Poor preparation is a lousy excuse for a last-minute selfish frenzy. That frenzy distracts us from doing it right the next time.”</em></blockquote><blockquote><a href="https://seths.blog/2018/06/cold-yeast/"><em>Seth Godin</em></a></blockquote><p>Also related to preparation, great teams use retrospectives. The best retrospectives are small (only the members of a close team) and many times have only the team, not leaders attending. Why? You have to make it safe to bring up flaws. That is a very difficult environment to create. But done well, will yield meaningful improvement in the team.</p><p><em>Key question: What could you prepare that would give you power during performance time?</em></p><h3>7. Make it visual</h3><p>The main job of <a href="https://hackernoon.com/tagged/management">management</a> is safety.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ey28klrADvM39Id_.png" /><figcaption>Williams Martini F1 Pit Stop <a href="https://www.youtube.com/watch?v=tFwcq5lf0wU">https://www.youtube.com/watch?v=tFwcq5lf0wU</a></figcaption></figure><p>These guys are controlling. The crew member at the front is watching everyone do their jobs. He is there to address any problems and control the traffic light. This is similar to the decider in a sprint — they control the light and signal to the rest of the team when needed.</p><p><em>Key question: What could you make visible that is currently assumed or hidden?</em></p><h3>8. Know evolution can happen</h3><p>This 5 minute video shows 13 formula 1 pit stops from the 50s to 2017.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fz6UHgfkbrMU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dz6UHgfkbrMU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fz6UHgfkbrMU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/830c1d51fce4e1eba27b17af6ac93459/href">https://medium.com/media/830c1d51fce4e1eba27b17af6ac93459/href</a></iframe><p>In 1950 the announcer says “Just 67 seconds!” Amazing to think that the best times today are more than 30 times faster. 30x improvement over time may seem crazy, but here’s what Mark Zuckerberg said about the best engineers.</p><blockquote>“Someone who is exceptional in their role is not just a little better than someone who is pretty good. They are 100 times better.” (<a href="https://www.nytimes.com/2011/05/18/technology/18talent.html?_r=2&amp;ref=todayspaper">NY Times</a>)</blockquote><p>Marc Andreessen pointed out something similar —</p><blockquote>“The gap between what a highly productive person can do and what an average person can do is getting bigger and bigger. Five great programmers can completely outperform 1,000 mediocre programmers.” (<a href="https://hbr.org/2011/06/great-people-are-overrated">HBR</a>)</blockquote><p>While something may seem great today, there are major breakthroughs to be made. In 20 years, we will look back on how many product teams function today and laugh at the clunkiness of it all. The best product teams today are already making exponential gains in terms of efficiency and effectiveness.</p><p>This is why growth mindset is key. If we are fixed in our thoughts about what we can do, we may stop at a 67-second pit stop and think we are great. Don’t stop improving.</p><p><em>Key question: Is there something you’re already doing well that you could improve more?</em></p><h3>9. Failure hurts</h3><p>This is what it looks like when done poorly.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZCVcT07YHmU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZCVcT07YHmU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZCVcT07YHmU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fde6d749648fee6921aa565eeddb6489/href">https://medium.com/media/fde6d749648fee6921aa565eeddb6489/href</a></iframe><p>For product teams, we have to be careful talking about failure. Even with elite teams, most product ideas won’t create the results you’re looking for. You actually want a decent failure rate when coupled with a healthy learning and testing culture. That means you’re getting closer to knowing what works.</p><p>The failure you want to avoid on product teams is failure of process. Not that an idea didn’t work. But that it was just executed poorly. A little process, adhered to, can take away the clumsiness of not having a clear problem statement, not involving all functions early enough in the process, getting a top-down edict to build something that’s “already been vetted”, or solutioning too early.</p><p>One last look at what this can be when done well</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FaHSUp7msCIE%3Fstart%3D30%26feature%3Doembed%26start%3D30%26showinfo%3D0%26rel%3D0&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DaHSUp7msCIE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FaHSUp7msCIE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/43562698adfc645bd548d4112a35013e/href">https://medium.com/media/43562698adfc645bd548d4112a35013e/href</a></iframe><p><em>Key question: What does failure of process cost your team?</em></p><p>It’s magical when you stop wasted time and wasted decisions, and perform at elite levels as a product team. Hope these questions are helpful to you and your team.</p><p>If you really want to geek out about this, watch this full breakdown of a pit stop —</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FtFwcq5lf0wU%3Ffeature%3Doembed%26showinfo%3D0%26rel%3D0&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtFwcq5lf0wU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FtFwcq5lf0wU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a1c7bc259864d4cc660fc4723836fc45/href">https://medium.com/media/a1c7bc259864d4cc660fc4723836fc45/href</a></iframe><p>Originally published at <a href="https://blog.sprintwell.com/9-lessons-product-teams-can-learn-from-formula-1-pit-stops/">Sprintwell</a></p><p>Join <a href="https://ryanseamons.com/">my newsletter</a> where I share practical links and advice from what I learn about product and parenting. Also reach out to me on <a href="https://linkedin.com/in/ryanseamons">LinkedIn</a> or <a href="https://twitter.com/ryanseamons">Twitter</a> to say hello.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2e23e22f9c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/8-lessons-product-teams-can-learn-from-formula-1-pit-stops-a2e23e22f9c">9 lessons product teams can learn from Formula 1 pit stops</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>