02
The Smooth Sprint
Fix or ship one defined operational priority.
The situation it addresses
You have a specific operational problem. Maybe you know exactly what it is and have been meaning to fix it for months. Maybe you just completed an Operating Diagnostic and have a clear priority. The problem is real, it has a cost, and you want it gone.
The Smooth Sprint is a scoped, focused engagement built around one defined result. Not a study of the problem. A fix.
Example applications
These are examples, not the full set of possibilities.
- Redesign a broken lead-to-onboarding flow so customers stop falling through the gap.
- Establish one source of truth for delivery status so five people stop maintaining five spreadsheets.
- Automate a repetitive administrative workflow with a named owner and fallback path.
- Design and implement management reporting that arrives before the decision window closes.
- Introduce a workable weekly operating rhythm that replaces status meetings with actual decisions.
- Recover and deliver a cross-functional project that has been stuck for too long.
- Prototype and operationalise a safe AI-assisted workflow with clear ownership and quality checks.
Who it is not for
Businesses that do not yet agree on what the priority is. If different people have different theories about the main problem, start with the Operating Diagnostic.
How it unfolds
Every sprint starts with an explicit definition: the problem, the owner, the success measure, and the handover plan. Then:
- Understand the current state: watch the work, map the flow, find the real constraint.
- Redesign across people, process and technology — not just one layer.
- Implement with the team, not alongside them.
- Address adoption barriers as they emerge, not after the engagement ends.
- Hand over with documentation and a named internal owner who is ready to run it.
What the result looks like
Actual outcomes depend on the problem and the business. These are indicative directions.
- A working system with clear ownership and a team that understands it.
- A measurable change in operating behaviour — not just a delivered output.
- Documentation that the internal owner can use to train successors.
- A defined escalation path for when things go wrong.
Scope boundary
Sprint scope is defined and agreed before work starts. A sprint is not a free-range engagement. If the scope expands materially mid-engagement, we treat it as a new sprint rather than adding work to an in-flight one. This protects both the quality of the original delivery and the coherence of the business change.