Give your sponsor a decision to make.

“We need more sponsor support” becomes easier to act on when you can name the decision the team cannot make.

A sponsor may need to explain why the change matters, resolve competing priorities or remove a barrier beyond the project team’s authority. Those are different jobs. A general request to be more visible does not tell them which one matters now.

Describe the consequence.

Start with what is happening and why it matters. Keep the account short enough that the decision remains visible.

For example, a fictional team might need staff released to practise a new process. The problem is not simply “training is behind”. Two departments have competing priorities, and nobody on the project team can agree the protected time.

That gives the sponsor something specific to resolve.

Bring a recommendation and a tradeoff.

Explain the available options, your recommendation and what it would mean for the work. Include the cost of waiting when there is one.

A useful request might be: “We recommend protecting two practice sessions before the change begins. That needs agreement from both department leads. Can you resolve the priority with them this week?”

The wording makes the responsibility clear. It also gives the sponsor a recommendation they can question or support.

Agree how the answer returns to the team.

A decision in a leadership meeting does not automatically reach the people who need it. Confirm who will communicate it, what the team needs to know and whether it changes the plan.

If the answer is no, explain what happens next. Does the scope change? Does the team need another option? Is the risk being accepted by someone with the authority to do so?

Make sponsorship part of the plan.

Identify the moments when the sponsor is needed before the team reaches a standstill. Build those decisions and conversations into the work, with enough context for the sponsor to prepare.

Before your next sponsor update, finish this sentence: “The decision we need from you is…”