Small businesses oscillate between two performance-management failures: nothing (feedback = the owner's mood, increments = negotiation theatre) and corporate cosplay (9-box grids for a team of eight). The right system for a small team is lightweight but written: clear expectations, a monthly conversation, honest annual decisions, and a humane-but-firm underperformance process. Here is that system, buildable in a week.
Expectations first: the role scorecard
- One page per role: the mission (why this job exists in one sentence), 3–5 key outcomes with numbers where possible (sales targets, wastage %, TAT, error rates), and the behaviours that matter here (customer tone, team reliability)
- Written with the employee, not delivered to them — the conversation is half the value
- Reviewed when the role changes; referenced in every later conversation ('scorecard ke hisaab se dekhein')
- The absence of this page is why most 'performance problems' are actually expectation problems
The monthly 1:1 — the engine
Thirty minutes, every month, per direct report — the highest-ROI management ritual that exists: their scorecard numbers reviewed together (data, not vibes), what's blocking them (the manager's to-do list comes from here), one piece of specific feedback each way, and notes kept (two lines in a shared doc — the running record that makes year-end honest and disputes defensible). The discipline rules: never cancelled (rescheduled, maybe; skipped, never), never only-when-problems (that trains people to fear the invite), and never a surprise repository — feedback saved for annual reviews is management malpractice; the annual conversation should contain nothing new.
In a 10-person company, differentiation is visible and personal — which is exactly why it must be criteria-based: rate against the scorecard (did the outcomes happen?) not against personality or hours-visible-in-office. The two questions that keep owners honest: 'would I enthusiastically rehire this person for this role?' and 'am I rating the work or my comfort?' Small teams smell favoritism instantly; written criteria are the antidote.
Increments and the annual decision
- Separate the three conversations: performance review (the scorecard verdict), compensation (market + budget + performance), and growth (what's next) — mixing them makes people hear only the number
- Increment logic worth writing down: a company pool (affordability first), differentiated by performance bands (top performers 1.5–2.5× the average increment; flat across-the-board increments quietly tax your best people)
- Market checks on key roles annually — retention beats counter-offers; the raise given before the resignation costs less than the one after
- Non-cash levers small companies underuse: titles that reflect reality, skill-training sponsorship, flexibility, and genuine ownership of visible projects
- Variable pay: only with measurable outcomes and paid as promised — a bonus scheme defaulted once is worse than none
Underperformance: the humane-firm process
The sequence that is both decent and defensible: (1) the direct conversation — specific gaps against the scorecard, asked-for causes (personal situations, unclear expectations and missing tools cause half of underperformance); (2) the documented improvement plan — 30–60 days, 2–3 measurable targets, support named, weekly check-ins (a real PIP is a rescue attempt with a record, not a firing ritual — and written, it protects both sides); (3) the honest verdict — improved: say so loudly; not improved: proceed to exit per the appointment letter's process (notice/pay-in-lieu, documented grounds) — because carrying chronic underperformance in a small team taxes exactly the people you most need to keep. The paper trail throughout (1:1 notes, PIP records) is what converts a potentially ugly dispute into a routine, respectful separation.
How Aidwish helps
Aidwish installs right-sized performance systems — role scorecards, the 1:1 ritual with templates, increment frameworks and compliant underperformance processes — inside its staffing and SOP engagements, so small teams get big-company clarity without the bureaucracy.