Criticism Triage Under Public Controversy
Separate valid criticism from power-shift noise by going and being your own user.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 90%
Any product that meaningfully changes behavior threatens someone invested in the old behavior, so conflict — and press — is structural, not a signal of failure. Adriel Frederick's method for PMs at Facebook, Lyft, and Reddit is to accept that a portion of criticism is just the sound of power shifting, isolate the portion that is genuinely valid, and find the truth by going and experiencing the product as a user rather than by responding to headlines.
Origin
Adriel Frederick, from working through public controversy at Facebook (traditional media, other social networks), Lyft (taxis, unions, Prop 22, driver pay), and Reddit.
Core principles
- 01You can't have meaningful influence on the world without changing a pattern of behavior, and someone is always invested in that pattern.
- 02Conflict makes the best stories, so press attention is a byproduct of mattering, not of failing.
- 03The PM's leadership job is a damping function — pull the team down after over-praise, pull them up under attack.
- 04The hard work is distinguishing valid criticism from a source of power being changed.
- 05Truth is found by staying close to users, not by parsing the coverage.
How to run it
- 1
Apply the damping function to your team
As PM you are a leader and provide a buffering effect in both directions. When the press says you're the best thing ever, slow the team's roll — you're not yet delivering the value you want to. When the press says you're the worst thing in the world, pull the team up and keep charging at the mission.
Pro tip Say explicitly: 'they don't see what we're doing and they will misunderstand us sometimes.'
- 2
Sort the criticism: valid problem vs. threatened incumbent
Ask of each complaint whether it names a real defect in your product, or whether it is a party losing power to your product. Both will appear in the same news cycle and often in the same article.
Pro tip Frederick's own honest split at Lyft: he felt no sympathy for medallion owners complaining about Lyft (cabs had driven past him in New York), but the complaints about driver pay structure were real.
Watch out Your emotional reaction to the complainant is not evidence about the validity of the complaint. Sort them separately.
- 3
Go be your own user
Don't adjudicate from the desk. Go do the job. Frederick, hearing driver complaints, got in his car and drove for Lyft to feel the problem himself.
Pro tip Take the worst-shaped instance of the job you can find — a long unpaid pickup drive — not a convenient sample.
- 4
Extract the structural truth behind the complaint
Convert the felt experience into the underlying product defect. For Frederick, driving 15 unpaid minutes to Rick — an 80-year-old who called a ride for a 2-minute trip because he'd had a drink and feared breaking his hip — revealed that real value was created but not captured: drivers weren't compensated for pickup time, and it wasn't passed through into pricing for the rider.
Pro tip Look for value created but not represented in the pricing or incentive structure — that gap is usually the real complaint.
Watch out The structural fix is harder than the anecdote suggests: pay drivers for pickup, keep prices reasonable, and don't create incentives that leave the riders who most need a ride unserved.
- 5
Plan the work, work the plan
Return to the job: solve for the customer in the middle of the storm. Build for a solution that works regardless of how the external controversy resolves.
Pro tip Frederick's test: through Prop 22, he was ready with a solution that worked for riders and drivers whether it passed or failed.
Watch out It is extremely easy to get sucked into the press cycle and mistake responding to coverage for doing your job.
- 6
Check whether the outrage is broad or loud
Talking to actual customers also reveals when a 'revolt' is a handful of loud voices — most users haven't noticed and don't care. Volume in the press is not prevalence among users.
In the wild
Frederick opened the Lyft driver app at home and got a ride request 15 minutes away — unpaid pickup time, and the rider might cancel. He drove over, dodging traffic and pedestrians, picked up Rick, an 80-year-old Japanese man, and saw the trip was only two minutes long. He was ready to curse Rick out until Rick explained he'd had too much to drink and was worried about breaking his hip.
→ Frederick reframed from resentment to recognizing real value delivered — and saw that neither the driver compensation nor the rider pricing structure captured the pickup cost. That insight drove his product work through the EB-5 and Prop 22 press cycles.
Two complaints hit Lyft simultaneously: New York medallion owners demanding Lyft be banned, and drivers complaining about pay structure. Frederick sorted them — the medallion complaint was an incumbent losing a power position (he noted cabs had refused to stop for him in New York), while the driver-pay complaint named a genuine structural defect around unpaid pickup time and deadhead return trips.
→ The legitimate criticism 'got us off our ass to go fix it' — the product team worked on pickup-time compensation, while the incumbent noise was correctly ignored.
Common mistakes
Responding to the specific criticism instead of the truth behind it
Getting lost in rebutting the headline means you never locate and fix the real product defect that made the story land.
Treating all controversy as illegitimate
Dismissing everything as incumbents whining means you miss the complaints that are real. Some criticism is the only reason a real problem gets fixed.
Mistaking loud for widespread
A press narrative that 'all hosts are furious' often survives contact with users as 'nobody knew, nobody cared.' Only talking to customers reveals which.
Is it for you?
Best for
PMs and product leaders at companies under sustained public or regulatory attack — marketplaces, social platforms, gig economy, anything disrupting an incumbent.
Not ideal for
Situations where the criticism concerns a genuine safety or legal breach requiring immediate escalation rather than product triage.
From the transcript
“as a PM you are a leader you have to provide a buffering or damping effect on the team”
“I don't think you're going to have any meaningful influence on the world without changing some pattern of behavior”
“you kind of have to find the truth behind it and try to find a way to work on that and not get too lost…”
“so easy to get sucked into like the press and it's like yo plan the work work the plan go back to your job”
“when a lot of the complaints were happening about driving on Lyft I drove”
From the episode
Humanizing product development
Adriel Frederick (Reddit, Lyft, Facebook)