Performance management

Performance management means setting expectations people can see, supporting them to meet those expectations, and following through with honest consequences when they do not. Fair process is the fourth element, and the one v1.0 left implicit. The person knows the bar, has been told where they stand, has been given a real chance, and can see that the same rules apply to everyone. The competency matters for two reasons. Its signature failure, avoiding the hard conversation, is paid for by the rest of the team, who see the gap and quietly lower their own standards to match. Its opposite failure, a consequence delivered without the expectation or the support, is unfair in a way everyone also sees. The examinations test it at every scope: the engineer whose slow delivery had a real cause, the manager who brings a formal plan for someone who was never told the bar, the leader whose results are excellent and whose methods are hollowing out the organisation.

1. People can only meet a bar they can see. Expectations are explicit, written down where it matters, and revisited when the role or the work changes. A performance conversation should refer to something the person already knew.
2. Early, private and specific. A gap is raised in the week it is noticed, one to one, with instances. Waiting for the review cycle turns a problem that could have been corrected into a verdict.
3. Diagnose before responding: skill, will, or conditions. Either the person does not know how, or they are not applying themselves, or they were not given what the job needed. Each calls for an entirely different response, and the third is more common than managers like to admit.
4. A formal plan is a real chance, or it is a lie. A time-boxed, well-supported improvement period with a clear bar is fair. Paperwork for a decision already taken is unfair, and the team knows the difference.
5. Follow through. When the period ends and the bar has not been met, the decision was made when the plan was set. Unwinding it teaches everyone that the bar is negotiable and the plan was theatre.
6. How results are achieved is part of performance. Output produced by fear, by burning out a team or by breaching the organisation's values is a performance problem, and the results do not offset it.

Performance management has plenty of process and little evidence. The models here are practitioner tools with clear provenance. The fairness claim rests on a body of organisational-justice research, which the cited article summarises for managers.

Skill and will practice

The diagnostic comes from Max Landsberg, The Tao of Coaching: Boost Your Effectiveness at Work by Inspiring and Developing Those Around You (1996). Before responding to underperformance, separate whether the person cannot (a skill gap, met with teaching and support) from whether they will not (a will gap, met with expectations and consequences). This unit adds a third branch that the original does not name, the conditions gap, where the person was never given what the job required: clear requirements, access, time, a functioning team. Treat a skill gap as a will gap and you demoralise the person. Treat a will gap as a skill gap and you coach endlessly at something coaching cannot fix. Treat a conditions gap as either and you produce an unfair review that the whole team recognises for what it is.

Fair process practice

W. Chan Kim and Renée Mauborgne, Fair Process: Managing in the Knowledge Economy (1997) sets out three elements (engagement, explanation, and clarity of expectation) drawn from the authors' research into why people accept decisions that go against them. Applied to performance, the person is heard, the reasoning behind the judgment is explained, and what is expected next leaves no room for doubt. This matters because people accept and learn from a consequence they regard as fairly reached, while the same consequence reached unfairly is resisted and remembered by everyone who watched. The grade here is practice because the management version is a synthesis, even though the justice research beneath it is substantial.

Output and leverage practice

In Andrew S. Grove, High Output Management (1983), Grove treats a manager's output as the output of the organisation under them. That is why a manager's performance cannot be read from their own report. It has to be read from sustained team health, sustained delivery and how the results were achieved, over time. The same idea explains why a leader who hits every number by leading through fear is a performance problem: the present number is being bought with the organisation's future capacity.

Calibration practice

Calibration, shared with hiring, is the mechanism that makes ratings mean the same thing across teams. It depends on shared standards, on evidence winning over advocacy, and on a joint review when two managers disagree about the same person. Its purpose is fairness, and it typically decays into horse-trading, where ratings are negotiated instead of evidenced. If the most assertive manager's people are consistently rated highest, the meeting is no longer calibrating anything.

Expectations, written

Each person has a short written statement of what the role expects at their level and what the next quarter is meant to produce. It is agreed in a one-on-one and revisited when either changes, and it is the document a later performance conversation points to. If it does not exist, the first act of performance management is to write it, before any gap is raised.

The early conversation

The first performance conversation is small. It covers the gap, an instance or two, the question of what is getting in the way, and an agreed next step. It happens in the week the gap is noticed and nobody calls it a warning. Most performance problems that reach a formal stage got there because this conversation was skipped.

The diagnosis before the plan

Before any formal step, the manager writes one paragraph answering three questions. Were the expectations explicit? Was feedback given and documented? Is this skill, will or conditions? If the answer to either of the first two is no, the formal step is premature and the manager's own gap comes first.

The improvement period

