Reason one: an idea beyond your reach
The most common. Three people get together and decide to build a social network, a marketplace or a chat app. A month later sign-up works, the hard part begins, and the enthusiasm runs out.
The fix: take a problem solvable in six to eight weeks. Not "a platform for something" but "a tool that does this one thing".
Reason two: nobody defined "finished"
A project without a definition of done never ends. There's always more to add, and at some point everyone realises there's no finish line.
The fix: write one sentence at the start — the result by which we'll know we're done. Anything outside it is deferred.
Reason three: unequal contribution
One person does the bulk of the work, another appears once a week. The first burns out and resents it, the second feels guilty and appears even less. The project dies of grievance.
The fix: agree hours up front. Not "we'll do our best" but "I can give six hours a week". An honest three beats a promised twenty.
And agree what happens when someone can't. People vanish without malice — work, exams, illness. Settling it in advance removes half the tension.
Reason four: silence
Nobody writes anything. Everyone assumes the others are working. Two weeks later it turns out nobody was.
The fix: agree a simple rhythm — a short check-in once a week, three lines each: what I did, what's next, where I'm stuck. That's enough for a stall to be visible immediately rather than a month later.
Reason five: arguing about the unimportant
A week choosing between two libraries, three days on a name. Discussing is more pleasant than building, and the team quietly gets stuck in conversation.
The fix: adopt a rule — if an argument runs past half an hour, take whatever most people know and move on. A technical choice can almost always be changed later; lost time can't.
What helps in every case
Visibility. When it's clear who is doing what and where the project stands, problems surface early. A shared task board where everyone notes what they've taken, plus one honest weekly conversation, is enough.
One more thing: when each person's part is recorded at the end — what they did, what they owned — it becomes easier to work carefully. Not out of fear, but because it's visible that the effort won't evaporate: it stays as a record you can show.
Открытые роли по теме статьи
Читать полезно, а делать — ещё полезнее. В эти команды можно написать прямо сейчас:
- iOS-разработчик — MAIBO - MedTech-пилот для клиник
- Контент-маркетолог / комьюнити — CohortX — платформа командных пет-проектовмаркетингtelegramseoконтент
Похожие статьи
- Agreeing on technical decisionsWhy technology arguments drag on, how to tell an important decision from an unimportant one, and what to record so you don't argue twice.
- Как договариваться о технических решенияхПочему споры о технологиях затягиваются, как отличить важное решение от неважного и что записывать, чтобы не спорить дважды.
- Handing a project over to someone elseWhat to prepare, what to say out loud, what the code won't tell them, and how to know the handover actually happened.