Get this template emailed to you
Three fields. Lands in your inbox in a couple of minutes. No drip campaign.
Sent.
If it doesn't show up in 5 minutes, check spam or reply to hello@servantium.com.
- Ch.1 What an EM actually does
- Ch.2 The Friday review (30 min)
- Ch.3 The Sunday-night block (45 min)
- Ch.4 Decision architecture: the four chairs
- Ch.5 The institutional-memory move
- Ch.6 Five failure modes and the fix for each
An engagement manager is the translation layer between the work that was sold and the work that gets delivered. Every week the EM absorbs the gap between the original plan and the actual situation and decides what to do about it. This 30-day playbook makes that decision process concrete: two recurring rituals, one decision rubric, one memory discipline, and the failure modes to refuse by name. Download the PDF and run the Friday review on your next engagement.
Most EM training is delivered by osmosis. A junior EM shadows a senior one, picks up which silences to interrogate, which sponsor moods to wait out, which fights are worth picking. Some of what transfers is real skill. A lot of it is idiosyncrasy. None of it is written down. That is what this guide replaces.
What the osmosis model costs
When an engagement manager leaves mid-flight without a written record, the replacement spends two to three weeks reconstructing decisions, context, and risk posture the previous EM carried in their head. During that window the team waits, the sponsor’s confidence drops, and week-eight decisions slip to week eleven. Those slips land in the margin report. Nobody traces them back to the missing playbook. A shared written playbook is the cheapest fix available.
The pattern shows up in industry data. Professional services on-time delivery has fallen from 80.2% in 2021 to 73.4% in 2024, with high-visibility firms delivering on time at a rate nearly ten points higher than low-visibility peers (83.9% vs. 74.4%), according to the SPI Professional Services Maturity Benchmark 2025. Execution discipline, not strategy, separates the two groups.
The compounding effect is firm-level. An operation full of EMs who each run the job a little differently cannot staff engagements cleanly, cannot back people up, and cannot build a learning loop across the portfolio. Every engagement debrief becomes an archaeology project.
What the 30 days cover
The playbook runs six chapters across 30 days. The first three cover setup and cadence; the last three cover the moves that separate an EM whose engagement survives a holiday from one whose does not. Read Chapter 1 before day one. Run the Friday review and the Sunday block for two weeks. Then layer in decision architecture and the failure-mode chapter as the engagement gives you the context to use them.
| Ch. | Chapter | What it gives you | Time to run | When to read it |
|---|---|---|---|---|
| 1 | What an EM actually does | The translation-layer framing, the authority gap, and the two questions that close it | One read | Before the engagement starts |
| 2 | The Friday review | A 30-minute agenda, scripts to make a Risk row defend itself, three anti-patterns to refuse | 30 min weekly | Day one, run for two weeks |
| 3 | The Sunday-night block | A capacity check, a cost-of-delay decision queue, the “what changed” paragraph | 45 min weekly | Day one, run for two weeks |
| 4 | Decision architecture | The four-chair model and a four-question filter for who owns a call | One read, applied daily | After your second Friday review |
| 5 | The institutional-memory move | The five-line milestone summary, the weekly replacement note, the clean handoff | 10 min weekly | Day one, no exceptions |
| 6 | Five failure modes | Each failure named, plus the single move that fixes it | One read | After you have made one of them |
That table is the whole guide in one screen. The PDF is the long form: scripts, worked examples, and the exact words to use when a room would rather keep a row comfortable.
Two rituals hold the role together
The Friday review (30 minutes) interrogates every open item: does this still reflect reality, or is it carrying fiction? The Sunday-night block (45 minutes) loads the week before it starts: capacity check, decision queue sorted by cost of delay, and the “what changed” paragraph that seeds Monday status. Together they replace two hours of reactive scrambling per week with one structured hour at the edges of it.
The Friday review is thirty minutes. You ask one question of every open item: does this still reflect reality, or is it carrying fiction? A Risk row that has not changed in three weeks is not a sign things are stable. It is a sign no one has been honest about it. The playbook gives you the scripts for that conversation, including the three anti-patterns a stakeholder reaches for when they want a row to stay comfortable.
The Sunday-night block is forty-five minutes. You load the week before it starts. Capacity check against confirmed assignments. Decision queue sorted by the cost of delay, not by who asked most recently. The “what changed this week” paragraph that becomes the seed of your Monday-morning status update. The block costs forty-five minutes. It saves two hours of reactive scrambling across the week.
Decision architecture: the four chairs
The four-chair model answers the question every EM faces at 4pm on a Tuesday with the room waiting: which chair does this decision belong in? Yours to make, yours to escalate, or the sponsor’s regardless. A four-question filter runs any call through those columns in under a minute. The calls that still do not resolve after four questions are precisely the ones to escalate, and the model gives you the language to say why.
Most EMs are under-equipped for the decisions they actually face. Not for want of intelligence. For want of a clear model for which decisions are theirs to make, which require escalation, and which belong to the sponsor regardless. Chapter 4 does not tell you what to decide. It tells you which chair a given decision belongs in.
| The decision is yours when | It escalates when | It is the sponsor’s when |
|---|---|---|
| It stays inside agreed scope and budget | It changes the commercial envelope (price, timeline, contract) | It commits the client’s organization to act or pay |
| It is reversible within the week | It is irreversible or hard to unwind | It trades off priorities only the sponsor can rank |
| You can name the trade-off out loud | Two senior people both claim the call | It exposes the client to risk they have not accepted |
| Waiting costs more than deciding | Legal, security, or compliance is implicated | The relationship, not the work, is on the line |
The full chapter gives you worked examples for each column, including the exact language to use when two senior people are both claiming the call.
The institutional-memory move
When a milestone closes, write five lines: what the milestone was, what the original assumption was, what actually happened, what changed as a result, and who made the call. Add a two-paragraph weekly replacement note answering what a new EM would need to know that is not in the tracker. Filed from day one, these two habits make any handoff clean and any re-org survivable.
The five-line milestone summary is the simplest thing in the playbook and the one most EMs skip under pressure. Written weekly, filed to the engagement record, it is the artifact that makes a handoff clean instead of an archaeology project. The weekly replacement note is the companion: two paragraphs answering “if someone took this engagement from me tomorrow, what would they need to know that is not in the tracker?” You do not send it to anyone. You file it.
How to run it
Read Chapters 1, 2, and 3 before the engagement starts. Run both rituals for two weeks. Read Chapter 4 after your second Friday review, Chapter 6 after you have made your first mistake, and start Chapter 5 on day one and never stop. The guide is a working document: print it, mark it up, and keep the version with your notes in the margin.
This is not a certification or a maturity model. It is a working document for one person doing one hard job, plus the system that should carry the load once the habits stick. Run the rituals by hand for a few weeks, then let Servantium hold the loop: it merges the sold scope and the delivered work into one record, forecasts capacity against confirmed assignments, and answers the questions the Sunday block asks by hand, where is the engagement, what is the scope, who can deliver it, are they available. The intelligence drafts the milestone summary and the replacement note; the operator approves. Argue with the parts that do not match your firm. The version that helps you is the one with your notes in the margin.
Frequently asked questions
-
An engagement manager playbook is the written version of a job that is usually taught by osmosis: the rituals, decisions, and memory habits that keep an engagement honest week to week. This one is a 30-day playbook for the operator running a single engagement, not a firm-wide methodology binder. It assumes you have a real engagement in front of you and gives you something to do with it on Monday.
-
A project manager owns the plan. An engagement manager owns the translation between what was sold and what can actually be delivered with the team and constraints that exist. The EM carries the commercial context, the client relationship, and the authority to make calls the PM does not hold. Chapter 4 of the playbook maps exactly which calls land in which chair.
-
A status meeting reports what happened. The Friday review interrogates whether open items still reflect reality. Every Risk row, decision, and milestone is asked to defend itself, and items that have not moved in two weeks are treated as fiction until proven otherwise. Chapter 2 includes the agenda and the scripts for running it with a room that would rather stay comfortable.
-
Start the five-line milestone summary on the next milestone that closes, not retroactively. Write one weekly replacement note this Sunday. You will not have the full history, but you will have a clean record from here forward. Chapter 5 covers the move; the companion post on building an institutional memory engine covers the firm-level architecture behind it.
-
No. The playbook is tool-agnostic. The rituals run on whatever tracker you already have: a spreadsheet, a RAID log, a PSA. Servantium happens to hold the same loop in software, where decisions, tickets, and the engagement record live together and capacity is forecast against confirmed assignments. The intelligence drafts; the operator approves. But the guide stands on its own, and the download asks for nothing but an email.
What's inside
- Chapter 1, What an EM actually does. The translation layer, the authority gap, and the two questions that close it on day one.
- Chapter 2, The Friday review. A 30-minute agenda, the scripts for asking a Risk row to defend itself, and the three anti-patterns a room reaches for when it wants a row to stay comfortable.
- Chapter 3, The Sunday-night block. A 45-minute capacity check, the decision queue sorted by cost-of-delay, and the "what changed this week" paragraph that seeds Monday status.
- Chapter 4, Decision architecture. The four-chair model: which decisions are yours, which escalate, which belong to the sponsor regardless, and the four-question filter that sorts them.
- Chapter 5, The institutional-memory move. The five-line milestone summary, the weekly replacement note, and the handoff-without-a-meeting.
- Chapter 6, Five common failure modes and the single move that fixes each.
Why we made this
The EM is the translation layer between the work that was sold and the work that gets delivered. The job is mostly taught by osmosis, by people who learned it on the way up, with no shared vocabulary and no playbook. This is the guide we wish we had on day one: concrete enough to use on Monday, structural enough to argue with.
