An engineer can deliver difficult work and still make the surrounding team less effective. Colleagues stop asking questions, reviews become confrontational, or people avoid a discussion until a small issue becomes expensive to resolve.
The spiky colleague among balloons is fictional. Its uncomfortable point is that an individual performance review can miss consequences experienced by everyone else. Those consequences deserve investigation rather than either automatic excuse or instant judgment.
Name the behavior instead of assigning a label
Start with observed actions and their effects. “Difficult personality” is too vague to act on fairly. A specific account of interrupting a colleague, dismissing a question, or using humiliating language gives the person something concrete to understand and change.
Separate sharp technical disagreement from mistreatment. A strong objection can protect a product. Discomfort with a challenged idea does not, by itself, establish poor behavior. Ask what happened, seek relevant context, and avoid relying only on the loudest account.
Netflix's culture memo rejects exceptional ability as an excuse for treating colleagues poorly. That is a corporate cultural position, not a controlled study or a universal personnel procedure. Its relevance is the standard it asks leaders to make explicit.
Include collaboration in the performance conversation
Discuss both the person's contribution and the conditions their behavior creates. Can teammates obtain help? Can a reviewer raise a concern? Does the engineer share knowledge or become a permanent bottleneck? Use concrete examples, including positive ones.
Be clear about expectations and support. Explain what needs to change, how improvement will be observed, and what help is available. Follow the organization's established people processes when an issue is serious. A public argument or a vague warning is unlikely to create a fair, useful evaluation.
Do not quietly ask colleagues to absorb the problem indefinitely because replacing the engineer would be inconvenient. That decision also has consequences, even when they do not appear in an individual output count.
Examine the dependency behind the exception
Sometimes leaders excuse behavior because one person holds essential knowledge. That is also a system issue. Documentation, shared ownership, pairing, and additional senior capacity can reduce dependence without denying the person's technical value.
Avoid making knowledge sharing a punishment. It should be a normal part of sustaining the product and developing the team. Recognize people who make others more capable, not only those who repeatedly rescue work that only they understand.
Use hiring to reinforce the standard
Assess how candidates explain disagreements, respond to feedback, and collaborate on a realistic problem. Ask for examples and use consistent criteria. A friendly interview alone is not evidence of effective teamwork, just as a blunt speaking style is not proof of harmful behavior.
EnzRossi combines technical screening with soft-skill evaluation for senior LATAM talent. Discuss the working standards your team needs. Engineering excellence includes producing good work and helping create a team in which other people can do the same.
