Disagreement isn't a disaster
A team that never argues usually isn't working but agreeing. Differing opinions mean people care.
The trouble starts when an argument doesn't resolve: it either drags for weeks or turns into a matter between people.
Three usual sources
A technical argument. How to store something, which library to take, what to call it. The most frequent and the most harmless, provided it's settled quickly.
Unequal contribution. One does a lot, another disappears. It accumulates silently, then detonates.
Different understandings of what we're building. Discovered late, usually when the pieces are assembled.
The first is cured by a decision rule, the second by a direct conversation, the third by agreements at the start.
Breaking a technical deadlock
The rule is simple: if half an hour hasn't settled it, the argument isn't about truth but about preference.
Then, in order:
- State what you're choosing between. It often emerges you were arguing about different things.
- Name what each option gives and what it costs. Point by point, out loud.
- Check whether the decision is reversible. If redoing it later takes half a day, take either option and move on. Arguing for an hour about something reworkable in thirty minutes is pure loss.
- If it's irreversible and you haven't converged, whoever owns that part decides. Or whoever will have to fix it.
That rule must be agreed in advance, not mid-argument.
Talking about unequal contribution
The most unpleasant conversation and the most necessary. Silence doesn't help: resentment accumulates and at some point the person simply leaves without explaining.
What helps:
Speaking early. In week two, not after two months.
Speaking about facts, not qualities. Not "you're irresponsible" but "no tasks closed in two weeks, and I don't understand what's happening".
Asking rather than accusing. It often turns out to be mundane: a crunch at work, illness, lost interest. Those can be worked with.
Offering a way out. "Maybe take a smaller piece?" or "maybe now isn't your moment, and it's better to bow out honestly?". Leaving on good terms is fine.
Where the line runs
On substance: "This storage approach won't survive growth, and here's why."
Off it: "You always suggest nonsense."
A simple test: if a sentence contains "you always" or "you never", it's no longer about the work.
A second sign: the discussion revolves around whose fault it is rather than how to do it.
If you lost your temper
Acknowledge it and move on. No excuses, no lengthy self-examination, just: "Sorry, I was sharp yesterday. On the substance, I still think this."
The ability to do that is a rare and highly visible sign of an adult in a team. And it's noticed far more than one more technology learned.
Prevention
Most conflict in small teams comes from what wasn't agreed. Who does what, what counts as finished, how much time each has, who decides when you disagree.
Half an hour at the start removes most future arguments. That isn't bureaucracy but a way of preserving good relations with people you want to keep working with.
Хватит читать — пора делать
На CohortX можно найти команду под пет-проект и получить тот самый опыт, о котором спрашивают на собеседовании.
Похожие статьи
- Dividing roles in a small teamWhy splitting by layers is risky, three workable ways to divide the work, and what to do when everyone wants the same part.
- Как разделить роли в маленькой командеПочему деление по слоям опасно, три рабочих способа разделить работу и что делать, когда все хотят делать одно и то же.
- When a teammate disappearsWhy people leave silently, how to agree about it in advance, and how to restart a project when half the team is gone.