Skip to main content
Steady at the Top
← All articles

When one impressive result distorts your view of a leader

When one impressive result dominates a leadership evaluation, separate the role’s requirements and examine evidence for each one. Keep the result as relevant evidence while checking what it does and does not demonstrate. A strong commercial win, for example, cannot by itself answer questions about delegation, judgment, or conduct.

The halo effect is the influence of a general impression on judgments of separate characteristics. In his 1920 paper on psychological ratings, Edward Thorndike described how a broad favorable or unfavorable impression could color ratings across dimensions. The paper provides a reason to examine separate evidence, not a formula for scoring modern executives.

The practical issue for a CEO is scope. An accomplishment may be important enough to change the evaluation. It should change the dimensions it supports, without silently supplying evidence for everything else.

The separate-evidence review below is a proposed management method. It is not a validated leadership assessment or a substitute for qualified employment advice.

Notice when an achievement starts answering unrelated questions

In this explicitly composite scene, a founder reviews a division leader before a succession discussion while waiting for a family member to finish an appointment. Their notes occupy the seat beside them instead of staying closed for the afternoon. The leader recently secured an important commercial agreement. The founder can recall the negotiation in detail, including the pressure it relieved. Other parts of the evaluation remain vague.

When asked about developing managers, the founder returns to the agreement. When asked about operating controls, the same accomplishment appears again. The achievement matters, but the discussion has begun using it as evidence for questions it cannot answer alone.

The correction is not to discount the result. It is to ask which role requirements the result demonstrates, what supporting evidence exists, and where the company still needs information.

Place the review within a consistent CEO decision system. Evidence standards should be clear before a particular leader’s successes or difficulties become the center of attention. Otherwise, the review can become a justification for an impression already formed.

The separate-evidence review

1. Define the role requirements before discussing the person

Write the responsibilities that matter for the role under review. Include the relevant commercial outcomes, operating duties, people responsibilities, and conduct expectations. Use requirements the company can explain and apply consistently.

Distinguish the current role from a possible next role. A leader may excel at personally closing major agreements while having little documented experience building a management team. That is an evidence gap about the next role, not a reason to erase the current accomplishment.

Avoid an exhaustive list that nobody can assess meaningfully. Choose a manageable set of requirements tied to actual work. Define what acceptable evidence would look like for each.

For consequential hiring, promotion, compensation, or dismissal decisions, obtain qualified employment counsel and appropriate internal review. This article provides general evaluation guidance. It does not determine lawful criteria or procedures for a particular organization.

Check whether the requirements were communicated and whether the person had a reasonable opportunity to demonstrate them. A newly invented expectation should not be presented as a long-standing failure without examining the context.

2. Put each observation in the dimension it supports

Create an evidence table with a row for each requirement. Record the observation, its source, the period covered, and its relevance. Describe what happened before assigning a broad label such as strategic, collaborative, or decisive.

A negotiated agreement might support evidence about commercial judgment, preparation, or stakeholder coordination. The record should identify which behavior the evaluator observed rather than assuming all three occurred because the result was favorable.

Separate direct observation from secondhand reports. Secondhand evidence can matter, but its source and limitations should remain visible. Do not repeat an allegation as an established fact because several people have heard the same original story.

Also distinguish absence of evidence from evidence of poor performance. The evaluator may not have observed delegation because the role provided little opportunity to demonstrate it. That uncertainty requires a different response from a documented pattern of taking work back from managers.

Thorndike’s paper concerns the problem of broad impressions affecting specific ratings. Applying that caution here means making each judgment explainable. It does not require pretending that role dimensions never interact.

3. Review the decision process separately from the result

Ask what the leader knew, what alternatives were available, and how the relevant choice was made. Use records created before the result where possible. A successful outcome can arise from a sound process, favorable circumstances, or some combination.

Baron and Hershey’s 1988 outcome-bias experiments examined judgments of decisions after people learned the outcomes. Their findings support caution about treating a good outcome as conclusive evidence of good decision quality. They do not imply that outcomes are irrelevant to evaluation.

For the commercial agreement, review the approved limits, unresolved risks, and commitments made. A favorable headline may coexist with obligations that the company still needs to understand. Conversely, an unfavorable result may follow a defensible choice under uncertainty.

