2026-06-29
Evaluation for small teams: start from daily facts rather than a complex system
However fine an evaluation system, it's meaningless if you can't run it. A realistic way for small companies and single teams to build evaluation from the facts in daily reports, without relying on a complex system.
The trap of a system that collapses
Copy a large company's evaluation system as-is and too many items make it unrunnable under the operating load. Building the system becomes the goal itself, the field is buried in form-filling, and the dialogue that matters withers — a common collapse in small organizations. In a small organization, both the time and the people available for evaluation are limited. An evaluation sheet with many items tires both writers and readers, and scores tend to walk off on their own. Start by asking whether it is light enough to run.
Start from 'leave the facts'
Before building an elaborate evaluation sheet, start by leaving daily facts in the report. With the evidence of when someone worked on what and how they reflected, the form of evaluation can be assembled later. The order is facts first, system second. For example, reread the actions and reflections in the reports at month-end and note a few scenes that stood out. In the interview you can point to facts — 'this judgment on this day was good' — so it is easier to gain agreement. It is also easier to stay fair than when relying on memory or impressions alone.
One axis: who you want them to become
Rather than adding evaluation items, make one coaching policy — 'how you want them to grow this term' — the single yardstick. The simpler the axis, the longer it runs, and the easier it is for both sides to share the criterion. Many axes usually go unused. For example, this term you might set 'being able to plan and move on your own' as the single axis. Telling everyone the axis makes it easier for them to align daily actions. The axis may change term by term to fit the state of the business.
Build the system while growing it
There's no need to wait for a finished system. Start small, run it, and review and update each quarter. On the premise that the axis of evaluation changes as the business and people change, growing the system itself is more realistic for a small company. At the review, check 'has it become heavy to run?', 'has dialogue increased?', and 'how do the evaluated people feel?' The rule of thumb is to boldly cut what doesn't fit and add only what is missing.
Common stumbles and how to avoid them
A common stumble is that only the boss holds the criteria and the person can't see them. If criteria aren't shared beforehand, only the result reaches people and it breeds distrust. Also, trying to recall everything at term-end skews toward recent events. Leaving daily facts is the shortcut to avoiding that skew. Another idea is not to tie evaluation to treatment in a hurry, and first use it as a coaching dialogue.
The smallest first step to try
Before the next interview, reread one person's reports and write out three good scenes. Just conveying them in the interview makes the talk about evaluation more concrete. If it feels like it works, widen the scope and settle the axis.
Related articles
- Make daily reports the basis for evaluation: building fair appraisal that doesn't rely on the manager's subjectivity
- Make company philosophy the axis of evaluation: connecting coaching policy to daily action
- Start improvement by department: build a PDCA culture without waiting for company-wide rollout
The feature that fits this article's topic: Fair evaluation →
A tool for a culture of improvement and fair evaluation that implements these ideas.