Teams Are Valuable Because People Are Incomplete

The purpose of a team is not to assemble perfect individuals, but to combine perspectives no single person can hold.

Organisations spend considerable effort trying to make individuals complete. Leadership models list what a senior person should possess: strategic thinking, decisiveness, empathy, commercial judgement, analytical ability, resilience and the capacity to inspire. Development plans identify the gaps and try to close them. The ideal is understandable, but it raises an awkward question. If each individual is eventually expected to contain every capability that matters, what is the team for?

Teams are useful precisely because people are incomplete. One person sees detail another ignores; one is comfortable challenging an assumption while another notices the social cost of doing so. Someone understands the customer, someone the equipment, someone the economics and someone the history of why the current arrangement exists. These differences are not defects to be trained away before collaboration can begin. They are much of the reason collaboration has value.

Difference does not guarantee good judgement. It can just as easily produce friction, misunderstanding and competition for status, and a team gains from diverse perspectives only if those perspectives are allowed to change the discussion. Inviting a specialist into a meeting and then forcing every contribution through the language of the dominant function creates the appearance of diversity without its benefit.

Competency models carry a related risk. They help identify development needs, but they also judge each person against an imagined complete performer. Someone with unusual depth in one area and obvious weakness in another looks less attractive than a balanced candidate who is adequate in both. Repeated across a team, the result is a group of well-rounded individuals who share remarkably similar blind spots.

A different approach begins with what the group as a whole needs to see. Which perspectives are essential to the decisions ahead? Where is the team exposed to shared assumptions? Which form of disagreement is missing because everyone was selected through the same filters? These are questions of composition rather than individual perfection, and they change what leadership means. The leader’s task becomes less about being the most capable person in the room and more about ensuring the room contains the capability the situation requires: that a junior person can contradict a senior one, that technical expertise survives commercial pressure and that commercial reality can challenge technical elegance.

This explains why teams sometimes deteriorate after sensible attempts to professionalise them. Roles are tightened, reporting is cleaned up and individual performance becomes easier to assess, yet the informal connections through which people compensated for one another weaken. The organisation gains clarity and loses some of the redundancy and mutual correction that made the group resilient. The lesson is not to romanticise informality, since teams still need accountability and structure. It is to distinguish structure that helps different perspectives interact from structure that standardises them until the differences no longer matter.

Individual development remains important, but it should not assume that every weakness must be removed before a person is valuable. Some weaknesses are best covered by another person’s strength, and some strengths become dangerous when nobody nearby sees what they miss. The strongest team is not the one with the strongest version of every individual, but the one whose incomplete views fit together into a more complete picture than any of them could hold alone.