The executive committee has given you forty minutes on the second Tuesday of the month, between a capital-expenditure review and a discussion about a distribution center lease. You have spent eleven weeks producing four rigorous artifacts: a calibrated framework scorebook, a Critical Dataset Register with a costed remediation backlog, a Process Maturity Grid covering thirty processes, and a People Readiness Atlas built from a survey, an interview program, and a shadow-adoption census. Stacked, they run to roughly eighty pages of evidence. The committee will read two. Not because they are lazy, but because that is what an executive committee is for: it does not absorb evidence, it allocates capital against structured choices. If your two pages structure the right choice, eleven weeks of audit work becomes a funded program. If they merely summarize the eighty, the committee will nod, praise the rigor, and move to the lease. This lesson is about the two pages, and about the difference between a summary and a decision.

Two Pages Against Eighty: Why This Is Not a Summary Problem

The instinct, after an audit this thorough, is to treat the final deliverable as a compression exercise: shrink the findings until they fit. That instinct produces a document that is accurate, complete, balanced, and inert. The room reads it, understands the organization better, and does nothing, because understanding is not what rooms do. Rooms decide. A deliverable that improves understanding without structuring a decision has simply moved the moment of decision somewhere else, usually to a follow-up meeting that loses to the calendar, or to six separate function heads who fill the vacuum with their own procurement.

So reframe the task. The compression is not a summary problem; it is a decision-architecture problem. Your job is to design the two pages so that the right strategic conversation becomes unavoidable: where readiness is pooled, where it is absent, what sequence follows from that shape, and what the first checks fund. Every element on the page either advances that conversation or steals attention from it, and everything that steals attention gets cut, no matter how hard you worked to produce it. Meanwhile, every cell that survives must remain challenge-proof, because this room contains a chief financial officer (CFO) whose profession is finding the soft number: each score must cite the audit evidence standing behind it, one tab away.

You have built this muscle before, one level down. In Level 2 you built the One-Page Readiness Report: one process, one verdict, one recommendation with a verb in it, every number recomputable from an exhibit behind the page. That discipline, compression with a chain of evidence, transfers whole. What changes at board altitude is the subject and the stakes. The Level 2 page compressed one process's verdict for a steering committee deciding one pilot. This page compresses an entire organization's readiness for the room where functions compete for the same capital, where the chief executive officer's (CEO's) public June expectation meets the actual terrain, and where the S&P Global finding that 42 percent of companies scrapped most of their AI initiatives in 2025 is either your organization's future or the thing your sequence is explicitly built to avoid. One process's verdict can be wrong and cost a pilot. This page's architecture can be wrong and cost a year.

The artifact this lesson builds is the Enterprise Readiness Heat Map: two pages, fixed anatomy. Page 1 is the map: your organization's functions against the four audit dimensions, every cell carrying its calibrated score and its evidence code, overlaid with where value wants to happen and which cells are moving. Page 2 is the narrative and the three moves: three paragraphs of honest position, and three funded, owned, dated moves that are the budget conversation, pre-structured. Around the artifact sits a presentation choreography, because a heat map that is merely admired has failed, and admiration is this deliverable's most seductive failure mode. We will meet a strategist to whom exactly that happened.

Page 1: The Grid That Shows Its Proof

Six functions, four dimensions, one calibrated number per cell

Page 1's core is a grid: your major functions as rows (for most mid-size enterprises, five to seven rows; our running example uses six), and the four audit dimensions as columns: Process, Data, People, and Governance. Each cell holds the calibrated score that dimension's audit produced for that function, on the same 1-to-5 scale the framework defined at the start of the chapter. Not a rolled-up letter grade, not a traffic light with no number behind it: the score itself, because this room will remember "Finance data is 3.1 and Supply Chain data is 1.9" long after it has forgotten an amber blob. Color the cells by band so the shape reads at a glance from two meters away, but keep the numbers in the cells, because the shape starts the conversation and the numbers survive the challenge.

The grid is where the chapter's rigor pays its dividend. These are not impressions gathered in a workshop; they are calibrated scores, and each one traces to a specific audit artifact: the Process Maturity Grid, the Critical Dataset Register, the People Readiness Atlas, the governance sections of the framework scorebook. That traceability is what makes the grid safe to put in front of a hostile reader. But traceability that lives only in an appendix is invisible, and invisible rigor buys no trust. Which is why page 1 carries something most heat maps omit, and which changes how executives read it.

