19 · Talking to Executives: Three One-Page Memos

Companion Templates

The Challenge. An executive gives you ten minutes at a time. The project runs for months. How many times do you actually deal with him, and what do you say each time? Too early is an interruption, too late is losing control.

What You Will Be Able to Do. Cover every contact between the deliverer and an executive with the three-memo system. Use a kickoff memo for authorization at the open, a decision memo for the call at the midpoint, an impact memo for renewed funding at the close, and let each one handle AI expectation management along the way.

Part V Navigation. Chapters 19 to 22 run from the pilot's close to stepping out of the daily. The impact memo (Monday of week 18, this chapter) → the annual budget and headcount review (Wednesday of week 18, this chapter and Chapter 22) → the survey team lead pushes back (week 20, Chapter 20) → three daily-active curves (week 21, Chapter 21) → the gradual withdrawal and the five self-sufficiency tests (weeks 22 to 27, Chapter 22) → the last retrospective (Friday of week 29, Chapter 22)

Asking for Renewed Funding with a Number That Missed Target

The pilot closed out on Friday of pilot week 8, and the North Star stopped at -22%. The charter says -30%. Wednesday is the annual budget and headcount (staff positions) review, and whether the project expands, holds, or gets archived right there turns on the one page you send out on Monday. You have to trade a number that missed target for the next phase's investment.

Most people's instinct at this point is to explain. The people arrived late, the list fix landed late. But the harder you explain, the more it reads like a justification.

You spread everything you have sent Grant Whitmore so far across the table to get a feel for it, laid out in time order. The pre-mortem in week 1, the weekly report in week 6 that sank without a reply, the ADR memo in week 8, the run chart report in pilot week 5, and the one-line short notice the week after. Five pieces laid out, and the ones that actually did something all sit in the same structure, while the only one that drew no answer is the one written with the most effort and the most pages.

There is a pattern in it. Every contact between the deliverer and an executive comes down to three moments. Authorization at the open, a decision at the midpoint, renewed funding at the close. Three moments, three forms. This chapter grows Chapter 13's one page into a system that covers the whole project, then uses it to write Monday's memo.

Why This Is Hard: Saying the Right Kind of Thing at the Wrong Moment

The common shape of failed executive communication is saying the right kind of thing at the wrong moment. Actually saying something wrong is rarer. At the open you talk implementation detail (he wants risk and commitments). At the midpoint you paint the vision (he wants the item to call). At the close you talk about how hard the work was (he wants the outcome and the next step). All of it is true, and all of it lands in the wrong moment. A mismatched form gets shelved and never even earns a rebuttal. An executive will not say "you wrote it wrong." He just does not reply.

You ran the controlled experiment yourself. Wednesday of week 6, with the reconciliation half done, you sent Grant the only "weekly progress report" email of the whole project. Five paragraphs of reconciliation progress, thorough and orderly, with one sentence that mattered buried at the end of paragraph three, "we propose taking the merged view as the source of truth for claim status, and will proceed on that basis unless there are objections." Zero replies. You told yourself silence meant consent.

At Friday's source of truth decision meeting, the merged view was settled on the spot with Kevin Doyle and Linda Marsh (Chapter 9). After the meeting you rewrote the request buried on Wednesday as half a page. One conclusion sentence (source of truth for claim status = the merged view), two lines of reasons, and one closing line, "This decides where the development effort goes next. Please confirm it for the record by Sunday." Kevin passed it up. The approval came back inside 48 hours, two words. "Proceed accordingly."

Same matter, same reader. The first time was five paragraphs of information and it sank without a reply. The second time was one decision request, closed out in 48 hours. The first email was not rejected. It was sorted. An executive's inbox sorts by "what do I have to do," and mail whose answer is "nothing" drops into white noise automatically. Executives do not reply to information. They reply to decision requests. This has nothing to do with arrogance. It is how the job is designed. His output is decisions, and what you hand him either joins that production line or joins no line at all.

Prior Art, and What AI Changed

Chapter 13 already put up the structural skeleton. Open with SCQA (Situation, Complication, Question, Answer), then lead with the conclusion. That comes from the Minto pyramid, where every level is driven by the reader's question. Amazon's narrative memo tradition (Working Backwards) runs important meetings around one page of full sentences rather than slides. What this chapter adds is the system, promoting "one page" from a single tactic to a communication protocol that covers the whole project. When to send, which one to send, and what skeleton each one has.

