Why Calling a Star Performer a “Genius” Can Ruin Them

Praise is a powerful signal that moves people. However, statements that define a person’s ability and identity—such as “You’re the best,” “You really are the ace,” or “You’re a genius”—can produce results that differ from what was intended. This is because team members may focus less on the work itself and more on the pressure to “maintain the perception that I’m competent again this time.”

That does not mean praise should be eliminated. The key is to reduce praise that grades people and replace it with recognition that identifies behaviors and judgments they can use again.

“Genius” Is an Identity Judgment, Not an Explanation

The word “genius” compresses a complex process of success into a single innate ability. It gives the whole person a high rating without explaining what was observed or which actions were effective.

Team members who repeatedly hear such expressions may feel the following pressures.

• They are expected to do well on easy tasks, while failure on difficult tasks becomes evidence of insufficient ability.
• Saying they do not know something or asking for help may feel as though it will cost them their reputation as the ace.
• They may choose tasks with a high likelihood of success over tasks that require trial and error.
• They may overestimate individual talent rather than the collaboration and environment that produced the results.
• Colleagues may also think, “The ace will take care of it,” instead of scrutinizing that person’s judgment.

In fiction, simply establishing a character as a “genius” can quickly convey that character’s extraordinary nature. Real organizations need observable judgments, actions, and results, not a character premise. A genius label that is not demonstrated through actual behavior can become a burden for the individual and look like unfair preferential treatment to colleagues.

What Research Says—and Does Not Say

In research by Carol Dweck and Claudia Mueller, children who were praised for intelligence after completing a task were more likely than children praised for effort to choose goals aimed at proving their performance, and they showed less favorable responses in persistence and performance after failure. The year of publication can be confirmed in the original study. This research is widely cited as evidence that ability-focused praise such as “You’re smart” can create motivation that is vulnerable in the face of challenges.

However, these findings should not be applied directly to every employee and every form of praise.

1. Participants in the representative experiments were children. These were not experiments that directly tested adult work environments.
2. The effects of praise vary not only with wording but also with relationships, trust, whether it is public, evaluation systems, and reward structures.
3. Process praise is not helpful if it sounds vague or controlling.
4. Workplace field studies have also examined the effect of recognition on actual performance, but findings from a particular design cannot be generalized to every organization.

Review papers synthesizing praise research explain that praise is not a simple stimulus that invariably raises or lowers intrinsic motivation. What matters is whether recipients interpret the words as information about their competence, interpret them as control and evaluation, and believe them to be sincere.

How Are Recognition, Praise, and Feedback Different?

These three terms are used interchangeably in everyday life, but they serve different functions.

A good leader’s words connect all three functions. They recognize the contribution, provide the observed evidence, and leave information that can be used in future actions.

Four Principles of Effective Praise

1. Describe Observed Behavior Rather Than Personal Traits

Instead of saying, “You’re meticulous,” explain what you saw that led you to that conclusion.

• Vague wording: “It’s perfect, as expected.”
• Specific wording: “By checking again with three types of user permissions before deployment, you found an access error.”

Specific praise tells team members which behaviors they should repeat. It also gives colleagues clues for learning how success was achieved.

2. Connect Behavior to Its Impact

Merely listing behaviors can make people feel watched. Connect the behavior to the impact it had on customers, the team, quality, or the schedule.

• “Because you grouped customer questions by type, the support team did not have to repeatedly write the same answers.”
• “By asking for opposing views first, you helped us identify a risk that the meeting almost overlooked.”

Do not exaggerate the impact; describe it only to the extent that it can be verified. Results with difficult-to-confirm causal relationships, such as increased sales, should not be attributed solely to one person.

3. Recognize Effective Processes and Judgment

Process praise does not simply mean saying that someone “worked hard.” It means identifying the strategies and corrective actions that were effective.

• Forming a hypothesis and testing it through a small experiment
• Sharing an error quickly instead of hiding it
• Revising a draft to reflect customer feedback
• Reducing bottlenecks by transferring information to colleagues
• Recording the cause of a failure and changing the next attempt accordingly

