There is a perfect version of the Product Manager job that lives on infographics, possibly, you saw it.
Know your users! Find problems worth solving. Test the riskiest assumptions first. Lead without authority. Own the outcome.
This is a good list. I can do all of it, and after enough years, most competent PMs can. That was never the hard part.
The hard part is that almost none of that list is actually up to the person on the poster.
Look closely at the words. “Own the outcome” only means something if someone is willing to hand you an outcome to own — a real decision, with real consequences attached to your name.
“Lead without authority” only works in a place where influence is even possible: where a good argument can move a decision, and where you are not quietly treated as replaceable.
“Find problems worth solving” assumes you are allowed to say that a popular idea is not worth solving — and be heard.
Every line on the ideal-PM poster describes a person. But whether that person can do any of it is set by the organisation around them, not by the person. The same PM is “sharp and reliable” in one company and “not senior enough” in the next, and the difference is often the company, not the résumé.
Once you see this, a lot of everyday frustration stops being frustration and turns into information. It becomes a way to read a place before you join it.
How I see it:
| What looks annoying | What it usually tells you |
|---|---|
| A five-stage interview for a role with three real responsibilities | The organisation confuses process with rigour — and likely makes decisions the same way |
| Managers who avoid decisions but are very good at being visible | Decision rights are unclear; no one here can truly “own the outcome” |
| “There’s a queue outside for your job” | People are treated as interchangeable — so no one leads by influence, because fear is the only currency left |
| Two people replaced by six, and everything slows down | Headcount grew, but decision clarity didn’t — responsibility is now smeared across layers |
That last one I watched happen. A team I worked with was small and worked well: a couple of people who could see the whole picture and were trusted to decide. Then it scaled. Where there had been two, there were now six. On paper, more capacity. In practice, every decision now had more owners and therefore no owner. Things that used to take an afternoon started taking a fortnight, and the good product thinking did not disappear in an argument — it just quietly stopped happening. Nobody was incompetent. The structure had made ownership impossible.
I want to be fair to the other side, because it is a real side. Handing the product you built — the thing you stayed up worrying about — to a hired stranger is genuinely frightening. I understand the instinct to keep control. But there is little point running a hard, careful selection to find the right person and then keeping that person in a straitjacket. If you don’t trust them to decide, the selection was theatre. The level of trust and the rigour of the selection have to match. When they don’t, you get the worst of both: a senior hire doing junior work, slowly, wondering why they were hired at all.
So the question I ask about a role is no longer “can I do this job?” I can. The more useful question is “is this a place where the job is even possible?” — where decisions get made, ownership is real, and a good argument can still move something.
That is not me being difficult, and it is not a complaint about employers. It is a filter, built from experience.
The best product thinking I have seen did not fail loudly. It died quietly, in rooms where nobody could make a decision. I would rather learn that before I join than after.
Latest Posts
- You can hire a strong product manager and still make product work impossibleThe ideal product manager lives on infographics: own the outcome, lead without authority, find problems worth solving. I can do all of it. The hard part is that almost none of it is up to me — it is set by the organisation, not the résumé.
- The First Workout Is a Trust DecisionThere’s a person in every gym who isn’t a beginner but never gets a program that goes anywhere. A product look at why trust is decided in the first workout — and what I’m building because of it.
- Survivorship Bias in Product Manager Hiring: The ‘Proven Track Record’ TrapWhy “proven track record of successful launches” in PM job ads hides survivorship bias — and what to ask product managers instead of launch metrics.
- GymBuddy: the app with exactly one user (me)GymBuddy is the fitness app I built with exactly one user — me. What dogfooding my own MVP taught me about scope, AI-assisted building, and real feedback.
- Product case study: SaaS Customer-Journey & Usability ReviewSaaS Customer-Journey & Usability Review — Conversion Audit for an Early-Stage B2B Messaging Product Context An early-stage B2B SaaS product — customer messaging for small, owner-operated businesses (cafés, salons, repair shops) in a bilingual EU market. The founder had built something genuinely opinionated: AI drafts every reply, but a human must approve each message before… Read more: Product case study: SaaS Customer-Journey & Usability Review
Leave a Reply