Startups Should Design Personnel Evaluation Around Purpose, Not Form

This is a question I get asked often, so let me lay it out here. As a premise, a company has no problem at all without personnel evaluation, as long as things are running smoothly. So “doing it anyway” means either there is “some benefit down the road” or there is “some problem right now.”
【Examples of future benefits】
- Being viewed positively during IPO screening or M&A negotiations
- Being able to tell candidates at hiring time that “this is a well-run company”
- As the organization grows, each member’s responsibilities and standards become clear (people do what gets evaluated)
【Examples of current problems】
- There’s pressure from below for a proper evaluation system, but the executive team feels “we don’t have time for that”
- There’s unexplained pay disparity within the company, and some people are unhappy about it
- There’s a low-performing employee, and in some cases dismissal needs to be considered, but there’s no evaluation process to serve as the basis for it
For a small company, introducing personnel evaluation is no small undertaking. But designing it around the purpose above lets you get it done with minimal effort.
Let’s go through the specifics below.
【When you want to create a good external impression】 It’s best to borrow a system from somewhere that won’t strain operations. It’s not worth the effort to customize one painstakingly, so applying a generic template should be enough. That said, on the premise that this isn’t really about substance, the most important thing is that it doesn’t strain day-to-day operations. A hollowed-out personnel evaluation system is easily spotted from outside. If that’s the case, it’s better to have a light, simple evaluation system suited to your size that continues steadily in a modest way.
【When you want to unify employee motivation, direction, and standards】 Up to a certain organization size, this doesn’t need to be a personnel evaluation system at all. You can see people’s faces and talk to them directly. For instance, the following are far more useful for shaping company-wide mentality:
- 1-on-1s (without personnel evaluation or salary negotiation attached)
- The CEO regularly speaking to everyone about the vision, the current situation, and the company’s position, including the broader social climate
- Cross-functional manager meetings and so on. But if you insist on introducing personnel evaluation anyway, something like 360-degree evaluation comes closest to the goal. That’s because unifying awareness, clarifying what needs to be done, and clarifying standards are things that should originally be achieved through leadership (though often that doesn’t go so smoothly). That said, “teamwork” is a good substitute for this, and documents or rules can hardly replace it. The sticking point is that what’s required changes depending on the situation (frequent updates are needed). If that’s the case, it’s more flexible and more effective to close the gap in awareness among people through mesh-like relationships.
【When member-level staff want to be managed】 This is a tricky situation for those doing the managing, but it really does happen. Why would people want to be managed? Is being evaluated really that pleasing? You might think that, but this kind of situation certainly exists. This tendency can be especially pronounced when some member-level staff come from large companies, but in any case, the root cause is that managers or the executive team aren’t paying enough attention to their subordinates, and are undermining their self-esteem. Self-esteem is built up through contact with others. It’s about the self, yet it comes from others. People are troublesome creatures. In this case, what’s actually needed isn’t “a perfectly airtight personnel evaluation system,” but rather things like one-on-one interviews and increasing the number of meetings focused on checking individual tasks and progress — those are far more effective. If you forcibly tie this to personnel evaluation anyway, the typical template response is to introduce regular interviews, share an individual’s medium-term tasks and goals at that time, review them at the next regular interview, and turn that into a score to serve as the personnel evaluation.
【When there are members unhappy with their salary】 This case is actually the trickiest and most complicated. Responding to each individual’s feelings tends to end in failure more often than not, so a macro-level approach is preferable here. To begin with, salary isn’t something that can be raised endlessly just because results are being produced. In fact, a scene where salary keeps rising forever and ever is almost absurd to imagine. If there’s a possibility of going up, there’s also a possibility of going down (tied directly to performance and results). If it doesn’t go down much, it also won’t go up much (no more and no less than the going rate). As the basis for this balance, it’s best to prioritize creating a budget. Having a budget means having a hiring plan for talent, and it means the future revenue plan generated by that budget investment has already been authorized. Also, a major point of having a budget is that it gives managers the excuse that “we can only spend within this range.” Use that to first get member-level staff to understand that salaries “won’t just go up however much,” along with the perspective of “do you actually want salaries going up and down all the time?” and the point that such a situation “wastes a lot of energy, both in the effort of evaluating and in the mental burden on those being evaluated.” Building on that understanding, you need to construct a generalized system for the salary decision process. The challenge is to design in a certain amount of abstraction (ambiguity) so that you can still make fine adjustments later. For example, one approach is to build in a certain range for salary amounts, so that, looking closely, it’s actually possible by design for someone in a grade one level lower in evaluation to earn more than someone in a grade one level higher. In any case, the key point is to firmly establish a situation of “budget” → “rules” → “well, that’s just how it’s decided, so what can you do.” So, this case really is quite a hassle in practice. Depending on the situation, it may actually be more convenient for the organization to exclude or separate out, in some form, members who make their dissatisfaction openly visible (members who spread a bad influence on those around them). That’s a judgment call to be weighed against the effort involved.
【When you want this to help with personnel turnover】 Suppose there’s a member whose salary you want to lower for negative reasons, or who you’d be fine with leaving the company, and suppose a pay cut for that member ends up looking arbitrary and blatant. (Even if management actually had solid reasons, the situation lacks objectivity and transparency.) If that member has a bit of savvy and goes to the right authority, things can get fairly troublesome. So as preparation for such situations, having a legitimate evaluation system is extremely desirable. Acts that are generally prohibited (such as violence or intimidation) should of course be clearly written into the employment contract, but what’s really needed is “a mechanism that allows salary to be lowered when performance is terrible.” With that single point as the focus, it’s good to discuss questions like “so what exactly counts as bad performance?” and “what will be tolerated (accommodated) and what won’t?” and establish a personnel evaluation system that can properly extract that point (it’s fine if it can’t extract everything else). The specifics will differ by organization, but for example, if an organization considers “valuing teamwork and completing tasks on schedule” to be the top priority, it should design a mechanism where anyone who disrupts that inevitably gets a lower evaluation, even if their other performance is good. For an organization that calls for “creative proposals and concrete creation,” it would be a problem if the mechanism raised the evaluation of someone who isn’t generating new ideas or actually making things with their own hands. In this way, the intent behind personnel turnover mentioned at the start has, as its highest-level purpose, a systematic nudge along the lines of “this isn’t a good fit for us, so please go elsewhere — surely there’s somewhere else you can thrive.” It’s not at all about wanting to exclude people you simply dislike.
Now, I’ve rambled on about general principles, but in most cases multiple purposes and problems are mixed together. Even then, rather than trying to achieve everything at once, I think the most important thing — not just for personnel evaluation but for introducing any system — is to narrow things down to the priority issue and introduce an appropriate, minimal level of precision. That said, in situations where, for instance in preparation for an IPO, you’ve made a firm decision to hire a large administrative staff all at once and build out an airtight management structure, there’s no choice but to brace yourself, accept the effort involved, tolerate the friction it causes, and push it through across the board. (It’s hard and quite exhausting, though.)
Similar Articles – clay tech > category > Organization and Career
Originally published in Japanese at https://clazytech.com/2020/12/441/. Translated with LLM assistance and reviewed before publication.