One front door
New work enters through a single intake and two light decision gates — Gate 1 (is this worth doing?) and Gate 2 (is it ready to build?). Effort is earned at a gate; nothing is built on a whim.
Service management a small team can actually keep up.
Just enough process to take on the right work and ship it so it lasts — one front door for new work, and a “done” that means operable, not merely running.
Small teams can’t run ITIL — it assumes a department and a budget for process nobody has. But they still have to decide what’s worth building, design it so it can actually be run, and avoid the 2 a.m. page for something nobody wrote down. FitSD is the smallest amount of that discipline a handful of people can keep up.
Two things do most of the work
Section titled “Two things do most of the work”Readiness is the finish line
Nothing reaches live service until it is evidenced as ready — documented, recoverable (with a tested restore), secure, monitored and supportable. “Done” means operable, not just switched on.
How it stays light
Section titled “How it stays light”FitSD owns only a thin set of testable requirements. It ships a full, ready-to-use process for one capability — Solution Development, the front door — and for the other four it states the requirement and points at the standard or process a team already runs. That single choice is how it can require change, incident and security discipline without rebuilding those disciplines.
QuickstartOne project, five moves — a win this week, not a rollout plan.
The CharterWhat FitSD is: principles, the capability model, roles, conformance.
RequirementsThe testable “shall” statements — the spine an auditor would check.
Adoption & PositioningWho it's for, why they adopt it, and how it fits by team size.
It’s a personal project, deliberately not tied to any one organisation, and released under Creative Commons Attribution 4.0 (CC BY 4.0) so any team can adopt and adapt it.