Strategy sprint vs long engagement: how to choose

The question comes up often in scoping calls: should we do a short sprint or a longer engagement? The answer depends on the nature of the problem, not the size of the budget. Some problems are genuinely complex and need sustained attention. Others just need a clear week of focused thinking. Knowing the difference saves time and money.

What a sprint is good for ¶

A sprint works when the problem is specific and the decision is imminent. You need to choose between two directions. You need a clear brief before a board meeting. You need to know whether a new market is worth pursuing before you commit resources. These are sprint problems.

The constraint of five days is a feature, not a compromise. It forces the question to be scoped tightly enough that a real answer is possible. If the question cannot be answered in five days, it is usually because the question is not specific enough yet.

When a longer engagement makes more sense ¶

A longer engagement is appropriate when the problem requires sustained input from multiple stakeholders, when the organisation needs time to absorb and respond to findings, or when the work involves building something rather than deciding something. A positioning review that requires multiple rounds of stakeholder input, for example, cannot be compressed into five days without losing quality.

The honest test is this: if you had a clear answer by Friday, could you act on it? If yes, a sprint is probably right. If the answer is 'we would need a few weeks to discuss it internally before we could do anything', a longer engagement might suit the pace of your organisation better.

The hybrid option ¶

Some clients start with a sprint to get a clear direction, then move to a retainer for ongoing advisory support as they implement. That sequence works well because the sprint produces a concrete output that the retainer can build on. It also means the retainer starts with a shared understanding of the problem rather than spending the first month establishing context.

If you are genuinely unsure, the scoping call is the right place to work it out. Bring the problem and we will tell you honestly which format fits.