Why people don't join ideas
Because ideas are plentiful and finished projects are rare, and people know it. On hearing "I've got a great idea", anyone experienced immediately thinks: this will stall in a month.
So the task isn't to describe the idea beautifully but to show that this project will end.
Describing it so people come
Say what specifically gets built. Not "a service for creative people" but "a site where a craftsperson can show their work and take orders". Clear on first reading.
State the size. "I'm planning on two months" shows immediately that you're being realistic.
Say what already exists. Anything: a sketch, a broken-down problem, a finished piece. That's what separates intent from conversation.
Describe roles concretely. Not "looking for developers" but "need someone on the interface and someone on data". Then people can tell whether they fit.
State your own hours. If the person with the idea will put in ten hours a week, others will join. If it's unclear, they won't.
What not to write
- "Huge potential", "will be number one", "nothing like it exists".
- "Payment after launch" — that frightens people off more than an honest "there's no money".
- A five-page description. Nobody finishes it.
- Requirements written like a job posting. You aren't an employer, you're looking for people who care about the same thing.
The first two weeks
The dangerous stretch: interest is high, there's no result yet, and any snag kills the momentum.
Start building in the first days. Small is fine. Nothing holds people like visible movement.
Give everyone a task immediately. Someone who waits a week for something to do leaves.
Make the work visible. A shared board where everyone notes what they've taken and finished. Without it, two weeks in nobody knows who's doing what.
Meet for fifteen minutes a week. What I did, what's next, where I'm stuck. That's enough.
Not losing people
The main reason people leave isn't difficulty, it's a sense of pointlessness. They can't see their work leading anywhere.
Three things cure it: a clear goal, visible progress, and recognition of what each person did. That last is badly underrated: saying "he built this part" takes a minute and holds people strongly.
And when each person's part is recorded at the end — what they did, what they owned — the work stops being a favour and becomes experience they can show. That changes how everyone treats it, including you.
Хватит читать — пора делать
На CohortX можно найти команду под пет-проект и получить тот самый опыт, о котором спрашивают на собеседовании.
Похожие статьи
- Agreeing on contribution before the project startsThe half-hour conversation that saves a project from resentment: hours, ownership, what happens if someone vanishes, and who owns the result.
- Как договориться о вкладе на старте проектаРазговор на полчаса, который спасает проект от обид: часы, обязанности, что делать при пропаже и кому принадлежит результат.
- Roles in a small team: who owns whatHow to divide work between three people, why someone must own the whole, and why 'everyone does everything' fails.