How do I run a first performance review cycle in a small company?
Run a short four-week cycle: a self-review, a manager review, a calibration meeting and a conversation with each person. Keep forms to one page, set a date for each step and name an owner. Ratings and pay decisions stay with people; the cycle only makes sure nobody is missed.
Who asks this: A founder or first HR hire at an Indian company of 10 to 50 people that has never run a formal review and wants something fair and light before the April increment season.
The steps
1. Week 0: decide what the review is for
Write one paragraph for everyone: what is reviewed, what is not decided in the review (for example, pay may be a separate conversation), and the dates. Founders who skip this paragraph find people expect a raise from every review.
2. Week 1: self-review
Send each person a one-page form with four prompts: what went well, what was hard, what I learned, what I want next. Give five working days. The HR owner keeps a list of who has submitted.
3. Week 2: manager input
Each manager writes a short note per person: strengths, one thing to improve and one example of each. Ask for facts and recent examples, not adjectives. Late notes are chased by the HR owner every second day.
4. Week 3: calibration
Founder, managers and HR spend an hour comparing summaries. The goal is fairness across teams: is the same effort described the same way. Record any change and the reason.
5. Week 3 to 4: one conversation per person
The manager meets each person for thirty minutes, shares the summary, listens to the response and agrees two goals. Hold these conversations before any letter or pay change is issued.
6. Week 4: file and follow up
Store each summary in a single folder with limited access. Link any increment or promotion decision to a separate letter. Set a date for a short mid-cycle check-in six months later.
7. Debrief the process itself
Ask managers and employees two questions: what was useful and what was a waste of time. Cut the waste before next cycle. A review process that gets lighter each time is a healthy one.
A worked example
illustrative
A 28-person SaaS startup in Hyderabad runs its first review in late March. Self-reviews go out Monday and 26 of 28 arrive by Friday; the HR owner reminds the other two. Managers submit notes by the next Wednesday, and calibration on Thursday changes two summaries after the founder notices one manager wrote far more detail for a favourite. By week four all 28 people have had a thirty-minute conversation, and increment letters follow in April. The conversations alone take fourteen manager hours (28 at half an hour), which at an assumed six hundred rupees an hour is eight thousand four hundred rupees; notes and calibration come on top.
What goes wrong
- The forms are five pages long, and nobody reads them.
- Managers write adjectives, such as 'good attitude', with no example behind them.
- Ratings and pay are announced in the same meeting, and the conversation turns into a negotiation.
- Some teams finish in a week and some take two months, and fairness is lost.
- Notes are kept in a shared folder anyone can open.
- The review is held once and never again, and people conclude it was a one-off.
How Demystify OS helps
Mysty WorkersEarly access
Mysty Workers can be set up with you to run the cycle calendar: draft the self-review prompts and the reminders to late submitters for a person to send, and assemble the input you pass to it into one summary pack per person for the manager and founder.
Mysty DeskEarly access
Mysty Desk is an approval screen in early access. The manager reviews each drafted summary pack there before it is shared, and what is sent from it is confirmed with the team before you rely on it.
WhatsAppProvisioned on request
Short prompts and reminders travel well in chat. WhatsApp is a channel on request; today it is click-to-chat and share links, so a person sends each prompt.
What it does not do. Demystify OS does not rate people, recommend increments or promotions, or decide pay; it keeps the calendar moving and assembles the pack so humans can make those calls.
Questions people ask
How long should a first review cycle take?
Four weeks is enough for a company of a few dozen people: one for self-reviews, one for manager notes, one for calibration and one for conversations. A longer cycle loses momentum, and a shorter one rushes the conversation.
Should pay be discussed in the review?
Many companies separate them, holding the performance conversation first and the pay conversation a few weeks later. That lets people hear feedback without the distraction of a number. Whatever you choose, tell everyone in advance.
What should a self-review form ask?
Four short prompts are enough: what went well, what was difficult, what I learned and what I want to do next. Short prompts get honest answers, and long forms get copied from last year.
How do I keep the review fair across managers?
Hold a calibration meeting where managers compare summaries, ask for an example behind every claim and check that similar work is described the same way. Record any changes with the reason.
Do I need software to run reviews?
Not for the first cycle. A shared form, a tracker and a calendar are enough for fifty people. Software becomes useful when several cycles a year make the chasing a full-time job.
Apply for the beta.
Demystify OS is invite only, and a person reads every application.
Apply for the beta