What to do instead
Give two people one deadline
Shared responsibility for an outcome produces the conversations that shared membership never does. The mechanism, the version that fails, and why.
The people this page is about, and which of them have ever worked together
- 01The senior engineerThe pair that came out of a shared on-call week
- 02The second engineer
- 03The designer
- 04The data analyst
- 05The product manager
five people · 10 possible pairs · 1 of them has worked on something together · 3 have only been in the same meeting · 6 have never done either
Five of the eight, with the manager left out so that what remains is what the team has without them.
When the manager is the only route between people, the group can explore the current features and use project-level patterns to identify where direct collaboration would remove delay.
For a separate perspective on teams and working practice, consult Carnegie Mellon University.
Two people, one output, one date. Not two tasks finishing on the same day — one thing that does not exist unless both of them act.
This is the sharpest instrument available and the one that most reliably produces a working pair, because it removes every option except talking to each other. It is also the one most often implemented in a form that does nothing, and the difference between the two forms is worth being precise about.
The form that works
The output is single and indivisible. One document, one feature, one decision, one answer to an outside party. If it can be cut into two halves that each person does separately, it will be, and the pair will not form.
Both names are on it. Not an owner and a helper, which is the version that gets written down because somebody has to be accountable. An owner and a helper produce a pair in which one person does the work and one reviews it at the end, which is a weak review rather than a collaboration.
The date is close. A week is ideal, three weeks is the outside limit. Beyond that the first conversation can be postponed indefinitely, and it will be.
Somebody is waiting for it. The strongest version is an external commitment — a customer, another team, a regulator — because then the deadline is not negotiable between the two of them.
The form that fails
- Joint ownership of an ongoing area. "You two own search between you." This sounds like the same thing and is the opposite: an area with two owners gets divided within a fortnight, informally, along whatever lines occur first, and afterwards each person owns half and neither says so. The pair that forms is a boundary negotiation, which is real work but not the kind that transfers much.
- A shared goal with separate contributions. Both people are measured against the same number and each affects it independently. No exchange is required at any point.
- A shared meeting about a shared thing. Coordination without joint production. This is the most common substitute and it produces the same result as every other meeting.
Why it works
Because a single output forces the hard conversations early and all at once.
Two people making one thing have to agree on what it is, which means discovering within the first day that they meant different things by the same words. They have to agree on what finished means, which is where most of the vocabulary problem lives. They have to divide the work, which means each stating what they are good at and what they would rather not do. And they have to resolve a disagreement in front of a deadline, which is the single most informative thing two colleagues can do together.
All of that happens in the first forty-eight hours of a week-long task. None of it happens in six months of shared membership.
What it costs
More than the other mechanisms in this part of the site, and it is worth being clear about that.
It is slower than giving the work to one person. Two people producing one small thing will take longer in elapsed effort than one person would have. That difference is the price of the pair, and on a week-long task it is a day or so.
It requires authority. The review rota and the rotating note can be started by anybody; assigning two people to one deliverable needs somebody who decides what people work on.
And it can go badly in a way that leaves a worse relationship than before. If the two people are mismatched in seniority, or if one of them regards the pairing as supervision, the week produces a pair on the grid and a resentment off it.
How to write the assignment
One short message to both people, containing four things and nothing else: what the output is, who is waiting for it, the date, and both names with no hierarchy between them.
What to leave out matters as much. No statement of why these two. No suggestion about how to divide it, because the division is the first conversation and doing it for them removes the most informative part. No offer to help, which converts the pair into a trio with the manager in it.
And no check-in halfway. If it is going wrong, it will come to you; if it is not, arriving in the middle routes the exchange back through the person it was designed to bypass.
Doing it four times a quarter
That is the realistic rate, and it is enough. Four joint deliverables across a team of eight, aimed at pairs the grid says do not exist, will move the count further than anything else on this site.
The one rule worth keeping: never pick the pair that would be easiest. Those two already have a relationship, the task will go smoothly, and nothing will have changed.