A formal plan states the specific bar, the specific support (pairing, reduced scope, a named reviewer), the duration, and what happens at the end. It is reviewed weekly. At the end, the outcome is the one the plan defined, delivered as directly as the plan was set.

Reading a manager's performance

For someone who leads others, performance is read over at least two quarters from their team's health (attrition, engagement and what skip-levels reveal), their team's delivery, and how the results were produced. One bad quarter with a cause outside the manager's control is judged on the quality of their decisions and their response, not on the raw outcome. One good quarter produced by heroics is not evidence of much.

At team scope the object is an engineer's performance against expectations the manager set, and the manager acts directly. At organisational scope the manager of managers has two jobs. One is quality control on how their managers handle performance, which includes declining a formal plan built on absent expectations and coaching the manager first. The other is judging the managers themselves, on evidence gathered over time instead of their own status reports. At executive scope the object is leaders whose results are tangled up with context, politics and the executive's own public bets. Fairness then means calibrating across organisations by the change a leader produced, setting aside how healthy the organisation they inherited was. The pattern is in How Judgment Scales; the managers whose performance is being read are the subject of PL-6 Leading through leaders.

• Sets expectations the person can see, and revisits them when the work changes. team
• Raises a gap early, privately and with instances, before it becomes a crisis. team
• Separates skill from will from conditions, and responds to the one that is in fact present.
• Treats a formal plan as a real, supported chance with a defined end, and follows through at the end.
• Protects the team by making a hard decision about one person when the damage outweighs the output, including the high performer whose behaviour breaches the team's values (see CC-5 Values, integrity, and ethical judgment under pressure).
• Failure mode: hoping the problem resolves itself. team
• Failure mode: vague feedback that never names the gap. team
• Failure mode: endless coaching of a will problem. team
• Failure mode: a formal plan for someone who was never told the bar.
• Declines a manager's formal plan when expectations were never explicit, and coaches the manager to set them first. org
• Judges managers on sustained team health, sustained delivery and how results were achieved, over time and in context. org
• Runs calibration as a fairness mechanism (evidence over advocacy, joint review when managers disagree) and never as a ranking ritual. org
• Names an equity problem when a manager gives all the high-visibility work to favourites; opportunity is part of compensation (see CC-3 Inclusive practices and equitable opportunity distribution). org
• Owns a headcount-reduction selection with consistent, defensible criteria after hearing the manager's case in full. org
• Failure mode: approving a plan built on absent expectations because "the manager owns their team". org
• Failure mode: judging managers by their own status reports or by likeability. org
• Failure mode: punishing outcomes without reading context, or excusing patterns because of it. org
• Failure mode: letting calibration decay into horse-trading. org
• Holds leaders accountable for how results are achieved. A leader who delivers through fear while capable people leave is a performance problem, without qualification. exec
• Gives a loyal, long-tenured leader whom the organisation has outgrown honesty, and either a reshaped role or a dignified transition, instead of quiet marginalisation. exec
• Acts on the evidence when a leader the executive publicly backed is failing; doubling down to protect the bet loses both the organisation and the reputation. exec
• Calibrates leaders across organisations by the change they produced and the quality of their decisions, setting aside the health of the hand they were dealt. exec
• Failure mode: tolerating a feared-but-effective leader until the pipeline beneath them is hollow. exec
• Failure mode: letting loyalty freeze the organisation chart. exec

Care versus clarity. The manager wants to protect the person from a hard message, and the person needs that message to have any chance of meeting the bar. Clarity delivered with care resolves it. Care offered in place of clarity is the failure this whole unit describes.

Fairness to the individual versus fairness to the team. A long improvement period is fair to the person and costly to the team carrying the gap. The resolution is a period that is properly time-boxed and properly supported, so that the person and the team both know when it ends.

Context versus accountability. Reading a bad quarter in context is fair. Reading every bad quarter in context is how patterns get excused. The judgment lies in the timescale: a single quarter is weighed by the decisions and the response, while a pattern across quarters is itself the performance.

Results versus methods. A leader with excellent numbers and departing people forces the question of what performance is. This standard holds that the methods are part of the result, since what is being spent is the organisation's future capacity. The pull toward the number is strong all the same, and the examination tests whether the candidate resists it.

Loyalty versus scope. Tenure and past contribution earn respect and candour. They do not earn permanent scope. Honouring the first while refusing the second is uncomfortable and is the only fair option. The alternatives are an organisation that cannot grow past its early leaders, or a quiet demotion that nobody was honest about.

A manager who reports to a senior manager arrives with a formal improvement plan for one of their engineers, drafted and ready to issue. The engineer's delivery has been slow for two quarters. Reading the plan and the history, the senior manager finds that the engineer's objectives were never written down, that the feedback over the period amounts to two informal comments in one-on-ones, and that by the manager's own account the requirements for the engineer's main project were unclear until six weeks ago.

