Agree on definitions up front: include cleaning, warm-up, first-article inspection, and any rework necessary to reach rate. Exclude unrelated breakdowns but log them separately. This clarity stops gaming and enables apples-to-apples comparisons across shifts and lines. When everyone trusts the number, energy shifts from arguing to improving, and cross-team collaboration becomes natural rather than forced.
Add two simple signals: readiness score before shutdown and recovery time back to planned cycle after restart. Readiness reveals whether externals were truly complete; recovery shows how quickly stability returns. Together they expose root causes faster than a single duration figure, pointing to training, tooling, materials, or programming issues that playbooks and coaching can immediately address.
Protect gains with layered audits, control charts on setup time, and visible countermeasures when drift appears. Tie coaching to metrics, not memory. Refresh visuals when revisions change. Celebrate stories in standups, pair mentors with new hires, and keep experimentation alive so playbooks evolve. Sustained speed feels quiet, predictable, and respectful, never frantic or risky for quality.