Running a project without a manager

What a manager does and who inherits it

In a team without a manager, their work doesn't disappear. It gets distributed — or it doesn't get done, and the project falls apart.

What you'll have to take on:

• Deciding what gets built first.
• Watching that tasks move rather than hang.
• Noticing that someone is stuck and helping.
• Resolving disagreements when opinions diverge.
• Holding the whole picture.

Practical advice: agree who owns these things. Not "all of us together" — that means nobody.

The minimum set

Five agreements, one sentence each:

1. What we're building. One phrase everyone understands the same way.

2. What counts as finished. The result that tells us we're done.

3. How much time each person has. Honestly, in hours per week.

4. Who takes what. Specifically.

5. Who decides when we disagree. The most skipped and most important.

About that last point

In a team of equals an argument can run for weeks: both sides are right in their way, there's no authority, and nobody is obliged to yield.

A working rule: if half an hour doesn't settle it, whoever owns that part decides. Or: take the option most people know. Or: flip a coin — seriously, for minor technical disputes that beats losing a week.

The point is to agree the rule in advance, not during the conflict.

Rhythm

At least two regular moments:

A short check-in every few days. Three lines each: what I did, what's next, where I'm stuck. Written is fine. Without it, a stall is noticed a month late.

A review every two weeks. What got in the way, what we're changing. Half an hour.

Plus a task board showing who's doing what.

That's all. A small team needs no more, and less is already dangerous.

What most often breaks such projects

Nobody watches the whole. Everyone builds their part and nobody thinks about how it assembles. It surfaces at the end.

Unequal contribution, undiscussed. One person carries it, another vanishes, both stay silent. Resentment accumulates and the project dies.

No way to settle disputes. Two weeks arguing about a library on a three-week project.

Scope creep. Without someone saying "no, that's for next time", a project grows indefinitely.

What helps

Visibility. A board, check-ins, a shared channel where decisions land. When it's clear who's doing what and where the project stands, problems surface early.

Short timeframes. Two weeks rather than three months. People don't have time to scatter in two weeks.

Recognising contribution. At the end, record who did what. Not a formality: work that exists only in memory feels wasted, and next time the person won't join.

When everyone's part is written down and confirmed, the project gains a purpose beyond the product itself — and that noticeably changes how people treat it.