Testing Beats Arguments: Make Feedback Frequent, Fast, and Actionable

Hard - Requires significant effort Recommended

The pattern repeats: teams debate button colors, new menus, and every pixel on a screen. Everyone’s convinced their personal taste matches ‘what users want.’ Steve Krug, working for years as a usability consultant, saw arguments dissolve the moment real users were observed navigating a live prototype. Even the most confident designer or manager went quiet as someone failed a simple task.

He realized you don’t need enormous budgets or big labs. Set aside one morning a month, recruit three people from roughly the right audience, and have them attempt three or four real tasks. The feedback is instant, the learning visceral, and the fixes obvious.

Team members suddenly stop arguing over opinions and focus on reality—fixing the painful friction points users hit over and over. It’s not about proving whose design is better, but about building what actually works. Regular testing shrinks decision cycles and pumps energy into teams that no meeting could deliver.

Mark your calendar for a morning next month and stick to it—even if nothing big is launching. Recruit three people, ideally resembling your actual users, and have each try your product’s core tasks while you watch and listen. Don’t jump in; just take notes. After the session, debrief with your team over snacks or lunch, and agree on which top issues to tackle before the next round. Testing this way builds momentum and kills endless arguments. Give it a try and see what really works.

What You'll Achieve

Dramatically reduce time spent arguing about design, surface real problems early, and create a habit of learning from real user behavior—resulting in more effective and loved products.

Run DIY Usability Tests Each Month

1

Schedule a morning for testing every month.

Set a definite, recurring time so it happens regularly, not just before launches or after arguments.

2

Test with three relevant but available users.

Don’t overthink recruiting; use people close to your actual audience but remember that even generalists can uncover major issues.

3

Watch users attempt real tasks.

Give each participant 3–5 typical challenges (like ‘find event details’), observe without guiding them, and note where they struggle.

4

Debrief as a team and prioritize fixes.

Immediately after sessions, discuss findings and agree on the top usability problems to address before next testing.

Reflection Questions

  • How often do you observe actual users—not teammates—using your work?
  • Where are debates holding your team back from making improvements?
  • What would monthly, small-scale testing reveal that reviews and meetings never will?
  • How quickly could you organize a test this month?

Personalization Tips

  • At school, run a lunchtime ‘open table’ where students use your app as you watch quietly.
  • For your business, ask three customers a month to attempt top goals in your new product.
  • In a creative group, test a draft website and snack together as you decide what to fix.
Don't Make Me Think, Revisited: A Common Sense Approach to Web Usability (Voices That Matter)
← Back to Book

Don't Make Me Think, Revisited: A Common Sense Approach to Web Usability (Voices That Matter)

Steve Krug
Insight 7 of 8

Ready to Take Action?

Get the Mentorist app and turn insights like these into daily habits.