Mike Mullaney All articles
Client Delivery

A Brief You Can Read Standing Up: How One Page Beats a Twenty-Page SOW

Mike Mullaney
A Brief You Can Read Standing Up: How One Page Beats a Twenty-Page SOW

Photo: Yazan.Masannat, CC0, via Wikimedia Commons

Most statements of work are written for the wrong audience. They are written to protect the supplier if something goes wrong, to satisfy procurement, or to tick a box in a shared drive. They are rarely written to help a human being deliver the work. That is why I have become a stubborn convert to the one-page brief.

I still use a contract. I still use a statement of work for the legal and commercial bits. But before any of that gets drafted, I want a single page that answers four questions: what problem are we solving, what does done look like, what is out of bounds, and who gets to decide? If those four cannot fit on one page, the project is probably not ready to start.

Why the long SOW creates false comfort

A twenty-page SOW feels rigorous. It has schedules, assumptions, dependencies, acceptance criteria, and enough defined terms to keep a lawyer happy. But length is not the same as clarity. In most UK engagements I see — SMEs, agencies, professional services firms, internal change teams — the long document gets skimmed once, filed, and then ignored when a stakeholder asks for 'just one more thing'.

Scope creep rarely starts with a dramatic change request. It starts with a small, reasonable-sounding sentence: 'While you're in there, could you also...' A long SOW does not stop that sentence. A clear one-page brief does, because everyone can see the boundary without opening a PDF.

The four boxes I insist on

1. The problem, in plain English

Not the solution. Not the deliverable. The problem. Write it as if you were explaining it to a smart friend over a coffee. For example: 'Our sales team is spending too long manually building quotes, and the error rate is embarrassing us with larger clients.' That is a problem. 'Build a CPQ tool' is a solution pretending to be a brief.

2. The outcome, with a finish line

What will be different when this is done? Be specific enough that a reasonable person could disagree. 'Better reporting' is not an outcome. 'The finance team can close the month in five working days instead of nine, using one source of truth' is an outcome. It gives you a finish line and a way to test whether the project has actually delivered.

3. The boundaries, named out loud

This is where scope creep gets stopped. List what is in, what is out, and what would need a new conversation. Include the obvious things people assume are included. If training is not included, say so. If data migration is limited to one export, say so. If you are not rewriting the client's internal process, say so. Boundaries are not unfriendly. They are the price of a clean project.

4. The one decision-maker

Not the steering group. Not the person who 'needs to run it past a few people'. One named human who can say yes, no, or change the priority. If that person does not exist, the project has a governance problem, and no amount of documentation will fix it. I ask for this before I write a proposal.

A brief that saved a project from derailing

Earlier this year I worked with a mid-sized training provider in the Midlands. They wanted a new client portal. The original statement of work was twenty-two pages and already had two change requests before kick-off. The project was drifting, and everyone was busy being precise about the wrong things.

We stopped and wrote a one-page brief. The problem was that learners were ringing the office to book courses because the existing form was confusing. The outcome was that 80% of bookings would be self-service within three months. The boundaries were clear: no new payment provider, no mobile app, no integration with the finance system in phase one. The decision-maker was the operations director, not the marketing manager, not the head of sales, and not the external web agency.

Two weeks later, a senior stakeholder asked for a reporting dashboard 'while we are building the portal'. It was a perfectly sensible idea. It was also outside the brief. Instead of a tense email chain, we pointed at one page: dashboard is not in phase one; it can be scoped as phase two. The conversation took four minutes. The project shipped on time. The dashboard became the first item in the next phase, with its own brief.

That is the real value. The one-pager does not just stop bad ideas. It gives good ideas somewhere to go.

The template I use

I keep it deliberately plain. A single page, four headings, and a version date. Something like this:

I write it live with the client in a 30-minute call, share the screen, and send it the same day. If they want to add something, we add it to the brief or we put it on the phase-two list. The brief is not a legal document. The contract still governs liability and payment. But the brief governs the work.

Make the brief the first deliverable

If you are a consultant, freelancer, or small business owner, try making the one-page brief the first thing you deliver. Not the proposal. Not the deck. The brief. It forces the client to be clear, it shows you are serious about delivery, and it gives you a polite, professional way to say 'that is a different project' when the inevitable extra request arrives.

Scope creep is not usually caused by bad clients. It is caused by fuzzy agreements. A single page will not solve every project problem, but it will solve the most common one: nobody is quite sure what we agreed to. And in my experience, that is worth more than twenty pages of well-formatted ambiguity.

All Articles

Related Articles

Closing Time: The Twelve-Point Handover Check I Run Before Any Project Ends

Closing Time: The Twelve-Point Handover Check I Run Before Any Project Ends

The Enquiries I Don't Chase — and the Margin I Keep

The Enquiries I Don't Chase — and the Margin I Keep

Nobody Claps for Fixed Invoicing — and That's Exactly the Problem

Nobody Claps for Fixed Invoicing — and That's Exactly the Problem