# User Research Published articles for User Research. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## From Concept to Restaurant Pilot in Under a Year DevFeed: [From Concept to Restaurant Pilot in Under a Year]() Original publisher: [Read original article]() Author: Global Technology Published: 2026-08-25T17:13:54Z Content type: article Language: en Sources: [McDonald's Technical Blog - Medium]() Topics: [User experience (UX)](), [User interface design](), [Usability](), [Front end](), [Testing]() Tags: [collaboration](), [digital-transformation](), [frontend](), [innovation](), [product-development](), [prototyping](), [testing](), [usability](), [user-research](), [ux](), [ux-design]() ### AI overview The article describes how McDonald's used user research, rapid prototyping, cross-functional collaboration, and real-world testing to develop Sesame UX and move it from concept to a live restaurant pilot in under a year. The work addressed crew needs, operational complexity, and business priorities for the company's global POS system. ### Source excerpt How McDonald's combined user research, rapid prototyping, and cross-functional collaboration to bring Sesame UX from idea to reality. by: Ryan Bush, Sr Manager, UX Design & Kartik Patel, Software Engineer II Quick Bytes Bringing a new Point-of-Sale (POS) experience to life at McDonald's scale required balancing crew needs, operational complexity, and business priorities Research, prototyping, and real-world testing showed a new approach could improve speed, accuracy, and usability for crew members Sesame UX moved from concept to a live restaurant pilot in under a year, demonstrating measurable improvements and a new approach to innovation at scale Creating meaningful change at the scale of McDonald's means navigating deeply entrenched operational practices, specialized technology, and market-specific requirements. Any new idea must not only solve a meaningful problem but also demonstrate value that resonates across a broad and diverse set of stakeholders. Driving transformative innovation in an organization at this scale requires building shared alignment around the root problem, the opportunity it presents, and the value a proposed solution can create. It also requires using cost-efficient methods to prove to stakeholders the undeniable value of the change, along with a team of determined individuals who can get creative and who aren't deterred by obstacles or setbacks. McDonald's global Point-of-Sale (POS) system, Sesame, is actively used by over one million crew members worldwide. Markets, Owner/Operators, and managers have invested significant time and resources in training crew members to use the system, and thousands of crew members have mastered the POS experience. With this level of scale and investment, how could an organization evolve the frontend POS experience while building on the strengths of an already proven platform? How could the benefits outweigh the cost of the change? Building on a foundation used by millions The Sesame platform has evolved over ## Dogfooding vs. QA vs. User Research DevFeed: [Dogfooding vs. QA vs. User Research]() Original publisher: [Read original article]() Author: Therese Fessenden Published: 2026-08-07T17:00:00Z Content type: article Language: en Sources: [NN/g latest articles and announcements]() Topics: [dogfooding](), [FIRST]() Tags: [article](), [bugs](), [development](), [dogfooding](), [qa](), [qc](), [quality-assurance](), [quality-control](), [user-research](), [user-testing]() ### AI overview Dogfooding--using a company's own products internally--can reveal bugs, broken flows, crashes, and missing features while building empathy and shared ownership. The article explains that it complements but cannot replace user research, because insiders understand the product too well to represent real users. It also distinguishes genuine dogfooding from performative displays of loyalty. ### Source excerpt Dogfooding, or using your own products internally, helps catch bugs, but it can't replace user research: your team knows too much to represent real users. ## UX Conference October Announced (Oct 26 - Oct 29) DevFeed: [UX Conference October Announced (Oct 26 - Oct 29)]() Original publisher: [Read original article]() Published: 2026-08-04T08:43:32Z Content type: news Language: en Sources: [NN/g latest articles and announcements]() Topics: [User experience (UX)](), [Artificial Intelligence](), [Usability]() Tags: [ai](), [conference](), [event](), [learn](), [skills](), [training](), [usability](), [user-research](), [ux]() ### AI overview NN/G announces live virtual UX training courses running October 26-29, 2026. The program covers UX best practices, hands-on exercises, collaboration, certification, and optional specialties including AI for design workflows, AI product strategy, usability testing, and AI-assisted user research. ### Source excerpt Take up to 2 in-depth training courses, teaching user experience best practices for successful design. Training focused on long-lasting skills for UX professionals. October 26 - October 29, 2026. ## Why You Need Mentorship and How to Get It Right DevFeed: [Why You Need Mentorship and How to Get It Right]() Original publisher: [Read original article]() Author: Evan Sunwall Published: 2026-07-31T17:00:00Z Content type: article Language: en Sources: [NN/g latest articles and announcements]() Topics: [User experience (UX)](), [Software]() Tags: [article](), [career](), [design](), [growth](), [user-research](), [work]() ### AI overview This article explains why mentorship is valuable throughout a career, challenges common reasons people avoid it, and describes how sustained guidance can improve work quality, confidence, relationships, and professional growth. ### Source excerpt Mentorship is an essential growth tool that offers substantial personal and career benefits, but only if you engage in it properly. ## What does a platform product manager do? DevFeed: [What does a platform product manager do?]() Original publisher: [Read original article]() Author: Mallory Haigh Published: 2026-07-23T08:14:05Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [Product Management](), [Developer experience]() Tags: [architecture](), [developer-experience](), [developer-platform](), [developers](), [engineering](), [internal-developer-platform](), [management](), [organizational](), [platform](), [platform-engineering](), [platforms](), [product](), [product-management](), [product-strategy](), [strategy](), [technical](), [user-research]() ### AI overview This guide explains the role of a Platform Product Manager (PPM) in driving strategy for an Internal Developer Platform. PPMs connect technical platform capabilities with developer needs through user research, feedback loops, roadmaps, stakeholder management, and outcome metrics. The article distinguishes product thinking from project management and describes how continuous prioritization and clear platform boundaries support adoption. ### Source excerpt Platform Product Managers drive internal developer platform strategy, bridging technical capabilities and developer needs through research, roadmaps, and stakeholder management. ## Time is Money: How Pre-Validated UX Research Protects Your Resources & Budget DevFeed: [Time is Money: How Pre-Validated UX Research Protects Your Resources & Budget]() Original publisher: [Read original article]() Author: Christian Holst Published: 2026-06-30T11:45:00Z Content type: article Language: en Sources: [Baymard Institute]() Topics: [User Experience](), [Usability](), [Testing](), [Website]() Tags: [cost-savings](), [subscription](), [usability](), [user-research](), [ux]() ### AI overview The article presents a calculator intended to estimate initial savings from using Baymard's pre-validated UX research instead of conducting new in-house research. It states that a moderated usability study with 15 participants requires about 55 hours of labor and estimates the cost of producing one UX insight at $362 in the US and $262 in the UK and Europe. ### Source excerpt (Note: Unfortunately, e-mail and RSS don't support advanced layouts and features. If the graphics in this article look strange, you may want to read the article in your web browser.) When you try to prove the value of your design decisions, you often hit a wall. To back up your designs confidently, you need robust usability research. But conducting that research yourself for every minor UI change or UX decision is expensive and time-consuming. Baymard's pre-validated research gives teams like yours access to established UX best practices in an instant, which helps you ship designs faster, more confidently, and protects your costs by reducing the research overheads. To demonstrate that value, we've created a calculator that shows how a Baymard subscription helps you move faster and keep your UX research costs down. Note: This calculator demonstrates initial cost savings based on consuming Baymard's insights versus running new user research yourself. Baymard users typically see further value realizations from implementing those insights and improving website user experience and conversion rates. The Hidden Cost of Your In-House User Research It's easy to fall into the trap of thinking: "We can just replicate this research in-house for less cost." But when you try to build everything from scratch without access to pre-validated UX insights, your team quickly runs into three major roadblocks: You move slower: Your product teams lose momentum and your project timelines stretch out because you are forced to conduct research from scratch You risk harming conversions: When timelines get tight, you risk making critical UX decisions based on gut feelings, which can ultimately harm your conversion rates You spend more money: To keep up with research demands, you end up spending vastly more on external agency services or expanding your internal headcount just to conduct baseline testing What It Actually Costs You to Produce a UX Insight To protect your resources, you need to sh ## The Benefits Of Cognitive Inclusion In UX Research DevFeed: [The Benefits Of Cognitive Inclusion In UX Research]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Kate Kalcevich) Published: 2026-06-10T10:00:00Z Content type: article Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [User experience (UX)](), [Accessibility](), [Usability]() Tags: [accessibility](), [design](), [digital-products](), [guide](), [insights](), [prototyping](), [research](), [survey](), [testing](), [usability](), [user-research](), [ux]() ### AI overview An exploratory UX research study examines whether participants with cognitive disabilities uncover more usability insights than general-population participants. It describes recruitment and screening, research practices, a pilot with 25 testers, user interviews, surveys, and a joint validation study using websites built with an AI prototyping tool. ### Source excerpt Findings from an exploratory user research study highlighting the unique insights and practical UX recommendations shared by participants with cognitive disabilities. ## Good designers, bad websites: a proposal DevFeed: [Good designers, bad websites: a proposal]() Original publisher: [Read original article]() Author: by Alan Dalton Published: 2026-04-23T12:57:21Z Content type: opinion Language: en Sources: [A List Apart: The Full Feed]() Topics: [User interface design]() Tags: [accessibility](), [accessibility-community-user-experience-user-research-workflow-tools](), [community](), [design](), [usability](), [user-experience](), [user-research](), [workflow-tools]() ### AI overview An opinion article arguing that accessibility must be central to website design. It discusses how designs can exclude people with different sensory, cognitive, and mobility needs, and proposes using usability heuristics to help designers recognize accessibility issues. ### Source excerpt I want to discuss accessibility because it is the most important thing for making websites. Other A List Apart articles give you innovation and insight. This article will give you homework. These are just my personal views, but they're pretty good. I want to start off with a couple of statements, and you will agree: Designers are good people. I have never heard a designer say, "I don't care if somebody can't read this text", "Not my fault if somebody can't use this device", or "Who cares if this is confusing?" Some designs exclude people. You have seen people unable to read the text on a website or app that somebody designed. You've seen people unable to use a physical device that somebody has designed. You've seen people utterly bamboozled while trying to use a service that somebody designed. So what? The first question is, "Is this life-or-death stuff?" The answer is, "Yes." In my favorite essay, This Is All There Is, Aral Balkan makes the point that pretty much everything that we design can affect life events and death events. Aral gives the example of how even a straightforward bus timetable app can affect life and death events, if we design it badly: somebody might miss a life event, such as their daughter's fifth birthday party; or somebody might miss a death event, such as the chance to say goodbye to a dying grandmother. The next--and frustrating--question is, "Why do some designs still exclude people?" After all, we know that: not everybody can see perfectly; not everybody can hear perfectly; not everybody thinks the same way; and not everybody moves the same way. I think the answer is that there's too much to recall. Consider, if you will, the wide variety of topics that A List Apart articles cover. Designers are expected to remember all of that guidance, plus all of the accessibility guidance, plus so much more. It is too much. Recognizing accessibility issues while designing I'd like to point toward one possible solution, starting from Jakob Nielsen's 10 U ## How We Hire Product Designers at Teleport DevFeed: [How We Hire Product Designers at Teleport]() Original publisher: [Read original article]() Author: sheila.maniago@goteleport.com (Sheila Maniago) Published: 2026-02-23T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [User Experience](), [Product Management]() Tags: [designer](), [hiring](), [interview](), [portfolio](), [product-design](), [product-strategy](), [prototyping](), [user-research]() ### AI overview Teleport explains its four-step Product Designer hiring process, covering the recruiter call, hiring manager interview, portfolio review, and a collaborative product design challenge. ### Source excerpt Learn how Teleport hires Product Designers -- a transparent 4-step process including portfolio review and a real design challenge. See if you're a fit. ## Strengthening ChatGPT's responses in sensitive conversations DevFeed: [Strengthening ChatGPT's responses in sensitive conversations]() Original publisher: [Read original article]() Published: 2025-10-27T10:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [OpenAI](), [Artificial Intelligence](), [Testing]() Tags: [ai](), [chatgpt](), [health](), [mental-health](), [openai](), [safety](), [testing](), [user-research]() ### AI overview OpenAI describes improvements to ChatGPT's handling of sensitive conversations, developed with more than 170 mental health experts. The update aims to better recognize distress, respond empathetically, de-escalate conversations, guide users toward professional or crisis support, and reduce unsafe responses. ### Source excerpt OpenAI collaborated with 170+ mental health experts to improve ChatGPT's ability to recognize distress, respond empathetically, and guide users toward real-world support--reducing unsafe responses by up to 80%. Learn how we're making ChatGPT safer and more supportive in sensitive moments. ## From Beta to Bedrock: Build Products that Stick. DevFeed: [From Beta to Bedrock: Build Products that Stick.]() Original publisher: [Read original article]() Author: by Liam Nugent Published: 2025-04-23T18:04:31Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [bedrock](), [Security]() Tags: [bedrock](), [business](), [business-industry-usability-user-experience-user-research-web-strategy](), [development](), [finance](), [industry](), [security](), [usability](), [user-experience](), [user-research](), [web-strategy]() ### AI overview The article argues that financial products should be built around a stable bedrock of clear customer value rather than an accumulation of features. It discusses the risks of feature-first development, the role of a Minimum Viable Product, and the need to resist internal pressures that can produce confusing, bloated experiences. ### Source excerpt As a product builder over too many years to mention, I've lost count of the number of times I've seen promising ideas go from zero to hero in a few weeks, only to fizzle out within months. Financial products, which is the field I work in, are no exception. With people's real hard-earned money on the line, user expectations running high, and a crowded market, it's tempting to throw as many features at the wall as possible and hope something sticks. But this approach is a recipe for disaster. Here's why: The pitfalls of feature-first development When you start building a financial product from the ground up, or are migrating existing customer journeys from paper or telephony channels onto online banking or mobile apps, it's easy to get caught up in the excitement of creating new features. You might think, "If I can just add one more thing that solves this particular user problem, they'll love me!" But what happens when you inevitably hit a roadblock because the narcs (your security team!) don't like it? When a hard-fought feature isn't as popular as you thought, or it breaks due to unforeseen complexity? This is where the concept of Minimum Viable Product (MVP) comes in. Jason Fried's book Getting Real and his podcast Rework often touch on this idea, even if he doesn't always call it that. An MVP is a product that provides just enough value to your users to keep them engaged, but not so much that it becomes overwhelming or difficult to maintain. It sounds like an easy concept but it requires a razor sharp eye, a ruthless edge and having the courage to stick by your opinion because it is easy to be seduced by "the Columbo Effect"... when there's always "just one more thing..." that someone wants to add. The problem with most finance apps, however, is that they often become a reflection of the internal politics of the business rather than an experience solely designed around the customer. This means that the focus is on delivering as many features and functionalities as pos ## Save time on building decks--without sacrificing design DevFeed: [Save time on building decks--without sacrificing design]() Original publisher: [Read original article]() Author: Jenny Xie Published: 2025-02-26T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [GUI]() Tags: [ai](), [animation](), [building](), [design](), [graphics](), [image](), [images](), [library](), [pdf](), [plugin](), [plugins](), [presentation](), [time](), [ui](), [user-research](), [video]() ### AI overview This Figma article announces the open beta of Figma Slides and highlights plugins that help users create and refine presentations. The examples cover image and icon libraries, gradient backgrounds, editable PDF imports, animation, AI-generated avatars, and video tools. ### Source excerpt From extensive image libraries to design cleanup, plugins for Slides are here to help you prepare and polish your presentation. ## User Research Is Storytelling DevFeed: [User Research Is Storytelling]() Original publisher: [Read original article]() Author: by Gerry Duffy Published: 2024-05-30T18:04:43Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [User experience (UX)](), [User Experience]() Tags: [best-practices](), [research](), [user-experience](), [user-experience-user-research](), [user-research](), [ux]() ### AI overview The article presents user research as storytelling. It recommends using a three-act structure--setup, conflict, and resolution--to explain research, engage stakeholders, understand users' problems, and show how research informs design decisions. ### Source excerpt Ever since I was a boy, I've been fascinated with movies. I loved the characters and the excitement--but most of all the stories. I wanted to be an actor. And I believed that I'd get to do the things that Indiana Jones did and go on exciting adventures. I even dreamed up ideas for movies that my friends and I could make and star in. But they never went any further. I did, however, end up working in user experience (UX). Now, I realize that there's an element of theater to UX--I hadn't really considered it before, but user research is storytelling. And to get the most out of user research, you need to tell a good story where you bring stakeholders--the product team and decision makers--along and get them interested in learning more. Think of your favorite movie. More than likely it follows a three-act structure that's commonly seen in storytelling: the setup, the conflict, and the resolution. The first act shows what exists today, and it helps you get to know the characters and the challenges and problems that they face. Act two introduces the conflict, where the action is. Here, problems grow or get worse. And the third and final act is the resolution. This is where the issues are resolved and the characters learn and change. I believe that this structure is also a great way to think about user research, and I think that it can be especially helpful in explaining user research to others. Three-act structure in movies (© 2024 StudioBinder. Image used with permission from StudioBinder.). Use storytelling as a structure to do research It's sad to say, but many have come to see research as being expendable. If budgets or timelines are tight, research tends to be one of the first things to go. Instead of investing in research, some product managers rely on designers or--worse--their own opinion to make the "right" choices for users based on their experience or accepted best practices. That may get teams some of the way, but that approach can so easily miss out on solving users ## The future of design systems is marketing DevFeed: [The future of design systems is marketing]() Original publisher: [Read original article]() Author: Ana Boyer Published: 2024-04-10T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Architecture & Design](), [Scalability]() Tags: [communication](), [design](), [design-systems](), [developers](), [efficiency](), [engineering](), [marketing](), [product-design](), [product-development](), [scalability](), [user-research]() ### AI overview The article argues that design systems should be treated as products and actively marketed to increase organizational adoption. It recommends developing compelling narratives, identifying internal champions, measuring impact, and researching the needs and frustrations of designers, developers, and decision-makers. ### Source excerpt Design systems promise consistency, efficiency, and scalability, but realizing these benefits hinges on widespread usage. To get your entire team on board, you'll need to tap into your inner marketer and craft a compelling adoption strategy. ## How Figma's data science and user research teams weave together insights that count DevFeed: [How Figma's data science and user research teams weave together insights that count]() Original publisher: [Read original article]() Author: Jenny Xie Published: 2023-10-25T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Data Science](), [data]() Tags: [collaboration](), [communication](), [data-science](), [figma](), [insights](), [research](), [user-research]() ### AI overview Figma's data science and user research teams combine quantitative analysis with qualitative research to understand why notifications fall short. Their investigation found that many users were not receiving notifications and identified opportunities to improve alert types and recipient timing. ### Source excerpt A cross-functional team brought together quantitative and qualitative learnings to figure out why notifications were falling short--and how to make them better. ## Heroku User Research Program: A Catalyst for Collaboration and Growth DevFeed: [Heroku User Research Program: A Catalyst for Collaboration and Growth]() Original publisher: [Read original article]() Author: Andrew McGrath Published: 2023-10-12T22:10:50Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [User experience (UX)](), [Development]() Tags: [customer](), [customer-experience](), [features](), [heroku](), [innovation](), [insights](), [new-features](), [news](), [product-development](), [products](), [research](), [services](), [user-research](), [voice]() ### AI overview Heroku describes its User Research Program, through which customers provide feedback, test new features, and share insights with product teams. The article reports interviews, UX studies, workshops, and feedback-driven influence on the public roadmap, while noting that future roadmap items are not guaranteed. ### Source excerpt At Heroku, we're on a mission to continuously improve our products and services to provide the best possible customer experience. Feedback is at the heart of our innovation, and we're excited to highlight the Heroku User Research Program. Through this initiative, our customers provide feedback, test new features, and share their insights directly with our [...] The post Heroku User Research Program: A Catalyst for Collaboration and Growth appeared first on Heroku. ## How To Create A Product Roadmap DevFeed: [How To Create A Product Roadmap]() Original publisher: [Read original article]() Author: Mike Wolfson Published: 2023-09-26T19:24:52Z Content type: tutorial Language: en Sources: [My Big Appetite - Mike Wolfson]() Topics: [Product Management](), [Users](), [App](), [Development]() Tags: [application](), [how-to](), [practical](), [product-management](), [user-research]() ### AI overview A practical introduction to creating a product roadmap for a new application. It describes validating an idea, researching users and pain points, defining features, and planning development in sequential phases. ### Source excerpt Overview of practical steps to create a product roadmap for a new application. ## Feature Definition DevFeed: [Feature Definition]() Original publisher: [Read original article]() Author: Mike Wolfson Published: 2023-09-02T21:13:02Z Content type: article Language: en Sources: [My Big Appetite - Mike Wolfson]() Topics: [decision-making](), [Users]() Tags: [article](), [decision-making](), [product](), [team](), [user-research]() ### AI overview An article about defining product features by researching users and their problems, brainstorming with stakeholders, capturing and grouping ideas, and prioritizing the resulting feature list. ### Source excerpt Introduction In this article, I will explain the tasks and objectives of the feature definition phase, which involves formalizing a list of things to do, and evaluating ideas to prioritize them. The difference between a great product and an average one often boils down to the features it offers and how they align with market demands. By the end of this phase, you will have a detailed list of features with high-level details about each of them, and an understanding of how they align to meet the company goals. Before diving into the this phase, you should conduct user research to gather valuable insights that inform your decision-making process. You should have identified your target audience and the key problems that you aim to solve. This will guide your decisions and should serve as a guide post for everyone involved in the process. Brainstorm To gather a list of features, you will want to brainstorm with the right people. This will ensure you capture diverse perspectives, foster creativity, validate assumptions, and get stakeholders involved. When creating a brainstorming process, keep the following things in mind: Define the objective: Clearly state the problem you are trying to solve, to keep everyone aligned. Gather the right team: Make sure your sessions have people with diverse perspectives from various teams. Logistics: Use a functional meeting environment, and have the right tools (whiteboards, sticky notes, comfortable room). The brainstorming process will follow this format: Set ground rules: Tell the team about the expectations, and priorities of the effort, and clearly state that all ideas are welcome, and criticism and debate are not. Select a brainstorming method: Choose which brainstorming technique you will use for this effort. Capture ideas: Have the team share all their ideas (nothing is too wild). Record every single idea on sticky notes, or in digital tools. Group and Prioritize: Clarify the ideas as a team, and group similar ideas together. Def ## User Research DevFeed: [User Research]() Original publisher: [Read original article]() Author: Mike Wolfson Published: 2023-09-01T21:17:58Z Content type: tutorial Language: en Sources: [My Big Appetite - Mike Wolfson]() Topics: [Users](), [Usability](), [iteration](), [Development]() Tags: [article](), [interviews](), [product](), [product-development](), [product-strategy](), [research](), [survey](), [testing](), [usability](), [user-research](), [users]() ### AI overview A practical guide to user research for new product development. It presents a recurring process covering research planning, audience definition, data collection, analysis, and applying findings to product iteration. ### Source excerpt Introduction When creating a new product, it is important to develop a process to gain insights into your target audience and refine your product strategy to create user-centric solutions. This article outlines a plan to systematically engage with users, to understand their needs, behaviors, and pain points. Executing this plan will ensure your product resonates with users, solves the correct problems, and will thrive in a competitive market. There are 3 phases to this process, and you likely will iterate through the entire process multiple times, as you develop your learnings. This article outlines the important tasks in each of these efforts: Planning and Preparation Data Collection and Analysis Application and Iteration Let's dig into each of these phases to understand how they collectively shape the trajectory of user-focused product development. Phase 1: Planning and Preparation The initial phase of user research starts the journey into understanding user needs and preferences. You will define clear research objectives, identify your audience, and establish the roadmap for engaging with them. Define Research Objectives Setting clear goals is important in any project. Make sure to spend time identifying them, and writing them down. Define Goals: Clearly outline the goals and objectives of your research. Clarify Research Output: Define the specific information you aim to collect? Understand User Needs: Understand the specific user needs, pain points, preferences, and behaviors you are going to focus on Identify Target Audience: Identify the demographics, behavior and characteristics of your users. Focus on specific personas, and gather insights from the right people. Create a plan With your objectives, and target audience in mind, create a plan to perform the research. Depending on research constraints, you will need to decide which research methods to use. There are a variety to consider, including interviews, surveys, usability testing, observations, and focus ## The anatomy of launching a Figma open beta DevFeed: [The anatomy of launching a Figma open beta]() Original publisher: [Read original article]() Author: Emily Brody Published: 2023-07-24T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Go]() Tags: [bugs](), [communication](), [dev](), [developers](), [features](), [figma](), [open](), [user-research](), [workflows]() ### AI overview Figma describes the two weeks after launching Dev Mode as a period for tracking feature usage, gathering community feedback, monitoring bugs, and iterating on the product. The article emphasizes cross-functional collaboration among product, marketing, support, design, data, and developer-focused teams. ### Source excerpt A go-to-market strategy doesn't just end on launch day. For this installment of Anatomy Lessons, an ongoing series where we go deep on how to make products and get work done, we're putting our very own Dev Mode under the scalpel to dissect what's at play in the critical two-week period after launch. ## The Management Poles of Developer Infrastructure Teams DevFeed: [The Management Poles of Developer Infrastructure Teams]() Original publisher: [Read original article]() Author: Mark Côté Published: 2022-10-28T17:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Developer Tools]() Tags: [career](), [developer](), [developers](), [infrastructure](), [management](), [product](), [software](), [software-development](), [support](), [systems](), [user-research](), [ux](), [workflow]() ### AI overview The article presents three competing management poles for developer infrastructure teams: management support, system and domain expertise, and road maps. It describes why infrastructure managers must balance coaching, operational support, and specialized team knowledge. ### Source excerpt There are 3 management poles for developer infrastructure teams that are thus tricky to balance: management support, system and domain expertise, and road maps. ## A Better Way to Upload Images DevFeed: [A Better Way to Upload Images]() Original publisher: [Read original article]() Author: Prabhat Godse Published: 2022-08-10T14:25:00Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [Website](), [Mobile](), [browser](), [App](), [Library]() Tags: [app](), [browser](), [images](), [library](), [metrics](), [mobile](), [user-research](), [website]() ### AI overview This Squarespace engineering article describes the design and development of a photo-importing experience that lets users access photos from the Squarespace Mobile App while editing a website in a desktop browser. It discusses user research, design trade-offs, and an initial Mobile Image Uploader whose engagement was below expectations. ### Source excerpt Imagine you are editing your Squarespace website on your desktop browser and you want to add great photos that make your site stand out. At that moment, you realize those great photos are actually on your phone. Wouldn't it be great if you could cut out all the intermediate steps and directly access your phone's photo library right from the desktop browser into your Squarespace website? ## Stay in the flow with redesigned comments DevFeed: [Stay in the flow with redesigned comments]() Original publisher: [Read original article]() Author: Ryhan Hassan Published: 2021-11-16T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Web]() Tags: [design](), [figma](), [prototypes](), [research](), [review](), [updates](), [user-research](), [web]() ### AI overview Figma is introducing a redesigned comment experience for Figma and FigJam. The updates make comments easier to discover, improve feedback quality through shorter comments and reactions, and help teams manage and act on feedback more effectively. ### Source excerpt Today, we're introducing updates to comments to make it more intuitive for teams to share, manage, and act on relevant feedback. ## How to Sell UX Research with Two Simple Questions DevFeed: [How to Sell UX Research with Two Simple Questions]() Original publisher: [Read original article]() Author: by Sophia V. Prater Published: 2021-10-21T14:00:00Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [User experience (UX)](), [Interaction Design](), [User interface design]() Tags: [article](), [design](), [interaction-design](), [user-experience](), [user-experience-user-research](), [user-research](), [ux]() ### AI overview This article explains how to use two questions--what the objects are and how they relate--to help stakeholders recognize risky assumptions, hidden complexity, and the need for UX research. It presents ORCA, an iterative methodology for turning research into a structural foundation for object-oriented UX, screen design, and interaction design. ### Source excerpt Do you find yourself designing screens with only a vague idea of how the things on the screen relate to the things elsewhere in the system? Do you leave stakeholder meetings with unclear directives that often seem to contradict previous conversations? You know a better understanding of user needs would help the team get clear on what you are actually trying to accomplish, but time and budget for research is tight. When it comes to asking for more direct contact with your users, you might feel like poor Oliver Twist, timidly asking, "Please, sir, I want some more." Here's the trick. You need to get stakeholders themselves to identify high-risk assumptions and hidden complexity, so that they become just as motivated as you to get answers from users. Basically, you need to make them think it's their idea. In this article, I'll show you how to collaboratively expose misalignment and gaps in the team's shared understanding by bringing the team together around two simple questions: What are the objects? What are the relationships between those objects? A gauntlet between research and screen design These two questions align to the first two steps of the ORCA process, which might become your new best friend when it comes to reducing guesswork. Wait, what's ORCA?! Glad you asked. ORCA stands for Objects, Relationships, CTAs, and Attributes, and it outlines a process for creating solid object-oriented user experiences. Object-oriented UX is my design philosophy. ORCA is an iterative methodology for synthesizing user research into an elegant structural foundation to support screen and interaction design. OOUX and ORCA have made my work as a UX designer more collaborative, effective, efficient, fun, strategic, and meaningful. The ORCA process has four iterative rounds and a whopping fifteen steps. In each round we get more clarity on our Os, Rs, Cs, and As. The four rounds and fifteen steps of the ORCA process. In the OOUX world, we love color-coding. Blue is reserved for objec [Next page]()