The Sponsor You Need But Don't Deserve

Hook: Every successful DX team has something in common: an executive sponsor who protects them from the organization. Here's why you need one, how to find one, and what to do if you can't.

---

Let me tell you about two DX teams.

Team A had great engineers. They identified real problems. They proposed smart solutions. They were systematically blocked at every turn. "We can't slow down for that." "Not this quarter." "That's not a priority." After 18 months of frustration, the team dissolved. Half the members quit the company.

Team B had similar engineers, similar problems, similar solutions. But they also had a VP of Engineering who attended their weekly syncs, backed their proposals in leadership meetings, and said things like "We're doing this" rather than "Let's get buy-in."

Team B transformed their organization. Team A became a cautionary tale.

The difference? A sponsor.

Why DX Teams Need Air Cover

Here's the uncomfortable truth about DX work: it often conflicts with short-term organizational pressure.

DX says: "We need to fix the build before adding more features." Quarterly pressure says: "Ship the feature, we'll fix the build later."

DX says: "We need to slow down and address tech debt." Quarterly pressure says: "Tech debt is fine. Ship faster."

DX says: "This deadline is impossible without cutting corners." Quarterly pressure says: "Make it happen. Figure it out."

Without organizational power, DX teams lose these battles. Every time. They become frustrated advisors preaching into the void while the org continues to degrade.

A sponsor is someone with enough authority to win these battles on behalf of the DX team.

What a Good Sponsor Does

A good sponsor isn't just a passive supporter. They actively enable DX work:

1. Provides Air Cover When someone pushes back on a DX initiative, the sponsor says "This is happening" in the leadership meeting. They absorb political heat so the team can focus on the work.

2. Allocates Resources Budget for tools. Headcount for the team. Time allocated for improvements. A sponsor with budget authority makes these happen.

3. Escalates When Necessary Some problems can only be solved at the executive level. A sponsor can take issues to the CEO when needed.

4. Translates for Leadership Technical people often struggle to explain DX value in business terms. A good sponsor speaks both languages and can make the case.

5. Protects the Long View When quarterly pressure threatens long-term health, the sponsor maintains perspective. "Yes, we could ship faster by skipping this. Here's why we won't."

The Reporting Structure Matters

Where the DX team sits organizationally determines how much power they have.

Bad options:

Reports to someone who doesn't code: They can't evaluate DX work or understand its importance.

Reports to someone without budget authority: Can't protect resources, can't invest in soil.

Reports to someone focused only on shipping: Constant conflict between short-term output and long-term health.

Reports to HR/People team: DX becomes an "engagement" problem rather than an engineering problem.

Better option:

Reports to VP Engineering or CTO level:

• Has dedicated budget (not begging for resources quarterly)
• Has authority to prioritize long-term health
• Can push back on unrealistic demands
• Can escalate to CEO when necessary

The sponsor doesn't have to be the direct manager. But they need to be senior enough, care enough, and be willing to spend political capital on DX work.

Finding a Sponsor

What if you don't have a sponsor? You have three options:

Option 1: Recruit One

Find an executive who cares about engineering quality, developer retention, or technical sustainability. Show them data: turnover costs, build time trends, incident frequency.

The pitch: "We have a systematic problem that's costing the organization $X. I have a plan to fix it. I need you to back me."

Not all executives will bite. Keep looking until you find one who does.

Option 2: Build Bottom-Up Support First

Sometimes you need proof before you get a sponsor. Pick a small, winnable battle. Fix something visible. Document the before and after.

Now you have a story. "We fixed X, saved Y, and developers are happier. Imagine if we could do this systematically."

Stories recruit sponsors more effectively than proposals.

Option 3: Accept Limited Scope

Without a sponsor, you can still do valuable work—just smaller. Fix your own team's environment. Document practices. Build community programs that don't require executive buy-in.

Think of it as building the case for future sponsorship. When a sponsor eventually appears, you'll have demonstrated value.

What If You'll Never Have One?

Some organizations will never sponsor serious DX work. Signs:

• Leadership genuinely believes extraction is the right model
• Short-term thinking is structural (VC pressure, imminent acquisition)
• Anyone who advocates for long-term health is labeled "not a team player"
• Multiple DX initiatives have died for political reasons

If this describes your organization, be honest with yourself. You have two options:

Work around it: Focus on what you can improve without sponsorship. Make peace with limited impact.

Leave: Find an organization that values what you're trying to do. Life is too short to fight battles you can't win.

The Sponsor's Test

If you have a sponsor, here's how to know if they're actually providing value:

1. When DX initiatives are challenged, do they defend them?
2. When you need resources, do they help secure them?
3. When short-term pressure threatens long-term health, do they hold the line?
4. Do they show up—to meetings, syncs, reviews?
5. When you escalate, do they act?

If the answers are yes, nurture that relationship. It's more valuable than any tool or process you could build.

If the answers are no, you have a sponsor in name only. That might be worse than having none at all.

The Bottom Line

A DX team without a sponsor is a car without an engine. It might look good, but it's not going anywhere.

Find your sponsor. Prove value to them. Protect that relationship.

Everything else in DX work depends on it.

---

Next in series: "Why Your DX Team Needs a Nitrogen Fixer"