What are the hardest truths about product management?

That speed no longer sets you apart, that killing the wrong feature earns no credit, that roadmaps get read as promises, that busy work isn't progress, and that your title won't protect your judgement. In the AI era, product managers stay valuable by making better calls and making those calls visible, not by shipping faster.

How do product managers stay relevant as AI gets better?

By competing on judgement rather than speed. AI makes execution cheap for everyone, so the advantage moves to deciding what to build, what to stop and what each piece of work should change. Practical habits help: write the problem in one sentence before building, name the metric each task should move, and keep a log of big decisions to review monthly.

How do I show the value of saying no as a product manager?

Keep a written list of what you turned down, one line per item, with the reason. When you kill a feature, put a number on what it saved, such as weeks of engineering time, and tell your manager. Bring the list to your performance review, because work you prevented is otherwise invisible.

What is the difference between output and outcome in product management?

Output is what the team produces: features, releases, tickets closed. Outcome is the change in user behaviour or business results that the output was meant to cause. A product manager should name the behaviour a feature should change before it ships and check afterwards whether it moved.

What is a product decision log?

A simple record of each significant product decision, one line per call, with the reasoning at the time. Reviewing it monthly shows which calls were right and which were wrong, which improves your judgement and gives you evidence of it. It also protects against hindsight bias, because you can see what you actually believed when you decided.

12 Brutal Product Management Truths (And What to Do About Each One)

1

The full infographic, as a PDF

The exact one from the post, sized to print or keep within reach.

2

A copy in your inbox

The download link lands in your email too, so it's there when you need it. No follow-up campaign.

3

The Product System, weekly

My note on leading product in the AI era. One idea a week that compounds. Unsubscribe anytime.

The faster AI makes you, the easier you are to replace.

Everyone around you got faster this year. It didn't change who gets kept. Speed is now cheap and widely available, which means it no longer sets anyone apart. The product managers who stay valuable stopped competing on speed. They compete on judgement: the quality of the calls they make about what to build, what to stop and what it should change.

Judgement isn't a personality trait. It's a set of habits, and most of them are small. Below are 12 truths about product management in the AI era, each paired with one move you can make this week. Master the same 12 calls and you can out-decide people with twice your experience.

1. Speed won't save you

AI made everyone fast. When everyone ships quickly, shipping quickly stops being an advantage. What's left is picking the right thing to build.

The move: before you build anything, write the problem it solves in one sentence. If you can't, it isn't ready, no matter how quickly you could build it.

2. Killing a feature is thankless

Nobody claps when you stop the wrong thing. A launch gets a celebration. A cancelled project gets silence, even when the cancellation saved more than the launch earned.

The move: when you kill something, put a number on what you saved, such as "that's three weeks back", and send it to your boss. Make the invisible win visible.

3. Roadmaps aren't promises

Leadership tends to read a roadmap as a list of commitments. You know it's a set of guesses about what will matter. That gap is where trust gets damaged every quarter.

The move: in your next review, say "this is our best bet", not "this is what we'll ship". Call each item a bet before you start it, and the conversation changes when one doesn't pay off.

4. Busy isn't progress

AI made it easy to look busy. Tickets close, documents appear and dashboards fill up, and none of it proves anything moved.

The move: add one line to every ticket, naming the number it should move. No number, don't start it.

5. The ask isn't the job

People ask you for features, not the problem behind them. A stakeholder who asks for an export button usually needs something else entirely: a report, an answer, a way to stop doing something by hand.

The move: when the next feature request comes in, reply with one question. "What would this let someone do that they can't do today?"

6. Momentum can fool you

A busy project can feel healthy while it's dying. Standups are full, demos look good, and the one result that matters hasn't moved in six weeks.

The move: at kickoff, write down the one result that means "stop". Check it every Friday, while stopping is still cheap.

7. Saying no is invisible

Nobody sees the work you turn down. Every bad idea you stopped, every distraction you kept off the team's plate, leaves no trace, and at review time it counts for nothing unless you can show it.

The move: start a "said no to" list today, one line each. Bring it to your review as evidence of judgement.

8. Delivery is a trap

You get judged on what you ship, not on what you decide. So it's tempting to report activity, because activity is easy to count.

The move: open your next update with the call you made, not the tasks you closed. Lead with decisions, and people start seeing you as the person who makes them.

9. Output isn't outcome

You can be rewarded for features that change nothing. The release notes look impressive and user behaviour stays exactly where it was.

The move: before you ship, name the one user behaviour that should change. After you ship, go back and check whether it moved.

10. You can't do it all

The list keeps growing because no one above you will say no. Every request is reasonable on its own, and together they're impossible.

The move: take the full list to your manager and ask one question: "Which of these do we drop?" That makes the trade-off a shared decision instead of your private failure.

11. You can't out-learn AI

New tools arrive faster than anyone can learn them. Sampling every one leaves you with shallow knowledge of many tools and real skill in none.

The move: stop sampling. Pick one tool and use it every day this week until it's muscle memory. Build it deep into how you work.

12. No one protects your judgement

Your title and years of experience won't protect you any more. The only protection is a record of good calls, and you need to be able to show it, including to yourself.

The move: keep a decision log. One line per big call, and why you made it. Revisit it monthly to see who was right.

The pattern behind all 12

Whiteboard of four sticky notes flying from a stick figure's thought cloud onto a wall for three colleagues to see, reading 'Write the problem down.', 'Name the number.', 'Decide what means stop.' and 'Log the call.'

Read the moves again and the same thing keeps coming up. Write the problem down. Name the number. Decide what means stop. Log the call. Every one of them turns a judgement that lives in your head into something you and others can see and check.

That's the shift AI forces on product management. When execution is cheap, judgement is the job, and judgement only counts when it's visible. If you want the longer version, the companion piece, 24 Harsh Truths of Product Management I Learnt the Hard Way, covers the same ground in more depth.

Pick the one truth on this list you live by least, and make its move this week. The PDF keeps all 12 on one page, so you can bring it to your next planning session.

Questions people ask

What are the hardest truths about product management?: That speed no longer sets you apart, that killing the wrong feature earns no credit, that roadmaps get read as promises, that busy work isn't progress, and that your title won't protect your judgement. In the AI era, product managers stay valuable by making better calls and making those calls visible, not by shipping faster.
How do product managers stay relevant as AI gets better?: By competing on judgement rather than speed. AI makes execution cheap for everyone, so the advantage moves to deciding what to build, what to stop and what each piece of work should change. Practical habits help: write the problem in one sentence before building, name the metric each task should move, and keep a log of big decisions to review monthly.
How do I show the value of saying no as a product manager?: Keep a written list of what you turned down, one line per item, with the reason. When you kill a feature, put a number on what it saved, such as weeks of engineering time, and tell your manager. Bring the list to your performance review, because work you prevented is otherwise invisible.
What is the difference between output and outcome in product management?: Output is what the team produces: features, releases, tickets closed. Outcome is the change in user behaviour or business results that the output was meant to cause. A product manager should name the behaviour a feature should change before it ships and check afterwards whether it moved.
What is a product decision log?: A simple record of each significant product decision, one line per call, with the reasoning at the time. Reviewing it monthly shows which calls were right and which were wrong, which improves your judgement and gives you evidence of it. It also protects against hindsight bias, because you can see what you actually believed when you decided.