Use hindsight bias in performance reviews as a related check. Information learned later should not be inserted into an account of what the leader should have known earlier.

Keep process and outcome visible in the same evaluation. The goal is a fuller judgment rather than replacing a results-only review with a paperwork-only review that rewards documentation regardless of performance.

4. Seek relevant counterevidence without collecting gossip

For each preliminary judgment, ask what observation would challenge it. If the leader appears strong at delegation, examine work that required others to act without their direct intervention. If the judgment concerns operating discipline, review relevant commitments and follow-through.

Choose sources because they have observed the work, not because they are likely to agree with the evaluator. Give reviewers a defined question and an appropriate confidentiality boundary. Avoid an open invitation to share personal impressions about the individual.

Protect sensitive records and limit access to people who need them for the authorized review. The article’s method does not authorize covert surveillance, unrestricted message searches, or informal investigations.

Lerner and Tetlock’s 1999 accountability review describes how the effects of having to justify a judgment depend on the arrangement. Asking evaluators to explain themselves is useful only when the review criteria support an honest examination rather than a performance for a powerful audience.

Invite evidence that changes the assessment in either direction. A process that only searches for weaknesses after a standout success can become a different form of distortion.

5. Compare evidence strength before assigning an overall judgment

Review each dimension independently before discussing the overall recommendation. Note confidence and gaps. Avoid averaging unlike dimensions automatically, especially when a requirement is essential to the role.

A strong commercial result may carry considerable weight in a commercially focused role. It may not compensate for an unresolved legal requirement or a documented conduct issue. Identify which dimensions allow tradeoffs and which require separate action.

The proposed discussion script is: “This accomplishment supports these conclusions. These other conclusions require different evidence. Here is what we know, and here is what remains untested.” These words are a suggested management script, not a source quotation.

Use status comparison and executive judgment to examine whether reputation or comparison with a more visible peer is influencing the review. Visibility can affect which evidence comes to mind without establishing relevance to the role.

If the evaluation remains uncertain, state that uncertainty. Do not translate a thin record into a precise score merely because the form contains a numerical field. Explain what additional observation could make the judgment more reliable.

6. Choose an action that fits the evidence

Decide whether the record supports recognition, a development assignment, a changed scope, further observation, or another authorized action. Keep the recommendation connected to the specific requirements rather than a broad story about the person’s potential.

For a possible promotion, a bounded assignment may provide evidence about responsibilities the current role has not tested. Define the assignment, support, decision authority, and review period. Do not promise that an informal test replaces the company’s formal selection requirements.

For a development need, describe the behavior to change and the support available. “Become more executive” is too vague to guide work. A clearer request specifies which decisions the leader should delegate and how the company will observe the change.

Preserve the impressive result in the final record. Correcting a halo effect should not become an effort to diminish achievement. The review should explain both the contribution and the limits of the inference drawn from it.

Confirm that any employment action follows the applicable process and professional advice. Evidence discipline improves the discussion; it does not remove legal obligations or replace responsible judgment.

Apply the same check to a negative impression

A disappointing result can also dominate unrelated judgments. An evaluator may begin treating a failed launch as proof that the leader lacks every important capability. The same separate-evidence approach can reveal which conclusions the record supports.

Do not force symmetry where the evidence differs. A serious conduct issue may require immediate action under the company’s procedures. A missed commercial target may call for a different review. The method separates questions so each receives an appropriate response.

Ask whether the evaluator can describe a strength and a limitation with equally concrete evidence. The purpose is not to manufacture a balanced scorecard. It is to check whether a general feeling has replaced examination of the actual work.

Make the final explanation specific

A useful evaluation names the relevant achievement, the responsibilities it demonstrates, and the requirements that need separate evidence. It explains the action without claiming certainty about the person’s entire character.

Give the leader an appropriate opportunity to correct factual errors through the company’s process. Maintain a distinction between disagreement with a judgment and an inaccurate observation in the underlying record.

One accomplishment can deserve recognition and still leave important questions open. A disciplined review honors the result by describing it precisely, then gives the remaining leadership requirements their own evidence and decision.

Sources

Steady at the Top