<?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 Travis Gohr on Medium]]></title>
        <description><![CDATA[Stories by Travis Gohr on Medium]]></description>
        <link>https://medium.com/@emptycontent?source=rss-969fffdd8739------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*z-KX269taD5z8i7IxVYIBw.jpeg</url>
            <title>Stories by Travis Gohr on Medium</title>
            <link>https://medium.com/@emptycontent?source=rss-969fffdd8739------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:13:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emptycontent/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[Design and Product; Making the Relationship Work]]></title>
            <link>https://medium.com/@emptycontent/design-and-product-making-the-relationship-work-df2ee917c3c5?source=rss-969fffdd8739------2</link>
            <guid isPermaLink="false">https://medium.com/p/df2ee917c3c5</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Travis Gohr]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 15:47:04 GMT</pubDate>
            <atom:updated>2018-11-01T17:46:25.649Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design and Product: Making the Relationship Work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HWihcu66Etvy1spjeIAjw.jpeg" /></figure><p>If you’re a designer, you’ve undoubtedly uttered the words, “product managers are the worst” at one point or another. And if you’re a product manager, I’m sure you’ve at least thought, “why are all designers so hard to work with?” a handful of times. This love/hate relationship seems to be a part of our industry that we just have to learn to live with.</p><p>Or do we? I’ve been the lead designer at <a href="https://www.chorus.ai/">Chorus.ai</a> for around six months now and haven’t found myself thinking “I hate product managers” even once! And after talking with our PMs, they’re just as surprised to be having much more positive relationships with our designers than at past jobs.</p><p>This isn’t an accident and we want to share with you our secret recipe for design and product happiness.</p><h3>The Problem</h3><p>I took a quick survey of our product managers and designers that resulted in this list of problems they had previously experienced:</p><p><strong>Problems PMs face with Designers</strong></p><ul><li>Too much focus on the perfect solution instead of an adequate solution</li><li>A lack empathy for the business side of the problem</li><li>Starting work without being aligned on the problem and constraints</li><li>A lack of clear and effective communication as to why a solution of higher complexity is important</li></ul><p><strong>Problems Designers face with PMs</strong></p><ul><li>Ignoring design’s concerns about the user experience</li><li>Focusing on the business needs over the user’s needs</li><li>Being prescriptive about a solution and just wanting the designer to execute it</li><li>Treating the design as a suggestion and modify it independent of the designer</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFD29YFwYPyAIG6SuH_fPg.jpeg" /></figure><h3>The Solution</h3><p>Here’s a quick rundown of the process we’ve been utilizing for our projects:</p><ul><li><strong>Ownership</strong> — The PM and Designer have full ownership of their project. This is important because it allows us to fully explore the problem, all the possible solutions, and own the success or failure of our efforts.</li><li><strong>Problem definition</strong> — The PMs own this step but that doesn’t mean they define the problem alone. They usually make a first attempt at defining the problem being solved then present it to the designer along with any research they’ve collected. The two parties then challenge the problem definition together and see if they can better define it. The problem is continuously challenged until more data and insights are uncovered. This process usually includes collecting feedback from other team members cross-functionally in the organization.</li><li><strong>User definition</strong> — Usually a team would just select the persona at this step, something we also regularly do. Lately, we’ve also started optionally picking a common behavior at this step. For example, we might define the user as customers who are incredibly busy. This is honestly one of the weaker points in our process, something I’ll touch on later.</li><li><strong>Success metric definition</strong> — This metric is what we use to determine if we’ve actually solved the problem. Though this metric needs to be measurable, we don’t require that it be a data point from our product. Once, we used customer success feedback as a proxy to determine if users had stopped requesting a feature.</li><li><strong>Solution</strong> — This step of the process is owned by design but done jointly with the PM, and a lot more open-ended than the previous steps at this point. We purposely didn’t define process here as a way to give the PM and designer the ability to pull from a wide range of processes and tools to help them find the right solution.</li><li><strong>Validation</strong> — We validate early, often, and with as few resources as possible to get an answer. One way we’ve added a bit of process here, is that we clearly define up front what it is we’re trying to learn in validation; the method of validation is then shaped to help us learn as quickly and as in-line with lean methodologies as possible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQW4CiEj6_UgLQvfYnIc4Q.jpeg" /></figure><h3>The Result</h3><p>In theory, this sounds great! But how has this changed the success of our efforts and the interactions between product and design?</p><p>Overall the features we’ve launched with this process have been 82% successful. That’s a pretty outstanding success rate!</p><p>And here are a few team member’s thoughts on how this has shaped our culture:</p><p>“There’s much more collaboration here compared to some of my past experiences. The way we handle and push on problem definition, as a team, makes me as a designer so much more efficient and my end designs better. In my opinion, it’s because my effort goes into solving the right problem for the user, and ultimately, a user problem is a business problem. I love it here!” <a href="https://www.linkedin.com/in/castellanoscarolina"><strong><em>Carolina Castellanos, Designer</em></strong></a></p><p>“The level of collaboration this process fosters, the clear sense of ownership I feel on my projects, it’s lead to better solutions that put the user first. In the past, I’ve worked with too many artificial constraints and come up with subpar solutions. When things work well, they just work! I’ve actually started to take it for granted but that’s because I’ve become so focused on the projects at hand.” <a href="https://www.linkedin.com/in/zmona/"><strong><em>Mona Zhao, PM</em></strong></a></p><figure><a href="https://blog.usejournal.com/meet-journal-d222fce8db1d"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMBwoU5bWkso8M2A1ocS9Q.png" /></a></figure><p>“I think the deliberateness with which we approach projects is why we’ve been successful as of late; overemphasizing clarity on problems and only starting a project if we’re aligned means agreement at the beginning of a project and ultimately design and product teams empowered to own the solution and be successful. It’s been essential in taking opinions out of the solution process. There have been times where we’ve decided not to ship projects and that’s turned out to be really important; knowing that what you ship and invest in has a meaningful impact on users is a common goal shared by design and product.” <a href="https://www.linkedin.com/in/dfacher/"><strong><em>Dominik Facher, Head of Product</em></strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7c3YRNIq4hdvsTkPw-Njbg.jpeg" /></figure><h3>We Still Have Work to Do</h3><p>So far so good! But as the team grows, we’ll need to iterate and add to this process. Here are a few areas we’ve identified that will need work sooner than later:</p><p><strong>Official Personas</strong> — We all have a pretty good understanding of our different personas but we believe more clearly defining them and sharing them with the sales, customer success, engineering, and marketing teams will lead to better understanding of why our solutions look, function, and delight the users the way they do.</p><p><strong>A toolkit for estimating project timelines</strong> — We’re learning that certain variables drastically affect the timeline of a project. We’re putting together a toolkit that will allow teams to better estimate the length of a project before they start.</p><p><strong>A toolkit for problem-solving</strong> — There is in-depth documentation across the internet of the different processes a team can use for solving problems. We want to make an internal collection of these with recommendations on how and when to use them.</p><p><strong>Kickoffs</strong> — We’ve been pretty lax with our kickoffs but recently we’ve introduced a step utilizing crazy 8s as a way to get the team’s biases and assumptions surfaced as early as possible. These are collected by the designer who can reference them later as possible solutions. We need to continue strengthening our kickoffs and finding new ways to increase a project’s success and momentum from day one.</p><p><strong>Surfacing our design system, past designs, and processes</strong> — We’re doing a lot of great work but we’re also starting to find it difficult for the entire team to easily reference all the work that’s been done.</p><h3>We Want Your Feedback</h3><p>How have you shaped the relationship between design and product managers? What’s your ‘secret sauce’ for building a winning product team? If you use any of our processes we’d love to know how it works out for you!</p><figure><a href="https://blog.usejournal.com/meet-journal-d222fce8db1d"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2IVAl0TbsfES9cFGYr40g.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df2ee917c3c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>