What a Year of Implementation Projects Teaches About Sponsorship in a Mid-Size Company

Twelve projects' worth of sponsor data, read once, sharpens every project after

Mid-size companies sit in an uncomfortable middle ground for sponsorship. They're large enough to have multiple concurrent projects with multiple sponsors, and small enough that there's no formal sponsor-development program. The result is that each project quietly inherits whatever sponsor habits the assigned executive picked up elsewhere — usually from a different organization, often a different industry. Across the portfolio, this produces the priority collision pattern at scale: each individual sponsor seems reasonable, but the collective behavior of sponsors creates contradictions the project teams absorb.

This playbook is for an individual contributor — typically a senior PM or program lead — who has visibility into a year's worth of implementation projects and wants to convert that visibility into something usable. The output is a sharper baseline for next year's sponsor relationships, framed as concrete protocol changes rather than vague observations.

The patterns that show up

When mid-size companies run this retrospective for the first time, three patterns recur with surprising consistency.

Pattern A: The disengagement cliff. Most sponsors at mid-size companies show high engagement for the first 60 days of a project, then engagement drops sharply. The cliff is usually visible at the third or fourth steering meeting. Diagnostically, this is rarely about the project — it's about the sponsor's other priorities reclaiming their attention. Protocol response: build a 60-day re-commitment ritual into project governance. A 30-minute conversation at day 60 with the sponsor about whether the project is still their priority, and what would change that.

Pattern B: The authority gap. Many mid-size sponsors have nominal authority but lack the peer relationships to enforce it. They can sign a budget but cannot get another team to prioritize work for the project. This pattern is most visible on cross-functional implementations. Protocol response: at sponsor onboarding, name the three peer executives whose cooperation the project will need, and ask the sponsor whether they have working relationships with each. If not, the project starts with a known dependency on the sponsor's relationship-building, which should be treated as an explicit risk.

Pattern C: The unannounced handoff. Mid-size companies have enough turnover that sponsors leave or change roles mid-project. Often, the change isn't communicated to the project team for weeks. By the time it surfaces, the project has been operating without functional sponsorship. Protocol response: a quarterly explicit confirmation that the sponsor of record is still the actual sponsor. Three lines of email. The cost is trivial; the protection is real.

Why the IC, not the executive, runs this

The retrospective is most effective when run by someone who has direct visibility into project execution but is not the sponsor of any single project. That's almost always an individual contributor — senior PM, program manager, or PMO lead. Executives don't have the time or the granular project visibility; sponsors have a stake in the outcome that biases the retrospective.

The IC running it has another structural advantage: they can identify protocol changes that affect sponsor behavior without requiring sponsor participation in the retrospective itself. The output — the protocol changes — gets ratified by an executive sponsor of the program management function, not by each individual sponsor whose project was retrospected. This separation makes the retrospective politically tractable.

The reusable artifacts

Four artifacts come out of this retrospective and become standing tools for the year ahead.

The sponsor onboarding checklist. A one-pager given to every new sponsor at project initiation. Covers the three jobs (decide trade-offs, defend externally, ratify changes), the response time expectations, the steering rhythm, and the day-60 ritual. Simple enough to fit on one page; specific enough to be unambiguous.

The day-60 conversation template. A 30-minute structured conversation between PM and sponsor. Three questions: 'Is this project still in your top three priorities? What's changed since we started? Is there a different sponsor who would be better positioned now?' The third question is the one that matters most, and the one that often produces a constructive sponsor change.

The quarterly sponsor confirmation. A three-line email sent quarterly to every active sponsor. 'You are listed as sponsor for X. Is this still accurate? Reply yes/no.' The protocol catches handoffs early and signals to the sponsor that their role is being tracked.

The sponsor health quarterly. A summary view of all active sponsorship arrangements in the portfolio, with each scored against the ten-question assessment. Used by the head of program management to identify portfolio-level risks. Not shared with individual sponsors.

Together, these four artifacts convert a one-time retrospective into a standing discipline. The first iteration takes a quarter to produce; subsequent iterations take an afternoon. The compound effect across years of projects is what makes the work pay off — sponsorship at the company gradually becomes a more reliable input, which makes every project better, which makes the next year's retrospective sharper.

For the per-project version of this work, see the sponsor health self-assessment and the engagement calculator. For the front-end of identification at startups, see the startup sponsor wizard.