User-centered design thinking and the product lifecycle

Can a one-person UX team inspire the organization to embrace a user-centered design philosophy?

Let's be honest: there's a long uphill battle ahead of you if you're going to affect change and instill a user-centered design thinking philosophy vertically with your superiors, and then horizontally throughout your organization. But it can be done. You just have to be willing to step up and prove it.

It all begins with looking for problems that need to be solved, then taking the initiative to prototype a solution that solves those problems. The most important thing to remember in this challenging (and sometimes rewarding) journey is that even if you're a team of one, you're not alone. Plenty of designers have walked this exact path—in this Insights Unlocked episode, one UX product designer talks about designing, testing, and launching products solo, including the personal and professional challenges of doing it without a built-in team around you.

"You can really be a team of one," said Karla Fernandes in the episode. "But you never build alone... you need to build with your customer. You need to build with a team. You need to build with your design friends because they are so good at giving you feedback."

Where do you find opportunities for improving experiences?

Anywhere. Opportunities for improvement are usually hiding in plain sight in your product or your place of business. It's like looking for extra tokens in a video game arcade; they are there, you just have to look for them. 

A classic example: a company relies on a static PDF report to inform an important internal process, but the data is outdated almost as soon as it's published, and the format can't do anything a live, interactive tool could. Recognizing that gap—a real workflow pain point, not a hypothetical one—is exactly the kind of "token" worth chasing.

Once you spot a problem like this, the fix is usually to build something real-time, searchable, and multimedia-enabled instead. It becomes much easier to convince colleagues to embrace user-centered design when they can see the pain points you're resolving and the waste you're reducing. Encourage everyone in your organization to find where customers (or they themselves) are struggling, and how you can help resolve those issues.

"Reducing friction and eliminating friction is really where we should focus, because those moments of reducing friction ultimately then generate that delight," said Craig Nishizaki in Episode 95 of Insights Unlocked, How to get executive buy-in for experience research.

How can you be sure you've discovered a problem that needs solving?

Once you've spotted your token, you'll need to pitch the idea to your manager to get buy-in. Next, start a conversation with your target audience—the people who'll actually use this product of yours.

Do your research and establish a list of stakeholders for the project from all angles: target audience, engineering, QA, project management, and so on. Reach out to these people. Boil your pitch down to something succinct that touches on the problem(s) you're solving and highlights the benefits—for them and for the company.

Getting this step right matters more than it might seem. If you want a deeper playbook for winning skeptics over before you've even built anything, these expert tips on getting stakeholder buy-in for user research are worth a read—including how to reframe pushback as its own kind of research problem.

Great, so you've validated the need for a solution. What's next?

Now that you've got a thorough list of requirements and are fully acquainted with the problem you're solving, it's time to open up your favorite wireframing tool—Figma is the go-to for most teams today—and start cranking out wireframes.

Start with a low-fidelity, clickable wireframe to validate your design assumptions. 

"It doesn't need to be high fidelity," said Leeyat Tessler, from the Capital One Innovation Lab in Episode 105 of Insights Unlocked. "It can be sketches on a whiteboard... as long as you're getting your idea across, you're succeeding."

Once you have clickable wireframes in front of you, put them in front of your primary stakeholder: your users. Observe them using your prototype (have them think out loud) and identify where they get stuck, what works, and what doesn't. Repeat this process until you've resolved the apparent problems with your assumptions.

Does prototype research end after wireframing?

Not at all. Because you want to test your design in the most realistic conditions possible, you'll want to bring those wireframes into a high-fidelity design. Design tools like Figma and Adobe XD have made this step faster and more collaborative than it's ever been.

AI-assisted features in tools like Figma can now generate design variations or speed up handoff, but they don't replace the validation step—a design still has to prove itself with real users before you trust it. And the UserTesting for Figma plugin and UserTesting's MCP server allow designers and others to easily get customer feedback from within the platforms they're using everyday. 

Once you have your high-fidelity design, you need to breathe life into it with a clickable prototype. This is an important step that's easy to overlook if you think your wireframes will be good enough—trust that the leadership you're pitching to won't understand the complete story you're trying to tell as clearly as a high-fidelity prototype would.

