To manage people without HR, start by dropping the guilt. A 10-person team does not need the same people function as a 500-person company. But a 30-person team cannot run people decisions from memory, vibes, and a founder's private judgement forever.
What you'll learn
- What a small team can handle without a dedicated HR department.
- Which people rhythms matter first: clarity, check-ins, feedback, records, onboarding, and escalation.
- Where a founder should stop improvising and bring in outside HR or employment-law help.
- How Cooperly supports manager follow-through without pretending to be the employer's HR function.
- A practical 30-day rhythm for 10-50 person companies that have outgrown ad hoc management.
If you are also the founder, operator, sales closer, product owner, and unofficial therapist, the problem is probably not laziness. The problem is that the team has crossed a threshold. This is the same pattern behind the founder bottleneck: what worked through direct memory starts breaking when more people need fair, repeatable decisions.
How do you manage people without HR without pretending HR does not matter?
The honest version is simpler than the guilt story. A permanent HR department is not the entry ticket for deliberate people management. What you need first is a system that stops every people issue from becoming a one-off founder mood.
That distinction matters because HR is doing more than paperwork in a mature company. HR protects consistency, keeps records, helps managers act fairly, watches compliance risk, supports hiring and onboarding, and gives employees a route when their direct manager is part of the problem.
A 10-50 person company may not need that full internal function yet. But the needs underneath it already exist: expectations must be set, performance issues must be documented, conflict needs a cleaner route than personality trial, and high-stakes decisions need a stop sign before improvisation takes over.
What changes when memory stops scaling?
At five people, the founder can keep most context in their head. By 15, that memory starts leaking. Around 30, it becomes unfair. Two employees can receive different answers because they asked on different days. A manager may give honest feedback while another avoids it. One new hire gets careful onboarding; another gets a rushed handoff and a stack of Slack messages.
Employees do not experience that as a normal stage of growth. They experience it as favoritism, chaos, or mixed standards. Inside the founder's head, it becomes emotional weight: too many small people decisions, too many exceptions, too many conversations delayed because every one feels personal.
Gallup's global work data is a useful reminder that the manager layer matters. In its 2026 workplace report, Gallup put worldwide employee engagement at 20% for 2025. Its estimate for the productivity cost of low engagement is huge. More useful than the headline number is the pattern: people management is not a side quest once work depends on other people's energy and judgement.
Your threshold is not a magic headcount. It is the moment when the founder's private context stops being enough for fair decisions. If people need to guess the rule, the rule is not really a rule yet.
What does an HR department actually give you?
The phrase "we do not have HR" often hides five missing systems: shared role standards, a check-in rhythm, clean feedback records, a route for conflict, and a clear point where outside help enters the decision.
CIPD's work on People Skills in small firms is useful because it does not treat small employers as miniature corporations. The support small firms used included practical help such as contract and policy review, recruitment support, templates, helplines, and group training. That mix tells you something important: small teams often need bite-sized HR capability before they need a full department.
| HR job | Full HR version | Small-team version |
|---|---|---|
| Role clarity | Job architecture, leveling, and formal role documentation. | One-page role cards: outcomes, decisions, working agreements, and current priorities. |
| Manager support | Training, coaching, templates, and review cycles for managers. | A weekly manager rhythm with prompts for clarity, feedback, risks, and follow-up. |
| Employee relations | Formal grievance, investigation, mediation, and case management support. | Clear escalation rules and outside help for conflict, complaints, or high-stakes decisions. |
| Records | HRIS, performance history, policy acknowledgements, and audit-ready documentation. | Simple dated notes for expectations, feedback, agreed actions, and follow-up dates. |
| Compliance | Jurisdiction-specific policy ownership and legal coordination. | A trigger list for when the founder stops and gets qualified support. |
This is the reframe for the overwhelmed founder: you are not trying to build an HR department in a weekend. You are trying to stop people decisions from living only in your head.
Which people rhythms should a founder run first?
Start with the boring basics. Boring is good here. A people rhythm should make the next conversation easier, not make the company feel like it hired a policy department overnight.
- 01
Write one-page role cards
For each role, name the outcomes, decision rights, recurring meetings, current risks, and what good work looks like in plain language.
- 02
Run a first-week onboarding checklist
Cover access, context, owner, expected first outputs, key relationships, and the first feedback point before the new hire is left to guess.
- 03
Hold one-to-ones with the same spine
Use the same questions every week: what changed, what is blocked, what needs a decision, what feedback should not wait, and what support is missing.
- 04
Turn feedback into dated notes
Keep short records of expectations, examples, agreed actions, owners, and follow-up dates. Do not write a diary of irritation.
- 05
Review people risks monthly
Look across workload, conflict, unclear roles, performance drift, compensation pressure, onboarding gaps, and founder bottlenecks.
- 06
Escalate high-stakes issues early
Use outside HR or employment-law support when the decision affects pay, dismissal, discrimination risk, formal complaints, protected leave, or serious conflict.
A better rhythm also protects managers from improvising under stress. For example, a better performance review process does not start with a form. It starts with useful feedback, specific evidence, agreed actions, and follow-through that happens before review season.
If you already have managers, keep the rhythm shared. One manager cannot run careful feedback while another runs on mood. The employee experience is the standard people see across the company, not the best manager's private craft.
What should you document without creating bureaucracy?
Documentation makes founders nervous because it sounds like bureaucracy or legal danger. Avoiding notes is usually riskier. If a decision affects someone's role, pay, performance, workload, growth, or exit path, the company should be able to explain what happened and what was agreed.
You are not writing a courtroom file for every awkward moment. The aim is to keep the work explainable. That means writing down the signal, the example, the decision, the owner, and the next date while the facts are still fresh.
| Moment | Record this | Avoid this |
|---|---|---|
| Feedback | Specific example, impact, expected change, support offered, follow-up date. | Labels like lazy, negative, not a culture fit, or always difficult. |
| Role change | New outcomes, changed decision rights, compensation effect if any, start date. | A vague promise that someone will grow into something later. |
| Conflict | Observed behaviours, affected work, agreements made, next check-in. | Private judgements about motives or personality. |
| Performance concern | Expectation, evidence, gap, support, timeline, consequence if unresolved. | A surprise verdict after months of undocumented frustration. |
| Pay or raise request | Decision criteria, current constraints, next review point, who owns the answer. | A casual maybe that becomes a remembered promise. |
This is especially important when money enters the conversation. If someone asks for a raise, link the answer to role scope, market context, performance evidence, and timing. The detailed playbook is here: How to Respond When an Employee Asks for a Raise.
How do you handle performance, conflict, and pay without HR?
These are the moments where small teams tend to swing between two bad options. One option is avoidance: the founder keeps the peace until resentment leaks into tone, promotion decisions, or sudden exits. The other option is overreaction: one painful conversation turns into a dramatic policy or a harsh ultimatum.
A better approach is boring and repeatable. Name the issue early. Separate the person from the pattern. Ask what changed. Set a concrete expectation. Document the next step. Return on the date you named.
Conflict needs the same discipline. Acas reported that 44% of people in Great Britain experienced workplace conflict in the previous 12 months. Even if your jurisdiction or team context differs, the management lesson travels: conflict is normal enough that a founder should have a response pattern before the first serious rupture.
When the problem is between two people, do not make yourself the informal gossip router. Use a clean structure like the one in How to Resolve Conflict Between Team Members: facts, impact, ownership, next agreement, and a follow-up point.
Pay needs even more care because every exception becomes a signal. A founder may think they made a one-off retention decision. Colleagues may read it as the new rule for negotiation, fairness, or who gets heard.
Where should a no-HR team stop and get help?
This is where the article has to push back on the tempting headline. HR still matters. Good management simply should not wait for a department. Specialist support still matters when the stakes rise.
In the U.S., several federal rules have headcount or coverage thresholds that can appear earlier than founders expect. EEOC guidance for small businesses notes that many federal discrimination laws apply at 15 employees, while federal age discrimination coverage starts at 20. Wage, leave, classification, and state or local rules can have separate tests, so the practical founder move is to slow down and get qualified help before acting.
Outside the U.S., the exact rules change by country, contract type, worker status, and local law. UK readers should treat Acas and GOV.UK as starting points for disciplinary, grievance, contract, dismissal, and workplace conflict process. The broader management rule is the same: do not improvise when the decision can affect rights, pay, protected status, dismissal, or formal complaints.
| Trigger | Founder can prepare | Bring in support |
|---|---|---|
| Employment contracts | Collect role, pay, location, working pattern, and start date details. | Have a qualified adviser review contract terms for the jurisdiction. |
| Protected leave or accommodation | Listen, record the request, keep the conversation private, and avoid snap decisions. | Get jurisdiction-specific guidance before deciding or communicating limits. |
| Disciplinary or dismissal risk | Gather dates, examples, prior feedback, support offered, and follow-up history. | Use outside HR or employment-law support before a formal process starts. |
| Discrimination or harassment concern | Take the report seriously, protect confidentiality, and avoid retaliation. | Get qualified support immediately because process integrity matters. |
| Multi-state or cross-border hiring | Map where people work and what employment setup is being used. | Review payroll, tax, leave, classification, and contract implications. |
A mature small team is not one that never needs help. A mature small team knows which work belongs to the manager, which work belongs to a specialist, and which decisions should slow down before they become expensive.
How can Cooperly support the rhythm without becoming HR?
The product boundary matters. Cooperly is not the company lawyer, payroll system, HRIS, or final decision-maker. Its value sits earlier in the chain: when a manager needs to understand team pressure, working style, relationship friction, onboarding gaps, unclear expectations, or follow-up that is going stale.
That is where the AI Context Layer matters. A founder does not need more scattered impressions. A founder needs a clearer way to review team signals, decide what needs attention, and turn the next management step into something visible.
That same logic sits inside Coop Profile, Fundamentals, and Pulse: context, team operating rules, and regular signal review help managers act sooner without turning every people issue into a heavy formal process.
The best use of Cooperly in a no-HR team is not to automate judgement. It is to make judgement less lonely. Managers still decide. The system helps them see what is changing, prepare the conversation, and remember the follow-up.
What 30-day rhythm can you start this month?
Do not start with a full handbook. Start with the conversations and records that will reduce the next month of avoidable confusion.
- 01
Week 1: map the current people risks
List unclear roles, delayed feedback, overloaded people, active conflicts, pay pressure, onboarding gaps, and decisions living only in the founder's head.
- 02
Week 2: standardize one-to-ones
Give every manager the same meeting spine: wins, blockers, decisions, feedback, support, and follow-up.
- 03
Week 3: create the five-line note habit
For live people issues, record date, signal, example, agreement, and next check. Keep notes factual and useful.
- 04
Week 4: define escalation triggers
Write the list of issues that require outside help before action: contracts, leave, dismissal, discrimination, formal complaints, serious conflict, or complex pay decisions.
- 05
End of month: run a people review
Spend 45 minutes reviewing roles, workload, conflict, onboarding, performance drift, pay pressure, and who owns each follow-up.
The rhythm should feel almost too simple. That is the point. If the system only works during a calm week, the system is decorative. The right system still works when sales are messy, delivery is late, and the founder is tired.
For listening and follow-through problems, pair this rhythm with Employee Surveys Without Action Waste Trust. When manager overload is the sharper issue, read What to Do When a Manager Never Delegates before adding another meeting to the calendar.
What should leaders do next?
The founder guilt is understandable, but guilt is not a system. Charisma and mission energy are not systems either, even when the team is full of good people.
A small company can care about people before it has a people department. Clearer roles can come before job architecture. Feedback can be recorded before an HRIS exists. Conflict can be handled before there is an employee relations team. Outside help can arrive before a preventable issue becomes a formal mess.
Start with the next visible rhythm: one role card, one one-to-one spine, one people-risk review, one escalation list, one follow-up date. Then repeat it until the team no longer has to guess how people decisions get made.