Case study

When the only expert is leaving.

SMART tag is a K-12 student transportation platform: software that school districts rely on every school day. The Director of Engineering was departing, and years of institutional knowledge lived in that one person: infrastructure, access, vendor history, the reasons behind the decisions. The team was mid-flight on a major platform migration.

The call

Fixing was the wrong first move.

The instinct in that moment is to start fixing things. But the window to capture what lives in one person's head closes on a date you don't control. Everything else can wait a week. That can't. The first job is making sure the fixing can continue after the person who knows everything is gone: diagnosis before prescription.

What I did

Diagnosis first, then de-risk.

Access and infrastructure audit

Mapped who holds what, and what breaks when they leave.

Credential consolidation

Moved credentials off individuals and into managed, recoverable storage.

Break-glass access model

Built recovery paths so no single departure takes the org's access with it.

Migration risk assessment

Assessed the mid-flight platform migration for risk under a thinned team.

Team capability

Stood up a recruiting pipeline for AI-capable engineers and trained the developers on AI tooling.

Where it landed

Continuity, on purpose.

Access is recoverable: nothing critical lives only with one person. The migration has a scoped risk picture instead of an open question. A compliance initiative became a scoped, sponsored workstream with an owner, not a someday-item. Hiring is running. The remediation plan is written, prioritized, and handed off.

The point

The deliverable is continuity.

When the only person who knows how it works is leaving, the deliverable is not code. It is continuity: the team's ability to keep operating, keep deciding, and keep fixing after the knowledge walks out the door.