The Operator's Manual (Answer First)
Answer the question, then explain — or shut up. The tactical checklist for PM communication
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 93%
McAllister's most tactical framework: a running checklist of communication behaviours that avoid the specific pitfalls senior leaders punish. The core move is inverting the natural order — lead with the answer, then explain, and often stop there. It began as a collection of a single tough leader's habits and grew into a general operating manual.
Origin
Originated as 'The Book of Kim' — a best-practices document McAllister and his first Amazon boss Russell compiled from feedback given by Kim Rachmeler, Amazon's first TPM and then SVP for Worldwide Discovery. McAllister later extended it and published it as 'The Operator's Manual'.
Core principles
- 01Answer first, then explain. Sometimes answer, then shut up.
- 02A 'when' question takes a date as its answer. Not context, not caveats — a date.
- 03Avoid weasel words. They signal evasion and cost trust.
- 04Own your problems rather than routing around them.
- 05Learn to use numbers to answer questions.
- 06Clear thinking and clear communication are the same test — you cannot fake one without the other.
- 07The stakes rise with the seniority of the room, so build the habit while the room is small.
How to run it
- 1
Identify the actual question being asked
Before speaking, name what the asker wants: a date, a number, a yes/no, a decision. Most rambling comes from answering a question that wasn't asked.
Pro tip If someone asks 'when', they are waiting for a date. Everything else you say before the date is noise.
- 2
Lead with the answer, then explain
Invert the instinctive order. Give the answer in the first sentence, then supply the reasoning, context, and caveats — for as long as they still want them.
Pro tip Sometimes the correct sequence is answer, then shut up. Silence after a clean answer is a senior move.
Watch out Explaining first and arriving at the answer last reads as hedging even when it isn't.
- 3
Strip the weasel words and own the problems
Cut hedging language. When something has gone wrong in your area, state it as yours rather than distributing blame or leaving it unowned.
Pro tip Use numbers where a number will do the work of a paragraph.
- 4
Write, because writing is a test of thinking
Force yourself to organise, compact, and de-ramble your ideas in writing — for an external audience if possible. Business writing exposes muddled thinking that a slide with three bullets conceals.
Pro tip Documents produce richer discussion than slides because they cannot hide behind bullets. Where you have latitude with your team, switch to docs.
Watch out You may not have the latitude to change how your leadership consumes information. You have far more leverage down with your team than up or across — recognise the environment you're in.
- 5
Grade yourself after every exchange
After each doc, meeting, email, or hallway answer, pause and ask how you could have done that better. Then do it better next time. Ask your manager the same question directly.
Pro tip After enough repetitions the self-grading becomes automatic and stops costing you anything.
- 6
Keep your own Book of Kim
Maintain a living document of communication best practices harvested from the toughest, sharpest leaders you work with. Add to it whenever feedback stings.
Pro tip Feedback that lands hardest is usually the entry most worth writing down.
In the wild
At Amazon, McAllister worked for Kim Rachmeler — tough, extremely smart, the company's first TPM. He and his first boss Russell began collecting the practices they were being taught the hard way: avoid weasel words, answer first then explain, own your problems. They named the collection The Book of Kim.
→ McAllister extended it over the following years and eventually published it as The Operator's Manual, which he names as the closest thing to a checklist for getting better at PM communication.
Early in his PM career at Microsoft, McAllister's product unit manager asked when something would ship. He responded with background — this thing is taking longer, and this other thing — without ever producing a date. The feedback was that he hadn't answered the question; his manager was waiting for a date.
→ It became the origin point of a communication practice he says he's still working on decades later, and the seed of the answer-first rule.
Common mistakes
Rambling toward the answer
Explaining first and answering last is the single most common PM communication failure. It reads as evasion, wastes the most expensive attention in the room, and teaches leaders not to ask you.
Outsourcing your writing
Writing effective copy — and effective docs — is a PM skill, not something to sub out. You have to be a clear thinker to be a clear communicator; delegating the writing means never testing the thinking.
Trying to force docs on a slide-culture leadership team
Different leaders process information differently. Pushing a document culture upward in an organisation that doesn't want it burns political capital. Change the format with your team, where your leverage actually is.
Is it for you?
Best for
Product managers at any level who get feedback that they're 'hard to follow', 'in the weeds', or 'didn't answer the question' in senior forums
Not ideal for
Genuinely exploratory or brainstorming sessions where thinking aloud is the intended mode
From the transcript
“Answer First and then explain own your problems and started building this”
“answer and then explain or sometimes answer and then shut up that actually is a tactical thing you can do to get better at communicating”
“you've got to be a clear thinker to be a clear communicator”
“I have more leverage down with my team versus up or across”
From the episode
What it takes to become a top 1% PM
Ian McAllister (Uber, Amazon, Airbnb)