Project Management and Scope
Small businesses run projects constantly and almost never call them projects. The new website. The move to different premises. The software change. The recruitment drive. Each one has a start, an end and a cost, and each one is run out of somebody's head between other jobs.
Then eleven months later the website is still not live, and nobody can say exactly why, because there was never a written statement of what it was supposed to be.
What the model is
Three constraints govern any piece of work. Scope is what gets delivered. Time is when it lands. Cost is what it consumes, in money and in your people's hours. They are connected: change one and at least one other has to move.
The rule is that you may fix two. The third has to flex. Fix all three and something still gives, and the thing that gives is quality, whether or not anybody agreed to that.
Why it matters to an owner
Two reasons, and they cost different money. Internally, undefined projects consume your best people in dribs and drabs. Nobody costed the website, so nobody noticed it absorbed sixty hours of the operations manager's year, which is a fortnight she did not spend on the thing you actually promoted her to do.
There is a compounding effect too. Because the internal project has no end date, it never formally finishes, so it stays on the list. Owners then look at a list of nine live initiatives, feel behind on all of them, and start none properly. Six half-run projects produce less than two finished ones, and they cost considerably more in attention.
Externally, scope is where margin dies. In client work the scope creeps by one small favour at a time, each one too trivial to raise, and it is absorbed by the team working later. The profit leaves the job quietly, and because nobody logged it, the next quote is built on the same wrong assumptions.
Deciding which corner flexes, before you need to
The useful discipline is choosing the flexible corner at the start, in daylight, rather than in week nine when everyone is tired and blaming each other.
If the date is genuinely immovable, because a lease ends or a season starts, then scope is your flexible corner and you should be planning what launches later, not pretending everything lands at once. If the specification is genuinely fixed, because it is a regulatory requirement or a customer's non-negotiable, then the date or the budget moves and somebody senior needs to say so out loud in week one.
Most of the time in a small business, cost is the corner nobody will move, because there is no budget line for it. Say that plainly. It means either the date or the scope must give, and the honest conversation is which of the two you would rather explain.
A worked example
Illustrative, but recognisable to anyone who sells time. A design agency quotes a website build at £12,000: 100 hours at £120, with a delivered cost of £60 an hour. Planned profit £6,000, a 50 per cent margin.
Then the project runs. The client asks for a booking form, described in the email as a small addition, which takes 14 hours. Two extra rounds of revisions beyond the two quoted take 9 hours. Content arrives three weeks late, and the restart costs 6 hours of re-briefing and re-familiarisation because the developer had moved on to something else.
129 hours against 100. Revenue unchanged at £12,000, so the effective rate is £93 an hour rather than £120. Delivered cost is £7,740, and profit falls from £6,000 to £4,260. Nearly 30 per cent of the profit on that job has gone, and the margin has dropped from 50 per cent to 35.
Not one of those three changes was unreasonable. Every one of them was a legitimate variation that should have taken sixty seconds to raise. Nobody raised any of them, because each felt too small to make a fuss about, and because raising the first one is the awkward part.
The mistake most owners make
They confuse scope with a to-do list, and they write only what is included. The half of the document that saves you is the exclusions. What is not in this price. How many rounds of revision. What we assume you will provide, and by when. What happens to the timeline if that is late.
The second mistake is treating variations as a relationship risk. Owners stay quiet because they do not want to seem money-grabbing. What actually damages the relationship is a project that runs late and over budget while the client is told nothing, then a difficult conversation at the end about an invoice they were not expecting. Raising a variation at the time is a sign of control. Raising it at the end is a sign that you lost control weeks ago.
And the third: fixing all three constraints and hoping. The date is immovable, the specification is fixed, and nobody may spend more. Everyone nods. Quality then absorbs the difference, and it is usually the testing, the training or the handover that gets sacrificed, which are exactly the parts you will pay for again later.
How to apply it this week
- Write one page for your biggest live project. What it delivers, by when, at what cost, and who owns it. If nobody can write that page today, that is the finding.
- Write the exclusions list. Five lines of what is not included. Every line is a conversation you will not have to have from a weak position later.
- Name one owner, not a committee. One person is accountable for delivery. Everybody else contributes. Shared ownership is how projects die slowly.
- Put a number on internal hours. Estimate the hours before you start and log them as they go. Internal projects feel free, and they are the most expensive thing in the building.
- Agree the variation rule up front, and use it the first time. Anything outside scope gets a note, a price and a yes or no before the work starts. The first small variation sets the precedent for the whole job.
- Review the three constraints weekly, for fifteen minutes. Which corner moved this week, and what did we consciously let move to absorb it? That question takes a minute and prevents most overruns.
The questions to sit with
- Out of 10, how clearly could you state what your biggest current project delivers and what it will have cost when it lands?
- Which project has been almost finished for the longest, and what would happen if you formally killed it this week?
- On your last three client jobs, how many hours went in beyond what was quoted, and who absorbed them?
- When you last fixed scope, time and cost all at once, what actually gave way instead?
This belongs to the Systems & Scale work. A business that cannot land a project on a date is not short of talent. It is short of a written agreement, internally as much as with customers, about which of the three corners is allowed to move.
