Kickoff Is a Meeting. Alignment Is a Process.
A kickoff that nearly relitigated the signed charter in the first fifteen minutes, and the engagement mechanism that was designed to make sure it did not happen again.
Sixteen People, Four Versions
The Falcon kickoff had sixteen people in the room and another six joining by video. The program manager had run the opening walkthrough: program objectives, the three firm commitments, the seven tolerances, the governance structure, the timeline. Clean forty-minute briefing. Charter pre-read had been on Confluence for five days. Everyone had access.
Q&A opened. Samuel Osei went first.
The room went quiet. Not hostile. Curious.
This was not a clarification. It was a question that, taken at face value, was in direct contradiction to Section 1 of the charter Osei had seen published eleven days earlier. The charter committed both channels in scope for go-live, because the central bank directive on digital financial inclusion required a compliant feature-phone channel. Dropping USSD from v1 was not a scheduling question. It was a scope change that would invalidate the regulatory justification for the program.
Junior PMs in this moment do one of two things. Either they contradict the business sponsor publicly, which costs political capital that the program will need later. Or they hedge and say something like "that's a great question, let's take it offline," which signals to the room that the charter is still open for negotiation. Neither works. The first burns relationships. The second burns the charter itself.
What Osei was doing was a narrative test. He was not trying to break the charter. He was checking whether the charter was live, or whether it was a piece of paper. If the PM let the question unfold without a clear anchor, the next three questions from the room would be variations on the same theme. By the end of Q&A, the kickoff would have quietly relitigated the commitment structure without anyone having to take an explicit position.
Redirect Without Contradiction
The program manager answered without looking at Osei directly. Eye contact at a moment like that tells the room there is a conflict to watch.
Amara Okonkwo, Head of Compliance, picked it up cleanly: "Correct. The directive requires a compliant feature-phone channel at launch. USSD-later is not an option available to us."
The exchange took forty seconds. Osei nodded, noted it down, moved on. The room recognised the question as answered. Nobody else raised a scope-adjacent question for the rest of Q&A.
What mattered was not the answer. It was the mechanism. The PM had not defended the charter personally. He had referenced it and pulled in the stakeholder whose function held the authority to confirm. That made the charter sound like an institutional artifact rather than a PM's position. Institutional artifacts are harder to relitigate in open forum.
The PM followed up with Osei privately the next afternoon. Ten minutes in Osei's office. The real question was not about USSD. Retail's P&L was under pressure. Osei wanted an earlier wins story to take to his own board. The USSD question was a trial balloon to see if the program had slack to give him one. Understanding that changed what Osei needed from the program: not scope relief, but a communications plan that would let him narrate the staged market rollout as early wins even though the full v1 feature set shipped to Market A first. The PM agreed to co-draft that narrative with him.
The charter was published on Confluence. The charter was not, apparently, read. Osei's question was a symptom, not a cause. Without a structured engagement mechanism between charter publication and steering meetings, Tier 1 members were free to arrive at any forum with their own version of what had been agreed. Kickoff had surfaced the pattern before it did real damage. The Engagement Plan needed to prevent it from surfacing again.
On Day 25, the program manager opened a working session with Ahmed Hassan to scope what would become the Stakeholder Engagement Plan. Two design constraints: use existing Atlas Bank tools (Confluence, the corporate calendar, Slack), and do not create reading-receipt theatre.
Tracking Is Not Alignment
Hassan's first suggestion was Confluence's page-watcher feature. Every critical program document would have Tier 1 members added as watchers. Confluence tracks opens. The PMO gets a weekly report on which Tier 1 members had opened which documents. Lightweight, uses existing infrastructure, no new tooling.
Priya Raman, dropping by the PMO room at 4pm that afternoon, disagreed.
Raman was right. Page-watcher tracks the mechanical act, not the understanding. But Hassan was also right that tracking was a necessary precondition. You cannot follow up on a missing pre-read if you do not know it is missing.
The compromise took the best of both: page-watcher for tracking, plus a mandatory pre-meeting one-on-one for Tier 1 members in the five working days before every steering committee. The 1:1 is not a status meeting. It is a pre-read confirmation. The PMO walks the Tier 1 member through the material, answers questions, surfaces concerns, and produces a written note of anything that needs to land in the steering agenda. Thirty minutes, Tier 1 member's calendar, owned by Ahmed Hassan.
Page-watcher catches the mechanical miss. The 1:1 catches the substantive miss. If Osei had walked through the charter with Hassan in the five days before kickoff, the USSD question would have been raised in that 1:1 (where it belonged), answered in writing, and either resolved or escalated before the room ever saw it. The kickoff would have been the closing-out of the alignment, not the first test of it.
With the mechanism shape locked, the next step was the full Engagement Plan: per-tier cadence, pre-read protocol, escalation path, decision authority versus veto authority distinction, owner for each. The PM used an AI-assisted pass to draft the plan before walking it through Hassan for review.
Drafting the Engagement Plan
The prompt below follows the RISEN structure: Role, Instructions, Steps, End goal, Narrowing. RISEN suits multi-part operational plans where the AI must generate structured entries across a defined set of buckets (in this case, four tiers) with consistent internal logic. The Steps dimension matters here: the plan has to work in sequence (pre-read arrives, 1:1 happens, meeting runs, follow-up dispatches), not just as a set of attributes. RISEN gives the model that sequence explicitly.
Tier 1 Plan, First Draft
The AI output for Tier 1 shown below. Full plan covered all four tiers; Tier 1 is where the most important design decisions sit and where the human edits landed.
Tier 1 — Direct and Govern (5 members)
Step 1Pre-read package dispatched via Confluence page-watcher plus email five working days before each monthly steering. Package includes: steering agenda, status dashboard, risk register changes, any proposed charter amendments, budget position.
Step 2Pre-read confirmation via 30-minute 1:1 between PMO Lead and each Tier 1 member, scheduled in the five-day window. Purpose: walk through material, surface concerns, produce written note of items for steering agenda. No 1:1, no agenda slot for that member's concerns.
Step 3Monthly steering meeting, 90 minutes, chaired by Program Sponsor. Cadence locked: first Thursday of each month, 14:00 UTC. Owner: Program Manager (agenda), Program Sponsor (chair), PMO Lead (minutes).
Step 4Follow-up dispatch within 24 hours: decision log, action items with owners and due dates, updated risk register, agenda for next steering. Distributed via Confluence page-watcher plus email.
Step 5Out-of-cycle challenge protocol. If a Tier 1 member raises a scope-adjacent question outside steering (kickoff, working group, ad-hoc meeting), the Program Manager routes it to the PMO for written response within 48 hours, not to the next steering agenda. Steering is for decisions; out-of-cycle is for clarifications.
Information access. Full: financial position, risk register, all steering decisions, all technical architecture decisions.
Decision authority. Scope changes above charter tolerances, budget above PM discretion, schedule slippage above two weeks, vendor contract amendments.
Veto authority not separated from decision authority in this draft. Amara Okonkwo (Head of Compliance, Tier 1) holds veto on central bank certification, which is not a "decision" in the same sense as a budget approval. The plan should distinguish. Without the distinction, the register implies Compliance has the same kind of authority as the CDO or CFO, which creates organisational friction the Post 03 outcome page already surfaced.
Stakeholder Engagement Plan, Tier 1 Extract
The finalised Tier 1 entry from the Stakeholder Engagement Plan v1.0, published 21 February 2025, after AI draft plus human revision. Tier 2, 3, and 4 follow the same structure with differing cadences and authority scopes.
- Separated veto authority from decision authority. AI flagged this as a review item. PM made it a first-class field in the template, named per veto holder (Compliance, Risk, CTO) with scope of veto defined. This closed the Post 03 CRO friction point structurally, not just narratively.
- Added the out-of-cycle challenge protocol. AI's Step 5 described the mechanism. PM elevated it from "protocol" to a named field in every tier's plan, with 48-hour PMO response SLA. Directly addresses the Osei-style scope-adjacent question pattern.
- Named pre-read ownership per Tier 1 member. AI gave generic ownership. PM assigned specific 1:1 slots: Hassan with Idris on day 1 of the window, Osei on day 2, Alemu on day 3, Benali on day 4, CFO on day 5. Predictability reduces PMO overhead and stakeholder friction.
In his month-3 pre-read 1:1 on 30 April, Osei raised a question about whether Market A's USSD channel could launch two weeks behind the app to ease the operational ramp. The question was scope-adjacent. Hassan surfaced it, drafted a PMO written response within 48 hours explaining the regulatory constraint (central bank certification requires both channels at launch for any given market), and the response went to Osei before the steering agenda was finalised. Osei accepted the response. The question never entered the steering room. If the 1:1 and the out-of-cycle protocol had not existed, the question would have surfaced at steering, consumed agenda time, and forced Okonkwo to re-argue the regulatory position in front of her peers. The engagement plan prevented that.
A fictional case study for teaching purposes. Atlas Bank, Project Falcon and all named individuals are invented. Technologies are industry-standard and publicly available.