How to organise tasks and projects so nothing stalls

I spent six months last year in a task management system with 449 tasks. I wasn't proudly productive. I was drowning. Every time I opened the system, I felt paralysed. Too many options, no clarity on what actually mattered.

The problem wasn't too many tasks. It was missing structure. Tasks need a clear owner, a next action, and a relationship to the projects they belong to. Without that architecture, tasks become noise.

David Allen's Getting Things Done describes the organise step: everything should have a home and a clear next action. That single idea transformed my task system. At Solid Growth, everything lives in one system with that structure baked in. Work moves instead of piling up.

The three-level structure

Goals sit at the top. These are your 12-week sprint goals, the things you're committed to finishing within three months.

Projects sit in the middle. A project is anything that has more than one step. If you have a sprint goal to "ship a new feature," the project breaks that down: design the feature, build the backend, write tests, ship to production.

Tasks sit at the bottom. These are the individual actions that move projects forward. Each task should take between fifteen minutes and a day.

Every task belongs to a project, every project serves a goal. This hierarchy keeps everything visible and connected.

Every project needs a next action

This is Allen's critical insight. If a project has no next action, it stalls. You come back to it, look at it, feel uncertain what to do, and move on.

The next action is the smallest, most concrete step you could take right now. Not "improve the website". "Write a customer interview guide and schedule three interviews." That's a next action.

Structuring tasks for clarity

Every task in your system needs five things: owner, priority, deadline, project, and status. Owner means who's responsible. Priority: high, medium, low. Deadline forces realistic thinking about capacity. Project is the connection to the larger work. Status: to do, in progress, blocked, done.

The weekly project review

Every week, review your active projects. Pick each one and ask: is this moving or stuck? If it's stuck, why? Get it unstuck before the week ends or put it on pause.

Saying no to new projects

The full plate principle: if you can't take on a project without pulling something else off your plate, you're full. Say no. The discipline to say no is the discipline to actually finish things.

Tool choices: keep it simple

You need one task tool. Not Notion and Todoist and Apple Reminders. One. The tool doesn't matter much. What matters is that you use it consistently.

Handling recurring tasks

Some tasks repeat. Weekly 1:1s, monthly reporting, quarterly planning. Mark these as recurring and set the pattern. The key is not letting recurring tasks hide other work.

How AI helps organise

I use Claude to audit my task list monthly. I dump the whole thing and ask: "What's stale? What's never going to happen? What looks blocked?" Claude spots patterns I miss.

When to archive and when to delete

Archive completed projects. Delete tasks that you know will never happen. Be honest. If you've been meaning to "read that book" for two years, delete it.

The three-project rule

For an individual, three active projects is the maximum. Individuals who try to manage five active projects end up managing none of them well.

A good task system is nearly invisible. You open it, see clearly what to do next, and start. If you're spending time managing the system, the system is too complex.