Supportive Sponsor, Missing Decision

Filed by: D.B. Trench

Field line: Support is not sponsorship until it spends political capital before the deadline passes.

The sponsor opened the update by thanking the team for its continued effort.

Kind. Also useless for the item sitting at the top of the action log for the third straight week.

The vendor variation needed approval by Thursday. Not “soon.” Not “once we have alignment.” Thursday. After that, the vendor would miss the build window, testing would move, and the launch message would begin its slow transformation from confident to interpretive.

The sponsor supported the project. Everyone knew this because the sponsor said so often. The deck said it. The minutes said it. The project charter said it in a sentence long enough to qualify for infrastructure funding.

The vendor variation remained unsigned.

This is one of the more dangerous project conditions because it looks friendly. Nobody is hostile. Nobody is blocking in daylight. Nobody is declaring war on the schedule. The sponsor is positive, available in principle, and very interested in success.

Meanwhile, the delivery team is waiting at a locked gate while the person with the key sends encouraging messages from another building.

The first few asks were too soft. I could see it in the email trail.

We would appreciate your guidance on the vendor variation.

Please let us know if you have any concerns.

We are looking for your support on the path forward.

Those sentences gave the sponsor too many places to stand without deciding.

Guidance can become a conversation. Concerns can become silence. Support can become a warm paragraph that leaves the approval untouched.

So I stopped asking for support.

We need approval on the vendor variation by Thursday at noon. If approved, the vendor starts the revised build sequence Monday and UAT remains on the current schedule. If not approved, we remove the reporting enhancement from this release to protect the date. If no decision is made by Thursday noon, UAT moves by one week. Please confirm which path you want us to proceed with.

That email did not accuse anyone. It treated sponsorship as work.

The reply came back fast.

Can we discuss options before deciding?

Of course we could. That is one of the classic ways a decision extends its life expectancy.

I sent the impact summary before the call. One page. Three paths. No motivational language.

At the call, Finance had a question about cost. The business owner wanted to keep the enhancement. The sponsor asked whether the vendor could absorb part of the impact. Reasonable questions. Useful questions. Questions that still had to end somewhere.

They did not.

The sponsor asked for another day.

That was not a disaster. It was just no longer allowed to pretend to be sponsorship.

The action log changed that afternoon:

Sponsor decision outstanding. Vendor variation approval required to maintain UAT date. If no decision by Friday noon, schedule impact to be recorded and UAT date to move.

Friday noon arrived with no decision.

No villain music. No dramatic refusal. Just silence, which is how many project decisions decline responsibility while remaining professionally dressed.

The vendor slot moved.

The sponsor approved the variation Monday morning and wrote, “Please proceed with urgency.” The team did. The project still lost three days because the build window had already gone to another client.

The sharp sentence did not save the date.

That matters.

Sometimes the right escalation does not create authority. Sometimes it only prevents the cost from being mislabeled later as poor coordination, vendor delay, or team responsiveness.

The final note said:

Decision received after vendor build-slot deadline. UAT impact is three working days. Impact is attributable to approval timing, not execution delay.

Nobody liked that sentence.

It stayed because the important record was not “sponsor supportive.” The important record was when authority arrived, what it arrived with, and what the delay cost.

A supportive sponsor can still leave a project exposed. When that happens, do not ask for enthusiasm. Ask for the decision, the deadline, and the consequence of silence.

If the answer is still silence, write down the silence.

---

Decision pressure test: Use this when encouragement is present but authority has not arrived.

Authority needed: Name the decision, the deadline, and what depends on it.

Boundary sentence: “The team can proceed once [decision] is made. Without it by [date/time], [impact] begins.”

If silence continues: Record the missed decision point and attribute the impact to approval timing, not execution delay.

Free field tool: Use the Trench Field Notes Kit to capture decisions, silence, and consequences before the project starts improving the memory.