Telling someone who has repeatedly used an ineffective method for a long time, “It’s fine because you made an effort,” may communicate low expectations. Rather than focusing only on the amount of effort, consider the quality of the strategy, learning, and adjustment together.

4. Deliver It as Close to the Event as Possible, Using Consistent Standards

When little time passes between the behavior and the praise, team members can more easily understand which moment is being discussed. Rather than waiting until the end-of-quarter review, it is more useful to briefly acknowledge it immediately after the work is completed.

However, “immediate” does not mean “impulsive.” If the facts need to be confirmed or emotions are running high, speak after sorting things out. For someone who feels uncomfortable with public praise, a private message or one-on-one conversation may be more appropriate.

Consistency also does not mean praising everyone the same number of times. It means recognizing contributions according to previously shared work standards rather than rank or personal closeness.

A Practical Sentence Structure for Praise

Connecting the following three elements in order makes it easier to speak specifically without exaggeration.

Observed situation and behavior → Confirmed impact → Point to reuse or expand

Here are some examples.

• “In today’s report, you clearly labeled uncertain figures as estimates. That allowed decision-makers to distinguish confirmed values from assumptions. Please use the same labeling method in the next report.”
• “Even before identifying the cause of the incident, you shared the current status first. That allowed the support team to inform customers about the delay early. Next time, let’s also record the initial items checked.”
• “During the meeting, you asked the new team member for their opinion again. We identified a usability issue that the existing proposal had missed. Please continue seeking input from people in different roles at the next planning meeting.”

If it is difficult for the leader to prescribe how the approach should be replicated, they can end with a question.

• “Which judgment was most effective this time?”
• “Which approach would you like to maintain in the next project?”
• “What should we document so the team can use this method together?”

What Can Be Recognized Even When the Result Is Poor?

Praising a failed result as if it were a success erodes trust. Conversely, treating every part of the process as worthless when the result is poor encourages team members to hide risks and choose only safe tasks.

In cases of failure, separate the result, the effective behavior, and the point for improvement.

• Result: “Our proposal was not selected by the customer this time.”
• Recognition: “It was good that you asked the customer for the reason immediately after the decision and shared it with the team.”
• Improvement: “Next time, let’s confirm early not only the price but also the internal personnel required for implementation.”

Do not stop at “It’s okay because you did your best.” Confirm what was learned and what will be changed in the next attempt. This is how to preserve psychological safety without glorifying failure.

When Praise for an Ace Becomes a Structural Risk to the Team

Repeatedly labeling one person as the ace creates a problem that extends beyond individual motivation. If work and decision-making authority become concentrated in that person, it can grow into an operational risk for the organization.

Protecting a true ace does not mean giving that person more work and attaching grander labels to them. It means turning that person’s judgment and knowledge into team capabilities and ensuring the work continues even in their absence.

Praise Leaders Should Avoid

• Comparative praise: “Unlike the other team members, you’re clearly smart.” This may only reinforce competition and hierarchy.
• Exaggerated praise: Calling a minor correction “the best result in company history” reduces the credibility of future recognition.
• Controlling praise: “A good employee should naturally do this.” It looks like recognition but demands obedience.
• Praise with an ulterior motive: If additional work is repeatedly assigned immediately after praise, recognition will be interpreted as a signal that more work is coming.
• Credit-monopolizing praise: Explaining a result created by several people as the genius of one highly visible individual.
• Linking character to results: Expanding one success into “You’re destined to succeed,” or one failure into “As expected, you lack ability.”

How to Turn Praise into Organizational Learning Data

Do not stop at saying something positive to an individual. The behaviors that produced success can be retained as team knowledge. This is a separate operational mechanism that reduces dependence on “one genius.”

1. Record the praised behavior in one sentence in the retrospective notes.
2. Identify both the conditions and the collaborators that produced the result.
3. Organize repeatable methods into checklists or case examples.
4. Include early warnings, documentation, verification, and peer support—not just results—as items worthy of recognition.
5. Regularly examine who is frequently recognized and who is left out to check for bias.

The goal of praise is not to require team members to “keep looking like a genius.” It is to help them understand what they did well, ask questions and learn even when facing difficult problems, and share their methods with colleagues.