Leeyat said you don't need a fully-built or even coded product to validate a flow—faking the mechanism (manually sending a "notification" a system would normally trigger) lets you test reactions long before engineering gets involved.

The good news is that prototyping tools have gotten so much easier and faster to use that you don't have to invest a ton of time that feels wasted if your idea isn't greenlit for production. This keeps you from getting too attached to your design and helps you rebound much more quickly if your idea is rejected.

Once your prototype is ready, and after you've played with it enough times that you're sure it's awesome, it's time to test it with real users. Nothing shows the effectiveness (or the healthy, humbling ineffectiveness) of your design like watching real people succeed or struggle with it. Record each session and schedule a review with your manager and whole team so everyone can see the value of observational research. For a deeper look at exactly what to ask yourself while running these sessions, this list of essential prototype testing questions is a solid companion piece.

Can you talk about the pitching process? What's it like taking your idea to stakeholders?

Probably the most fun part after all this work is pitching your product to stakeholders.

Remember to be confident. You've iterated on your idea many times, and you've validated it again and again. It's a great idea, and your company will benefit from the improved user experience. Highlight the problem(s) you're solving, the benefits you're creating, and the value you're adding with your solution.

Craig describes a client at Microsoft who was skeptical of user research until he watched real users struggle with a prototype—after that, he requested research on every subsequent project, because seeing the value firsthand changes the calculus for skeptics.

"Once you see insights and value, you can't unsee it," he said.

If you want to sharpen this further, it's worth studying how experienced researchers frame ROI for leadership—these tips for investing in UX research and convincing stakeholders walk through prioritizing business impact and combining data types to make your case land.

What happens after the pitch is approved?

This is where the product lifecycle really kicks in. Getting sign-off isn't the finish line—it's the handoff into build, launch, and iterate. A few things worth carrying forward from everything you just did:

• Keep testing post-launch. The research doesn't stop once the product ships. Continued usability testing catches issues real usage patterns reveal that a pre-launch prototype never could.
• Track the outcomes you promised. If you pitched improved efficiency or reduced support tickets, follow up with the actual numbers. It's your best ammunition for the next pitch.
• Loop findings back into the next cycle. User-centered design is a lifecycle, not a single sprint — insights from this release should shape the backlog for the next one.

Teresa Torres, in her Insights Unlocked episode, "How to build products customers actually love with continuous discovery" reframes the $2 trillion/year rework problem: you can't eliminate rework, but you can control when it happens—cheaply, in prototypes and sketches, versus expensively, after the code is shipped.

"How do we have that rework happen when it's really inexpensive?... How do we have these mistakes and rework and iteration happen when it's basically cost free?"

For a broader view of where design and testing fit across every phase of building a product, this breakdown of the stages of the product development process is a useful reference to bookmark.

Do you have any advice for people who want to foster a user-centered design culture in their organization?

If you (like many designers once did) feel like a lone advocate dying to champion a user-centered design thinking philosophy in your workplace, you'll be amazed at how effective this approach can be. It all starts with taking a step back and looking at things differently.

Discovering unrealized needs requires intentionality. It's amazing how much you'll learn, and how quickly ideas will come, by indulging your curiosities and starting conversations with folks outside your department. Ask them what their biggest pain points are, and what they'd change if they had a magic wand.

Another huge benefit of this process is that it gets you outside your comfort zone and gives you the opportunity to meet and interact with people outside your normal environment.

AI tools can help you synthesize research findings and spot patterns across sessions faster, but they're a shortcut for the busywork, not a substitute for actually watching and talking to your users.

If you're looking to build this out into an actual program rather than a one-person crusade, it's worth learning from teams that have done exactly that—this walkthrough of starting a UX research program from scratch covers how to align user goals with executive priorities and build a real business case for the investment.

Those opportunities for improvement are out there, waiting to be found. Will you be the one to find them?

Additional resources

• Blog: What is User-Centered Design (UCD)?
• Blog: Mastering Product Design Prototyping and 31 Essential Prototype Testing Questions
• Podcast: How to succeed as a solo UX designer
• Webinar: Starting a UX Program from Scratch
• Webinar: Proving the Business Value of UX Research
• Guide: UX Research Field Guide: What is User Research and Why Does It Matter?
• Blog: The UX Designer's Guide to User Research