The Mandate That Almost Had No Sponsor

About This Series

This is a 22-post series that follows a single fictional program, Project Falcon at Atlas Bank, from inception through closing. Each post covers one decision point, one framework, one template, and one AI prompt used to navigate the moment. Across the series, the same technology stack, the same stakeholder cast, and the same financial baseline carry through, so the program evolves as a traceable whole rather than twenty-two disconnected lessons.

Project Falcon at Atlas Bank

Before the story of the missing sponsor, the story of the program itself. The decision described later in this post, to stop all planning work for two weeks at the very beginning, only makes sense against the shape of what Falcon was trying to do and what stood to be lost if it failed.

Atlas Bank is a mid-sized universal bank operating across three markets in a regional economic bloc. Retail, corporate, and SME divisions. Approximately four million customers at the time Falcon began. A legacy core banking system, siloed, branch-first. Regulated by a central bank that had recently issued a directive on digital access. A competitor had launched a comparable digital platform six months earlier and was already taking market share. The board had approved the capital expenditure publicly. The chief executive's next contract renewal was tied to delivery.

That is the pressure context, and it matters. Every decision the program touched carried a political shadow behind it. A program manager who does not read the political room is a program manager who gets blindsided in the steering committee.

The Mandate

Project Falcon was the delivery vehicle for a national digital banking platform. One platform, three markets, two channels. A smartphone application for customers with data access, and a USSD channel for customers on feature phones. The smartphone app was the future. The USSD channel was the present. One could not be built without the other. Losing the feature-phone segment meant losing financial inclusion, which meant losing the regulatory alignment that justified the program in the first place.

Everything else was secondary. Features, aesthetics, roadmap aspirations, none of them mattered if any one of those three failed. The shape of the commitments, the named cast, and the technology stack are summarized on the next page.

Program at a Glance

The numbers, phases, methodology, and named cast at a single view. The technology architecture follows on the next page. This is the reference every subsequent post in the series traces back to.

Nineteen Services, One Integration Surface

Falcon was built on standard, industry-available technology. Nothing on this page is exotic. The stack was selected deliberately to avoid being the first customer for any single layer. That choice cost some architectural elegance. It bought stability in delivery. Each layer is listed with its purpose, not just its components.

Approval Without Ownership

Everything summarized on the dashboard, the mandate, the commitments, the cast, the technology, was in place when the program manager walked into Atlas Bank on 15 January 2025. The brief received across the first forty-eight hours contained roughly what you have just read.

What it did not contain was a sponsor.

Atlas Bank had been talking about Falcon for fourteen months. The board had voted. The budget had been allocated. The PMO, under Ahmed Hassan, had been standing up the governance framework for six weeks. And yet, on the morning of Day 1, when the program manager asked Hassan for the program business case, a 47-page document arrived by email within the hour. It was well-structured. Strategic rationale, financial projections, risk summary, proposed timeline, technology stack overview. Page seven is where the problem surfaced. The sponsor field was blank.

Not missing. Not marked as to-be-confirmed. Blank. As if the field had been deliberately left empty, hoping no one would notice.

Phone calls across the afternoon confirmed the shape of it. Two board members had separately told the PMO they supported the program. One had introduced it at the board meeting that approved the budget. The other had championed the business case through finance. But neither had been formally designated as program sponsor. Neither had agreed to own escalations. Neither had committed to sign the program charter.

By the end of Day 1, the picture was clear. Atlas Bank had approval without accountability. The program had a budget, a timeline, and a team. It did not have a sponsor.

Stop Everything Until Sponsorship is Named

The temptation in week one is to start building things. Stakeholder registers. Risk logs. Draft charters. Architecture decision records. It looks productive. It signals energy and competence to the PMO and the executive team. And most of all, it avoids the uncomfortable conversation about who is actually on the hook for this program.

The program manager chose not to start anything until the sponsor question was resolved.

That is a decision that looks obvious written down. In practice, it is hard, and every senior program manager has made the opposite decision at least once in their career and paid for it. When new in a role, the pressure to demonstrate motion is intense. The PMO wants to see a Gantt chart. Executives want an updated risk view. Holding the line and saying "I am not starting planning until we have a named sponsor" sounds bureaucratic, even defensive, to people who do not yet trust the new PM's judgment.

