Skip to content
Log in
← Glossary

project sponsor

Also called: sponsor, project sponsors

The senior person who needs the project's result, pays for it and makes the calls the project lead cannot: changing the goal, the budget or the fixed date. The sponsor answers for why the project exists; the lead answers for how it gets done.

The project sponsor is the senior person who needs the project's result, pays for it and makes the calls the project lead cannot: changing the goal, the budget, the fixed date or the success criteria. The sponsor answers for why the project exists; the project lead answers for how it gets done (the plan, the buffer, the status, bringing decisions forward). In a small company the sponsor is often the CEO or a founder.

A good sponsor does a few things well. They sign off the brief and its limits, decide changes quickly and in writing, remove obstacles that sit outside the lead's authority (another team's priorities, a budget owner's veto) and hold the management reserve for surprises. After the launch they check whether the expected benefits arrived. They don't run the tasks, and they don't hand work to the team around the lead.

Most sponsor trouble comes from the second part. A sponsor who asks people directly for new things, or changes priorities every week, makes the plan drift without anyone deciding it. The fix is not to say no but to show the price: each request goes through one channel, gets its cost in days and money from the owners, and comes back to the sponsor as options for a written decision by a date. "Not now, reviewed on a set date" is a real answer.

When an expert's quality bar and a success criterion collide, the sponsor decides, after hearing the expert. The bar is never lowered quietly by the team.

Example

Leo, Klasna's CEO, sponsors the physics launch. The brief he signed gives him three jobs: decide changes in writing within 2 working days, hold a 40,000 UAH management reserve released only on a written request, and own the success criteria, including "at least 8 tutors who passed a demo lesson".

In December only six candidates have passed. Counting two near-misses would lower Vira's bar, and changing the criterion is Leo's decision. The lead brings him two options: a second round of demo lessons paid from the contingency reserve, or opening with six tutors and fewer learners.

Two weeks later Leo asks Danylo for a mobile preview (8 to 12 working days plus about 60,000 UAH for a contractor) and then Vira for group classes (10 to 15 days of her January). Both were on the brief's out list. Danylo had already spent two days on mock-ups, which took the shared buffer from 8 days to 6 without anyone deciding it. The lead pauses that work without blame and sends Leo one message: the worry behind both requests, the cost of each in days and money, the options, a proposal that new requests come through one channel, and a decision needed by a date.

Common mistakes

  • Treating the sponsor as the project lead. The sponsor decides why, money, dates and changes; the lead runs how.
  • Letting requests bypass the lead. Work started on a direct request eats the buffer without a decision.
  • Saying no instead of showing the price. Give each change its cost in days and money and ask for a written decision.
  • Decisions only in meetings. A decision nobody wrote down gets remembered differently by everyone.
  • A sponsor who disappears after kickoff. Without quick decisions the lead ends up making calls they have no right to make.

Learn it in the course

  • Roles: sponsor, lead, expert, one owner per task · Who decides, who does and who is consulted in a small team where one person holds several roles, and a light responsibility table with exactly one owner per task.
  • The one-page brief · Goal, success, scope in and out, limits, testable assumptions, names and a change rule: one page a sponsor can sign.
  • Case: the brief for the physics launch · Turn Leo's list of outputs into the one-page brief he will sign: a goal that names the change, two-part success criteria, an out list and assumptions you can test.
  • Case: the sponsor changes priorities every week · Leo wants a mobile preview one week and group classes the next. Find what is behind it, show each change's cost in days and money, and ask him to decide in writing.
  • Re-plan from today · Reforecast the remaining work from where the project stands, keep the range, let sunk effort stay out of the choice, and tell the sponsor what changed and what you need.