<?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 Stephen W. Webster on Medium]]></title>
        <description><![CDATA[Stories by Stephen W. Webster on Medium]]></description>
        <link>https://medium.com/@swwebsterdesign?source=rss-2cc51693df1f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DoVAMG55pq5QLfXYvXVxsg.png</url>
            <title>Stories by Stephen W. Webster on Medium</title>
            <link>https://medium.com/@swwebsterdesign?source=rss-2cc51693df1f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:16:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@swwebsterdesign/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[Product Design Teams: Shipping designs can’t be your only success metric]]></title>
            <link>https://medium.com/@swwebsterdesign/product-design-teams-shipping-designs-cant-be-your-only-success-metric-51b8c824e89?source=rss-2cc51693df1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/51b8c824e89</guid>
            <category><![CDATA[design-maturity]]></category>
            <category><![CDATA[design-metrics]]></category>
            <category><![CDATA[product-design-team]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-team]]></category>
            <dc:creator><![CDATA[Stephen W. Webster]]></dc:creator>
            <pubDate>Tue, 02 Jan 2024 15:58:42 GMT</pubDate>
            <atom:updated>2024-01-02T15:58:42.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A dart board with two darks hitting the bullseye (center of the dart board)." src="https://cdn-images-1.medium.com/max/1024/1*aJjSXlBGqzEWzdhfOE2EsA.png" /><figcaption>Photo by <a href="https://unsplash.com/es/@javaistan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Afif Ramdhasuma</a> on <a href="https://unsplash.com/photos/jl4BQJs87Do?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You’ve probably been there before: the design or project you’ve been working on for the last few weeks or months isn’t going to get shipped. Priorities or the roadmap changed, budgets got cut, or the development team couldn’t contain it. And while it might be disappointing, there’s a significant silver lining to investigate: pay close attention to why your project was shelved or deferred, and notice how often that happens in your design organization.</p><p>Early on in my career, I was very disappointed when this happened because I put a lot of emphasis on seeing my work get implemented and start benefiting users. And I’ve noticed this same behavior with other young designers on my team. When you’re just beginning in design, it <em>is</em> essential to understand and experience what it’s like to ship a design — the proverbial “first dollar earned” that burgeoning restaurant owners have framed on their wall. Learning the ins and outs of shipping an experience is vital to growing your career and influence as a product designer.</p><p>But this is an easy trap that young Design Teams fall into: getting designs shipped can’t be the <em>only</em> metric you use to measure your work. That might be a no-brainer to some in mature product design organizations, but that realization was something my own Design Team took a while to work through. In addition to having an abundance of young designers, our team also reports through development leadership. This org structure understandably affects our perceptions of “success” because most of our immediate teammates are hyper-focused on delivery and hitting committed program dates.</p><p>This mentality didn’t jive well with what we knew in the industry at large. It also led to situations where experiences and functionality shipped at a lower quality to meet deadlines. My team knew there were <a href="https://uxplanet.org/a-quick-guide-to-ux-metrics-d271a937149a">many <em>better</em> metrics</a> that Product Design Teams could use to measure their success. But we quickly realized we did not have the processes to easily track these other metrics, nor the broader team’s buy-in, to shift our definition of “success.” But through a bit of trial and error and lots of negotiation, we are slowly shifting away from this mentality to better and more accurate ways to measure success.</p><h3>Healthy negotiations</h3><p>Product Design Teams must collaborate (and negotiate) with their stakeholders to provide a healthy balance of innovation and big-picture thinking. There’s a spectrum here: if a product team doesn’t implement <em>any</em> of a Design Team’s proposed projects, that is most likely a sign of dysfunction. But if a product team implements <em>all</em> their proposed projects without changes, that could signify an immature Design Team (that most likely makes whatever development requests and nothing more).</p><p>At first glance, you might not agree with that assessment. So, I’ll explain by flipping the teams around: suppose Product Management and Design only ever ask Development for the minimum required in any sprint or release. In that case, there’s a strong chance this product team has some areas to grow. In a mature product team, there should be a healthy amount of negotiation taking place to find the perfect balance of viability (determined through Product Management), desirability (determined through Design), and feasibility (determined through Development). Over-emphasizing feasibility could mean that viability and desirability aren’t given enough emphasis.</p><p>Here’s a quick theoretical example (that in no way reflects something that frequently happened to my team and me…): a Design Team works with Product Management to prototype or storyboard a user experience. The Design Team validates that the experience is desirable via Design Research. But the Development team defers the delivery of the experience or introduces limitations that significantly change the experience to make it containable. The Design Team could reasonably be frustrated by desirable user experience getting deferred. This situation indicates that the Product Team needs to improve how it prioritizes what is truly important to its users.</p><p>Or, in the right circumstances, this situation means that the Design Team is doing its job right: creating designs that dream big and push their organization toward understanding what users need.</p><p>In this case, Design Teams may need to lean into a positive thinking negotiation tactic: “Shoot for the Moon. Even if you miss, you’ll land among the stars.” For the sake of our users, my Design Team needed to begin “shooting for the moon.”</p><h3>Gradually tipping the scales</h3><p>When my Design team first worked on getting traction with the broader product team and got their “seat at the table,” we were less inclined to do this — to challenge the status quo. Our desire to demonstrate design’s value to our Development and Product Management made us worry about aggressively proposing experiences that exceeded the feasibility of a given release or sprint. We felt doing so would jeopardize the fledgling relationships we were nurturing. But after a certain point in our journey of Design maturity, we realized that we needed to start gradually proposing more and more aspiration experiences. Frequently we would encourage each other when faced with challenges or setbacks, Slacking each other privately after the gutting of a proposed experience: “Baby steps. We will get there one day!”</p><p>This process of gradually dreaming big and pushing our product organization started with our own Design Team: we had to break habits and improve our own operations. We became more assertive negotiators. For example: if you’re familiar with the <a href="https://blog.devgenius.io/cake-experience-roadmap-design-thinking-explained-50e74ec5e1fc">“cupcake, birthday cake, wedding cake” framework</a> of user experiences, my team had jokingly made up an even smaller deliverable, called a “cake pop”, to represent the experience we often had to ship due to aggressive timelines and a focus on delivery over quality. Because of this, we far too quickly jumped to a “cake pop” experience — without fully exploring the vision of an experience’s roadmap and letting the PM and Development team negotiate for the desired experience.</p><p>Recently, an executive brought up this habit during a design review. Having previously worked in other areas of IBM with larger and more mature Design Teams, he commented that our designs are “too tied” to what Development <em>could</em> release, rather than what <em>needs</em> to be released to provide the best experience for our users. He intuitively picked up on our habit of wimpy negotiation and lack of aspirational exploration. We needed to aggressively defend our ability to explore and define visionary experiences for our users — to dream big and push boundaries.</p><h3>Our next (baby) step</h3><p>Now that we’ve grown more comfortable bringing aspirational designs forward, our next step is to (1) define metrics outside of successful delivery, and (2) prioritize where we focus our design efforts.</p><p>Every design project should have a true success metric. At IBM, these success metrics are actually woven into “<a href="https://nife.medium.com/what-are-hills-in-ibm-design-thinking-446315959774">Hills</a>”, which are supped-up user stories with <em>explicitly-measurable</em> user outcomes. On our team, we require every design project, no matter how big or small, to have a Hill written to describe the work and capture the metric. Currently, this work is largely Design-led, and while we’d like our broader team to buy into writing Hills for most of our work, we realized that the best way to encourage this was to do it ourselves as a part of our Design work.</p><p>Along with this change, we are also learning that the best way to produce aspirational designs to learn to say “no” to design requests. This approach has become a part of our current “healthy negotiations”: we are asking the PM and Engineering teams what are the highest priority projects that need the most attention from our Design teams. Previously, we spread our Design team across too many projects, making it almost impossible to deliver exceptional experiences. Now, with our more focused efforts, we are able to dream big and push our product team!</p><h3>Join the conversation!</h3><p>Have you experienced similar struggles with your maturing Design teams? How do <em>you</em> find the sweet spot of feasibility, desirability, and viability? Let me know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51b8c824e89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear UX Design Students,]]></title>
            <link>https://medium.com/@swwebsterdesign/dear-ux-design-students-a468871a9bfc?source=rss-2cc51693df1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a468871a9bfc</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Stephen W. Webster]]></dc:creator>
            <pubDate>Mon, 30 Jan 2017 19:52:26 GMT</pubDate>
            <atom:updated>2017-01-31T04:17:43.118Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*se1RqF53MXosWLP44kBNMQ.jpeg" /></figure><p>I remember being in your place just over a year ago. I was wrapping up a UX immersive course at General Assembly and working on my portfolio: how to best convey myself, my work, and my skills so that I could ultimately land a job in this coveted field. I was nervous and excited and pumped and stressed. All the feelings.</p><p>I finished a first draft of my portfolio and sent it out to get critiques, partly because I was encouraged to do so by my instructors; most of these critiques originated from my fellow design students. But, I also reached out to people in the industry that I respected: people that are practitioners of this craft I was immersing myself in. Some of these industry designers replied, and some didn’t; I was expecting this, honestly. We all lead busy lives. But someone did get back to me, and the advice I received from this designer ultimately shaped my perception of UX Design, especially when reviewing potential UX Design candidates:</p><blockquote>“Always, always return to the user.”—Kathryn McElroy, <a href="http://kathrynmcelroy.com/">kathrynmcelroy.com</a></blockquote><p>You might be thinking that should be obvious. It’s in the role’s title: <strong>USER</strong> Experience Designer. That’s frankly how I felt when I received the advice. But as I went back through my portfolio and the narratives I used to explain my work, I could see how the user got lost in all the design processes: card sorting, stakeholder interviews, and persona formulation. I went back to the drawing board, rewriting and redesigning my portfolio to demonstrate that I did, indeed, have the user as the centerpiece of my design process and the decisions my team and I made.</p><p>But as I review portfolios as part of IBM Design’s recruiting process, this seems to be a recurring theme that I see. The students have learned the design process and the exercises that can be used to come up with solutions. They can do these tasks well. But time and time again, they lose track of the user during their process—at least that’s what their portfolios communicate. These portfolios contain robust projects that run the full gamut of design practice, from generative research all the way through prototyping and usability testing, showing the hundreds of decisions made during their undertaking. And somewhere along the way, it becomes more about the project and process than the user.</p><p>Don’t fall into this trap.</p><p>It’s important to explain what you specifically accomplished in a project (especially if it’s a group project). But it’s very easy to become so focused on explaining and showing the process that you forget to explain your thinking, and ultimately forget about the user. Why did you decide to do a card sorting exercise here? Were your personas based on actual users? How did you formulate them? Why did you decide to do [insert decision here]? These are some of the many questions that run through my head as I’m reviewing portfolios.</p><p>It’s vitally important for you to demonstrate that in the midst of the hustle and bustle of projects that you are keeping the user as the touchstone and driving force behind the project. <strong>It’s your job</strong>. When you get on teams, you are going to be pulled in many different directions by product/offering managers, developers, engineers, and even fellow designers. Depending on the company you end up working for, there could be hundreds of people involved in your process—perhaps not directly, but they’ll see your work and have opinions on it. Students aren’t typically exposed to intense factors such as these during school, probably because it would be counterproductive to the educational process. Regardless, if during these simpler projects, you lose sight of the user in your explanation and process, how can we be sure that you will be the user’s advocate on real product teams?</p><p>But, don’t fret! There’s hope! As was the case with my own portfolio, I had simply neglected to remember the importance of the user even in writing my case studies. I suspect that for many students, this is the case. Simply rewriting and reforming the narratives of your case studies to center around the user may be all that it takes. And while you’re at it, here are some other quick tidbits of advice:</p><ol><li>Always, always return to the user.</li><li>Clearly state the problem you are trying to solve. If it emerged from generative research, explain how the problem was formulated.</li><li>If you’re explaining a group project, make sure you make it as obvious as possible what your specific contributions were to the project. The part of the project that features your work should be the most detailed part of the explanation.</li><li>Show the messy, nitty-gritty details of your process: sketches, sticky notes, whiteboard drawings, etc. The design process isn’t always nice, pretty interfaces. This under the covers look into your thinking and process shows a lot about who you are.</li><li>And always, always return to the user.</li></ol><p>This is my first Medium post! Please let me know your thoughts in the comments. Also, if you’re a design student and need some eyes on your portfolio, don’t hesitate to reach out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a468871a9bfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>