The evidence code: making triangulation visible

Next to each score sits a small code marking what kind of proof stands behind it, using the four evidence types your framework's triangulation discipline defined: D for document review (the SOP existed and was current; the policy was read, not reported), S for system extract (the score rests on data pulled from the system of record, not on what someone said the system contains), V for survey or interview (self-reported, valuable, softest), and C for sample coding (a hand-verified sample: fifty vendor records actually inspected, twenty process instances actually walked). A cell reading "1.9 S C" tells an executive: this ugly number comes from the system itself and from a coded sample, not from a pessimist with a grudge. A cell reading "2.6 V" honestly discloses: this one is self-reported; hold it more loosely.

Executives trust cells more when they can see what kind of proof stands behind each, and they trust the whole page more when it visibly distinguishes its hard evidence from its soft. This is the same instinct that makes an auditor's opinion letter state its basis. The evidence code costs you four characters per cell and one footnote line defining the legend. It buys you the single most valuable property a contested document can have: the reader stops arguing with the page and starts arguing with the terrain.

What does not go on page 1

Just as important is what page 1 refuses to carry. No methodology section: the method lives in the appendix, one tab behind, exactly the appendix architecture you learned in Level 2, now at full scale: eighty pages standing behind two, every exhibit numbered, every cell's citation resolvable in under a minute. No caveats longer than a footnote: a caveat that needs a paragraph is a finding, and findings live on page 2 or in the appendix. And no 90-cell detail view: your Process Maturity Grid scored thirty processes on multiple axes, and every fiber of your assessor's pride wants to show that resolution. Resist it. Six rows by four columns is 24 cells, and 24 is close to the ceiling of what a decision-grade page can hold.

The governing test is one you learned as the forwarded-reader rule, now operating at its highest altitude: page 1 must survive being photographed and forwarded. Someone in this room will photograph the grid and send it to a board member, a divisional president, a private-equity operating partner, with no appendix, no narrative, and no you. Read your draft page 1 as that stranger: if the shape of the organization's readiness, the location of the value, and the direction of travel are not legible in ninety seconds on a phone screen, the page is not done. Everything the stranger needs, on the page; everything the challenger needs, one tab behind it.

The Two Overlays That Turn Scores Into Strategy

The demand overlay: readiness only matters where value wants to happen

A grid of readiness scores, alone, is a diagnosis without a stake. The first overlay gives it one. Down the right edge of the grid, add one column per function: the value of the AI use-case pipeline currently pointed at that function, from your demand inventory (Chapter 4.2 will build the full scored portfolio; even a rough, honestly labeled pipeline estimate transforms the page). This is the demand overlay, and it encodes the sentence that reorders every priority discussion: readiness matters only relative to where value wants to happen. A red cell under $40,000 of speculative pipeline is a note. A red cell sitting under $400,000 of qualified pipeline is a headline, arguably the headline, because it prices what the unreadiness is blocking. Without the overlay, the room's eyes go to the worst scores. With it, they go to the worst collisions, which is where the money is.

The overlay also protects you from the heat map's classic misread: the assumption that the reddest function needs the most money. Gartner's finding that 63 percent of organizations lack AI-ready data practices means red data cells are the normal condition of the market; you cannot fix them all, and trying to is how readiness programs become boil-the-ocean programs. The demand overlay is your triage rule made visible: remediation dollars flow to red cells under heavy pipeline, not to red cells in general.

The trajectory markers: turning a photograph into a forecast

The second overlay is temporal. A heat map is a photograph, and executives rightly distrust photographs: the terrain is already moving. So mark the cells that are in motion, sparingly, with a direction glyph and a one-word cause. An up marker on a data cell whose remediation is already funded and scheduled: this red is dated. A down marker on a cell in the path of a known collision: the enterprise resource planning (ERP) migration that will freeze a function's master data for a quarter, the reorganization that will scatter a pooled team. Three to five markers, no more; a grid covered in arrows is a weather map, not a decision aid. The markers convert the photograph into a forecast, and a forecast is what the room actually needs, because the committee is not funding the organization as it was during your audit; it is funding the organization as it will be in the two quarters the money covers.

