<?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 Rebecca Granat Shapiro on Medium]]></title>
        <description><![CDATA[Stories by Rebecca Granat Shapiro on Medium]]></description>
        <link>https://medium.com/@rebeccashapiroux?source=rss-d3d661d1c30e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fxJUBV8lKxGKAw3La49fXg.jpeg</url>
            <title>Stories by Rebecca Granat Shapiro on Medium</title>
            <link>https://medium.com/@rebeccashapiroux?source=rss-d3d661d1c30e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:04:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rebeccashapiroux/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[How to Put Your UX Roadmap to Work]]></title>
            <link>https://medium.com/indeed-design/how-to-put-your-ux-roadmap-to-work-489300139e5a?source=rss-d3d661d1c30e------2</link>
            <guid isPermaLink="false">https://medium.com/p/489300139e5a</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Rebecca Granat Shapiro]]></dc:creator>
            <pubDate>Thu, 22 Feb 2024 16:42:53 GMT</pubDate>
            <atom:updated>2024-03-21T17:41:12.917Z</atom:updated>
            <content:encoded><![CDATA[<h4>Your planning master doc can be an effective hub for everyone. A senior UX director breaks down how to create your team’s roadmap.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GWisSe0HSzTIF-ot1OPN5Q.png" /></figure><p><em>This is the final article in a four-part series. To start at the beginning, read the article </em><a href="https://indeed.design/article/guide-to-ux-planning-how-to-create-a-roadmap"><em>Guide to UX Planning — How to Create a Roadmap</em></a><em>.</em></p><p>A lot of work goes into building a UX roadmap. In previous articles, I’ve shared how to make sure you and your cross-functional partners are speaking the same language when it comes to <a href="https://indeed.design/article/4-types-of-design-projects-for-ux-roadmapping">project types and expectations</a>, and how to lead <a href="https://indeed.design/article/how-to-lead-effective-ux-roadmap-planning-discussions">effective project planning and prioritization conversations</a>.</p><p>But how do you actually take that information and make it into a clear quarterly roadmap document that accurately represents everyone’s capacity? Here’s a peek into my process for creating a UX roadmap that teams and partners can actually use, as well as some tips to keep in mind when you’re building your document.</p><h3>1. Create a roadmap document</h3><p>Start by creating a roadmap document using whatever platform works best for you and your team. Some teams use a spreadsheet, a Miro or FigJam board, or software like Asana. The easiest path forward is to use a simple shared document like a Google spreadsheet like this <a href="https://tinyurl.com/uxroadmap">sample roadmap</a>, which you can use as a template.</p><p>First, map the dates on your spreadsheet to the upcoming quarter. Try to use the same sprint schedule and cadence as your engineering teams, and mark out any holidays or upcoming vacations so you remember to limit your workload during those sprints.</p><p>If there are multiple UXers on your immediate team, I find it helpful to give everyone a section in the same spreadsheet, including non-design disciplines like UX Research and UX Content Design.</p><p>Then, refer to your <a href="https://indeed.design/article/how-to-lead-effective-ux-roadmap-planning-discussions/">project list</a> for the quarter and enter each project into your roadmap document in order of timing and priority. In addition to vacation time, call out anything that might take up some of your velocity, like annual reviews, personal goals you have deadlines for, trainings, or team on-sites.</p><h3>2. Scope your design work</h3><p>Next, you’ll need to estimate how long each project or task will take you and add that to your spreadsheet. There are tons of methodologies for scoping design work. Some teams use t-shirt sizing, story points, or sprint percentages. Use whatever model works best for you and your team.</p><p>If you don’t already have a scoping model that’s working for you, here’s one of my favorites: The “Perfect Day” points system.</p><ul><li><strong>Start by being realistic about how much time a designer actually has</strong> to work on a project. Sure, there are 30 days in a month, but how much of that is really heads-down design time? Imagine about a third of our time is taken up by meetings and weekends. Another third is evenings and responding to emails. That leaves about ten uninterrupted heads-down days’ worth of work time each month.</li><li><strong>Don’t ask how much time you’ll need to get something done</strong>. Instead, imagine you had an entire workday with no meetings to attend or emails to respond to; all you had to do was work on this project. How many of those imaginary days would you want to get this project done?</li><li><strong>Use that ideal day as a base unit for scoping work</strong>. These 7.5-hour, heads-down days may not happen often, but it’s an easy mental model to use.</li><li><strong>Review your list of projects</strong> and decide how many perfect days each project would need. Half a day? Give it half a point. Two days? Give it a 2. Would you like to dedicate a whole two week sprint? That’s 5 points. How about an entire month devoted just to that project? Give it 10 points. If you’re not sure, round up. It’s always better to deliver early than promise early and be late.</li></ul><p>The nice thing about the Perfect Day points system is that you can split the math across sprints to fit in smaller requests without giving less time to a project than it needs.</p><h3>3. Plan out your work</h3><p>In your roadmap document, start assigning blocks of sprint time to work on each line item. Decide ahead of time how much work is realistic for you within a sprint. If you’re using the points and days method mentioned above, cap each designer at four or five points per two-week sprint.</p><p>So if you have a five-point project, you may decide to put all five points towards that project in the one sprint. But if you have urgent competing priorities or vacation time that sprint, you might decide instead to spread the five points for that project over two sprints, putting three points on one and two on the other.</p><p>It’s normal for large or ongoing projects to get split across multiple sprints, but if you have the option, I recommend designers stay focused on one project per sprint so they can go deep and not lose time context switching between projects.</p><p>Rearrange projects as needed to get your sprint totals below your maximum workload, and try to meet the scheduling requests from your team where you can. It won’t be perfect, and that’s OK.</p><h3>4. Be realistic about your time</h3><p>Often, demands on your time will exceed the actual time you have in the quarter. You’ll be asked to do more and to do it faster. When this happens, you may feel tempted or pressured to work extra hours to fit in every request. Stay strong and avoid that impulse. The point of this exercise is to improve the quality of your design work by ensuring you have enough time to do it well.</p><p>Here’s what to do instead: Map out all the projects on your roadmap, assigning each the amount of time they need to be done properly. They’ll overflow into the next quarter (or beyond). Show your cross-functional partners where things net out, and have a <a href="https://indeed.design/article/how-to-lead-effective-ux-roadmap-planning-discussions">healthy conversation</a> about which projects should be prioritized for this quarter over others and what the tradeoffs will be. Maybe project scope can be cut back or divided into phases. If there are other designers on your team, maybe you can look into sharing the load.</p><p>It’s important to take care of yourself; after all, you’re not a UX robot, and UX is not a bottomless resource.</p><h3>5. Socialize your plan</h3><p>Share your roadmap, even in draft form, with your product and engineering leads, and get their agreement. You’ll move things around quite a bit before you find a plan that works for everyone, but you can use this roadmap as a shared visualization to illustrate your capacity and that of your team.</p><p>When an urgent new project comes in and disrupts your plans, look at the roadmap together to visualize how subsequent projects will get pushed out and displaced. This makes it easier for your partners to understand the effects of adding something new.</p><p>And of course, expect that your plans will change over time. Decide with your cross-functional team early on how frequently you want to check in and revisit timelines and priorities.</p><h3>Best practices to keep your UX roadmap working for you</h3><p>Now that you’ve built your roadmap, here’s how to keep it in good working order:</p><h4>Keep your roadmap accessible and up-to-date</h4><p>Maintain your roadmap in a shared space so it’s accessible to your partners and always up-to-date. Get your partner teams and manager used to looking at this as the ultimate source of truth.</p><h4>Review and revise as needed</h4><p>Periodically review and update the roadmap with your product team as priorities shift.</p><p>Things change! And they often have a ripple effect: emergency projects coming up mean other work needs to get pushed out or deprioritized. When this happens, use your roadmap to help your partners to visualize the cascading effects of a change. This forces healthy discussions about prioritization and reminds your partners that, just like engineering, you are not a bottomless resource.</p><h4>Ask for advance notice</h4><p>Ask your partners to let you know as far in advance as possible about any upcoming work or demands on your time. It’s easier to commit resources when you have the lead time to plan adequately. This way, you can slip the project into next quarter’s roadmap when you’re planning it, instead of trying to cram it in (and move everything else around) after the roadmap’s been set.</p><h4>Scoping will differ from designer to designer</h4><p>I generally assume that scoping will vary by designer, experience, and product space, so a project that’s scoped at 30 points for an intern might be a 10 or 15 for a more experienced designer.</p><p><em>The goal isn’t to set a deadline. It’s to accurately predict how long it will take a specific designer to do a project well.</em></p><p>Round up on scoping if there’s any uncertainty, which there will be any time you try a new scoping method, work with a new team, or get familiar with a new product space.</p><h4>Keep your roadmap easy to read</h4><p>If you’re using a spreadsheet, hide rows and columns after the dates or projects have passed, so they’re not distracting. You want any partner to be able to see at a glance what’s happening now and what’s upcoming.</p><h4>Use your roadmap to anticipate resourcing spikes</h4><p>Most of us find there’s more work planned or requested than we can reasonably do in a quarter. The roadmapping process will help you and your manager understand exactly when additional resources are needed and what work will be below the line if additional resources are unavailable.</p><h4>We rule the roadmap, not the other way around</h4><p>Stress to your partners that the roadmap is a planning and prioritization tool, not dates set in stone, especially as you onboard your team to the process. Dates and projects can be adjusted as priorities shift, but those shifts require healthy cross-functional conversations about tradeoffs.</p><p>In short, the roadmap helps us visually understand the impact of these tradeoffs. It helps keep workloads manageable, makes it easier to identify gaps in resources, and ensures our shared understanding of the downstream impact.</p><h3>Share your learnings</h3><p>As with everything in UX, the methodologies outlined in these articles should be iterated and improved upon. As you embark on your roadmapping journey, feel free to find Indeed Design on LinkedIn and Twitter to share your learnings, your success stories, new tips, or great improvements you’ve made to this process. Happy roadmapping!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=489300139e5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indeed-design/how-to-put-your-ux-roadmap-to-work-489300139e5a">How to Put Your UX Roadmap to Work</a> was originally published in <a href="https://medium.com/indeed-design">Indeed Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Lead Effective UX Roadmap Planning Discussions]]></title>
            <link>https://medium.com/indeed-design/how-to-lead-effective-ux-roadmap-planning-discussions-44b3c057eb07?source=rss-d3d661d1c30e------2</link>
            <guid isPermaLink="false">https://medium.com/p/44b3c057eb07</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-planning]]></category>
            <dc:creator><![CDATA[Rebecca Granat Shapiro]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 15:10:23 GMT</pubDate>
            <atom:updated>2024-02-05T15:10:23.827Z</atom:updated>
            <content:encoded><![CDATA[<h4>7 questions to ask and a spreadsheet template you can use to get your partners and team on the same page.</h4><figure><img alt="silhouetted heads speak to each other with an infinity symbol in background" src="https://cdn-images-1.medium.com/max/1024/1*v9TtWl_7hNVMm6HJR4y5Lg.png" /></figure><p><em>This is the third article in a four-part series. To start at the beginning, read the article </em><a href="https://medium.com/indeed-design/guide-to-ux-planning-how-to-create-a-roadmap-9e0ccb379d55"><em>Guide to UX Planning — How to Create a Roadmap</em></a><em>.</em></p><p>So you’re building a UX roadmap for your team. You’ve already aligned with your product and engineering partners on <a href="https://medium.com/indeed-design/4-types-of-design-projects-for-ux-roadmapping-7047a1d73ab6">what types of design projects</a> are on the table. Check! And everyone’s aware of what types of timelines and deliverables to expect from each type of project. Double check!</p><p>Now it’s time to talk specifics.</p><p>Knowing how to lead an effective conversation with your partners about what priorities are ahead is an essential UX skill. Read on for tips on maintaining the momentum with your cross-functional team as you define your upcoming work and build out your UX roadmap.</p><h3>Host a meeting to discuss upcoming work</h3><p>The most critical part of roadmapping is having ample time and a mechanism in place for you and your cross-functional partners to learn about and discuss upcoming work. Do this well in advance of the period you’re planning for (think one to two months). Use the meeting to give input and get answers to key questions that will help prioritize that work. I recommend teams have these conversations at least once ahead of each quarter, with follow-ups as necessary.</p><p>Before the quarter starts, set up an hour or two with your product manager and engineering lead for an open discussion about the UX work you want to consider for prioritization during the upcoming quarter and beyond. You’ll want to discuss the following:</p><ul><li>What does each partner feel should be on the list for the coming quarter? And what do they consider top priority?</li><li>What’s coming up in the next few quarters? Depending on UX scope, if development work is scheduled for the next quarter, you’ll probably want to plan your UX work for the current one.</li><li>What user problems need investigation?</li><li>What big questions does your team have?</li><li>Where is research or discovery work needed?</li></ul><p>This should be an open discussion, not a clinical intake. Bring insights from user research. Review past vision work or remind the team of followup improvements to projects that still need to be prioritized. Raise big questions about future direction that require foundational research or discovery work.</p><p>Your voice here matters. And more importantly, your users’ voices matter. Our responsibility as UX professionals is to advocate for our users’ needs. Use this time to advocate for the projects that will most impact your users for the better.</p><h3>Set expectations for your UX roadmapping partners</h3><p>Pro tip: A lot of cross-functional partners have a natural reaction to want to over-prepare for discussions like this. They might bring an already completed roadmap because they want to be good partners and bring clarity. So help your partners understand what to expect from your session — what they should prepare, and what they shouldn’t.</p><p>Save them time by setting clear expectations ahead of time. They should absolutely bring a list of problems to solve or initiatives they’d like to prioritize. But it doesn’t have to be finished — and they should expect to receive suggestions, questions, ideas, and input. Remind them you’re not working with a final plan yet, you’re collaborating on creating that final plan.</p><figure><img alt="Screenshot of spreadsheet you can copy and use to document ux roadmap discussion decisions" src="https://cdn-images-1.medium.com/max/1024/1*n477Pp38dV6AtJ0e1PuYjw.png" /></figure><h3>Give participants a clear frame for the discussion</h3><p>I use the following questions to frame the conversation. Add your own or adjust them to meet your team’s needs. I’ve also created an <a href="https://docs.google.com/spreadsheets/d/e/2PACX-1vSGW-HPN9sppBMl4zCDu4Lwto8XZQekJuP1kNpVTG59kajWf7Nso5NMMqSXfexcm68suNVLDW9S5xXC/pubhtml">Initiative Identification spreadsheet</a> you can copy and use to keep track of the projects discussed and the answers to each question. Share this on your screen and fill it out together as you discuss potential projects with your partners.</p><h4>1. What is the project?</h4><p>What are you calling this project? Use a simple, descriptive name that differentiates it from other projects on the board so you can all remember what it refers to.</p><h4>2. What is the user problem you’re trying to solve?</h4><p>Designers often receive very specific requests from partners or leaders about how they’d like us to solve a problem. Use this as an opportunity to recenter the project around a customer problem versus a specific solution. It may take a few tries to identify an accurate problem statement that’s truly focused on user needs versus business or technology needs. Workshop this together if you need to. If you’re working on internal tools, the customer problem may be a few steps removed from the solution, and that’s OK.</p><p>If you’re ultimately unable to identify a real user problem this initiative would solve, the project may not be user-focused enough. You may need to question whether it should be prioritized at all.</p><p>Centering projects around customer problems is also a great way to find similar initiatives across your team or company. You may find that others are working on the same problem but from different angles. These can be great opportunities to schedule work at complementary times and collaborate.</p><h4>3. What’s the timing on this? When do they want to start development work?</h4><p>Make sure your team is committed to putting development resources into this project, even if it’ll be next year, in the case of vision work.</p><p>Schedule design work to finish a few weeks ahead of starting development work in case the project runs long or increases in scope or complexity.</p><h4>4. What type of project is it?</h4><p>Don’t forget how <a href="https://indeed.design/article/4-types-of-design-projects-for-ux-roadmapping">different types of design projects</a> can influence your roadmap. An experiment looks different in terms of timeline, effort, and deliverables from a launch project or vision work. Be clear about what type of project you’re working on so you and your partners are aligned on expectations.</p><p>Also, make sure this is the right type of work for your team’s skill set. For example, if it’s a more visual project like a banner ad, consider bringing in a visual designer.</p><h4>5. Who are the partners and decision makers?</h4><p>Who’s the product manager for this project? If there isn’t one, why not?</p><p>Who needs to sign off on design decisions? Is there an executive sponsor? Find out and document ahead of time to reduce rework.</p><h4>6. What are the known dependencies?</h4><p>Does the team need to complete another project before this one? Keep this in mind when planning your roadmap.</p><p>Does it need up-front research or discovery work? Make a separate line item for that. Will you need to bring in other partners or teams to collaborate with? Try to predict this ahead of time since it will add scope to your timeline, and you’ll need to give those partners a heads-up.</p><h4>7. How does this compare to other projects in terms of priority?</h4><p>Does it map to a goal or OKR? If so, what kind? Some goals are more important than others. Company-wide goals tend to trump team or personal goals. Are some of these projects more urgent than others? Work with your product team to prioritize competing projects.</p><h3>Align on the problems with your UX peers</h3><p>Once you’ve identified the quarter’s projects, timing, and priorities, meet up as a UX team to go through each of your projects and problem statements. My teams have often identified repeating or related customer problems, which are great opportunities for collaboration. They’ve also found duplicate efforts that one designer can handle at the same time. Reassign or adjust projects to simplify work streams or even out the workload by assigning some projects to designers with more bandwidth.</p><h3>Taking time for a meaningful discussion leads to greater impact</h3><p>Roadmapping is a highly collaborative undertaking that can feel daunting at first. After all, you and your partners are learning new, collective ways of planning and communicating. But it’s also important to know that it gets much easier each subsequent quarter, where your project list tends to be pre-populated with all the projects that didn’t fit into the timeline for the current quarter.</p><p>So don’t rush through the process. Take the time to make sure your users and their needs are well-represented in your team’s prioritized work. In the long run, being thorough and transparent in your planning will help save everyone time. You’ll create less wasted work, build common ground among teams, and establish timelines that work for everyone.</p><p>But your job isn’t quite done. It’s time to take what you’ve learned from these conversations, scope out your projects and ultimately build your roadmap.</p><p>Watch this space on February 19 for the next article in my UX roadmapping series: 8 Tips for Drafting a UX Roadmap Document Teams Will Actually Use</p><p><em>Go back to the series hub: </em><a href="https://indeed.design/article/guide-to-ux-planning-how-to-create-a-roadmap"><em>Guide to UX Planning — How to Create a Roadmap</em></a></p><p><em>Illustrated by </em><a href="https://www.linkedin.com/in/jimmyxpark/"><em>Jimmy Park</em></a></p><p><em>Stay in touch. </em><a href="https://medium.com/indeed-design"><em>Follow our publication</em></a><em> on Medium and learn about Indeed’s user experience team at </em><a href="http://indeed.design/"><em>Indeed Design</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44b3c057eb07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indeed-design/how-to-lead-effective-ux-roadmap-planning-discussions-44b3c057eb07">How to Lead Effective UX Roadmap Planning Discussions</a> was originally published in <a href="https://medium.com/indeed-design">Indeed Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Types of Design Projects for UX Roadmapping]]></title>
            <link>https://medium.com/indeed-design/4-types-of-design-projects-for-ux-roadmapping-7047a1d73ab6?source=rss-d3d661d1c30e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7047a1d73ab6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[roadmapping]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Rebecca Granat Shapiro]]></dc:creator>
            <pubDate>Wed, 24 Jan 2024 23:52:18 GMT</pubDate>
            <atom:updated>2024-02-02T17:23:07.528Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to align your team’s expectations on timing, deliverables, and process.</h4><figure><img alt="Along a winding doodled road, papers fly around and icons like pins, Xs, question marks pop up." src="https://cdn-images-1.medium.com/max/1024/1*OxJczYTFDWGBohbJG-87gg.png" /><figcaption>Illustration by <a href="https://www.linkedin.com/in/jimmyxpark/">Jimmy Park</a></figcaption></figure><p><em>This is the second article in a four-part series. To start at the beginning, read the article </em><a href="https://indeed.design/article/guide-to-ux-planning-how-to-create-a-roadmap"><em>Guide to UX Planning — How to Create a Roadmap</em></a><em>.</em></p><p>Good UX takes time and planning. Lots of it. That’s why your team needs a UX roadmap.</p><p>Getting on the same page with your teammates about what types of design projects will be included on the roadmap is an essential first step. UXers pull from a range of skills and methodologies to do their work depending on the needs of the project and team. That often means that the terminology we use, the timelines and processes we follow, and deliverables our partners can expect will differ significantly from project to project. Before we even get to planning, it’s critical that we start from a place of shared language and expectations.</p><p>Follow along as I share a framework for setting clear expectations with your partners on timeline and deliverables by design project type.</p><h3>Choose design projects to help you meet your unique goals</h3><p>It all starts with defining your terms. Most design work falls into one of the following categories, each with its own unique expectations for deliverables and timeline:</p><h3>1. Launch projects</h3><p>A launch project is a resourced initiative intended to provide lasting customer benefit. Most UX design projects fall into this category. They can be any size (XS through XXL), and large ones may be subdivided into smaller initiatives.</p><p>Critical criteria for launch projects:</p><ul><li>They must include a clear understanding of the user problem and success metrics.</li><li>Design solutions are thorough, thought through well, and intended to last.</li></ul><p>UX deliverables for a launch project generally include some or all of the following:</p><ul><li>Mockups of the complete designed experience, including final copy, edge cases, and error states</li><li>Redlines or other development documentation for your engineers to follow when building, including any additional interaction specifications that may be needed.</li><li>Insights and learnings from any relevant tests, experiments, or user research.</li></ul><h3>2. Experiments</h3><p>Have you ever had a partner balk at the timeline you’ve given for a project and ask, “Can’t we just be scrappy and get a quick test out to learn?” My response is to propose an experiment: a lightweight (sometimes scrappy) test to prove (or disprove) a specific hypothesis over a limited period of time.</p><p>In this case, we agree to temporarily try a less thorough, faster-turnaround solution in exchange for a few agreed-upon guardrails:</p><ul><li>By definition, each experiment must include a clear hypothesis, testing criteria, success criteria, and thresholds, as well as clear next steps based on the outcomes.</li><li>This experience will only stay live for as long as it takes to answer the hypothesis. Most often, it’s just a few weeks — not a long-term solution.</li><li>The live experience must still meet team standards for public use, even if it’s just for a short period of time.</li></ul><p>In most cases, experiments offer the quick answers needed to determine the direction for a launch project that will be a more lasting solution.</p><p>UX deliverables for an experiment generally include some or all of the following (in addition to the experiment criteria listed above):</p><ul><li>Mockups or wireframes, including final test copy.</li><li>Development documentation, ad-hoc conversations, or collaborative working sessions with engineering partners to ensure the production test meets your standards for UX quality.</li></ul><h3>3. Vision work</h3><p>Vision work is forward-looking, user-focused exploration. It results in a shared north-star vision or strategy that teams align around, even if that vision isn’t yet achievable. This tends to be cyclical work that informs annual or three-year planning. It can also happen at key points when teams are in need of renewed clarity or alignment on the future of their product.</p><p>The deliverables here are quite different from those for a launch project or experiment. Instead of outlining details and specifics, design deliverables for vision work are just high fidelity enough to communicate the high-level concept. Typically, the end result is a shared vision, recommendations for achieving it, and the outline of a phased approach for how to get there.</p><p>UX deliverables for vision or strategy work generally include some or all of the following:</p><ul><li>High-level concept visualizations of future ideas or direction</li><li><strong>Tip:</strong> Stay just high fidelity enough to communicate your idea and get partners excited about the direction. Avoid including any details that distract from your high-level concept.</li><li>A clear explanation of how this vision solves for the user problems, including evidence from research and experiments that support the proposed direction.</li><li>A proposal for additional research or experiments to validate the direction or answer critical open questions, if needed.</li><li>Recommendations for achieving this vision, including a high-level proposal for a phased approach to getting there made in partnership with your product management and engineering peers.</li><li><strong>Remember:</strong> These recommendations will likely include dependencies on other teams.</li><li><strong>Ask:</strong> What could we start doing in our first quarter of work to move us in this direction? What could be done the quarter after? What about the following year?</li><li><strong>Consider:</strong> Because there are frequently unforeseen delays between phases, make sure each phase will be a solid standalone experience that meets your standards for quality.</li></ul><p>I often find that vision work done one quarter informs my team’s roadmaps for the following several quarters or years. A healthy product team should plan to conduct some form of vision work at least once a year, especially ahead of annual planning.</p><h3>4. Consultation and development support</h3><p>Sometimes, our partners just need a consultation: some lightweight input rather than solutions or deliverables. We can help with that. Lightweight support takes less time but should still be marked on roadmaps.</p><p>We also need to keep in mind that projects that are actively in development take time and attention from UX practitioners, too. You’ll be pinged with questions, asked to review experiences in pre-production, and need to help troubleshoot late-breaking issues. I recommend designers mark upcoming periods of development support on their roadmaps as a reminder that their time and velocity for other project work will likely be reduced.</p><ul><li><strong>Tip:</strong> If you find you’re getting interrupted and randomized by constant pings and questions, consider setting up a regular meeting series or office hours for the duration of the support period.</li></ul><p>UX deliverables for development support or consulting time:</p><ul><li>Generally none other than your real-time input and feedback!</li></ul><h3>Get the right mix of project types on your roadmap</h3><p>The types of UX projects on a quarterly roadmap depend on a few things:</p><ul><li>The overall maturity of your product.</li><li>Where you are in your annual product planning cycle.</li><li>What you’ve done in the last quarter or two.</li></ul><p>When a product or problem space is nascent, you’ll need to schedule a lot of time for vision work. But established projects also need vision work (or vision refreshes). Any time there isn’t a clear strategy for what’s next — or the strategy you had feels dated or irrelevant — earmark time to define a new vision to take you through the next few years.</p><p>Finally, keep the future in mind by making sure your work can inform the next year’s direction. Carve out dedicated time for vision work and generative research on big questions at least once a year, ahead of your product team’s annual planning cycle.</p><p>Once your team has aligned on a strategy, the roadmap for your next few quarters may look very different. It will primarily be comprised of launch projects and experiments that help move you toward your vision.</p><p>After each project has been designed, plan on a slower velocity sprint as you support your development team as they build your designs.</p><p>In general, from concept to execution, your roadmaps will likely end up following these paths:</p><ul><li>Vision &gt; launch projects &gt; development support for those projects</li><li>Vision &gt; experiments &gt; launch projects &gt; development support</li><li>Consulting &gt; experiments &gt; launch projects</li></ul><h3>A shared understanding is only the start</h3><p>Aligning with all your partners to find shared definitions for project types, their timelines, and deliverables is a great first step to building your UX roadmap. But it’s not the end.</p><p>Now you’re ready to talk as a team about choosing specific projects, and competing priorities will likely be at play on any team. In the next phases of planning, stay focused on having effective conversations with your cross-functional partners ahead of each planning cycle. This will help you carry on the hard work you’ve done in this phase to lay a solid foundation of shared understanding for your roadmap.</p><p>Watch this space on <strong>February 5</strong> for the next article in my UX roadmapping series: How to Lead Effective Roadmap Planning Discussions</p><p>Go back to the series hub: <a href="https://indeed.design/article/guide-to-ux-planning-how-to-create-a-roadmap">Guide to UX Planning — How to Create a Roadmap</a></p><p><em>Stay in touch. </em><a href="https://medium.com/indeed-design"><em>Follow our publication</em></a><em> on Medium and learn about Indeed’s user experience team at </em><a href="http://indeed.design/"><em>Indeed Design</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7047a1d73ab6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indeed-design/4-types-of-design-projects-for-ux-roadmapping-7047a1d73ab6">4 Types of Design Projects for UX Roadmapping</a> was originally published in <a href="https://medium.com/indeed-design">Indeed Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide to UX Planning — How to Create a Roadmap]]></title>
            <link>https://medium.com/indeed-design/guide-to-ux-planning-how-to-create-a-roadmap-9e0ccb379d55?source=rss-d3d661d1c30e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e0ccb379d55</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[roadmapping]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Rebecca Granat Shapiro]]></dc:creator>
            <pubDate>Wed, 24 Jan 2024 23:51:12 GMT</pubDate>
            <atom:updated>2024-02-05T20:06:45.482Z</atom:updated>
            <content:encoded><![CDATA[<h3>Guide to UX Planning — How to Create a Roadmap</h3><h4>Three steps and some elbow grease will have your team cruising through KPIs with a clear master document.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bZT05IkMxTTLIjQgSPsh6g.png" /><figcaption>Illustration by <a href="https://www.linkedin.com/in/jimmyxpark/">Jimmy Park</a></figcaption></figure><p>Most UXers say they don’t get enough time to do their projects justice: Last-minute requests keep coming in for fast turnaround projects, there’s no time for discovery, they’re not even certain how the project will actually benefit users. Some try to get ahead of these asks, but find that by the time they’re halfway through their deliverables, priorities have shifted, and the team wants to pivot to something new.</p><p>This happens all the time in UX, but it doesn’t have to be the norm.</p><p>To avoid these common pitfalls, a comprehensive and thoughtful roadmap led by UX and for UX is important. But roadmapping is a huge undertaking that’s dependent on close alignment with product and engineering — UX can’t do it alone. So how do you kick off a quarterly plan to set you and your team up for success later?</p><p>In the long run, being thorough and transparent in your planning will help save everyone time, create less wasted work, build common ground among teams, and establish project definitions and timelines that work for everyone involved.</p><p>Keep reading to learn a three-step process for kicking off UX quarterly roadmapping that I’ve used with my teams over many years to prioritize decisions, stay user-focused, and collaborate effectively.</p><h3>Start with the why</h3><p>UX roadmapping empowers designers to advocate for their product ideas, ensures they have adequate time to do their projects justice, and prevents burnout. It increases transparency between UX, product management, and engineering by helping partners understand the effects that changes to the roadmap have on deliverable schedules.</p><p>Because UX is often the first step in product development, we work weeks or even months ahead of our engineering counterparts. This makes us particularly vulnerable to shifts in roadmap priorities that lead to frustration, churn, and abandoned work. This vulnerability makes it mission-critical for UXers to partner closely with product and engineering partners to share a clear understanding of the roadmap, timelines, and priorities.</p><p>I’ve created three resources to help you put an effective, complete roadmap together.</p><h3>Step 1: Identify the type of work you do</h3><p>Setting the right expectations with your partners on what you’re going to deliver is key. After all, different projects require different ways of working and different output. Start by creating a shared understanding of what different types of UX design projects look like, and what kinds of deliverables and timelines they result in.</p><p>Use this resource to create clear expectations for your partners of what kind of work you’ll be doing, what the deliverables will be, and why you might want to prioritize one type of project over another.</p><p>Read more in <a href="https://medium.com/indeed-design/4-types-of-design-projects-for-ux-roadmapping-7047a1d73ab6">4 Types of Design Projects for UX Roadmapping</a>.</p><h3>Step 2: Hold effective planning discussions</h3><p>Lots of talking goes into roadmapping UX projects — often between people with different expertise and perspectives. It’s important you have strategies ready to clarify, justify, and engage the people you need to stay aligned with.</p><p>This second part of planning is critical to ensuring everyone understands the plan and supports it. Read this resource to get a breakdown of talking points and questions.</p><p>Read more in <a href="https://medium.com/indeed-design/how-to-lead-effective-ux-roadmap-planning-discussions-44b3c057eb07">How to Lead Effective Roadmap Planning Discussions</a>.</p><h3>Step 3: Draft your shareable roadmap</h3><p>OK, now it’s time to actually sit down and write the document. You’ve gathered information, aligned with your colleagues, and know the way forward. It’s time to document your work.</p><p>But a blank document can be intimidating, and you want to create a clear roadmap so any teammate on the project can find their way. Read this resource for a step-by-step description of what to put in your document and how to organize it.</p><p>Read more in 8 Tips for Drafting a UX Roadmap Document Teams Will Actually Use, available <strong>February 19</strong>.</p><h3>Don’t get overwhelmed by the process</h3><p>Roadmapping is a highly collaborative undertaking that can feel daunting at first as you and your partners learn new, collective ways of planning and communicating. But it’s also important to know that it gets significantly easier the more you do it. Over time, you’ll all become more comfortable with these conversations — and projects that didn’t fit into the timeline for the current quarter tend to roll over to subsequent quarters.</p><p>So it’s important not to rush through the process. Instead, take the time to make sure your users and their needs are well-represented in your team’s prioritized work. You’ll notice a big payoff in efficiency and clarity. Happy roadmapping!</p><p><em>Stay in touch. </em><a href="https://medium.com/indeed-design"><em>Follow our publication</em></a><em> on Medium and learn about Indeed’s user experience team at </em><a href="http://indeed.design/"><em>Indeed Design</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e0ccb379d55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indeed-design/guide-to-ux-planning-how-to-create-a-roadmap-9e0ccb379d55">Guide to UX Planning — How to Create a Roadmap</a> was originally published in <a href="https://medium.com/indeed-design">Indeed Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a User Experience Is Social Work]]></title>
            <link>https://medium.com/indeed-design/building-a-user-experience-is-social-work-8ec000f12c01?source=rss-d3d661d1c30e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ec000f12c01</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[conscious-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Rebecca Granat Shapiro]]></dc:creator>
            <pubDate>Mon, 27 Mar 2023 16:29:27 GMT</pubDate>
            <atom:updated>2023-03-30T16:15:36.574Z</atom:updated>
            <content:encoded><![CDATA[<h4>How adopting a human advocacy mindset can help you serve users better.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yJLcdjKAm5daTvps-bgmCA.jpeg" /></figure><p>Before formal UX training programs were widely available, many people (including me) came to this field from different backgrounds: graphic design, web design, <a href="https://indeed.design/article/failing-into-tech-and-content-design">engineering</a>, psychology, medical research, anthropology, <a href="https://indeed.design/article/why-former-academics-make-great-ux-pros">academia</a>, and <a href="https://indeed.design/article/what-i-learned-switching-careers-from-taxonomy-to-content-design">technical writing</a>. And we brought with us the skills we’d learned in those earlier disciplines, collectively making our new field richer by sharing and incorporating the knowledge we’d gained elsewhere.</p><p>At first glance, my previous career seems pretty unusual for a transition to UX design. For years, I worked in homeless services in Seattle as a shelter and housing counselor. I served homeless and formerly homeless adults living with serious mental illness like schizophrenia, often compounded by co-occurring medical disabilities or self-medication.</p><p>When the economy hit a major downturn in the late 2000s, I decided I needed a change of career. I took advantage of new educational benefits and went back to school to study graphic design. I wanted to be a book designer.</p><p>But then something incredible happened. My program added its first-ever UX design class. On the first day, as my instructor discussed the basics of starting with your user and understanding and advocating for them, a lightbulb went off: “Oh! This is just the design version of social work.” Suddenly, my life path made sense.</p><p>A few key experiences from social services stayed with me as I <a href="https://indeed.design/article/9-lessons-from-my-switch-to-a-career-in-ux/">transitioned into a UX career</a>, and I’d like to share those with you in hopes they’ll help you see your users in a new way.</p><h3>UX is a lot like social work</h3><p>In both UX and social work, the job is to understand people, their unique needs and motivations, and how to connect and communicate with them. And in both roles, the practitioner’s job is to advocate for people who aren’t always able to advocate for themselves.</p><p>Social services systems in the US tend to be a network of byzantine bureaucracies designed piecemeal rather than holistically. They’re notoriously difficult to navigate even without a significant mental illness or disability, and people need expert advocates to help them get their needs met.</p><p>As UX practitioners, we need to be advocates for our users simply because they’re not in the room when we’re making key decisions on their behalf. The root causes are different, but our role is the same: Provide understanding and accommodation, and make it as easy as possible for our customers to achieve the outcomes they need.</p><h3>Success can be difficult to measure, so celebrate the small wins</h3><p>As a social worker, I saw the impact of my work firsthand, every day. Sometimes these wins were huge and measurable: A woman who had lived without a home for decades, consistently refusing housing or shelter, finally agreeing to move into an apartment.</p><p>At Indeed, we celebrate major wins like this all the time: A job seeker who’s been out of work for months or even years finally lands a great job.</p><p>But most of the time, as a social worker, these wins came in small, unmeasurable increments: A client finally trusted me enough to accept a hot chocolate packet. Another told a joke for the first time in decades. Someone let me cut the dust bunnies out of his hair and wash it for the first time in years.</p><p>We didn’t always have a great way to measure progress like that, but it didn’t make these victories any less important.</p><p>At data-focused companies, it can be easy to overlook the importance of building trust in small, difficult-to-measure ways. For example, at Indeed, I’m a UX director for the service that recommends job seekers we think will be a great match to employers and vice versa. And we work hard to build user trust with how we explain our recommendations. Or at least we believe this is building trust.</p><p>Trust is a difficult sentiment to regularly and reliably measure. But we can’t let this limitation of measurement get in the way of doing the right thing for our users.</p><p>We must continue to push our data, matches, and experiences in a trustworthy direction. We can’t forget the big picture: Human beings are frustrated with byzantine job searches and hiring processes, and we can help them.</p><h3>Overcome assumptions about people and their needs to make more meaningful impact</h3><p>The clients I worked with in homeless services were considered the most vulnerable within Seattle’s unhoused population. Most had significant co-occurring mental, physical, or chemical dependency conditions. And most were chronically homeless, meaning they’d lived in shelters or slept outdoors for decades.</p><p>People made assumptions about my clients, their needs, and their motivations all the time. We’ve all heard the damaging stereotypes about what unhoused people are like or why people are without a permanent residence in the first place.</p><p>One of my favorite clients was in her seventies. Let’s call her Gloria, but that’s not her real name. She was a pixie of a woman with dark eyeshadow in big circles around her pale blue eyes and a big, striped sweater.</p><p>I saw a lot of mental illness in that time, but Gloria’s intense hallucinations of being tortured were beyond terrifying. She constantly hit herself on her head to try to make them go away. Gloria had been homeless for decades before moving into supportive housing at one of the facilities where I worked.</p><p>It was easy for people to make assumptions about her, and about all my clients: That they don’t want to work, that they don’t have families, or good intentions. And if you give them money, they’ll spend it on drugs. To many, they’re lost causes.</p><blockquote><em>We need to continually remind ourselves that people regularly defy our assumptions about them.</em></blockquote><p>What most people couldn’t see was that Gloria was the strongest, kindest person I’ve ever known. As much pain and anguish as she lived with daily, she spent every evening cooking for the women who stayed in the small shelter on the first floor of our building. She looked after them.</p><p>She looked after me. I was 25, broke, and trying to figure out my life. We’d sit and talk in the evenings. Gloria told me about the shoes she saw in a store window that day and how she wanted me to have all the best things in life. She’d talk about jazz with a dreamy smile. She never talked about her past, but from off-hand comments about thoroughbreds, antiques, and estates, we guessed she’d had a privileged upbringing.</p><p>Two years after I went back to school for design, just before Christmas, I found out Gloria had had a stroke and was in the hospital. I went to visit her and brought gifts. The wonderful nurses there wanted to give her personalized care but didn’t know how because she was no longer verbal. I was able to tell them about her love of jazz, makeup, fine clothes, and antique furnishings. So they played music for her. They painted her nails.</p><p>Gloria passed before Christmas, but she wasn’t alone, and she was cared for in a personalized way that was especially important to her.</p><p>We need to continually remind ourselves that people regularly defy our assumptions about them.</p><p>In homeless services, most of my clients wanted to work but couldn’t hold a job because of their illness or their lack of housing. My clients had families they still had relationships with, but who could no longer care for them, or children from whom they’d been separated. Most had lived in housing for short periods but were quickly evicted because of the behaviors that can accompany schizophrenia.</p><p>They needed personalized housing where it was understood that they might shout in the middle of the night, need help with their hygiene here and there, and need vigilant protection from others who could take advantage.</p><blockquote><em>As UX professionals, we’re not helping our users if we’re not standing up and voicing their needs.</em></blockquote><p>At Indeed, we have the opportunity to think about our recommendations in a similar way.</p><p>Instead of only showing businesses the profiles of people with perfect resumes who exceed requested qualifications, we help people get jobs by connecting job seekers and employers using more efficient and effective parameters.</p><p>Indeed aims to provide helpful, transformational, and ethical experiences that help employers think beyond their assumptions of what the “perfect fit” candidate must look like. Our suggestions intend to broaden the playing field, encouraging employers to become more inclusive about who they hire. And we encourage job seekers to look beyond their own assumptions of what their abilities, helping them see their own strengths in a new light.</p><p><em>Is this article helpful? </em><a href="https://indeed.design/signup/"><em>Subscribe</em></a><em> to get occasional emails with new stories like it.</em></p><h3>Guiding principles UXers can take from social work</h3><p>Maybe the products you build and work on aren’t related to helping people get jobs or making sure they have basic survival needs. How you dedicate time, resources, and energy to your user still matters — a lot.</p><h4>1. UX is advocacy</h4><p>Our job is giving users a voice in our products. As UX professionals, we’re not helping our users if we’re not standing up and voicing their needs. Advocacy can be hard work and it can be uncomfortable, but we need to do it.</p><h4>2. Data and metrics often show us what’s easiest to measure</h4><p>Think about the streetlight fallacy: People who’ve lost their keys on the sidewalk spend all their time looking under the streetlight no matter where they actually lost their keys because that’s where it’s easiest to look.</p><p>If your data is only shedding a light on some of your wins, a whole lot of customers out there are still in the dark where it’s harder to shine that light and measure the win. Those customers need your help just as much as the folks under the lamppost.</p><blockquote><em>Truly great human-centered design means more than creating smooth technological interactions; it means opening up a world of everyday benefits to our users.</em></blockquote><p>As UX professionals, we don’t have the luxury I once had of immediate feedback, like a smile. But that shouldn’t stop us from trying to make those smiles happen, even if we can’t see them.</p><p>Think about it this way: If my agency had only focused on meeting numbers, we would’ve spent our time serving a population that was a lot less vulnerable, much easier to serve, and easier to move into housing. And in that case, like a lot of social service agencies, we would have left my clients out in the cold.</p><h4>3. We have a responsibility to help our users overcome their assumptions and make products more equitable</h4><p>At Indeed, we’re building the best job platform in the world. We have the power and the responsibility to make great jobs accessible to everyone.</p><p>But this mindset can be beneficial for any project at any company. As UX practitioners we sometimes work on life-or-death products like medical equipment. Others work on more everyday products like e-commerce sites or communications platforms.</p><p>Regardless of the stakes involved, our job is critical. We know every time someone interacts with a design, there’s a risk they won’t understand how it works, that they’ll make mistakes, that they’ll feel they’re not good enough, or that they can’t keep up with the world. Our users should never feel like this, and ensuring they don’t is one of the most important responsibilities we have as UX professionals.</p><p>But what if our products did even better: What if using our experiences made users feel confident, capable of using technology, and more independent? What would that unlock for them? Truly great human-centered design means more than creating smooth technological interactions; it means opening up a world of everyday benefits to our users.</p><h3>Treat every user like a human being</h3><p>At the end of the day, our job is to understand our users as unique individuals and design ways to effectively meet and solve for their unique needs. Advocacy without first fully understanding your users’ wants, needs, and struggles ultimately won’t be impactful for them.</p><p>With my clientele in homeless services, it wasn’t enough to simply offer someone an apartment. It had to be a place they felt safe, where the property staff were trained to support them through their struggles, and where they wouldn’t be evicted and back on the street the minute their mental health symptoms led them to exhibit unusual or “disruptive” behavior. It had to be personalized care.</p><p>The most important lesson I learned from my time in social services was the critical value of listening — really listening. Even if a user’s feedback doesn’t make sense to you or goes against what you believe to be true. Even when you think they’re just wrong or maybe don’t know what they’re talking about. Dive a little deeper than the specific thing they’re asking for.</p><p>Look for the underlying need being expressed. That’s what we need to solve for.</p><p><em>Stay in touch. </em><a href="https://medium.com/indeed-design"><em>Follow our publication</em></a><em> on Medium and </em><a href="https://indeed.design/signup"><em>Subscribe to our newsletter</em></a><em> to get occasional emails about new articles. Learn about Indeed’s user experience team at </em><a href="http://indeed.design/"><em>indeed.design</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ec000f12c01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indeed-design/building-a-user-experience-is-social-work-8ec000f12c01">Building a User Experience Is Social Work</a> was originally published in <a href="https://medium.com/indeed-design">Indeed Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>