The AI era changed two things. The first is in your favor. AI drafting takes "I cannot get it written" off the table. An SCQA draft, the evidence laid out, the charts tidied, all a matter of minutes. From here the one-page rule has one bottleneck left, thinking it through. Once the cost of writing has collapsed, sending a long and muddled email exposes the fact that you have not thought it through, and time stopped being an excuse a while ago.

The second is a new burden. Executive communication on an AI project carries an expectation management job of its own. Before your executive ever meets you, the media has already calibrated his AI expectations, calibrated them into a diode with two states, conducting or not conducting, and no scale in between. Either "AI can replace half a department" or "it is all a bubble, money burned for the noise." Both extremes are fatal. The first makes -22% look like failure. The second makes any added investment look like waste. So each of the three memos keeps one expectation management slot. The pre-mortem summary in the kickoff, the decision rights ladder in the decision memo, the honest gap in the impact memo (write the number that missed target exactly as it is, do not dress it up into "close to target"). Calibrate one memo at a time and acceptance day does not collapse.

The Core Framework: The Three-Memo System

Monday of week 9, right after Grant Whitmore made the call (the pilot call in Chapter 13), he said the sentence this whole system starts from. "Everything you send me from now on gets written the way this page is written." Half of it is an order and half of it is a permission. From that day your one page carries default priority with him. Sorting it out later, you find that "the way this page is written" splits into three by moment.

The three-memo system. Every contact between the deliverer and an executive comes down to three moments, authorization at the open, a decision at the midpoint, renewed funding at the close. One form per moment, and all three share the same one-page rule.

