"The Purpose of an Organization Is to Enable Ordinary People to Do Extraordinary Things" — Peter Drucker on Designing Teams That Win Without Geniuses

'Enabling Ordinary People to Do Extraordinary Things' — What Drucker Saw in Organizations

Peter Drucker defined the reason organizations exist in a single line: 'The purpose of an organization is to enable ordinary human beings to do extraordinary things.' It is a quiet sentence, but it puts a sharp question to anyone who works on a team. If your team only performs when an unusually talented person happens to be in the room, then it has not actually been designed as an organization.

We tend to think, 'If only we had a star.' Drucker's view runs the other way. Results do not come from having brilliant people; a team's real strength is whether it is built so that ordinary people doing ordinary work produce extraordinary outcomes. Managing a team while waiting for a genius means nothing happens until the genius arrives.

And almost every real workplace is made of an ordinary you and ordinary colleagues. That is exactly why this question is not somebody else's problem. The quality of your results starts to change the moment you stop demanding the extraordinary from people and start demanding it from your design.

Placement, Not Talent, Decides the Outcome

Drucker left another well-known principle: build on strengths. Hauling weaknesses up to average costs enormous effort and produces almost nothing extraordinary. Move an existing strength to the right position, however, and the same person starts functioning like someone else entirely.

Gallup's long-running employee research has repeatedly shown that people who feel their manager focuses on their strengths are dramatically more engaged than those who do not. The sequence matters: people do not perform where they are appreciated, they get appreciated once they are placed where they can perform.

The trick in thinking about placement is to look at people through verbs, not job titles. Is this person fast at digging up information? Naturally good at consolidating? At ease standing between people and smoothing things over? Two people with the same title of 'planner' will move work through the team at very different speeds depending on who drafts the structure and who writes the final version. You don't have to raise anyone's ability; simply swapping the order and the owner moves the result.

Role Ambiguity Quietly Weakens a Team

In 1913, the French agricultural engineer Maximilien Ringelmann measured how hard individuals pulled on a rope. As group size grew, individual output fell: roughly 93 percent with two people, about 85 percent with three, and down to around 49 percent with eight. The phenomenon later became known as the Ringelmann effect, or social loafing.

What matters is that this is not a story about laziness. As a group grows, your own contribution becomes harder to see, and the thought 'someone else will probably handle it' arises automatically. Slacking is not a character flaw; it is a design flaw.

The countermeasure is simple: attach one name to one piece of work. 'We'll all do it' is, very often, another way of saying no one will. A decision that leaves owner, deadline, and definition of done blank evaporates the instant everyone walks out of the room.

Making contribution visible helps too. The Ringelmann effect is strongest when people feel their output is invisible to everyone else. Conversely, when who has moved what how far is visible at a glance, loafing quietly declines. The order matters here: you share progress in order to make it visible, not in order to blame anyone for it. On teams that keep that order, visibility functions as reassurance rather than surveillance.

Systems Multiply What Ordinary People Can Do

In The Checklist Manifesto, the surgeon Atul Gawande describes what happened when the WHO's surgical safety checklist was piloted at eight hospitals around the world: postoperative deaths fell by roughly half and complications dropped sharply. No one made the surgeons more skilled. Someone simply wrote down the order in which things should be confirmed.

That is precisely the power Drucker meant by 'organization.' You take what used to depend on individual memory and goodwill and move it into a system. Then people of average skill start producing above-average results, reliably.

Konosuke Matsushita prized the phrase 'gather the wisdom of many.' The idea is that a mechanism for pooling many people's knowledge beats any single genius's judgment. The key word, though, is mechanism — not the wish to pool knowledge. Deciding who speaks in what order, requiring at least one dissenting view, condensing the discussion into a single shared page: unglamorous formats like these are what actually put collective wisdom into circulation.

Systems have one more benefit that gets overlooked: resilience to turnover. A team whose procedures live only inside someone's head stops on the day that person is out. A team whose procedures are written down can put a new member to real work by day three. That continuity — the reproducibility of results without dependence on any particular individual — is exactly what Drucker meant by the word organization.

What I Noticed on an Afternoon a Meeting Ran Thirty Minutes Over

A personal aside. Some time ago a meeting ran a full thirty minutes past its slot and still broke up without anything resembling a conclusion. No one had objected. Everyone agreed on the direction. And yet, walking out of the room, I noticed the air never quite lightened.

The next day, the matter had not moved a millimeter. The reason was almost comically simple: we had decided to do it, but never decided who, or by when. Worse, I was one of the people who had quietly assumed somebody else would pick it up. I still remember how uncomfortable that realization felt.

After that, I started using the last three minutes of meetings to write a name and a date beside each decision. Three added minutes, nothing more. The following mornings looked completely different. Nobody had changed — only the way decisions were written down had — and I remember finding that faintly strange.

Four Practices for Extraordinary Results From Ordinary Members

First, attach one name to one piece of work. Put owner, deadline, and definition of done into words on the spot, and leave it as a line of text rather than a verbal understanding. Even just asking at the end of a meeting, 'Whose task is this, and by when?' will do.

Second, take inventory of strengths. Ask each member to name three tasks they do quickly, three they enjoy, and three that drain them. Then look for draining tasks that can be traded for someone else's strong ones. Every successful trade increases the team's total output.

Third, externalize what worked. Don't leave a successful approach inside someone's head; convert it into a checklist or template. The more judgment a job requires, the more the non-judgment parts should be handed to a system — that is what raises the quality of the judgment itself.

Fourth, aim your post-mortems at systems, not people. Ask not 'why couldn't that person do it' but 'how would an ordinary person avoid failing in the same situation.' The first question produces defensiveness; only the second produces prevention.

Is Your Team a Vessel That Produces the Extraordinary?

Drucker's line hands us reassurance and responsibility in the same breath. The reassurance: you don't have to be an extraordinary human being. The responsibility: building the vessel in which extraordinary things happen is on us.

Hiring a star is largely luck, but clarifying ownership and writing procedures down are available to you today. And curiously, in teams where that vessel is in place, members everyone assumed were unremarkable begin to shine one after another. Perhaps the extraordinary was inside them all along, invisible only because no vessel existed to hold it.

Try turning the last three minutes of today's meeting into time for writing names and dates. Building the vessel that lets ordinary people do extraordinary things starts somewhere that small.