Both easy responses are wrong. Approving the plan because the manager owns their team hands an unfair consequence to someone who was never given a fair chance, and everyone on that team will read it correctly. Taking the case over, by rewriting the plan or talking to the engineer directly, settles the case and teaches the manager nothing, while telling their team that the manager is not really in charge of it.

The senior manager declines the plan and explains why to the manager, as feedback on the manager's own performance. Expectations were never explicit, feedback was neither given nor documented, and for most of the period the conditions for the work were poor. The engineer has not yet had the chance the plan claims to give. On the evidence, the engineer's problem is at least partly a conditions gap, and the manager's is a skill gap in performance management.

The senior manager then coaches and leaves the doing to the manager. The manager is asked to write the engineer's expectations for the coming quarter this week and agree them in a one-on-one, to give specific, documented feedback at least every fortnight, and to sort out the requirements problem with the product partner, which is the manager's job whatever happens with the engineer. A date eight weeks out is set to look at the evidence together. If delivery still falls short once expectations are clear and support is real, a formal plan will then be fair. The senior manager says so now, so that the manager does not take the refusal as protection for the engineer.

The senior manager keeps one thing for themselves, the observation about the manager. A manager who reaches for a formal plan before setting expectations has revealed a gap of their own. The senior manager records it as an item for the manager's development and for their own reading of the manager's performance over the next two quarters.

• PL-2 Feedback and difficult conversations: the feedback that comes before any performance conversation, and the difficult conversation itself.
• PL-6 Leading through leaders: managing the performance of managers, and quality control on how they manage performance.
• CC-5 Values, integrity, and ethical judgment under pressure: the high performer whose behaviour breaches the team's values, and the costly right call.
• CC-3 Inclusive practices and equitable opportunity distribution: opportunity as part of compensation, and the equity problem inside performance decisions.
• PL-3 Hiring and onboarding: the hire that is not landing, and the early intervention that comes before any formal step.

1. Why is skill, will or conditions the first diagnostic question?
   Answer

   The responses are entirely different: teaching and support for a skill gap, expectations and consequences for a will gap, and fixing what the person was not given for a conditions gap. Responding before diagnosing produces the wrong one, and the team sees it.
2. What makes a formal improvement plan fair rather than paperwork?
   Answer

   A clear bar the person already knew, specific support, a defined duration, a stated outcome at the end, and a real chance of meeting it. A plan written after the decision has been taken is the opposite of fair, and everyone can tell.
3. A manager brings you a formal plan for an engineer who was never given clear expectations. What do you do, and what does it tell you about the manager? org
   Answer

   Decline the plan, coach the manager to set expectations and give documented feedback first, and set a date to look at the evidence again. It shows the manager has a skill gap in performance management, which becomes an item in their own development and in your reading of their performance.
4. How do you read a manager's performance, and why not from their status reports?
   Answer

   From sustained team health, sustained delivery and how results were achieved, over at least two quarters and in context. Their own reports are the most filtered source there is, and a manager's output is the output of their team.
5. Two of your managers cannot agree on the rating for an engineer who worked across both their teams. What is the resolution, and what are the two wrong ones? org
   Answer

   A joint review of the evidence against the shared standard. One wrong resolution is seniority, where the more senior manager's view wins. The other is splitting the difference, which rates the negotiation instead of the person.
6. A vice-president hits every number and leads through fear; capable leaders keep leaving beneath them. What exactly is the performance problem, and what does delay cost? exec
   Answer

   The methods are the problem. The present number is being bought with the organisation's future capacity, and the results do not offset that. Delay costs the pipeline of leaders who leave, and teaches everyone that results buy exemption from how they were achieved.
7. A leader you publicly backed is clearly failing. What is the credibility move? exec
   Answer

   Act on the evidence. Executives who double down to protect the appointment lose both the organisation and the reputation they were trying to protect. Acting is what credibility looks like here.
8. A long-tenured director whom the organisation has outgrown is loyal to you personally. What are they owed? exec
   Answer

   Honesty: an explicit conversation, and either a role reshaped around their real strengths or a transition with dignity. Tenure earns respect and candour and does not earn permanent scope. Quiet marginalisation is a form of neglect.

• Max Landsberg, The Tao of Coaching: Boost Your Effectiveness at Work by Inspiring and Developing Those Around You (1996): the skill and will diagnostic.
• W. Chan Kim and Renée Mauborgne, Fair Process: Managing in the Knowledge Economy (1997): engagement, explanation, clarity of expectation.
• Andrew S. Grove, High Output Management (1983): a manager's output as the output of their organisation.