Step one: the big stages
Before writing individual tasks, define the project's major stages. Individual tasks then naturally attach to those stages, instead of forming a flat list with no hierarchy.
How to write a useful task
- A clear, actionable title, "Send design draft to client", not "Design".
- One owner, not a generic "team".
- A deadline, even an approximate one, better than no deadline at all.
When to add details
Not everything needs to be decided on day one. Tasks can be added as the project progresses and becomes clearer, the initial structure needs to be useful, not complete.
Bottom line
A good structure from the start doesn't mean perfect planning, it means enough clarity to know what's next, at any point in the project.