Illustrative sprints.
Examples of the shape of the work. Not case studies. Not client names.
Illustrative sprint
Small fleet / Part 135 — the week nobody can see
Problem: utilization, duty/rest, and the weekly ops brief lived in the chief pilots head.
Measure: aircraft days available vs flown, holds, unbilled time, duty/rest collisions.
Handoff: one-page weekly brief, constraint model with two or three courses of action, cadence the assistant chief can run.
Window: 3-week sprint.
Illustrative sprint
Flight school — the schedule that cannot tell the truth
Problem: aircraft and instructors looked busy. Utilization was not.
Measure: scheduled vs flown, pairing, repeat lesson failures, unbilled time.
Handoff: utilization brief, next-block training view, billing/ops checklist the front desk can keep.
Window: 2–4 week sprint.
Illustrative sprint
Flight department — three rooms, one week
Problem: pilots, maintenance, and scheduling each had a version of the week.
Measure: request → crew → aircraft → squawk → return-to-service. Time lost in the handoffs.
Handoff: single weekly brief format, handoff rule between the three desks, punch list of the five reports that matter.
Window: 3-week sprint.
Illustrative sprint
Civilian shop — the process that retires when one person does
Problem: lead-to-delivery lived in one inbox. Reporting was a rebuild every month.
Measure: real path vs stated path, where work waits, which numbers the brief actually requires.
Handoff: written process with an owner, cleaned reporting pack, light tooling only if the brief still needs it.
Window: 2–4 week sprint.