Model the Change Before You Ask for It
Every sponsor says the transformation is important.
The great ones prove it through behavior.
This is the moment where credibility is built or quietly destroyed:
A sponsor says: “We support the new way of working.”
Then they keep operating the old way:
they ask for the legacy report
they bypass the new workflow “just this once”
they send a delegate to the session where everyone is supposed to learn
People always notice.
Prosci emphasizes that sponsorship must be active and visible, which includes consistent attention, championing, and accessibility throughout the change. HBR reinforces the sponsor’s role in creating the conditions where adoption is possible, not just approving the effort.
What excellent sponsors do differently
They let themselves be seen learning. Not performative vulnerability. Real participation.
They accept short-term friction. Modeling change means living with some inconvenience. That inconvenience is part of the signal.
They stop rewarding the old world. If you still praise heroics that depend on broken processes, you reinforce the pre-transformation culture.
They create “follow-me” moments. “Here is how I used the new process this week,” not “How is adoption going?”
A field vignette
One sponsor made a different kind of commitment: they went first, publicly, with AI.
Not a polished demo. Not a slide about “the future.” Real work.
For the first 45 days of an enterprise Copilot rollout, they did three things consistently:
They joined the pilot cohort as an actual user, not an observer. They showed their own prompts, their own misses, and how they corrected course.
They told one short “I used it yesterday” story every week in an exec forum and then in a broader leader meeting. Not a case study. A real example: the meeting prep they summarized, the messy spreadsheet they cleaned up, the first draft they improved.
They made it safe to learn by being imperfect in public. When Copilot gave a mediocre answer, they didn’t hide it. They said, “Yep, that wasn’t great. Here’s how I adjusted the prompt, and here’s what I learned.”
The impact was immediate. Teams stopped treating AI as a side experiment for the tech-forward few and started treating it as an organizational capability they were allowed, even expected, to build.
Nothing about the technology changed. The signal changed.
A practical sponsor move you can steal
Pick one high-signal behavior that proves you’re not delegating the change, and commit to it for 30 days.
Here’s a simple version that could work for an AI tool or new platform or process:
1. Volunteer to be part of the pilot (as a user, not an observer)
Block 60 minutes per week for hands-on use.
Use it on real work you already do (meeting prep, writing, analysis, summarization, decision framing).
2. Pick two repeatable “signature tasks.” Choose tasks that are common, relatable, and safe:
“I’ll use Copilot to prep for every leadership meeting.”
“I’ll use it to turn messy notes into a one-page brief.”
“I’ll use it to draft the first pass of internal comms and then edit it.”
3. Share one weekly story. Every week, share a 90-second update:
What I tried
What worked
What didn’t
One tip that helped
This is the “follow-me” moment. It’s the signal.
4. Remove the escape hatch for yourself, not for everyone. Make one rule you follow consistently:
“If I’m asking my team to learn this, I’m going to use it first.”
“If I want AI adoption, I’m going to create my own use cases in public.”
5. Recruit one peer sponsor. Ask one other exec to do the same 30-day commitment in parallel. Two leaders doing this together changes the tone of the entire organization.
The Takeaway
You cannot ask the organization to change faster than you are willing to change yourself. Adoption follows modeled behavior, not endorsed messaging.
Engage with the original LinkedIn newsletter.