What a 4-Week Sprint Actually Looks Like

“We'll start with a four-week sprint” is the first thing most engagements here include, and it's fair to wonder what actually happens in those four weeks. The short version: a sprint exists to produce a result and a decision, not a report. Here's what the inside of one looks like.

The whole reason to box it at four weeks is that open-ended engagements drift — the same failure mode as an AI pilot with no end date. A deadline forces focus onto the one thing that matters and protects you from paying for motion that isn't progress.

Week 1 — Find the real problem, not the stated one

The problem an owner describes and the problem actually costing them money are often two different things. Week one is diagnosis: sit inside the workflows, watch where time and money leak, and write down what “now” costs in hours, dollars, and turnaround. By the end of the week there's a single, specific target — the number we're trying to move — and a baseline to measure it against.

Week 2 — Design the smallest thing that moves it

With the target named, week two designs the narrowest intervention that could move it. Not a transformation — the one change with the best return for the least disruption. This is also where the build-vs-buy-vs-skip call gets made: rent what a vendor already does well, build only what's genuinely specific to how the business works, skip what isn't worth it yet.

Week 3 — Build it and put it in real hands

Week three is execution: stand the thing up and get it in front of the people who'll actually use it, in the real workflow, not a demo. Getting a system working before the team is fully leaning on it is its own discipline. A couple of years ago, a national food-services operator stood up the technology and operational plans for three new business units before the teams ever arrived on-site — and the launches its regional managers later called critical worked precisely because the systems were ready and tested before anyone depended on them. A sprint mirrors that: by week three the change is live in real hands, with the rough edges found while the stakes are still low.

Week 4 — Measure, decide, hand off

Week four closes the loop. Put the new number next to the week-one baseline and answer the only question that matters: did it move? Then make the call — keep it, expand it, or kill it — and hand off something the team can run without you: the SOP, the training, the owner's manual for the change. A sprint that ends with a dependency on the consultant failed, even if the result was good.

Why four weeks, and not twelve

Four weeks is long enough to produce a real, measured result and short enough that nobody can hide in it. It caps your risk: a focused month with a clear target beats a quarter-long engagement that bills steadily while the goalposts wander. At the end you have a decision and a thing that works — not a slide deck and an invitation to renew.