By Scott Scoble in DX First Principles — 30 Jan 2026

The 3-Year Mission: Why DX Teams Should Plan Their Own Obsolescence

Hook: The best DX team is one that works itself out of a job. No, really.

"Developer Experience: the formation frontier. These are the endeavors of the DX team. Our three-year mission: to cultivate sustainable engineering practice, to seek out friction and remedy dysfunction, to boldly improve what others accept as inevitable."

Yes, that's a Star Trek reference. Yes, it's also a serious strategy.

The best DX teams don't plan to exist forever. They plan their own dissolution—not as failure, but as the ultimate success.

The Crutch vs. The Cure

There are two ways a DX team can operate:

The Crutch Model: The team becomes essential infrastructure. Developers depend on them for everything. When the DX team is overwhelmed, developers suffer. When DX team members leave, institutional knowledge disappears. The team is a permanent fixture—and a permanent bottleneck.

The Cure Model: The team improves the environment systematically. They build capability in others. They cultivate self-sustaining practices. Over time, the organization becomes healthy enough that the specialized team isn't needed anymore.

The crutch model feels good in the short term. The cure model creates lasting value.

The Dissolution Test

Here's the litmus test for your DX team:

What happens if the DX team disappeared tomorrow?

If the answer is "chaos"—things fall apart, practices degrade, nobody knows how to maintain the tools—then you've built a crutch.

If the answer is "practices continue, community maintains standards, systems keep working"—then you've built a cure.

The goal isn't to make the DX team indispensable. The goal is to make the DX team unnecessary.

The 3-Year Arc

A healthy DX team should plan in three phases:

Year 1: Foundation (Establish and Diagnose)

Complete comprehensive soil assessment
Deliver 2-3 quick wins for credibility
Establish measurement baselines
Build relationships and trust
Develop the remediation roadmap

This is when the team is most visibly active. You're diagnosing problems, shipping fixes, proving value.

Year 2: Remediation (Systematic Improvement)

Address top soil deficiencies
Build self-sustaining community programs
Transfer ownership of tools and practices to product teams
Develop internal champions who carry the work forward
Shift from doing to enabling

This is the transition phase. You're still doing work, but increasingly your work is teaching others to do the work.

Year 3: Cultivation (Prepare for Dissolution)

Practices are peer-maintained without DX coordination
Community programs run themselves
Measurement is institutionalized in engineering leadership
Knowledge is distributed, not concentrated
Exit triggers are being evaluated

This is when you know you've succeeded: things work without you.

Exit Triggers

How do you know when the team can dissolve? Define specific, measurable triggers:

Trigger	Threshold	Sustained For
Practitioner Retention	< 10% voluntary turnover	4 quarters
Junior Promotion Rate	80%+ within 24 months	2 cohorts
Incident Frequency	50% reduction from baseline	2 quarters
Psychological Safety	90%+ "can admit mistakes"	2 surveys
Self-Sustaining Practices	Programs continue without DX	2 quarters
Peer-Maintained Standards	Enforced by teams, not DX	3+ teams

When all triggers are green, the team has succeeded.

Exit Options

Dissolution doesn't mean everyone gets fired. It means the specialized team isn't needed. Options include:

Full Dissolution: Team disbands. Members return to product teams as senior practitioners who model good practice throughout the organization.

Maintenance Mode: Reduce to one person at 20% time. They run quarterly soil assessments and report to leadership. No active intervention—just monitoring.

Platform Absorption: Tooling work absorbed by Platform Engineering. Community work becomes "everyone's job." The DX function is distributed, not centralized.

Rotation Model: DX responsibility rotates annually among senior engineers. No dedicated team—just rotating stewardship.

What Triggers Re-Formation

Sometimes, even after dissolution, a DX team needs to re-form:

Voluntary turnover exceeds 15% for two quarters
Major organizational change (acquisition, rapid scaling, leadership turnover)
Soil assessment shows degradation in 3+ components
Community practices atrophy (no craft talks for 6 months, mentorship collapses)

Re-formation requires the same sponsorship and budget commitment as initial formation. It's not failure—it's the system self-correcting.

The Ego Problem

Let's be honest: planning your own obsolescence is hard on the ego.

DX teams that have successfully improved their organization can feel proud. They've done good work. Why should they dissolve?

But clinging to the team structure after it's no longer needed is a failure mode. It's choosing team survival over organizational health.

The best DX practitioners embrace this: success means the specialized team becomes unnecessary. The practices, culture, and capability live on—just not in a dedicated team.

This is how a doctor thinks about health. The goal isn't to keep treating the patient forever. The goal is to make the patient healthy enough that they don't need the doctor anymore.

The Boldest Move

Most teams want to grow. More headcount. More budget. More scope.

The boldest move a DX team can make is to shrink—because the organization no longer needs them.

That takes confidence. It takes security. It takes leaders who measure success by outcomes, not team size.

But it's the right goal.

Three years. Clear exit triggers. Planned dissolution.

To boldly improve what others accept as inevitable—and then to boldly step back when the work is done.

Next in series: "Soil Scientists, Not Gardeners: What DX Teams Actually Do"