Managing People
Most small-business owners become managers without ever being managed well. This hub covers the practical mechanics: expectations people can meet, conversations that happen on a schedule rather than in a crisis, and a fair, careful approach to problems.
Reviewed by a qualified professional
James Whitfield — FCCA, Chartered Certified Accountant — 18 years advising UK SMEs on employment costs, payroll and business finance. Reviewed 5 August 2026.
Last updated 2 August 2026
Where are you stuck?
Overview
Why most founders manage badly by default, not by nature
Very few small-business owners have ever been well managed themselves, which means the habits they bring to managing others are improvised rather than learned. That is not a character flaw; it is a gap that can be closed with a handful of concrete mechanics.
The mechanics that matter most are unglamorous: clear expectations, a predictable rhythm of conversation, specific feedback, and a fair process when something goes wrong. None of this requires a management qualification, but it does require doing it on purpose rather than reactively.
Founders who improve fastest tend to treat management as a set of repeatable habits rather than a personality trait to develop. You do not need to become a naturally confident manager; you need a small number of reliable routines.
The order to work through it
Start with expectations, because almost every other management problem — feedback, underperformance, conflict — traces back to expectations that were never written down or agreed. If a role's standards live only in your head, disappointment is inevitable.
Next, establish one-to-ones as a fixed, short, predictable rhythm, separate from status updates or crisis conversations. This is the container that makes feedback and early conversations about problems possible without them feeling like an event.
Only once that rhythm exists should you build out a formal approach to underperformance and conflict. Without expectations and regular conversation already in place, a formal process arrives as a shock rather than a natural next step.
Common failure modes
In Kayley's experience, the most common failure is avoiding a difficult conversation until it becomes unavoidable, at which point it is bigger, more emotional and harder to resolve fairly. Small, early, calm conversations are almost always kinder than delayed, large ones.
A second failure is treating feedback as an occasional event rather than a habit — saving everything for an annual review that arrives too late to change behaviour and feels like an ambush.
A third is skipping fair process when performance is a genuine concern: no written record of what was expected, what happened and what support was offered, which leaves both the employee and the founder exposed if the situation escalates.
What to write down
For each role, write what good looks like in plain language, and share it directly rather than assuming it is obvious. Keep a simple, repeatable one-to-one agenda: their topics, blockers, progress, feedback both ways, agreed actions.
When a performance concern arises, keep a written record of the conversation: what was discussed, what was agreed, and by when. This protects everyone and creates the evidence trail that a fair process requires.
For remote or hybrid teams, write down what visibility actually looks like — which artefacts of work (documents, updates, output) replace physical presence — rather than relying on instinct about who seems busy.
What "done" looks like and where to get advice
You are managing reasonably well when one-to-ones happen on schedule regardless of how busy the week is, when feedback is specific and timely rather than saved up, and when nobody is surprised by a formal conversation because informal ones happened first.
For anything approaching disciplinary action, redundancy or dismissal, follow the Acas Code of Practice and take advice from a qualified employment adviser before taking a formal step — this hub explains the shape of good process, not the legal detail of your specific situation.
Reasonable workload is also part of managing well: a role that reliably requires evenings and weekends to complete is a design problem, not a resilience test for the person doing it.
The five-minute action
Subtopic map
What this hub covers
Expectations
Role clarity, standards and the difference between preference and requirement.
How to Set Clear Expectations for Employees (10 min read)One-to-ones
A short, regular, predictable conversation that is not a status report.
How to Run Effective One-to-Ones With Your Team (10 min read)Feedback
Specific, timely, behavioural and separated from performance theatre.
How to Give Feedback That Actually Changes Behaviour (9 min read)Underperformance
Fair process, written records and early professional advice.
How to Handle Underperformance Fairly (12 min read)Conflict
Small teams have nowhere to hide. Address it early and calmly.
How to Handle Workplace Conflict in a Small Team (10 min read)Remote and hybrid teams
Visibility through written work rather than surveillance.
How to Manage a Remote or Hybrid Team Well (10 min read)Reasonable workload and support
Wellbeing, capacity and the duty not to build a role that breaks people.
How to Support Reasonable Workload and Wellbeing (11 min read)Subtopic map
Guides in this hub
Each guide answers one question in full and ends with something you can write down today.
How to Manage People When You Have Never Been a Manager
Start with a small, consistent set of habits rather than trying to learn management theory: a regular one-to-one with each person, clearly stated expectations for their role, feedb…
Read (12 min read)How to Set Clear Expectations for Employees
Clear employee expectations are written, specific standards that distinguish non-negotiable requirements from preferences, shared directly with each person before performance is as…
Read (10 min read)How to Run Effective One-to-Ones With Your Team
Run a short, regular, protected one-to-one — thirty minutes, fortnightly is a workable default for a small team — that opens with their agenda, not yours, covers progress and feedb…
Read (10 min read)How to Give Feedback That Actually Changes Behaviour
Effective feedback is a specific, timely, behaviour-focused observation — not a character judgement — delivered close to the moment it is earned and linked to a concrete outcome. E…
Read (9 min read)How to Handle Underperformance Fairly
Underperformance management is the structured process of identifying a performance gap, ruling out unclear expectations or missing support as causes, and following a documented, fa…
Read (12 min read)How to Handle Workplace Conflict in a Small Team
Workplace conflict in a small team is any ongoing tension between two or more people that affects the quality of work, the working environment, or the team's ability to function. A…
Read (10 min read)How to Manage a Remote or Hybrid Team Well
Remote team management is the practice of replacing physical presence with visible, written work — clear outcomes, shared progress records, and regular structured conversations — s…
Read (10 min read)How to Support Reasonable Workload and Wellbeing
Reasonable workload management is an employer's legal and practical duty to ensure that the demands of a role do not routinely exceed what a person can complete in their contracted…
Read (11 min read)Featured tool
Founder Bottleneck Assessment
Finds where the business queues behind you across decisions, money, knowledge, customer relationships, systems and absence — and what to move first.
Use the Founder Bottleneck AssessmentTemplate
One-to-One Meeting template
A repeatable agenda: their topics, blockers, progress against outcomes, feedback both ways, and agreed actions.
Use the template online or print a copy for your team. No email address is required.
Founder stories
If you learned to manage the hard way in a business under ten people, your account would help someone currently making the same mistakes.
Contribute your storyFrequently asked questions
How often should I hold one-to-ones?
Every two weeks for around thirty minutes is a reasonable default for a small team. Predictability matters more than length.
What should I do about underperformance?
Start with clarity and evidence: what was expected, what happened, and what support was offered. Follow the Acas Code of Practice, keep written records, and take advice from a qualified employment adviser before any formal step. This site is not legal advice.
Can I manage well without HR software?
At this size, yes. A shared document with expectations, notes from every one-to-one and agreed actions is enough for most teams under ten.