Reading a program before you join it

The brief is good. The platform is one you know, the sponsor was persuasive, the rate or the package is right and the start date suits. Six months in, the sponsor has moved to another division, the program is “re-planning” without new money, and your contract is being extended a month at a time. Nothing in the brief told you this. The funding story would have.

Senior program directors are assessed hard at interview. Very few assess the program back with the same rigour.

Why the brief tells you less than the funding story

A brief is a description of intent, written by the person who wants the program to happen, usually before the hard decisions about scope and money were settled, and written to attract you. That does not make it dishonest. It makes it incomplete.

The funding story is a chain of specific events: a business case, a paper, a committee, a signature, a line in a budget, a contract with a vendor. Each link either exists or it does not, and each can be checked. A program with a complete chain survives a bad quarter. One with gaps is a reforecast away from “phase two”.

The questions that reveal whether it survives the next budget round

Ask these once interest is established on both sides, as a program director would, not as an auditor.

Who sponsored it, and where does that person sit now? A program whose executive sponsor is the CEO or CFO is funded differently from one sponsored two levels down. If the sponsor has changed since approval, ask why.

Which paper approved it, and at which committee? The answer tells you how hard the program is to cancel. A board-approved program needs a board paper to stop. A divisional one needs an email.

What does the benefits case say, and who signed it? Benefits with a named owner in the business, and a number that owner has agreed to be measured on, hold. Benefits that live in a slide the program wrote for itself do not.

How many times has the scope been re-baselined? Once is normal. Twice is a question. Three times without new money is a program being managed down slowly.

Is the vendor contract signed? A signed implementation contract cannot be walked away from quietly. One “in final negotiation” while the director is being hired is a program that still might not happen.

What happened to the last person? If there was none, why is the role being created now. If there was, where did they go, and does the sponsor speak about them freely. How the answer is given tells you more than its content.

Reading the governance

Governance on paper is a diagram. Governance in practice is who turns up.

Ask how often the steering committee meets and who actually attends. A monthly committee where the sponsor sends a delegate is a program nobody senior is watching. A fortnightly one the sponsor attends in person is a program the organisation has decided matters. Then ask whether the CFO, or a direct report of the CFO, is in the room. A program that finance is not watching closely is one that finance will find easy to cut.

Ask to see the last two steering papers. The gap between them and the brief is your risk, written down.

The signals of a program about to be paused

Some are visible from outside, before the first conversation.

The sponsor has moved, been promoted or announced a departure. The program is “re-planning” or “resetting” with no corresponding funding announcement. The language has shifted to “phase one” and “phase two”, and your work is in phase two. A new CFO or CEO has arrived and has not yet backed the program. Any one of these is worth a direct question. Two together are a pattern.

Asking without sounding difficult

The concern we hear most is that these questions will read as negativity. They do not, if the framing is right.

Frame every question as the first act of running the program. “If I start in March, the first thing I will want to see is the benefits case and who owns each line; how does that look today?” is not a difficult question. It is the question a sponsor wants to hear, because it is the one the board will ask them.

Ask about the past as context rather than judgement. “What did the organisation learn from the last baseline?” lands differently from “why has it slipped twice?” Save the sharpest questions for the sponsor rather than the panel, and for when the offer is close.

A sponsor who bristles at these questions has told you something useful as well.

When the answers are poor

Most large programs have at least one gap in the chain, and a director who only joins fully funded, board-approved, contract-signed programs will spend a lot of time between roles. The point of reading the program is not to avoid risk. It is to price it.

If the funding is soft, negotiate the terms that protect you. On contract: a longer initial term, a notice period that runs both ways, a rate that reflects the risk you are carrying, and clarity on what happens to the engagement if the program is paused rather than ended. On permanent: what the role becomes if the program closes, who you report to when it does, and what is in mind for you after go-live. Get it in writing before you start; the moment to negotiate exit terms is before anyone needs them.

The honest read from us

When a senior program director brings us an offer and asks what we think, we read the funding story with them before we read the brief. We often know the organisation, the sponsor and what happened to the last person, because we work this market every week. Sometimes the program is sound and the rate is light. Sometimes the program is a year from being real and the terms need to say so. Sometimes a better program is funding next quarter and this one is worth declining well.

The programs we are working on now are on our live roles page. The ones not yet public are the ones most worth a conversation.

Questions candidates ask