When I was hired as a senior product designer in one of the previous companies I worked for, one of the first things I was asked to do was build a usability testing process. It was a priority for the role. At the time, the team hadn't done much usability testing, not even informally. The challenge was equal parts intimidating and exciting.

At a previous job, I’d relied on guerrilla testing; they were quick, scrappy sessions that offered valuable insights even without formal structure. Those early experiences showed me just how much clarity and momentum usability testing could bring to a project. So when the opportunity came to start a formal process from scratch, I understood its importance. But I needed to get a process on digital paper and buy-in from stakeholders.

Demystifying Usability Testing

Krug's "Don't Make Me Think" has been helping designers and anyone involved in making digital products understand usability since it was first published in 2000. There’s a common mental hurdle around usability testing: the assumption that it’s complicated, expensive, and best left to specialists. But Krug demystifies usability testing in a way that makes it feel approachable.

He reminds us that testing doesn’t have to be a massive, budget-heavy operation to be effective. You can learn an incredible amount just by watching one person try to use the thing you're making, at any stage in the process. He makes the case, with humor and clarity, that small, frequent tests are not just possible, they’re often better.

That simplicity was key in getting my team and stakeholders on board. Once people saw that usability testing could be fast, lightweight, and immediately insightful, they were more than willing to try. And once they saw a real person struggle with something we thought was intuitive? That’s when they became believers.

From Ground Zero to a Real Process

I started by building the basics, which included a reusable template for observer instructions and participant tasks, a simple test script, and a lightweight recruiting process. We ran sessions monthly to start, recording everything and inviting team members to observe and take notes. Each session ended with a collaborative debrief, where we surfaced key findings and translated them into next steps.

Those debriefs turned out to be one of the most powerful parts of the process. They created shared understanding, fueled iteration, and helped everyone—regardless of their role—feel connected to the user experience.

Over time, our process matured. We worked out timing, solidified scripts, streamlined scheduling, and invited broader participation. EVen client-facing team members got involved. Usability testing went from a design initiative to a cross-functional habit.

Now, three years later, we’re running consistent usability sessions across multiple projects twice a month. The process is collaborative, adaptable, and embedded in how we work. Product managers know how it works and have been able to facilitate them. And the process continues to improve because team members feel empowered to contribute ideas and take ownership.

Why Usability Testing Matters

It’s easy to think we can design flawless experiences just by being thoughtful, but no amount of best practices or expertise can replace watching someone actually try to use your product. As soon as we started running usability testing sessions, we saw how they:

• Reveal the gap between intention and experience
• Help prioritize what really matters to users
• Speed up iteration and reduce risk
• Build team-wide empathy and alignment

Even brief sessions can uncover moments of confusion or frustration that aren’t obvious in design files. And once you see those, you can’t unsee them, which makes the product better, faster.

What I Learned Along the Way

Facilitation is a learned skill. In the beginning, I leaned heavily on scripts and was a little rigid. But over time, I learned to be present, listen actively, and respond to what was happening in the moment. A good facilitator makes space for discovery without leading participants too much.

Testing is even more valuable if you talk about it with stakeholder. Running a session is one thing, but debriefing with the team is where the real value shows up. Those conversations are where insight turns into action. They also create shared language across teams and foster alignment.

Trust is everything, especially with client-facing teams. When testing with real clients, trust is crucial. These teams need to know that the testing process won’t embarrass them or damage relationships. I worked hard to communicate our goals clearly, respect the context, and demonstrate how testing improves client outcomes. That trust took time to build, but it made the entire process stronger.

You Don’t Need a Perfect Plan

If you’re thinking about starting usability testing but feeling overwhelmed, here’s the truth: you don’t need a perfect system. You don’t need a lab. You don’t need a full research team. You just need to start.

Start with one person. One test. One honest debrief. Then do it again. And again. That’s how culture changes. That’s how products get better. That’s how teams build empathy and alignment around what really matters: making things that work for the people they’re meant to serve.