Your SOW is the game plan, not the strategy
A statement of work (SOW) documents what will be delivered, but it doesn't create value on its own. Before you write one, you need to settle the outcome, the constraints, how success will be measured and who is accountable. Without that strategy behind it, even a well-written SOW leaves you unable to adapt when things change.
I love cricket, and it's a useful way to think about this. You can pick a strong XI, but without a plan for the conditions and the opposition, you're just hoping individuals perform.
- The suppliers are your team sheet.
- The SOW is your game plan.
- The outcome-based strategy is the captaincy: the preparation, the tactics and the ability to adjust when the pitch changes.
The mistake: confusing paperwork with planning
An SOW feels like progress. It has structure, deliverables and milestones. But it only records the intent. If the thinking hasn't been done first, you're locked into a plan that can't flex when someone underperforms or the conditions change.
Seven things to settle before the SOW
1. The business outcome. Not "I need someone who can code", but "I need this module delivered, tested and handed over in four weeks". That clarity is the difference between staffing and buying a service.
2. The conditions. Every project has constraints: the budget, compliance requirements such as IR35, and how experienced the supplier is. Some suppliers need more captaincy than others.
3. How you'll measure success. Completion time, quality, performance after delivery? If you don't define this first, the SOW can't reflect it.
4. Accountability. The supplier owns the outcome, payment is tied to delivery, and changes to scope are handled through an agreed process rather than informally.
5. Dependencies and assumptions. Projects rely on things outside the supplier's control: internal approvals, other systems, access to people. Write them down, or your plan will be blindsided when they shift.
6. A definition of done. Is the work done when it's written, or when it's tested and live? Don't assume everyone agrees. Spell it out.
7. Contingency. Rain can turn a 50-over match into 20. Plan for scope changes, delays and supplier issues with clear change clauses and a fallback.
What happens without a strategy
- Scope creep: no boundaries means overruns.
- Compliance risk: vague deliverables make IR35 harder to defend.
- Low accountability: suppliers get paid without delivering value.
- Contractors treated like employees: people drift into ongoing roles with no clear outcome.
- No way to adjust: when things change, there's no plan to change with them.
I regularly see SOWs that describe tasks and hours rather than measurable outcomes. If yours do, the underlying question is still the same one: do you need someone present, or something delivered?
What to do next
Before your next SOW, check you can answer:
- What's the outcome?
- What does success look like, and how will it be measured?
- Who owns delivery?
- What assumptions and dependencies are we relying on?
- Have we defined "done"?
- What happens if things go off-plan?
How I can help
I help organisations put the strategy in place before the SOW, set up practical SOW processes and keep them compliant.
A first conversation, on me
Tell me what's going on with your business. You'll come away with a clearer view of your options, whether or not we work together.









