How to Set Clear Expectations for Employees

Why unwritten expectations quietly wreck small teams

In a business with under ten people, the founder usually knows exactly what 'doing this job well' looks like — because they've done most of the jobs themselves at some point. The trouble is that this knowledge rarely gets written down or said out loud in full. It sits in the founder's head as an assumption, and the person doing the job is left to infer it from tone of voice, from being corrected after the fact, or from guesswork.

This produces a specific and avoidable kind of conflict: the founder feels let down because 'obviously' the standard wasn't met, and the employee feels blindsided because nobody ever told them what the standard was. Neither party is being unreasonable. The gap is structural — it's a missing document, not a missing effort or a missing character trait.

The fix is not a personality change on either side. It's treating expectation-setting as a specific task with its own output: a short written statement, agreed and revisited, rather than an ambient feeling the founder assumes everyone shares.

Non-negotiables versus preferences

One of the most useful distinctions you can make explicit is between things that must always happen — non-negotiables — and things you'd simply prefer, which are open to different approaches. Treating every preference as if it were a non-negotiable creates a rigid, exhausting workplace where people are afraid to use their own judgement. Treating every non-negotiable as a soft preference erodes the standards that actually protect the business, its customers and its finances.

A non-negotiable is something like: customer complaints are always acknowledged within one working day, expenses are always submitted with a receipt, safety procedures on site are always followed. A preference is something like: you like reports formatted a particular way, or you'd rather people used a particular tool for notes when several would do the job fine. Say out loud which is which — people will generally respect a clearly stated non-negotiable far more readily than one they suspect is really just your personal habit dressed up as a rule.

• Non-negotiables: safety, legal and compliance requirements, financial controls, core customer commitments
• Preferences: formatting, tool choice, working style details that don't affect the outcome
• When in doubt, ask yourself: would I actually escalate this if it were done differently? If no, it's a preference.

Writing the one-page expectations document

For each role, a single page is usually enough to cover what matters. It should describe what 'doing this job well' looks like in concrete terms, the non-negotiables that always apply, the expected standard for communication (response times, when to flag a problem, when to escalate), and how and when progress will be reviewed.

Write it in plain language, using real examples rather than abstractions. 'Respond to customer emails within four working hours' is usable; 'be responsive to customers' is not, because it leaves the actual standard open to interpretation and gives you nothing concrete to point back to if the standard isn't met.

1. What does doing this job well look like — described as outcomes, not just tasks
2. The non-negotiables that must always happen, regardless of workload or circumstance
3. The expected standard for communication and reliability
4. How and when progress will be reviewed, and against what measure
5. Where to go for help when something is genuinely blocking the work

If an expectation only exists in your head, it does not exist for the purposes of holding someone to it. Write it down before you can fairly expect it to be met.

Saying it out loud, not just handing over a document

A written document reduces ambiguity, but it doesn't replace the conversation. Talk the expectations through with the person directly, invite questions, and check they can restate the non-negotiables in their own words before you consider it landed. People rarely absorb a full page of written standards from a single read, especially in their first weeks.

This matters even more for expectations that carry real consequences — anything tied to safety, money, or a customer commitment. Confirm understanding explicitly rather than assuming a nod in a meeting means the standard has genuinely registered.

Revisiting expectations as the role changes

Roles in small businesses shift constantly — new tools get adopted, priorities move, the business grows into new areas. An expectations document written on someone's first day and never looked at again will drift out of date within months, and holding someone to a stale standard is both unfair and ineffective.

Build a habit of revisiting expectations at a regular one-to-one, not only when something has gone wrong. A short check — 'does this still reflect what we actually need from the role' — costs a few minutes and prevents a much larger conversation later, when a gap has been allowed to widen unaddressed.

When expectations aren't being met

Before assuming a performance issue when a standard isn't met, check the expectation was genuinely clear, communicated, and reasonable given the person's training and resources. A large share of what looks like underperformance is actually an expectations gap, and treating it as a character or effort problem too early damages trust unnecessarily.

If the expectation was clearly communicated, reasonable, and still isn't being met after a fair period, that becomes a genuine performance conversation. At that point, follow a fair, documented process, and use Acas guidance as your reference for what a reasonable process looks like — this guide is not a substitute for that.

Common mistakes with expectations in small teams

A handful of patterns come up repeatedly and are worth checking yourself against.

• Assuming an expectation is obvious because it's obvious to you, the founder
• Setting an expectation once at induction and never revisiting it
• Treating every personal preference as a hard rule, which breeds resentment
• Correcting someone for missing an expectation that was never actually stated
• Holding people to a standard that changed without telling them