In a small business, what looks like a performance problem is usually a clarity problem. The fix is that every person can answer three questions without hesitating: what do I own, what does good look like, and how will I know if I am doing it well? Where any of those draws a blank, you are looking at a leadership gap rather than a talent gap, and it is repairable in weeks with a page of writing per role.
The second half is standards. High-performing teams have high standards that are consistently held — named clearly, recognised when met, and addressed promptly when not. A manager who avoids the difficult conversation in the name of being supportive is not being supportive; they are creating ambiguity, which is what low performance thrives in. Below is how to build both, starting with what you can write down this week.
Are you looking at a performance problem or a clarity problem?
Test it before you conclude anything. Ask three people separately what their main responsibility is and what good looks like in it. If the answers differ from each other, or from yours, the problem is not effort. People underperform in small businesses far more often because they lack a clear picture of what is expected and how to prioritise than because they are lazy or unable.
The test is uncomfortable and it is worth doing properly. Most owners discover at least one role where the answers do not match, and it is usually the role that has been quietly frustrating them for a year.
What are the three questions every person should be able to answer?
- What do I own? Not a job title — the outcomes that are theirs, and the decisions they can make without asking.
- What does good look like? Written in terms someone could check: turnaround times, quality standards, what a finished piece of work includes.
- How will I know? One or two measures they can see for themselves, plus a regular conversation where the two of you look at the same picture.
One page per role covers all three. It is not a job description for the file; it is the thing you both refer to when something is not working, which is exactly when memory becomes unreliable.
What does an unclear role actually cost?
An invented illustration of the shape — not a client, and not a claimed result. Two people both believe the other is checking work before it goes out, so nothing is properly checked. Errors reach clients at a rate of roughly two a month, each taking about four hours to correct across two people at a loaded £30 an hour: around £240 a month in rework, or £2,880 a year, before any goodwill discount. Add one lost client a year at an average value of £7,500 and the real figure is over £10,000. The fix is a written standard naming who checks what and when, plus a line in the delivery checklist. That is an afternoon's work, and it is why clarity is a commercial exercise rather than an administrative one.
How do you write down what good looks like?
Take one role and one process, and write the standard as observable behaviour rather than intention. Not "responsive to clients" but "enquiries answered within four working hours, quotes out within two working days". Not "good attention to detail" but the checklist of what a finished job includes.
Do it with the person, not at them. They know more about the work than you do at this point, and a standard they helped write is one they will hold. Then use it: refer to the page in your one-to-ones, and update it when the work genuinely changes. A standard nobody has looked at in a year is decoration.
Standards or cheerleading — which does your team get?
Holding a standard means three things done consistently: naming what good looks like in advance, recognising it out loud when it happens, and addressing it promptly and specifically when it does not. Skip the third and the first two lose their meaning, because the standard becomes optional for whoever is willing to test it.
The hardest part is timing. A standard addressed within a week is a small conversation; the same issue raised six months later is a serious one, and you have to explain the silence as well. Our guide on difficult conversations covers the structure for having it well, and this is the ground leadership coaching works on most.
What about the person who is good at the job but difficult to work with?
This is the hardest version of the problem, and it is common. Someone delivers — the work is right, the clients like them, the numbers are fine — and they are also short with colleagues, dismissive in meetings, or the reason two people have quietly asked to be moved off their jobs. Because the output is good, the behaviour gets tolerated for years.
The cost of tolerating it is not paid by you, which is why it is easy to underestimate. It is paid by everyone who works around them, and it shows up as people who stop raising problems, stop volunteering for that person's projects, and eventually leave without ever giving this as the reason. In a team of six, one person the others manage around removes a large share of the advantage a small team has in the first place.
The way through it is to treat behaviour as part of the standard rather than as a personality question. Write it into the page for the role in the same observable terms you used for the work: how disagreements are raised, what is expected in a meeting, how handovers happen. Then have the conversation about that standard, not about who they are. "You are difficult" is unanswerable and puts anyone on the defensive. "In Tuesday's meeting you cut across Aisha twice and she stopped contributing — I need that to be different" is specific, and a specific request can be met.
Two things make it work. Separate the two judgements out loud, so they hear plainly that the work is valued and the behaviour has to change, rather than inferring that everything is now in question. And be consistent afterwards — a standard applied to one strong performer and not to another is the fastest way to lose the rest of the team's trust. If nothing changes after a fair, clearly stated run at it, you are into a formal process, and that is the point to take proper HR advice rather than coaching guidance.
What do small teams do better than large ones?
Small teams have real structural advantages: communication is direct, contribution is visible, course corrections take days rather than quarters, and there is none of the process that slows a large organisation down. High-performing small teams use those advantages deliberately — short decision paths, information shared openly, and a genuine connection between what somebody does and what happens to the business.
The corresponding risk is that everything depends on the owner's habits. Your standards, your energy and your willingness to have the right conversations shape the team more directly than any process or incentive scheme could. That is the challenge and the leverage at the same time. The Team Development model is a useful map of the stages a team moves through, and what great leadership looks like in a small business covers the day-to-day version.
What should you do this week?
- Ask three people what they own and what good looks like. Compare the answers with yours.
- Write one page for the role where the gap is widest, with the person, not for them.
- Name one standard that has slipped and address it within the week, specifically and calmly.
- Give one piece of specific recognition — what they did, and why it mattered.
- Put a fortnightly one-to-one in the diary for each direct report and protect it.
- Pick one measure per person that they can see without asking you for it.
- Check what you are modelling: turning up late, cancelling one-to-ones or letting your own standards slide teaches faster than anything you say.
None of this needs an HR system or a new process. It needs a page per role, a fortnightly conversation and the willingness to say something in week one rather than month six. If the team meeting is where the ambiguity shows up, our guide on running a team meeting that works is the practical next step.
Get the next one in your inbox
One practical, plain-English guide for business owners each week. No spam, unsubscribe any time.
Frequently asked questions
How do I know whether it is a clarity problem or the wrong person?
Write the clarity down first, then give it a fair run. One page for the role, agreed together, with what they own, what good looks like in observable terms and how progress will be measured. Then a fortnightly conversation against that page for two or three months. If performance moves, it was clarity, which is the more common answer by some distance. If nothing changes despite the person understanding exactly what is expected and having the support to do it, you have a different problem and you now have a fair, documented basis for addressing it. Take proper HR advice before any formal process, since coaching is not a substitute for that.
What if the team is used to lower standards?
Change it openly rather than by stealth. Say what is changing, why, and what it means in practice, then apply it consistently from that point rather than retrospectively punishing what happened under the old rules. Expect a testing period of a few weeks where somebody quietly checks whether you mean it, because that is normal and it is where most attempts fail. Hold the standard calmly and specifically the first time it slips. One prompt, unremarkable conversation does more to reset a standard than an announcement or a policy document, and it is noticed by everybody, not just the person you had it with.
Do small teams need formal one-to-ones?
Yes, and the smaller the team the more useful they are, because informal contact all day creates an illusion of communication that rarely covers the important things. Thirty minutes a fortnight, in the diary, with a simple shape: how is the work going against the standard, what is in the way, what do you need from me, and one thing about the longer term. Protect the slot as you would a client meeting. Cancelling it twice teaches people that their development is negotiable, which is a message you cannot easily take back later.
How much does pay affect performance in a small team?
Pay has to be fair and defensible, and if it is clearly out of line with the market you will lose good people regardless of anything else you do. Beyond that point, pay is a poor day-to-day motivator and a reliable source of resentment when it is unclear how it is decided. What tends to move performance more is knowing what you own, being told plainly how you are doing, having the tools to do the job well, and seeing that standards apply to everybody including the owner. Get the clarity right before you assume the answer is a rise.
What if the person whose standards have slipped is a long-serving, loyal employee?
Loyalty earns a careful, private, well-prepared conversation. It does not earn an exemption, and treating it as one is unfair to everybody who is being held to the standard. Two things usually make the conversation easier than owners expect. First, name the loyalty explicitly and mean it, then be equally plain about the specific thing that has to change — people can hear both when they are said in the same breath. Second, ask before concluding: long-serving people often slip because the role grew around them without ever being redefined, or because something outside work is going on. You may find the answer is a rewritten page for the role rather than a performance conversation at all.