Most teams already have docs. The missing piece is often not information, but recall. New teammates know where the runbook lives, but they still hesitate when a log, branch, container, service, or file permission needs a quick first move.
Drills fit between docs and incidents.
A good drill is short, specific, and tied to a workflow the team expects people to use. It does not replace a runbook. It makes the first few safe moves more familiar before the runbook is needed under pressure.
- Onboarding: practice the commands used in the first month.
- Platform practice: reinforce shared Git, shell, Docker, and Linux workflows.
- Incident readiness: rehearse inspect-first habits before a broken environment is loud.
The product should earn team features.
Drill Atlas is not launching a team dashboard on faith. The current website collects demand signals: topic, team size, use case, and the workflows people should remember without looking up.
The right team product starts with real workflow demand, not a generic LMS feature list.
What to ask for.
Good team drill requests are concrete. "Git recovery for junior developers" is better than "Git training." "Docker logs, exec, inspect, and port conflicts" is better than "containers." The narrower the workflow, the more useful the drill pack can become.