Learning objectives
By the end you can:
- Run the full engagement arc solo: problem definition → structure and workplan → analysis with exhibits → synthesis → recommendation → implementation plan → answer-first storyline, as one continuous argument rather than a sequence of disconnected deliverables, and explain why the governing thought at the top of your final recommendation is the same day-one hypothesis you used to structure the work.
- Triage under a clock. Given a fixed time budget, allocate minutes to the analysis that can actually change the answer (minimum killing analysis), consciously refuse the analysis that cannot, and execute a defined recovery move when you fall behind, the "capstone economy."
- Deliver a SteerCo-style interim update that is answer-first and held loosely: lead with your current best answer and its confidence, show the evidence so far, name what is still open, and run the room to a decision, the opposite of "we're still gathering data."
- Handle client pushback as a professional, in dialogue, distinguish the four kinds of pushback (data, logic, feasibility, politics), metabolize each with the trust equation rather than ego, and know when to hold your answer with new evidence versus fold it honestly when the client is right.
- Produce a workplan and team plan you could hand to a real team (workstreams derived from the issue tree, a RACI, a milestone sequence, and a staffing/effort estimate that reconciles) turning your private structure into a shared operating plan.
- Write an implementation plan that makes the recommendation actionable, phased initiatives sequenced by value and feasibility, an owner and a first step for each, and a value-capture bridge whose arithmetic reconciles to the size of the problem you diagnosed.
- Assemble the answer-first storyline (governing thought → MECE key line → support → risks & mitigations → next step) and hand it off correctly, the consulting logic of the storyline is yours to build here; deck production and slide craft belong to the Presentation galaxy (G4), and you will state that boundary out loud.
- State the honest scope of a capstone, what passing it certifies (the teachable floor: the arc, the triage, the leadership moves, the answer-first discipline) and what it cannot manufacture (the judgment that compounds only from real engagements), and describe the requirements of the timed, candidate-led, ≥90% certification case on an unused company.
What this capstone can and cannot certify (the honest scope, restated for the crown). CN0.01 opened this galaxy by drawing a hard boundary, and it is nowhere more important than here. A great partner's judgment, the pattern-recognition that lets someone smell a wrong number across a boardroom, or know which of a CEO's stated worries is the real one, compounds from hundreds of live engagements over years, and no capstone can manufacture it. What this node certifies is the teachable floor: that you can run the arc end to end, triage your time, lead a client interaction without breaking, and land an owned, actionable answer. Passing the Partner Capstone does not mean you are a partner. It means you have built the scaffolding a real partner's judgment will later compound on top of, that you are ready to be trusted, tomorrow, with a real workstream on a real team. Hold that boundary honestly; it is exactly what makes the belt worth earning.
Prerequisites & connections
Builds on, the whole galaxy, by design. This is the one node in the Consulting galaxy that assumes everything before it, because a capstone that let you skip a branch would not be certifying an engagement. Concretely: CN0.01–CN0.02 gave you the consulting mind and the shape of an engagement (proposal, SOW, scope, team, the trust equation), the capstone runs the delivery half of that arc under time. CN1.01–CN1.03 are load-bearing throughout: MECE issue trees become your workplan, the day-one hypothesis (CN1.02) becomes your workplan's spine and later your governing thought, and the answer-first synthesis (CN1.03, the crown of Structuring) is the discipline that carries from your first SteerCo to your final recommendation. CN2.01–CN2.04 are the arithmetic and the case formats you will chain under the clock, by now the math cannot be a bottleneck, because your attention has to be free for judgment. CN3.01–CN3.03 decide whether to reach for a framework at all (Rumelt's diagnose-before-prescribe), which is exactly the trap a timed capstone punishes: framework-as-theater burns minutes and impresses no one. CN4.01–CN4.02 let you read an unfamiliar industry fast enough to be useful in the first ten minutes. CN5.01–CN5.03 and CN6.01–CN6.02 supply the diligence and deal logic a strategy engagement often turns on. And CN7.01–CN7.02, immediately upstream, gave you operating-model and org design, transformation-roadmap sequencing, program governance, and the craft of running a working session and a steering committee, the raw leadership moves this capstone now asks you to perform while also carrying the analysis.