Between the evidence codes, the demand overlay, and the trajectory markers, page 1 now answers, on sight, the four questions the strategic conversation needs: where is readiness pooled, where is it absent, where does the value want to happen, and which of these facts are already changing. That is the map. Now the moves.

Page 2: The Narrative and the Three Moves

Three paragraphs, fixed anatomy

Page 2 opens with a narrative of exactly three paragraphs, and the anatomy is fixed because each paragraph does a distinct, non-optional job.

Paragraph 1: the honest position, in three sentences, anchored to the public failure record. State the organization's overall calibrated position plainly, then place it against the market's documented base rates: "We are a 2.3 organization in a market where 42 percent of companies scrapped most of their AI initiatives; here is why ours will not be among them." This is the scrap-year context converted from shame to rationale. The 2025 failure record, MIT's 95 percent of pilots with no measurable return, S&P Global's 42 percent scrap rate, is not an embarrassment to soften; it is the reason your sequenced, evidence-gated program exists, and paragraph 1 conscripts it. A room that has read about the scrap year in the business press is braced for either denial or doom; the honest position, stated without flinching and immediately harnessed to a plan, is the credibility event of the page.

Paragraph 2: where the asymmetry is. Strategists sell asymmetry, not adequacy. No committee funds "we are uniformly mediocre"; every committee leans forward for "readiness is pooled in two places, and here is what that concentration lets us do first." Name the build-ready functions, the pooled skills, the self-taught population the People Readiness Atlas surfaced. This is the asset read of the same terrain paragraph 1 assessed honestly, and the sequence matters: honesty first, then asymmetry, or the asymmetry reads as spin.

Paragraph 3: the constraints, stated plainly. The data backlog's total effort, the collision on the calendar, the functions with no champion bench. No euphemism, no burying. Three sentences of unblinking terrain. The constraints paragraph is what makes the three moves that follow feel inevitable rather than pitched: by the time the reader reaches the moves, the moves are simply what the terrain implies.

The three moves: the budget conversation, pre-structured

Then the page's business end: three moves. Never five, never one. One move is a bet, and the room knows organizational readiness is not a one-lever problem. Five moves is a menu, and menus invite the room to order à la carte, which destroys the sequence that makes the program work. Three moves, each funded, owned, and dated, is a strategy: small enough to hold in the head, structured enough to survive the CFO. Each move carries exactly three attachments: its ask in dollars, its owner-designate (a name, proposed in advance and pre-wired, not "TBD"), and its evidence checkpoint (what proof arrives by what date, and what the proof gates). The three moves have a fixed grammar across almost every readiness program worth funding:

