Most problems of work are sociological, not technological. But most managers spend their time on convoluted technical puzzles as if they were going to do the work rather than manage it. The manager’s function is not to make people work but to make it possible for them to work.
Simple Picture
A manager who cannot tolerate uniqueness in their team is like a gardener who pulls up every plant that does not match a template. The garden ends up orderly — and empty. The work of management is creating the conditions under which people coordinate themselves, not imposing coordination from above.
The Sociology of Work
A novice manager believes work can be completed without people’s emotions getting involved. Anyone with experience has learned the opposite. The major arouser of emotions at work is threatened self-esteem. When a person’s sense of competence is at risk — from bad estimates, from quality pressure, from being treated as interchangeable — the emotional response overrides everything else.
This is the feedback pipe problem at the team level: threatened self-esteem closes the pipe. No signal gets through until the threat is addressed. And the threats most managers create — unreachable deadlines, annual merit reviews, enforced uniformity — are precisely the ones that threaten self-esteem most directly.
The need for uniformity is a sign of insecurity on the part of management. It becomes difficult or impossible to hire the one person who matters if that person does not look like the rest. The term “unprofessional” is often used to characterize surprising and threatening behavior. Conversely, “professional” means unsurprising — you are considered professional to the extent that you look, act, and think like everyone else. A perfect drone.
People require a sense of uniqueness to be at peace with themselves, and they need to be at peace with themselves to let the team-jelling process begin. When management stifles uniqueness, it expresses itself across uncontrolled dimensions — someone takes perverse pride in being difficult to manage or hard to motivate. He may be reacting to too much control. This is boundaries at the organizational level: suppress a person’s legitimate self-expression and it re-emerges as resistance.
Methodology as Anti-Thinking
A Methodology is an attempt to centralize thinking, destroying self-healing capacity. Implicitly it says that people aren’t smart enough to do the thinking.
Defensiveness is encouraged when you try to systematize the process, imposing rigid methodologies so that key strategic decisions cannot be made lest they be made incorrectly. This is the Agile critique stated a generation earlier: the methodology strips ownership and replaces judgment with compliance. Voluminous documentation is part of the problem, not the solution — nothing is more demotivating than the knowledge that management thinks you incompetent.
The result is malicious compliance: if people did exactly what the Methodology said, process would grind to a halt. The OSS sabotage manual describes the same behavior — insisting on following every procedure to the letter — except Peopleware reveals that well-meaning managers create the conditions for malicious compliance without any saboteur required.
The engineering algorithm captures the lost principle: time should be spent on the key question “ought this thing to be done at all?” Instead, organizations announce it is time to improve, each person interprets “improve” through their own lens, and everyone marches off on personal missions without questioning whether the constraint is where they think it is.
The Jelled Team
A jelled team is when the whole becomes greater than the sum of its parts. The purpose of a team is not goal attainment but goal alignment — and alignment cannot be commanded. It emerges from shared small successes, mutual trust, and the safety to fail. Trust is the transmission medium: in a high-trust team, ambiguity is resolved charitably and mistakes are absorbed. In a low-trust team, even precise communication is misinterpreted — and the overhead of compensating for distrust consumes more energy than the work itself.
What kills jelling:
- Annual salary and merit reviews — the things managers spend the most time on are the most teamicidal
- Competition fostered within teams — a competitive nature is often rooted in childhood emotional undernourishment
- Quality pressure — when management forces a product that does not measure up to the builders’ own quality standards, the team loses the will to look each other in the eye
- Excessive coordination — when you over-coordinate for your people, they under-coordinate their own efforts. A good coach understands that their job is not to coordinate but to help people self-coordinate.
A team jells through frequent closure — small, demonstrable wins. A good manager divides a project into twenty closed iterations when only two are necessary for upper management. Closure builds trust. Trust enables jelling. Jelling produces self-coordination that no amount of external management can replicate.
An insecure need for obedience is the opposite of natural authority. The manager who thinks “I belong to the thinking class; those beneath me carry out my decisions” has confused hierarchy with competence. Any easily separable task requires no management — just get out of the way. The manager adds value only in the spaces where coordination is genuinely ambiguous.
Change and Safety
Change will not even get started unless people feel safe — when they know they will not be demeaned for proposing a change or catch flak for floundering in the inevitable chaos that follows. This is the creativity framework applied to organizations: play requires safety, and organizational change is the highest-stakes play there is.
Organizational learning is limited by the ability to keep people. When turnover is high, learning cannot stick. Attempts to change are futile, or accelerate the exodus. The average cost of replacing a person is five months of salary — but the real cost is the knowledge that walks out the door and the team cohesion that must be rebuilt from scratch.
The mark of the best manager is to single out the few key spirits with the proper mix of perspective and maturity and then turn them loose. Do not wrestle the bull — you cannot. Awaken the sleeping giant: your body of co-workers and subordinates.
Dimwit / Midwit / Better Take
The dimwit take is “management is about setting goals and holding people accountable.”
The midwit take is “management is about removing blockers and optimizing processes.”
The better take is that management is about creating the conditions under which people can do their best work — which means protecting them from the organization itself. The marketplace, clients, and upper management will never make the case for quality that a team needs to jell together. The manager must fight for quality against the very institution they represent. The manager must tolerate uniqueness in a system that rewards uniformity. The manager must create safety in an environment that generates threat. The Gervais Principle would say this is the rare Sociopath who uses their power to shield rather than exploit — and the rarity explains why most organizations are as dysfunctional as they are.
Main Payoff
The deepest insight is the shortest: people perform better when they are trying something new. This single observation invalidates the entire apparatus of standardization, repetition, and process optimization that constitutes modern management theory. The local optimum of the familiar task is stable and measurable — but the energy, creativity, and engagement that come from novelty produce unmeasurable surplus that no metric captures. The organization that cannot tolerate novelty will retain only the people who do not need it — and those people, by definition, have stopped growing.
References:
- Tom DeMarco and Timothy Lister, Peopleware: Productive Projects and Teams