Moment	Memo	His Question	Middle Section	The Anchor & Helm Piece
Authorization at the open	kickoff memo	What are you promising, what do you want me to commit, how will it die	The outcome promised + the investment needed + the pre-mortem summary	The week 19 expansion kickoff
A decision at the midpoint	decision memo	What am I calling, what does it cost, what happens when it goes wrong	Three pillars + the trade-off said out loud + the decision rights ladder + risk and backstop (Chapter 13's ADR as it stands)	The week 8 pilot ADR memo
Renewed funding at the close	impact memo	Was it worth it, how far short, which next step	Run chart evidence + the honest gap + the next-step options	The week 18 retrospective memo (the Monday after the pilot closed)

Two new terms. Kickoff memo, the one page sent to the sponsor before a phase starts, putting on record the outcome promised, the investment needed, and the ways to die already rehearsed. Chapter 1's pre-mortem stops being a standalone document here and becomes the opening act of every phase. Impact memo, the one page sent to the person who calls it when a phase closes, presenting the result with running evidence, presenting the gap honestly, and giving next-step options with one of them recommended. The midpoint one is Chapter 13's ADR memo, and this chapter does not rewrite it.

The three share four rules.

One page of body text, attachments unlimited.
Lead with the conclusion, the pyramid apex test as before (Chapter 13). Who you want and what you want him to call, in one sentence. If you cannot write it, do not start writing.
The ending always carries "what I need from you," even if it is as small as "hold ten minutes on your calendar."
Send it early, delivered 48 hours before the meeting, so the meeting runs around the document.

The sameness and the difference are visible at a glance. The opening (SCQA) and the ending (the ask) are identical across all three, and the middles differ. The kickoff faces the future, the decision memo faces the present, and the impact memo faces the past plus one exit.

One more thing is easy to miss. The three memos link into a loop. The moment the impact memo's recommended option is approved is the Situation (S) of the next kickoff. However many phases the project has, that is how many times the loop turns.

Turning that loop inside a company needs recalibrating in four places. The first is the cost of reporting bad news. Your sponsor is most likely on your performance review chain too, or one layer away from it. Writing the gap section means admitting to the person who grades you that you did not make it, and the instinct is to write -22% as "close to target." Do not write that. An honest gap costs more inside a company, and it is worth more for exactly that reason. What it buys in one stroke is this person's default belief in every number you give him afterward, and that deposit is not for sale anywhere else.

The second is the nature of the ask. The "investment needed" line inside a company is usually not about making the business side honor what it already claimed. It is about asking the sponsor to require a peer department to send people. So the internal version splits it into two columns, who sends the people and who gives the word. Who sends the people takes real names and hours per week. Who gives the word takes whose mouth the sentence has to come out of before it counts, the sponsor or the other side's manager. The week 19 kickoff is split exactly that way. Split it and you see that every item landing in the "who gives the word" column is a political act, not a clause you can cite. You hold no authority over that department and can only rely on the sponsor to go persuade a peer manager, so before it goes into the memo, work out whose standing you are spending.

The third is timing. Your closeout calendar is not set by the project. It is set by the fiscal year. The impact memo's send date is worked backward from the day budget preparation starts, and a week late means your numbers can only make next year's pot. The kickoff is planted a quarter ahead, so that next year's headcount (that is, the staff positions) has a written origin before the headcount table freezes (once settled, nothing more can be added). And there is one more that only the internal version needs. A year after the system goes live, not one bill reminds anyone that it is still alive, and by then one page is your only tool for winning resources back on a regular basis. Written the way the impact memo is written, to the same recipient, except that this time nobody comes asking you for it.

The fourth is the copy line. All three memos go to the sponsor as the primary recipient, with three fixed copies, your manager Owen Hartley, the business-side owner Kevin Doyle, and the PMO. Owen's copy is not politeness. Your schedule and your review sit in his hands, and if he hears from someone else what you sent Grant, the next time your people get pulled away nobody will tell you first. Kevin's copy lets him see the ask before it goes out, since the people and the time you want mostly come through him. The PMO's copy keeps the project status matching the ledger. Going over a head has a real cost inside a company, and the copy line is the paperwork that turns going over a head into not going over one.

There is another half page only you have. The day before the memo goes out, hand it to Grant's assistant to read and ask what question has been chasing him this week. Rewrite the subject line on that answer, and reorder the first piece of evidence. Then pull two words out of the company strategy document into the conclusion paragraph, and find one comparable number from a similar system in another department for the evidence section. A consultant brought in from outside either does not have that assistant or cannot get those numbers. You have both.

At Anchor & Helm: One Short Notice and Two Pages

Monday of week 15, one line. The weekly numbers come out, and the run chart's sixth weekly point falls below the baseline median. "Six points on one side," a special cause holds (Chapter 18), and -18% turns from "one point short" into a shift that stands up. That day you send Grant a one-line short notice with one chart attached.

You said to tell you the day the sixth point comes in. It came in today, still below the median. Six points on one side, which by the rule is a structural shift, not fluctuation. Chart attached.

No request, no next step, nothing asked for. Ten minutes later the reply comes. "Noted." But it honored a promise made the previous Friday, and the reliability term in the Trust Equation's numerator is built up exactly this way (Chapter 5). Three weeks later you will see what that deposit is for.

Monday of week 18, the impact memo. The raw material is all ready-made, Chapter 18's run chart page, the incident retrospective record, and the kill criteria check records. Here it is in full.

To Grant Whitmore, from [you], Monday of week 18 Subject. The exceptions queue pilot retrospective, for you to call the next step at Wednesday's annual budget and headcount review One page of body text. The full run chart, the incident retrospective record, and the metric tree detail are attached.

Background. The 8-week pilot closed out last Friday (auto exception claims, the eight people on Linda's team). But, the North Star finished at -22%, short of the charter's -30%. So the question to answer, was the pilot worth it, how does the shortfall get closed, and where does the next investment go.

Conclusion. The pilot validates, and I recommend approving an expansion to go deeper. Extend auto exception claims to two more review teams, and put the North Star on the -30% target line within eight weeks.

Evidence (run chart attached) 1. The improvement is structural, with all eight weekly points below the eight-week baseline median, and the day the sixth point landed it already formed the "six points on one side" signal. A shift, not fluctuation. 2. The mechanism can be explained, with most of the drop coming from chasing missing documents earlier and from clearing queue aging. The two chase-side people you added in week 14 and the repair shop list fix only entered the curve in the last three weeks. 3. The defense has been tested in the field, one unsafe-class incident during the pilot, caught in the Human Call column, same-day notice, root cause located within 48 hours (the data layer), and the incident case is in the golden cases. The kill criteria were checked by the book every week, zero triggers.

The gap. (this section is the expectation management slot) -22% against -30%, 8 percentage points short. Two attributions, both verifiable. The chase-side people covered only half the stretch, and the weak-signal prompt for new entities not on the list went live only in week 15. Both levers are working and neither has run a full cycle yet, which is the basis for "-30% within eight weeks," and its whole basis. If the North Star stops falling four weeks into the expansion, this judgment is void and we go back to option three.

Three next-step options 1. Expand and go deeper (recommended), two review teams onboarded, the investment set out in next week's kickoff memo, using the validated mechanism to eat the remaining 8 percentage points. 2. Start home property, whose revival condition reads "the first extension after the pilot North Star hits target" (exclusive, the line written down in Chapter 8, meaning that once the target is hit it stands ahead of every other extension). The target line is -30% against -22% today, so the condition is not ripe and I do not recommend starting it now. The day the expansion hits target it goes first automatically, with no new project approval needed. 3. Hold and watch, no expansion and no withdrawal, four more weeks. Choose this one if you doubt that the last three weeks' drop will hold. The cost is stopping the scale-up just as both levers start working.

The two things I need from you 1. At Wednesday's annual budget and headcount review, call one of the three options (we recommend 1). 2. If the expansion is approved, agree to start the responsibility transfer plan alongside it. Running and maintenance move to Kevin Doyle's team step by step through the expansion period, with the plan attached to next week's kickoff memo.

At Wednesday's annual budget and headcount review, two approvals come back. The expansion goes through as submitted, and the handoff plan is agreed to start. The meeting first goes through the graduation criteria (Chapter 14). Four of the five pass and only the North Star is missing, so what gets approved is the expansion plus an extension of the pilot rules, with the reassessment date set at week 26, not a conversion to formal project approval. Grant also pays a compliment at that meeting, and it pushes the handoff into the main subject (that sentence of his is picked up in Chapter 22). Record one detail only. He points at the "gap" section and says that had it been written as "expected to hit target soon," what he approved would have been option three. An honest gap, number against number, attributed to verifiable events, carrying its own void condition. It turned "missed target" from a justification into grounds for a decision, and the posture came along for free.

Of the three artifacts, the decision memo is not rewritten here, and its one-page structure and the full Anchor & Helm piece are in Chapter 13. One thing to add. Its expectation management slot is the decision rights ladder inside the trade-off section, and what an executive sees on that ladder is a boundary, not the AI in the media that can do anything.

Monday of week 19, the expansion kickoff memo. The loop turns back to the open, and this is exactly what goes out next once the expansion is approved.

To Grant Whitmore, from [you], Monday of week 19 Subject. The expansion period starts, for the record. Promises, investment, and ways to die One page of body text. The handoff plan and the full pre-mortem are attached.

Background. The annual budget and headcount review has approved the expansion. But, the pilot's adoption was built on eight weeks of co-build with Linda's team, and the two teams coming in have neither Linda nor those eight weeks. So the question to answer, what do we promise in this phase, what do we need, and how is it most likely to die.

Conclusion. An eight-week expansion period, auto exception claims extended to two more review teams. We promise the North Star reaches the -30% target line, and one business win worth announcing inside the first month.

Investment needed, who sends the people. Kevin Doyle, schedule protection for the two new teams, 2 hours a week each on the precedent of Linda's team. Linda Marsh, taking part in transplanting her experience as the two teams come on, with the time agreed between her and Kevin. The two chase-side people continue to the end of the expansion period (already confirmed at the annual budget and headcount review, recorded here).

Investment needed, who gives the word. The first two sit inside Kevin's own line, and his word is enough. The two on the chase side do not, so at the next monthly meeting please say a line to the chase side's manager about continuing them, with the review's own resolution as the wording.

Pre-mortem summary (full text attached), the three most likely ways this dies. 1. The new teams have no Linda, daily actives start high and fall off, the system is "usable" and nobody uses it → the defense is embedding the queue retrospective into both teams' existing morning standups, and announcing wins in business language. 2. The new teams accept everything as is, with none of Linda's kind of challenge, and the errors all land on the last line of defense → the defense is that an override rate clearly below Linda's team's baseline in the first month triggers a spot check, because abnormally low is bad news too. 3. The larger claim volume overruns the monitoring surface, and alert fatigue drowns the real signal → the defense is resetting the escalation rules' thresholds and recipients for the expanded volume.

(this section is the expectation management slot)

The one thing I need from you. This memo is for the record, no call needed. The only request is ten minutes at each monthly meeting, one look at the run chart in week 22 and one in week 26.

Put the three artifacts side by side, the week 19 kickoff, the week 8 ADR (full text in Chapter 13), and the week 18 impact memo. The same opening and the same ending, and three completely different middles. When you were writing the pre-mortem, writing the ADR, and reporting honestly, you did not know you were building a system. Grant's sentence strung them together, and later Kevin picked up the same way of writing (Chapter 22). That is how a system usually comes about. First a few pieces that did something, then someone names them, aligns them, and writes them down as rules. You do not have to wait for that step to happen on its own. Name the moment, pick the form, leave the ask, and in three moves the next one is written inside the system.

Failure Modes

1. Moment and form mismatched. The opening memo is all architecture detail, and the closing memo is all war stories. The writer writes whatever he is most immersed in at the time. At the open your head is full of the plan, at the close you remember the overtime best. The form follows the writer's state of mind instead of the reader's decision moment. The fix is mechanical. Before writing, answer "which moment is this," and if you cannot answer, check the calendar, because phase boundaries are objective.

2. Expectations left unmanaged. The memo carries only numbers and requests and never calibrates "what AI can actually do." On acceptance day the executive measures your system against the AI in the media, and -22% gets read as "so much for AI." An executive's AI expectations are not a blank sheet. The media pre-calibrated them into a diode, and calibrating him is on nobody's task list. The fix is already sitting in the three expectation management slots, the pre-mortem summary, the decision rights ladder, and the honest gap. Calibrating once per memo beats one reconciliation on acceptance day.

3. Showing up only when you want resources. Zero contact outside the three memos, every appearance carrying a request, and the executive starts guarding the budget by reflex. Contact with no ask "produces nothing," so it is the first thing cut when you get busy. But honoring a promise mostly comes with no request attached. The short notice in week 15 asked for nothing. It only honored the line "tell me the day the sixth point comes in." Three weeks later the impact memo traded a number that missed target for renewed funding, and that short notice was the interest landing. One test. If every item in the communication record carries a request, you are the person who wants resources, not a partner.

Next Monday

Spread out everything you have sent an executive on this project so far and label each one. Information, or a decision request? Compare the reply rates of the two kinds. That is your own controlled experiment.
Work out which of the three moments the project sits in right now (look at the calendar, not at how it feels), and check whether what you are writing matches that form.
Write the next memo with Template 19. Check one thing before sending, whether the ending carries "what I need from you" with a date.
Find a promise you made an executive and have not honored yet (the "tell you the day X shows up" kind) and set a reminder. The message that honors it carries no request at all.

Want an agent to get you started? In the repo you set up following Start Here, paste this to your coding agent:

In the repo/ directory of the the-last-mile repository, help me with the Chapter 19 Next Monday actions. I will list everything I have sent
executives on this project so far. You only classify, information or decision request, and I fill in the reply rates. Then follow the instructions in
templates/memo-suite/prompt-memo-scaffold.md and draft the skeleton of the next memo for the moment I name (kickoff, decision, impact). The numbers
and the conclusion are mine to fill in, you invent none. Run python3 templates/memo-suite/remind_milestones.py and runchart_signal.py on the
built-in samples and tell me which moment each one is useful in. Before sending, check one thing only, whether the ending carries "what I need from you" with a date. If any command errors, stop and show me the output.

Chapter Kit

Judgment frameworks. The three-memo system (three moments × three forms, kickoff at the open / decision at the midpoint / impact at the close, the loop closing back on itself); the four shared rules (one page, lead with the conclusion, an ask at the end, delivered 48 hours before the meeting); the three expectation management slots (pre-mortem summary / decision rights ladder / the honest gap)
Templates. Template 19, Three-Memo Set (with ADR) (the kickoff and impact templates plus the Anchor & Helm examples; the decision memo is section 19.2 inside the same file)
Key judgments
"Executive communication has only three moments, authorization at the open, a decision at the midpoint, renewed funding at the close."
"Executives do not reply to information. They reply to decision requests."
"Three moments, three forms. Mix them and they stop working."
"The evidence of communication is the other person's changed behavior, not your sent folder."