• Move 1 is always the enabling fix, with the beneficiary arithmetic stated: the small number of remediation items from the backlog whose completion unblocks a disproportionate share of the pipeline. This is the Critical Dataset Register's top lines promoted to executive visibility: effort-days on one side, unblocked pipeline value on the other, division performed for the reader. Move 1 is deliberately unglamorous and deliberately first, because it makes everything after it cheaper and faster, and because a committee that funds the boring fix has psychologically committed to the program.
• Move 2 is the proof engine: pilots in the build-ready functions, where the asymmetry is, charter-governed with the full Level 3 machinery: baselines instrumented before launch, success and kill criteria pre-committed, human gates designed, evidence delivered by a named week. Move 2 is the quick-win logic, but notice what you are actually selling: not just the targets, the discipline. The heat map sells the program's method as much as its outcomes, because the method is what distinguishes your pilots from the 95 percent, and this room has read about the 95 percent.
• Move 3 is the foundation program: the remediate-first functions' data and process foundation work, plus the training program shaped by the atlas's actual skills distribution (built on the real population the audit found, not the org chart's fiction), dated to lift the terrain before wave 2 needs it, and gated on Move 2's evidence checkpoint. The gate is the committee's own risk control, handed to them pre-built: they are not asked to believe in wave 2 today, only to fund the proof that will earn it.

The sequencing logic, stated as a principle the room can adopt

Beneath the three moves, one labeled sentence states the rule the whole page obeys, because the room needs to be able to repeat it after you leave: readiness-gated investment. Value flows to terrain that can hold it; terrain investment flows to where value waits. The rule is two-sided on purpose, because it answers the room's two opposing challenges with the same principle. To the CFO's "why not everywhere?": because BCG's 10-20-70 finding (10 percent of the challenge is algorithms, 20 percent technology and data, 70 percent people and process) means capital poured onto unready terrain buys pilots, not returns, and McKinsey's numbers show what that looks like at scale: 88 percent of organizations using AI, only about 39 percent seeing any earnings impact. To the CEO's "why not faster?": because the fastest sustainable path is this one; the apparent shortcut, six simultaneous initiatives on unaudited terrain, is the exact mechanism that produced the 42 percent scrap year, and the organizations that internalize the gating rule are the ones that stop generating scrap years at all. That is the largest claim this lesson makes, and the chapter has earned it: the heat map's deepest function is not to allocate this quarter's budget. It is to teach the leadership a rule that outlives the page.

The heat map is not a summary of what you learned. It is the architecture of the decision you need the room to make: leadership acts on structured choices, never on understanding alone.

The Worked Example: Both Pages for the Enterprise

Here are both pages for the enterprise this chapter has audited, compressed for print. All figures are illustrative, carried forward from the four audit lessons. Page 1's grid, with the demand overlay at right and trajectory markers in the moving cells (evidence codes: D document, S system extract, V survey, C sample coding):

Ninety seconds with this page and the forwarded reader knows the story: readiness pools in Finance and Customer Operations, exactly where $790,000 of the $1.43 million pipeline wants to happen. Supply Chain's 1.9 data score under $340,000 of pipeline is the page's headline collision, and its up marker says the fix is already specified. Sales has a down marker: the ERP cutover will degrade its master data in Q3, so nothing fragile gets built there this year. Legal's strong governance score with a red everything-else, and its empty champion bench, make it a wave-3 conversation. Page 2's narrative, verbatim and copyable:

"We are a 2.3 organization, calibrated across four audited dimensions, in a market where 42 percent of companies scrapped most of their AI initiatives last year and 95 percent of pilots showed no measurable return. Ours will not repeat that record, for one reason: we now know exactly where we are ready, where we are not, and we propose to invest in that order. Every score on page 1 traces to audited evidence; nothing below is aspiration.

"The asymmetry is our asset. Finance and Customer Operations are build-ready today: mature processes, workable data, and the deepest pools of the 1,700 employees our census found already using AI tools on their own initiative. More than half of our qualified pipeline value sits in those two functions. We do not need the whole organization ready to start compounding; we need these two, and we have them.

"The constraints are equally clear. Our data remediation backlog totals 210 effort-days, concentrated in Supply Chain's vendor master. The ERP cutover will disrupt Sales data in Q3, so we build nothing fragile there this year. Legal and HR currently have no AI champion bench; they are wave-3 terrain until the training program changes that."

Then the three moves. Move 1, the enabling bundle: $85,000. The vendor-master cleanup plus the access fast-path, the backlog's top two lines: 55 effort-days that unblock $340,000 of Supply Chain pipeline and accelerate both pilots. Owner-designate: the data governance lead. Checkpoint: register lines closed and verified by week 10. Move 2, the proof engine: $120,000. Two charter-governed pilots, one in Finance, one in Customer Operations, instrumented baselines, pre-committed success and kill criteria, human gates designed. Owner-designates: the two function heads, named. Checkpoint: measured evidence against baseline by week 20, in June, which is exactly what June now proves. Move 3, the foundation program: $240,000, gated. Supply Chain and Sales data foundations plus the training program shaped by the atlas's skills distribution, releasing only on Move 2's evidence checkpoint. Owner-designates: the chief operating officer and the head of learning and development. Total ask: $445,000, which the page states plainly is less than half of the roughly $1.1 million this enterprise wrote off on scrapped AI initiatives during its own 42-percent year. The arithmetic is the closing argument: the disciplined program costs less than the undisciplined one already did.

The committee meeting ran its full forty minutes. Three challenges came. The CFO questioned the Supply Chain data score; the answer was the coded sample from the Critical Dataset Register, exhibit 4, fifty vendor records, hand-verified. A function head disputed his people score; the answer was the atlas's survey base and his own pre-wire conversation, where he had already seen it. The CEO asked why not faster; the answer was the readiness-gating principle and the Sales down-marker, and it had already been rehearsed privately. All three moves approved, Move 3 staged on the gate as designed. Forty minutes, eighty pages behind two, three challenges each answered from an audit artifact. That is the choreography working. All of it illustrative, and all of it the pattern.

The Failure Story: The Admired Heat Map

Now the same play with the decision architecture missing. A strategist at another firm, a genuinely skilled one, runs a comparable audit: honest scores, real evidence, defensible method. Her deliverable is the full assessment: 80 pages, presented in a 90-minute committee marathon, methodology first, findings by dimension, caveats faithfully attached. The room is impressed. The room is, in fact, moved: the chair calls it the most rigorous piece of internal analysis in years. The committee thanks her, commissions "a follow-up on next steps," and allocates nothing, because nothing on the table was allocatable: there were findings everywhere and a decision nowhere.

The next-steps deck takes six weeks, because next steps designed after the room are negotiated with everyone the findings touched. By the time it lands, two function heads, unwilling to wait, have independently bought tools: the vacuum filled itself, unsequenced, ungoverned, on exactly the unready terrain the assessment had flagged. The assessment itself is now aging: two of its scores are already stale. The follow-up meeting gets scheduled, deferred, rescheduled. Within two quarters, the firm is running the scattered, unbaselined portfolio the audit existed to prevent, and the strategist's masterwork is a PDF that people cite to explain problems rather than an instrument that prevented them.

Run the autopsy and notice what did not fail. The evidence was sound. The scores were calibrated. The rigor was real, and really admired. What was missing was the interface: the deliverable was evidence without decision architecture. Leadership rooms act on structured choices; they do not act on understanding, however deep, because converting understanding into a fundable structure is work, and a committee will not do your structuring for you in real time, and should not have to. Understanding is the strategist's job. Choosing is the room's. The heat map is the interface between them, and in its absence, rigor converts to applause, applause converts to delay, and delay converts to shadow procurement. The 90-minute marathon did not fail to inform. It failed to ask.

The Choreography, the Private Sentence, and the Standing Artifact

The pre-wire, scaled to the executive committee

You learned in Level 2 that findings never ambush their owners: the pre-wire, the private preview that converts a would-be public defender into a room ally. At executive-committee scale the discipline is the same and the stakes are higher, so the machinery gets formal. Every function head sees their own row before the room does, in a one-to-one, with the evidence behind each of their cells and, critically, with the remediation offer attached: here is your row, here is what stands behind it, and here is what Move 1 or Move 3 does for you. A function head who arrives at committee having already seen their 1.9, argued with it, touched the coded sample, and heard what the program funds for them, spends the meeting negotiating sequence instead of disputing scores. Six pre-wires is six hours of calendar. It is the cheapest insurance in the entire program.

The CFO's analyst gets the full workbook a week early. This is the hostile-analyst investment you have made before, now at its highest-stakes table: somewhere behind the CFO is the person who will actually recompute your numbers, and you want that recomputation to happen before the meeting, with you available, rather than during it, with you on stage. An analyst who has traced the $340,000 pipeline figure to its source arrives as your verification, not your ambush.

The CEO, and the sentence that saves careers

Then the most delicate visit. The CEO has, somewhere, publicly attached an expectation to this program: in our storyline, results by June, and the unexamined assumption behind it was six functions moving at once. Page 1 says the terrain supports two. That gap gets closed privately, before the meeting: "June is two functions, not six, and here is what June proves, on the record, with baselines." This is expectation surgery, and its venue is the entire game: performed in private, it is strategy, and the CEO walks into the room already owning the sequenced version as their own discipline. Performed in public, the same sentence is insubordination, a correction of the chief executive in front of their committee, and it will be remembered long after your grid is forgotten. Same words, different room, opposite career. Do the surgery early, do it with the map in hand, and give the CEO the readiness-gating principle as the language they can use publicly: leaders adopt rules faster than they adopt corrections.

The standing artifact: readiness is a trendline

Finally, decide what the heat map is, institutionally. A one-time heat map is a photograph that starts aging the day it is presented, and the trajectory markers on your own page 1 prove you know it. So the last line of page 2 makes it a standing instrument: the heat map refreshes quarterly, with a named owner for the refresh, scores re-evidenced on a rolling basis, markers updated, and the demand overlay re-synced to the portfolio. Readiness is a trendline, not a snapshot, and a committee that saw a 1.9 turn into a 2.7 two quarters after funding Move 1 is a committee that never again needs convincing that readiness investment is real. The quarterly heat map will acquire a sibling later in this level, Chapter 4.5's value scorecard, and together they become the strategist's recurring instrument set: one page of terrain, one page of returns, every quarter, forever. That cadence, more than any single meeting, is what makes you the person the organization cannot make this class of decision without.

One dependency remains exposed, and honesty requires naming it: page 1's demand overlay presumed a use-case pipeline with credible values attached. This chapter audited the terrain; it did not build the demand side. A heat map with a hand-waved overlay is half an instrument, which is exactly why the next chapter builds the AI use-case portfolio: value scored against readiness, the other blade of the scissors.

What to Do Monday Morning

1. Build page 1 from your four audit artifacts. Functions as rows, the four dimensions as columns, calibrated scores in the cells, evidence codes (D, S, V, C) beside each score. If a cell has no evidence code you can defend, that cell is not ready for the page, and now you know your last audit gap.
2. Add the demand overlay and the trajectory markers. Attach your best honest pipeline value per function, labeled as preliminary if it is. Mark at most five moving cells with a direction and a one-word cause. Then apply the forwarded-reader test: photograph the page and hand it to someone outside the program for ninety seconds.
3. Write the three-paragraph narrative and aloud-test it at three minutes. Honest position anchored to the failure record, the asymmetry, the constraints. If reading it aloud takes more than three minutes, it is carrying appendix material; cut until it does not.
4. Structure your three moves: enabling fix with beneficiary arithmetic, proof engine with charter discipline named, gated foundation program. Each with its dollar ask, its owner-designate, and its evidence checkpoint. Compute the total and place it beside your organization's own scrapped-initiative history if you have one; that comparison is your closing argument.
5. Book the choreography. Six function-head pre-wires with rows and remediation offers, the analyst's workbook delivery a week ahead, and the private CEO session for the expectation surgery. The room comes last; by the time it convenes, the only open question should be sequencing.
6. Set the quarterly refresh with a named owner, on the calendar, before the first presentation, so the heat map is introduced to the committee as a standing instrument rather than a one-time report.

Key Takeaways

• Treat the final compression as decision architecture, not summary: the Enterprise Readiness Heat Map's job is to make the right strategic conversation unavoidable, because committees allocate capital against structured choices, never against understanding alone.
• Build page 1 as a grid of functions against the four audit dimensions, with calibrated scores and evidence codes (document, system, survey, sample coding) in every cell, so the room argues with the terrain instead of the page.
• Overlay demand and trajectory: a red cell under $400,000 of pipeline is a headline while the same cell under no demand is a note, and three to five direction markers turn the photograph into the forecast the committee is actually funding.
• Keep methodology, long caveats, and full-resolution detail off page 1, behind the appendix architecture, and test the page against the forwarded reader: legible in ninety seconds, on a phone, with no author present.
• Write page 2 to the fixed anatomy: three sentences of honest position anchored to the 42-percent scrap year, the asymmetry read (strategists sell asymmetry, not adequacy), the constraints stated plainly, then exactly three funded, owned, dated moves with evidence checkpoints.
• Sequence the moves by the grammar that survives every committee: the enabling fix with beneficiary arithmetic first, the charter-governed proof engine second, the gated foundation program third, with Move 2's evidence gating Move 3's release.
• State readiness-gated investment as an adoptable principle: value flows to terrain that can hold it, terrain investment flows to where value waits, answering both the CFO's "why not everywhere" and the CEO's "why not faster" with one rule.
• Run the choreography before the room: function heads see their rows one-to-one with remediation offers attached, the CFO's analyst gets the workbook a week early, the CEO gets expectation surgery in private, and the heat map enters the calendar as a quarterly standing instrument with a named owner.