The Rules of the Game

Every business already has rules. The question is only whether they are written down or learned the hard way, by being told off for something nobody had mentioned.

Unwritten rules are expensive in a specific and measurable way. They make the owner the permission department. They produce inconsistency, because the answer depends on who asks and what kind of day it is. And they punish good people for guessing wrong, which teaches everyone that the safest move is to check first, always, about everything.

The Rules of the Game is a single page: what a person may decide alone, what they must check first, and what never happens under any circumstances. Three zones. Written down. Applied to you as well as to them.

What this is, and what it is not

It is not a staff handbook. Handbooks are written for tribunals and read by nobody. It is not a set of values on the wall either. Integrity and excellence do not tell anyone whether they can authorise a £400 refund on a Friday afternoon.

It is a short, specific statement of decision rights and non-negotiables. Money limits with numbers in them. Who can promise what to a client. What we do when something goes wrong. What ends a conversation regardless of who is asking, including the owner.

The green zone is the important one, and it is the one that gets left out. Most businesses have a long list of things you must not do and no list at all of the things you are free to decide. That is why people check everything.

Why it matters to an owner

Because most bottlenecks in a small business are permission bottlenecks, not capacity bottlenecks. The work is not waiting on skill or hours. It is waiting on an answer from one person who is in a meeting.

Because inconsistency destroys authority faster than strictness ever does. If the same request gets three different answers depending on the week, people stop making decisions altogether and start managing you instead of the work.

And because you cannot take a proper holiday without this. A business where nobody knows their limits is a business that phones you on the beach, and it is worth less to a buyer for exactly the same reason.

What belongs on the page

Six categories cover almost everything in a small business. One or two lines each is enough.

• Money. What can be spent, by whom, up to what figure, and what happens above it. Numbers, not adjectives.
• Client promises. Who can commit to a date, a price or a piece of scope, and in what form. This is where most of the damage happens, and it is almost always caused by someone being helpful.
• People. Who can hire, who can agree hours or leave, who can have the conversation when something goes wrong.
• Quality. What gets checked before it leaves, and by whom. If nothing is checked, say so deliberately rather than by accident.
• Information. What is confidential, what gets recorded in the system, what never goes in an email.
• The hard nos. The short list of things that end the conversation regardless of who is asking or how good the reason sounds.

A worked example

Illustrative arithmetic. Take a fourteen-person business where the owner signs off effectively everything. Log the permission questions for a week and the count comes to 22.

The owner's direct cost is modest: 22 questions at around six minutes each is a little over two hours. That is not the expensive part. The expensive part is on the other side. If each question holds up a piece of work for an average of four hours while it waits for an answer, that is roughly 88 hours a week of stalled work sitting in the business, and every hour of it is invisible on any report you produce.

Now write the rules. Spend under £250, no approval needed. Between £250 and £2,000, the team leader. Above that, the owner. Refunds up to one month's fee at the account handler's discretion. Any discount above 5 per cent comes to the owner. Nothing is promised to a client unless it is in writing. And one hard rule with no exceptions: we do not commit to a delivery date the delivery team has not agreed.

Run the same log a month later and the 22 questions typically fall to a handful, because most of what was being asked was money under £250 and permission to do the obvious. The owner's two hours come back. The 88 hours of waiting largely disappear. Nothing was hired, nothing was bought, and the only thing that changed was that somebody wrote down what people were allowed to do.

How to apply it this week

1. Log every permission question for five days. Who asked, what about, how long it waited. Do not fix anything yet. The log is the argument.
2. Sort the log into three piles. They could have decided this. They should check. This must never happen. Most owners are surprised by the size of the first pile.
3. Put numbers on the money rules. Vague authority is no authority. Two hundred and fifty pounds is a rule. Reasonable amounts is not.
4. Write one page and hand it out. One page. If it runs to four, you are writing a handbook and it will not be read.
5. Decide what happens when a rule is broken. A rule with no consequence is a suggestion, and everyone works out which is which within about a fortnight.
6. Review it quarterly and widen the top band. The goal is that the green zone grows every quarter. If it never grows, you are not delegating, you are documenting your own bottleneck.

The mistake most owners make

Writing rules only after somebody gets something wrong. Rules created as punishment are experienced as punishment, they arrive attached to a bad mood, and they teach the team that the safest thing is to do nothing new. Write them when nothing has gone wrong. That is what makes them a structure rather than a telling-off.

The second mistake is exempting yourself. The owner who sets a spending limit and then buys something on a whim, or who insists on written commitments and then promises a client a date in a phone call, has not weakened one rule. They have cancelled the whole page. Everybody notices.

The third is making everything amber. If almost every decision needs checking, you have written a description of your bottleneck and called it governance. The test of a good page is how much freedom it gives, not how much control it keeps.

The questions to sit with

• Out of 10, how clearly could each of your people state what they are allowed to decide without asking?
• How many questions reached you last week that somebody else could have answered?
• Which of your rules exist only in your head, and how would anyone else know them?
• Which rule do you break yourself, and what is that teaching the team?

This is foundational to Team Performance. Accountability is not a personality trait you hire for. It is what happens when people know exactly what is theirs to decide and exactly where the edges are.