How to Handle Frustrating Users: A Lesson From My CEO
How to handle frustrating users.
There was a user who had extreme difficulty using our product, no matter how obvious the UI and UX seemed to us. This was during the early days of a startup I used to work with.
Over time, I got frustrated with his negative feedback on every single new release. Nothing was ever good enough. Every feature had something wrong. Every flow was "confusing."
I raised this concern with my CEO. And he gave me some important lessons that I would carry forward for the rest of my product career.
TL;DR: Not all user feedback is equal, but all feedback has value if you know where to apply it. A persistently critical user represents the segment who "can't think" or wants everything to be extremely obvious. Ignore their feedback on expert features, but deeply value their input on end-user experiences. A strong critic is 100x better than a silent user in the early stages.
The conversation that changed my perspective
CEO: "First of all, do not get offended."
Me: (trying not to look offended)
CEO: "Second, you are not looking at this guy in the right way."
Me: (surprised) "How are you looking at him?"
CEO: "See, he best represents the population who can't think. Or the ones that want everything to be extremely obvious. He's not an edge case. He IS the average user in many segments."
Me: "OK, then should we consider all his feedback?"
CEO: "Not really. I always ignore his feedback on features targeted at Admins. They're technical enough and may not expect so much hand-holding on everything. But I always value his feedback, or at least stop and think for a moment, when he comments about end-user use cases. Because we would want to provide a buttery smooth UX for them."
And then the line that stuck: "Also remember, a strong critic is always 100x better than a silent user in the early stages."
Why this reframing matters
Before this conversation, I saw this user as:
- Annoying
- Unreasonable
- "Not our target user"
- Someone who just complains
After this conversation, I saw him as:
- A signal for an entire user segment
- A free, ongoing usability tester
- Someone who surfaces friction that others silently tolerate
- A gift (especially in early-stage products)
The reframing didn't change the user. It changed how I used his input. And that made all the difference.
The framework: when to listen vs. when to ignore
Not all feedback from a critical user is equally valuable. The key is matching feedback to context:
| Feedback about | Response | Reasoning |
|---|---|---|
| End-user flows (simple tasks) | Listen deeply | This user represents non-technical users who need clarity |
| Admin/power-user features | Acknowledge but don't over-index | These features serve a different, more technical audience |
| Core workflows | Listen and investigate | If the core flow confuses this user, it'll confuse many |
| Advanced settings | Note but deprioritize | Advanced users can tolerate complexity |
| Visual/aesthetic opinions | Filter carefully | May be personal preference, not usability |
The principle: match the feedback to the audience the feature serves. If the feature is meant for everyone, this user's confusion is a valid signal. If it's meant for experts, their confusion might not be relevant.
Why silent users are worse
The dangerous users aren't the ones who complain. They're the ones who leave silently.
A critical user who gives negative feedback on every release is telling you:
- They're still using the product (engagement)
- They care enough to articulate problems (investment)
- They believe the product could be better (hope)
- They trust you enough to be honest (relationship)
A silent user who finds something confusing just... leaves. No feedback. No ticket. No complaint. They hit a friction point, get frustrated, and quietly switch to a competitor or workaround. You never know why.
In the early stages of a product, when you have 10-50 users, every vocal critic is gold. They're giving you information that silent users are withholding. Information that could prevent churn you'd never diagnose otherwise.
How we started using this user's feedback
From that conversation onward, I changed my approach:
1. Welcomed his feedback. Instead of dreading his messages, I started treating them as a free usability audit. "Let's see what he finds this time."
2. Applied the filter. Admin feature feedback? Noted but filed. End-user flow feedback? Investigated immediately.
3. Celebrated his positive feedback. The CEO and I felt genuinely overjoyed whenever he gave positive feedback. We'd congratulate the UX team: "Now the whole world will understand this design!" 😄
4. Used him as a baseline. "Would [this user] be confused by this?" became a legitimate question in our design reviews. Not the only question, but a useful one.
The broader lesson
Every PM will encounter "that user." The one who's never satisfied. The one who seems to complain about everything. The first instinct is to dismiss them. "They're not our target user." "They just like to complain." "We can't design for the lowest common denominator."
Sometimes that's true. But often, they represent a real and significant segment of your user base. The segment that wants things to be obvious, intuitive, and frictionless. The segment that will determine whether your product achieves mass adoption or stays stuck with power users.
Don't get offended. Get curious.
- What specifically confuses them?
- Which part of the flow trips them up?
- Is this an isolated reaction or a pattern?
- Does this feedback apply to the audience this feature serves?
Types of critical users and how to handle them
Not every critic is the same. Learning to distinguish helps:
The confused user (like ours): Genuinely struggles with UX. Their feedback reveals real friction. Listen to them for end-user flows.
The power user who wants more: Constantly asks for advanced features. Their feedback reveals opportunities for premium/pro features. Listen to them for roadmap expansion.
The competitor comparison user: "Product X does this better." Their feedback reveals competitive gaps. Evaluate whether those gaps matter for your strategy.
The entitled user: Expects everything, contributes nothing beyond complaints. Acknowledge but don't over-invest. They'll never be satisfied.
The constructive critic: Points out problems AND suggests solutions. These are your most valuable users. Protect the relationship.
The bottom line
The takeaways from that CEO conversation:
- Don't get offended by critical feedback. It's data, not an attack.
- Reframe the critic. They represent a segment. Understand which segment.
- Apply a filter. Not all their feedback applies to all features. Match feedback to audience.
- Value vocal critics over silent users. Silence doesn't mean satisfaction. It often means disengagement.
- Celebrate when they're happy. If your hardest critic approves, you've nailed it for everyone.
A strong critic is always 100x better than a silent user in the early stages. They care enough to talk. That alone makes them invaluable.
How ProductResume helps
Customer empathy and the ability to act on feedback are skills hiring managers evaluate on PM resumes. If your bullets show you turned difficult customer relationships into product improvements, that signals maturity. Score your PM resume to see how well your customer-facing experience reads.