The Manager's Toolkit

Every part before this one taught you how to think — about decisions, people, meetings, communication, the work. This part is different. It doesn’t add new ideas. It hands you the artifacts: nine templates that take the principles you’ve already learned and turn them into something you can copy, fill in, and use before lunch. Where earlier parts answered “why,” this part answers “give me the thing.”

That’s the whole promise of a toolkit. A principle in your head is easy to forget under pressure. A principle written as a template — a one-on-one agenda, a project one-pager, a feedback script — is a rail that keeps you on track exactly when your judgment is stretched thin. This page frames what the toolkit is, how each page is shaped, one meta-rule that matters more than any single template, and a roadmap to all nine.

What the toolkit actually is

Think of the rest of this book as a set of ideas, and this part as those same ideas pressed into reusable form. Nothing here is new theory. Each template is a principle you’ve met before, made into a document you can reach for:

• The one-on-one agenda is the principle “a one-on-one is the report’s meeting, not yours” turned into a structure.
• The decision document is “decide well and record why” turned into a page.
• The feedback script is “separate behavior from judgment” turned into three sentences you can actually say out loud.

A template does three quiet, valuable things. It lowers the cost of doing the right thing — you don’t have to invent structure while also handling the hard part. It raises the floor — even on a bad day, following the template gets you a decent result instead of whatever you’d improvise. And it makes the work legible — when everyone uses the same shape for a status report or a charter, people can read each other’s work at a glance, because they already know where to look.

In practice — the template that saved a hard conversation

A ward manager in a hospital had to tell a senior nurse that her handover notes were too thin to be safe. She dreaded it, and left to herself she’d have softened it into vagueness or hardened it into an accusation. Instead she opened the feedback script and filled in three lines — the situation, the specific behavior, the impact. The script didn’t have the conversation for her. But it kept her out of the two ditches she’d have fallen into on her own, and the whole exchange took four minutes instead of the sleepless week she’d have spent circling it.

The shared shape of every page

To make the toolkit fast to use, every template page in this part follows the same four-part shape. Once you’ve read one, you know how to read all of them:

1. WHAT IT'S FOR      — the problem this template solves, in a sentence or two.
2. THE TEMPLATE       — a blank artifact you can copy straight into a doc.
3. A FILLED-IN EXAMPLE — the same template completed for a realistic situation.
4. WHEN NOT TO USE IT — the cases where this template is the wrong tool.

That last part matters as much as the template itself. A tool that never tells you when to put it down becomes a hammer looking for nails — you end up writing a formal decision document for a choice you could reverse in an afternoon, or running a heavyweight retro on a two-person task. Knowing when not to reach for a template is part of using it well.

The one meta-rule: a template is a starting point, not a form

This is the single most important idea in the whole part, so read it slowly: a template is a starting point to adapt, not a form to obey.

Templates fail in one of two opposite ways, and the meta-rule guards against both. The first failure is treating the template as sacred — filling in every field because it’s there, adding ceremony no one needs, turning a helpful structure into bureaucratic theater. The second is ignoring the template’s intent while keeping its shape — going through the motions of a one-on-one agenda while making it entirely about your status update, which is exactly the thing the template exists to prevent.

The rule that dissolves both: overhead should match the stakes. A template is overhead — time and ceremony spent on structure rather than the work itself. Spend that overhead where getting it wrong is expensive or hard to undo, and strip it down to nothing where the stakes are low.

low stakes, reversible  ──►  use a lighter, shorter version (or skip the template)
                             e.g. a one-line "decision note" in chat

high stakes, hard to undo ─►  use the full template, carefully
                             e.g. a complete decision document + RACI

A hiring decision and a decision about which font the newsletter uses can both, in theory, get a decision document. Only one of them should. If you find yourself resenting a template, that’s usually the signal that the overhead has outgrown the stakes — trim it. If you find yourself surprised by an avoidable mess, the overhead was probably too light — add structure next time.

The common trap — process worship

The most common way toolkits go wrong is process worship — the moment the artifact becomes the goal instead of the outcome it was meant to produce. You can spot it by a simple test: ask “what would go wrong if we didn’t fill this in?” If the honest answer is “nothing,” you’re doing the ceremony for its own sake. The templates in this part are servants of the throughline — reliable outcomes without chaos, burnout, or politics. The day a template starts causing burnout or busywork, it has stopped serving that goal, and the right move is to shrink it or drop it, not to comply harder.