So the two weeks were framed differently. They were called "governance readiness". A daily fifteen-minute check-in was scheduled with Ahmed Hassan so the rhythm of the program stayed visible. And the time was used for the conversations that actually needed to happen.

What Makes a Viable Sponsor

The Standard for Program Management is precise on this point. The program sponsor is the individual or group who authorizes the program, provides resources and support, and champions the program within the organization. This is an active role, not an honorary one. It requires authority, alignment, and appetite for accountability, in that order.

Twelve senior stakeholders at Atlas Bank had some level of proximity to Falcon. Over the next two weeks, the task was to map which of them actually had all three of the following:

1. Organizational authority to make resourcing decisions without seeking further approval from above
2. Strategic alignment between their own mandate and the program's stated outcome
3. Appetite for accountability, meaning a genuine willingness to own failure as well as success

Most of the twelve had one or two of these. Very few had all three. That was the filter.

To structure the classification and make it defensible, the prompt on the next page was used.

Stakeholder Power Mapping

After one-on-one conversations with seven of the twelve stakeholders over Days 2 to 6, the following prompt was used to structure the classification and surface the clearest sponsor candidates. The prompt is reusable. Any program manager walking into a program without a named sponsor can adapt it.

What the prompt produced when the seven stakeholder profiles were fed into it is shown on the next page.

Classification and Recommendation

Recommendation and Risk

The output gave a structured view of the landscape in under ten minutes. It also did what a good advisory output should do: it named the risk in its own recommendation. The first conversation with Fatima Idris was not about whether she would accept the sponsor role. It was about what sponsorship would actually cost her in time and political capital, and whether she was willing to pay it.

The answer came on 28 January 2025 (Day 14). Idris accepted the role on the terms documented, including the four-hour critical-escalation response commitment and the monthly steering cadence. That acceptance unlocked the full governance stack and made charter approval possible.

Program Business Case, Version 1.0

The full Program Business Case submitted for charter approval on 1 February 2025 (Day 17), after the two-week governance readiness exercise was complete. The sponsorship section that was previously blank is now populated. Every figure, date, and name below carries forward into the rest of the series.

The business case above was submitted for charter approval on 1 February 2025. Every figure, every named stakeholder, every commitment becomes a reference point across the remainder of the program. When the EVM numbers are read in a later post, the $14.2M anchor on this page is what the earned-value math traces back to. When the go-live readiness review is described, the success criteria listed here are the specific metrics reviewed against.

A program without a populated business case is a program without a benchmark. Everything that happens later is measured against what was promised here.

What the Two Weeks Bought

Fatima Idris agreed to the sponsor role on 28 January 2025 (Day 14). She countersigned the program charter on 2 February 2025 (Day 19). The formal kick-off meeting took place on 7 February 2025 (Day 24).

The two-week delay at the start was real, and it was visible. The PMO flagged it on the weekly status report. One board member asked, during an informal conversation, why planning had not started. The explanation held: the governance foundation was being built, and commencing planning without a named sponsor would have created a program that could not be governed. Running a $14.2M program where nobody was willing to sign for it was not an option the new program manager was prepared to accept.

That explanation held. Nobody pushed back further.

What Changed in the Business Case

Version 1.0 of the business case differed from the draft received on Day 1 in three important ways beyond the sponsor field. These are the details that get skipped in most governance templates and cost the most when they are missing.

1. The escalation path was documented explicitly with named roles and response-time commitments, not titles and aspirational availability. The sponsor would respond to critical escalations within four hours. That number was in the document.
2. The sponsor's authority ceiling was stated in specific numbers, so the team knew exactly what decisions could be made at program level and what required board escalation. Clarity on authority ceilings prevents about half the political friction on a large program.
3. The sponsoring body was named as the Executive Digital Transformation Committee, with a defined meeting rhythm and a defined decision log, rather than a generic reference to "executive leadership".

None of these required renegotiating scope or budget. They required sitting in rooms with people and asking direct questions about accountability that most programs avoid asking until it is too late.