Why the split fails small teams
Decoupled, both halves rot: reviews without stakes become pleasant and vague, and pay without process goes to whoever asks loudest, which correlates with confidence, not contribution, and quietly builds the inequities that surface as resentment or departures. Under twenty people there is no committee to hide behind; the founder’s pattern is the policy.
Coupling them does not mean rating formulas. It means the same conversation window holds both truths: how the work went, and what that means for the money.
The review that fits this scale
Twice a year, three questions each way, written first, discussed for forty-five minutes: what went well, in evidence; what should change next, concretely; where are you heading here. The employee writes theirs before seeing the manager’s, which surfaces the perception gaps that are the real material of the conversation.
Same-day summary into the file, three sentences. The paper-trail guide explains why future-you insists on this.
Pay decided against a budget, not a mood
Before the cycle, the raise pool is set from the people budget; during it, increases are proposed against three inputs: sustained contribution from the review, market movement for the role, and internal consistency across the team. After it, every decision is explainable in one sentence that names those inputs, including the no: "not this cycle, here is what would change it, we look again in six months."
Explainable beats generous. Teams forgive tight budgets; they do not forgive mystery.
The intersection discipline
This cycle is where HR and finance literally meet: the review supplies the evidence, the budget supplies the constraint, and the founder supplies a decision that respects both. Skipping either side breaks it, generosity that ignores the budget becomes next year’s layoff, and budgets that ignore the review become this year’s resignation letter from your best person.
Solo operators rehearse the same muscle on themselves: the owner-pay review, against the same three inputs, on the same calendar.
One cycle, both desks
Run the review side in the HR Desk, employee reviews, notes and the file, and the pay side in the Finance Desk, the raise pool and the people plan, with Velora drafting review summaries and the one-sentence rationales from your notes.
The employee’s side of the same table is covered in the Career guide to reviews and advocacy; it makes you a better decider to know their playbook.
Frequently asked questions
Should performance reviews and pay decisions be connected?
At small scale, yes, in one twice-yearly cycle: reviews supply the contribution evidence, the people budget supplies the constraint, and every pay decision becomes explainable in a sentence. Decoupling them hands raises to whoever negotiates hardest.
What does a good small-team review look like?
Three questions each way, written before the conversation, discussed in forty-five minutes, summarized into the file the same day: what went well in evidence, what changes next, where the person is heading.
How do I say no to a raise request well?
Against the three inputs: sustained contribution, market movement and internal consistency, with what-would-change-it named and a date to look again. An explainable no keeps trust that a mysterious yes destroys.