The roadmap: all nine templates

Here is every template in this part — the problem each one solves, and roughly how often you’ll reach for it. These are reference pages, not a story. You don’t need to read them in order; you need to know they exist so you can find the right one when the situation lands on your desk.

#	Template	The problem it solves	How often you’ll reach for it
2	The One-on-One Agenda	A recurring one-on-one that drifts into status updates or gets skipped	Weekly, per report
3	The Project Charter (One-Pager)	A project starting without a shared, written definition of what “done” means	Once per project, at the start
4	The Weekly Status Report	Stakeholders unsure what’s on track, what’s at risk, and what you need from them	Weekly
5	The Decision Document	An important choice made with no record of why, re-litigated months later	Occasionally, for high-stakes calls
6	The RACI Matrix	Work where nobody’s sure who owns what, who just advises, and who to inform	At the start of anything with muddy ownership
7	The Retro Format	A team that repeats the same mistakes because it never pauses to learn	Regularly — end of a sprint, project, or quarter
8	The Hiring Scorecard	Interviews decided on gut feel and “culture fit,” inconsistent across interviewers	Every time you hire
9	The Feedback Script (SBI)	Feedback that comes out vague, personal, or too late to act on	Often — whenever behavior needs to change
10	The First-90-Days Checklist	A new manager (or new hire) losing the critical first months to drift	Once, when you or someone starts a new role

When you’ve used a few of these, close the loop with the Toolkit Recap, which pulls the whole set together and shows how the templates reinforce each other.

The thread

Unlike other parts, the toolkit isn’t a single argument that builds page by page. It’s a workbench — a row of tools hung on the wall, each for a different job. But there is a thread running underneath all of them: every template exists to move a principle out of your head and into a shared artifact, so that doing the right thing costs less and shows up the same way every time. Read the overview once for the meta-rule, then treat the other pages the way you treat a cookbook — you don’t read it cover to cover, you open it to the page you need when you’re standing in the kitchen with a problem.

How it connects

This part is the practical outlet for nearly every earlier part. The one-on-one agenda applies what you learned about managing people; the decision document and RACI matrix apply the parts on decisions and ways of working; the status report and charter apply communication and project management. If a template ever feels arbitrary, go back to the part it came from — the “why” lives there, and the template is only its portable form.

Try this

Pick the one problem from the roadmap table above that is most alive on your team right now — the status reports nobody trusts, the hiring done on vibes, the feedback you keep postponing. Open just that one template page this week, copy the blank template into a real document, and fill it in for a real situation. Don’t try to adopt all nine; adopt one, use it once, and notice whether the outcome improved. A single template used for real teaches you more than reading all of them.

Reflect

1. Which of the nine problems in the roadmap table is currently costing your team the most — in wasted time, confusion, or repeated mistakes?
2. Think of a process your team already follows religiously. Would anything actually go wrong if you stopped? What is it really protecting against?
3. Where in your work is the overhead mismatched to the stakes — heavy ceremony on a reversible choice, or no structure at all on something expensive to get wrong?
4. When you’ve used templates before, did they tend to become sacred forms or get quietly ignored? Which failure are you more prone to?
5. Which principle from an earlier part do you believe but keep failing to practice under pressure — the kind of gap a template is meant to close?

Show reflections

1. The point is to find your highest-leverage template before reading further. The costliest problem is usually the one that recurs — the same confusion or mistake every week — because recurring costs compound, and a template is most valuable exactly where a situation keeps coming back.
2. This is the process-worship test applied to your own team. An honest “nothing would go wrong” means you’ve found ceremony to trim; a specific answer (“we’d lose the audit trail,” “handovers would get missed”) means the process earns its overhead. Both answers are useful.
3. Mismatched overhead is the master error of this part. Most teams have both kinds at once — agonizing over trivial reversible calls while high-stakes decisions get no record at all. Naming a concrete case of each tells you exactly where to add structure and where to strip it.
4. Knowing your default failure mode tells you which guardrail to hold. If you make templates sacred, practice shrinking them; if you let them slide, practice honoring their intent (not just their shape) even when you’re busy.
5. This is the heart of why the toolkit exists. The gap between believing a principle and practicing it under pressure is precisely what a written template bridges — it carries the principle for you when your judgment is stretched. Name the gap, and you’ve named the template you most need.