Why collaboration, complementary strengths and discerning leadership matter more than winning an internal competition.
An employee completes an assignment ahead of schedule. The manager is impressed. The employee receives public praise, and another success is added to their performance record. On the surface, everything looks right.
But there may be another story beneath that achievement. Did colleagues receive the information they needed? Did someone quietly repair mistakes before the work reached the manager? Was another employee’s contribution acknowledged? Did the assignment move the organisation forward, or did one person simply become more visible?
These questions matter because organisations can mistake individual visibility for collective effectiveness. When employees begin treating colleagues primarily as rivals, the workplace can become a stage on which everyone is performing and fewer people are cooperating.
Ambition is valuable. Employees should want to grow, produce excellent work and earn recognition. The problem begins when advancement depends on appearing superior to the people whose cooperation the organisation needs.
For leaders, the question must extend beyond, “Did John get the work done?” It must include, “How did the team get the work done, and what did John contribute to that shared result?”
The difference between excellence and internal rivalry
Excellence is a commitment to doing meaningful work well. Internal rivalry becomes destructive when another person’s success is interpreted as a personal loss.
An excellent employee can admire a colleague’s skill, ask for advice and share a useful method without feeling diminished. A person caught in unhealthy rivalry may withhold that same method because helping someone else feels like surrendering an advantage.
The difference appears in everyday decisions. One employee corrects a colleague privately so the final report is accurate. Another waits until the meeting to expose the error. One shares an update promptly. Another holds it back until the manager is present. Both may claim to care about performance, but their choices have different effects on the team.
Not every competitive activity is harmful. A voluntary challenge can generate energy when the rules are fair and people do not need to undermine one another to succeed. Problems arise when essential cooperation conflicts with the way rewards are allocated.
A leader should ask whether a contest encourages employees to improve the work or gives them a reason to obstruct each other. The answer depends on the task, incentives and behaviour it produces.
An organisation is a system of connected contributions
Most organisational results pass through several hands. A sale becomes valuable when the promise can be fulfilled, the customer is supported and payment is collected. A financial report becomes useful when underlying records are reliable and decision-makers understand what the figures mean.
Consider a hypothetical business in which a salesperson promises an unusually fast delivery without checking stock. The sale is celebrated immediately. Procurement must then find unavailable materials, operations rearranges its schedule, and customer service manages the complaints.
If the salesperson is assessed only on booked revenue, they may appear highly effective. Yet the organisation has absorbed disruption, additional costs and damaged trust. An individual measure has concealed a wider problem.
This does not mean that every delay should be blamed on sales. It means that leaders need to trace the complete process before deciding what good performance looks like.
A team becomes stronger when people understand their dependencies. Employees need to know who supplies their inputs, who uses their output and what quality means to the next person. Completing a task is only part of the responsibility; making the result usable is another.
Complementary strengths are an organisational advantage
A team does not need every person to be equally good at everything. It needs relevant strengths that connect effectively.
One employee may identify patterns in complex data. Another may explain those patterns clearly to a customer. A third may notice procedural risks. Someone else may coordinate the work and ensure that decisions become action.
These contributions are complementary when each improves the usefulness of the others. Analysis without communication may never influence a decision. Communication without reliable analysis can create confidence in the wrong answer. Coordination without technical understanding can move a flawed plan forward efficiently.
The leader’s task is to make these relationships visible. Employees should be able to explain both their own contribution and why another person’s expertise matters.
However, complementary roles should not become permanent labels. Calling someone “the quiet detail person” can restrict opportunities just as much as calling another employee “the natural leader.” Strengths should guide assignments while leaving room for development, stretch opportunities and changing interests.
Building around strengths also requires backup. A team is vulnerable when only one person understands a critical process. Sharing knowledge protects continuity and gives colleagues opportunities to grow.
What research contributes to the discussion
Research provides useful guidance, although no single study supplies a universal formula for every workplace.
Amy Edmondson’s 1999 study of 51 manufacturing teams found an association between team psychological safety and learning behaviour. Psychological safety concerns whether people believe they can take interpersonal risks within the team, including asking questions or acknowledging mistakes. The finding supports taking the conditions for speaking up seriously; it should not be read as proof that friendliness alone guarantees results. [1]
Google’s Project Aristotle work identified five dynamics associated with effective teams in its organisational setting: psychological safety, dependability, structure and clarity, meaning, and impact. This combination is instructive because interpersonal trust sits alongside reliable delivery and clear expectations. Google’s findings are valuable organisational evidence, rather than a guarantee that identical practices will work everywhere. [2]
Research by Anita Woolley and colleagues also found that collective intelligence was associated with social sensitivity and a more equal distribution of conversational turns. Their study suggests that how people interact deserves attention alongside the abilities of individual members. These are associations from the study, not a reason to assume that equal speaking time automatically creates an effective team. [3]
For managers, a practical implication is to look beyond the most impressive individual. Examine whether the team can exchange relevant information, raise concerns and combine what its members know.
Leadership discernment begins with observation
Discernment is the ability to distinguish what is happening from what merely appears to be happening. A discerning leader does not automatically confuse confidence with competence, silence with agreement or personal visibility with leadership potential.
In a meeting, the person who speaks first may be well prepared. They may also be preventing others from contributing. The colleague who says little may be disengaged, or may have learned that speaking produces interruption or embarrassment. The same outward behaviour can have different explanations.
Leaders therefore need evidence gathered over time. Observe how employees respond when a colleague receives praise, when responsibility is shared and when a mistake is discovered. Ask people about actual incidents rather than inviting broad accusations about personalities.
Useful questions include: Who shares information without being chased? Who makes work easier for the next person? Who acknowledges assistance? Who raises problems while there is still time to solve them? Whose apparent success repeatedly leaves others with avoidable repairs?
These questions should guide inquiry, not become a secret scoring exercise. Employees deserve a fair opportunity to explain constraints, correct misunderstandings and improve their behaviour.
Understand why rivalry develops
It is easy to blame employees for being competitive while ignoring the system surrounding them. Sometimes rivalry is a rational response to leadership practices.
If managers consistently recognise the person presenting the final result, employees may compete for presentation opportunities. If promotions depend on being indispensable, people may hesitate to train a replacement. If asking for help is treated as weakness, they may hide difficulties until deadlines fail.
Scarce opportunities can intensify these pressures. Employees may reasonably worry that collaboration will make their individual contributions harder to see. Telling them to “be team players” does little to address that concern if recognition remains arbitrary.
Leaders should therefore examine both personal conduct and organisational incentives. Are promotion criteria clear? Is work allocated fairly? Can less visible contributions be demonstrated? Do managers reward knowledge sharing in practice?
A collaborative culture becomes credible when employees can help others without making their own work disappear. Fair recognition and shared success should reinforce each other.
A leadership lesson from Satya Nadella
Microsoft’s published account of Satya Nadella’s leadership approach describes a shift from a “know-it-all” culture toward a “learn-it-all” culture. In that framing, learning and understanding unmet customer needs are central to innovation. [4]
The relevance to teamwork is straightforward. Someone determined to appear knowledgeable may experience a colleague’s correction as a threat. Someone committed to learning can treat the correction as useful information.
For leaders, this suggests modelling curiosity in observable ways. Ask for another perspective. Acknowledge an incorrect assumption. Explain when an employee’s evidence changed your decision. Thank the person who identified a risk before it became a larger problem.
These actions do not remove managerial authority. They show employees that authority can coexist with learning.
This leadership example is not evidence that one cultural principle explains all of Microsoft’s outcomes. Its value here is narrower: it gives managers a practical alternative to a workplace where everyone must constantly demonstrate that they already know best.
Psychological safety must coexist with accountability
Collaboration cannot mean avoiding difficult conversations. A team may be polite while missed deadlines, poor-quality work and unresolved disagreements accumulate underneath the surface.
Employees need room to ask questions and acknowledge uncertainty. They also need clear obligations. When someone cannot meet a commitment, they should communicate early, explain the constraint and help agree on a workable response.
A useful standard is that people can speak honestly about the work while remaining responsible for their part in it. An honest mistake invites investigation and learning. Repeated disregard for an agreed process requires a different response. Deliberate concealment should not be excused as an ordinary learning experience.
The leader must distinguish among these situations rather than treating every failure as either a character flaw or an unavoidable accident.
Likewise, an employee who disagrees with a proposal is not automatically uncooperative. Sometimes the colleague willing to challenge a weak assumption makes the most valuable contribution in the room.
Make disagreement productive
A collaborative team needs a way to disagree without turning a work problem into a contest over status.
Begin by identifying the decision. Are people debating a customer promise, an accounting treatment, a project deadline or the allocation of resources? Then clarify the evidence and constraints relevant to that decision.
Employees should be encouraged to explain their reasoning and identify what might change their view. This makes disagreement more useful than simply repeating positions with greater confidence.
Leaders must also establish who decides. Consultation does not mean every decision requires consensus. Once relevant input has been considered, a responsible person should make the decision and communicate the reasoning, ownership and next steps.
Safety, ethical concerns and material new evidence should still have an appropriate escalation route. Cooperation should never require employees to suppress a serious concern merely because a discussion has ended.
The objective is a decision that benefits from the team’s knowledge and can then be implemented coherently.
Recognise individual contributions within shared results
Collective success and individual recognition can coexist. In fact, fair recognition helps sustain collaboration because employees know that helping the team will not erase their contribution.
Consider a hypothetical month-end close. John prepares the reconciliation, Mary resolves a supplier discrepancy, and Aisha identifies a duplicate entry before the reporting deadline. Praising only John because he submitted the final document creates an incomplete account of the work.
A stronger response identifies each contribution and explains the result they produced together. This gives credit accurately while helping the team understand how its work connects.
Leaders should also recognise preventive work. A clear procedure, a reliable handover or early identification of an error may attract less attention than a dramatic rescue. Yet these contributions can reduce the need for repeated emergencies.
Recognition should be specific. “Good teamwork” is pleasant but vague. Explaining that an employee documented a process so two colleagues could complete it independently tells everyone what behaviour the organisation values.
Measure results and the way results are achieved
Performance assessment should consider both delivery and contribution to the wider team. The appropriate balance will vary by role, but neither dimension should be invisible.
For an accounting team, leaders might examine accuracy, deadlines, unresolved exceptions and the quality of supporting documentation. They might also consider whether handovers are usable, recurring errors are addressed and critical knowledge is shared.
For customer service, a high number of closed tickets means little if customers repeatedly reopen them because the underlying issue remains unresolved. For sales, revenue needs to be understood alongside the feasibility and quality of the commitments made.
These are examples of assessment questions, not a ready-made universal scorecard. Measures should reflect the actual work and should be reviewed for unintended consequences.
Peer feedback can add context, but it should focus on observable behaviour. Ask for examples of useful support or delayed information rather than asking whether someone is “a good team player.” Popularity is an unreliable substitute for evidence.
Address the high performer who weakens the team
One of leadership’s hardest tests is responding to someone who produces strong individual results while undermining colleagues.
Ignoring the behaviour tells everyone that collaboration is optional for people with impressive numbers. Yet acting without careful investigation can also be unfair. A demanding employee may be blamed for raising legitimate quality concerns, or a workload problem may be misread as unwillingness to help.
The leader should document specific incidents, explain their effects and hear the employee’s account. Expectations must then be concrete: share a necessary update by an agreed time, acknowledge contributors, stop personal criticism or train a colleague in a critical procedure.
Provide support where the problem involves skill, workload or unclear expectations. Review progress against the agreed behaviour. Persistent undermining should have consequences consistent with organisational policy and a fair process.
Technical output matters, but it cannot be the only evidence used to decide whether a person strengthens an interdependent organisation.
Protect collaboration from becoming exploitation
There is another danger: capable, generous employees can become the permanent safety net for everyone else.
They train colleagues, repair incomplete work and absorb urgent requests while their own responsibilities remain unchanged. Eventually, “teamwork” becomes an expectation that the most dependable person will carry an unreasonable burden.
Leaders need to recognise this pattern. Review workloads, assign ownership clearly and distinguish temporary assistance from recurring dependency. If someone regularly supports others, that contribution should be acknowledged and reflected in realistic capacity planning.
Employees should also have a professional way to communicate limits: they can explain what they can assist with, what must be reprioritised and where additional support is needed.
A collaborative organisation should strengthen everyone’s ability to contribute. It should not depend indefinitely on a few people sacrificing their time and absorbing preventable failures.
Build collaboration into daily work
Culture becomes tangible through routines. Begin projects with a shared outcome, clear responsibilities and visible dependencies. Agree on where decisions and updates will be recorded so essential information does not remain in private conversations.
Use short progress discussions to identify blocked work and make specific requests for support. Avoid turning every meeting into a performance in which employees list achievements while concealing difficulties.
After important work, review the process as well as the result. What helped? Where did information arrive late? Which handover created confusion? What should change before the next cycle? Assign responsibility for agreed improvements so the discussion leads somewhere.
These practices need proportion. Excessive meetings and unnecessary consultation can become barriers themselves. Coordinate where work is interdependent and allow people space to execute independently where it is not.
The leadership question that changes the culture
An organisation becomes stronger when talented people make one another more effective. That requires ambition directed toward useful outcomes, fair recognition, clear responsibilities and leaders willing to examine how success is produced.
Employees should not have to choose between being recognised and helping colleagues. Leaders should create conditions in which producing excellent work and strengthening the team are both credible routes to advancement.
The next time a manager celebrates an individual achievement, it is worth asking a few additional questions. Who contributed? What happened at the handovers? Were problems surfaced early? Has the team become more capable of delivering the next result?
“Did John get the work done?” remains a legitimate question. “Did John help the team succeed?” makes it a better one.
Editorial note: Workplace scenarios in this article are hypothetical illustrations. Research findings and the leadership example are attributed below. Practical recommendations represent editorial analysis rather than claims that one approach guarantees success in every organisation.
References
- Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383. https://dash.harvard.edu/entities/publication/13a7b031-0fdd-45ec-a7e0-2b80e2bc679f
- Google re:Work. Understand team effectiveness. https://rework.withgoogle.com/intl/en/guides/understand-team-effectiveness
- Woolley, A. W., Chabris, C. F., Pentland, A., Hashmi, N., & Malone, T. W. (2010). Evidence for a Collective Intelligence Factor in the Performance of Human Groups. Science, 330(6004), 686–688. https://pubmed.ncbi.nlm.nih.gov/20929725/
- Microsoft (2017). Microsoft CEO Satya Nadella: AI must be built with empathy. https://ukstories.microsoft.com/features/ai-must-be-built-with-empathy-microsoft-ceo-satya-nadella-says-during-uk-release-of-book-hit-refresh/