Directory · T
New here? Start with the premise →
Teams
3 min read · 676 words
Teams are coordinated configurations of multiple operators directed at outcomes no single operator could produce alone. The coordination itself is an operation, separate from the work the team is performing.
The hardware was built for small-group coordination. Operators in earlier body suits operated in bands where the coordination was tight, roles were clear, and the consequences of poor coordination were immediate. The modern team environment often runs at scales the hardware was not optimized for, with coordination overhead consuming much of the capacity that would otherwise go to the actual work.
TWO COMMON MISREADS
Assembling capable operators ≠ capable team output. The assembly is one input. The coordination — how the operators communicate, how decisions get made, how conflicts get resolved, how work gets distributed and integrated — is a separate input, and often the determining one. The team of capable operators with poor coordination produces less than the smaller team of less capable operators with strong coordination.
Optimizing for individual performance at the expense of team output. The operator who completes their assigned work brilliantly while making the next operator’s work harder has produced negative net output for the team. The configuration that warrants attention: what does the next operator in the chain need from this operator’s work in order to do their own well?
ASSESSING THE COORDINATION
For the team configurations the inhabitant participates in:
- Is the coordination overhead matching the complexity of the work, or is it consuming capacity that should be going to the work itself?
- Are the communication channels appropriate to what is actually being communicated?
- Are decision rights clear, or are decisions stalling because no one is sure who decides?
- Are handoffs between operators working, or are dropped balls accumulating?
- Is conflict being addressed when it arises, or being allowed to compile?
The team that holds five meetings per week to coordinate work two emails could coordinate has miscalibrated. The team that operates without coordination on work that requires coordination has miscalibrated in the other direction.
FOR UNDERPERFORMING TEAMS
Examine the coordination operations first.
The communication channels. The decision rights. The handoff procedures. The conflict resolution mechanisms. The improvements often come from reducing friction in these rather than from individual operators trying harder at their own pieces. The team running with good coordination produces more than the team of harder-working individuals running with poor coordination.
This is often counterintuitive. The instinct under team underperformance is to push the individuals harder. The leverage is usually somewhere else — in the structure of how the work flows between operators, where the bottlenecks actually live, and what coordination work has been quietly absent.
SOLO WORK AND TEAM PRACTICES
The inhabitant who works alone often has the option to import some team practices to improve solo output.
Scheduled check-ins with a peer. Regular external review of work product. Deliberate handoffs at completion of work segments. The structure that a team would provide can be partially constructed for solo work, with substantial returns. The inhabitant working alone without any of these often loses what coordination provides — the external pressure of accountability, the feedback loops that a team supplies, the partial review of work that catches what the inhabitant alone misses.
WHEN TO DISBAND
Some teams outlive their function and persist through institutional inertia.
They consume the time of the operators in them while producing little. The original purpose has been served or has shifted; the team configuration has not updated. The functional response: ask whether the team configuration still serves the outcome it was assembled for, and if not, propose its restructuring or dissolution.
The inhabitant who has been on such a team often experiences the time as drained without being able to name what is wrong. The naming — this team has outlived its function — is sometimes the operation that allows either renewal of purpose or clean exit, both of which are better than the continued running of a configuration that has stopped producing what it was assembled to produce.
The team is the coordination, not just the operators.