CASE MANAGEMENT D.I.R.
A manager-led enablement kit that compressed new hire time-to-performance from 9 months to 3 — built with Confluence and Generative AI, without modifying a single official process.
Why D.I.R.?
In technical diving, D.I.R. — Doing It Right — is a philosophy that strips away unnecessary complexity and replaces it with highly deliberate, rigorously trained practice. A D.I.R. diver carries less than a recreational diver, but is more prepared for more. The setup is streamlined. The execution is disciplined. The training is intentional.
That philosophy directly informed this initiative. The goal was not to give new hires more material. It was to give them the right structure, at the right moment, so that doing the job correctly became the path of least resistance.
“The goal was not to give new hires more material. It was to give them the right structure, at the right moment.”
Three simultaneous learning curves.
Technical Product Knowledge
Deep, vertical-specific, and not abstractable. No shortcut to learning what the product actually does.
Support Operations Processes
Documented in Confluence, but written in policy language that doesn’t translate directly to floor execution.
Customer Service as a Craft
Tone, pacing, follow-through, managing ambiguity with live customers under pressure.
Associates do not begin learning defect documentation until they are formally preparing for promotion to Analyst. The skill arrived late — after months of handling cases where it would have been actively useful.
A three-part enablement kit.
Lifecycle-Structured Operational Guidance
Rather than restructuring existing official pages, a new Confluence page was created to serve a distinct purpose: bridging the gap between policy documentation and floor-level execution. The page is structured around the lifecycle of a Case — not by topic or role.
First Call Summary Email Form
Structured with Generative AI, the First Call Summary Email form gives Associates a consistent framework for documenting and communicating case details after initial customer contact. The deliberate inclusion of Steps to Reproduce, Actual Result, Expected Result, and Business Impact Details was not accidental — these fields mirror the core anatomy of a Defect submission.
Associates are building defect documentation literacy with every case they close — before they are ever formally trained on it.
Defect Draft Form
When an Associate identifies a potential defect during investigation, the Defect Draft Form is initiated and stored as a case note for Analyst review. This form does two things simultaneously: it accelerates the Associate-to-Analyst feedback loop, and it builds the Associate’s defect documentation muscle before formal training begins.
STORED AS CASE NOTE FOR ANALYST REVIEWWalk the lifecycle.
Step through each stage of a case. See the operational guidance surface as the case develops.
What this system carried forward.
Structure the workflow before you automate it.
The form fields that trained Associates to document cases correctly are the same fields that make a knowledge base machine-readable. The structure came first. Everything that followed — the distribution system, the performance insights tool, the dashboard — built on top of what the structure made legible.
Embed skill-building into daily practice, not into training events.
Muscle memory built during live casework is more durable than knowledge acquired in isolation. Associates who drafted defect records on every case they closed arrived at Analyst readiness already fluent. The formal training period reinforced what was familiar rather than introducing skills from zero.
The Case record is not the container — it is the surface.
The forms, the Confluence hub, the structured notes: these are early expressions of a larger idea about where operational intelligence should live and how it should be accessed. The Case record is where every meaningful interaction originates or lands. Making it the hub means making it intelligent.