what one project actually needs

You start something real - a renovation, a course, a move - and you decide that this time you'll be organized about it. An hour later you have folders, categories and a colour code, and you haven't done any of the actual work.

Then life arrives at 11pm as a screenshot of a message from a plumber, it doesn't fit any of the categories, and the whole structure quietly stops being used.

Here's the thing: one project needs four things, and none of them is a structure you design in advance.

1. Somewhere to put things in three seconds

A renovation happens standing up, in a dusty room, with someone waiting for an answer. A trip happens in a queue. A course happens between two other things.

Anything that takes four taps and a decision about where it goes will not happen - the photo goes to the camera roll instead, and you'll never find it again.

So the first requirement is brutal and simple: catching something takes three seconds and no decisions. Sorting can wait for the sofa, or never happen at all. Catching is what matters.

2. Everything about the thing, together

Your notes about the bathroom, the photo of the tile, the link to the shop and the reminder to call the joiner are all about the same bathroom. They usually live in four different places - which is why the answer to "what did we decide about the tile" takes ten minutes to find.

Together doesn't mean tidy. It means one project holds its own stuff, so there's exactly one place to look.

3. More than one way to look at it

Some days you need the whole picture: everything spread out, so you can see what's missing. Some days you need a plain list of what's left. Some days you just want to read it top to bottom, like a document.

That's not three tools. It's the same material, shown three ways - and being able to switch is the difference between a tool that fits every day and one that fits Tuesdays.

4. Something you can hand to someone

At some point a person outside your head needs to see this: a contractor, a supervisor, a friend picking you up from the airport. What they need is a file - one document with the pictures, the decisions and the prices, that opens without an account and prints if it has to.

If your project can produce that in one move, the handover takes a minute. If it can't, you rebuild the same summary in a message every time something changes - and something changes constantly.

Four things: catch it fast, keep it together, look at it any way, hand it over. Everything else is decoration.

What this rules out

Anything you have to build first. If you're deciding on categories, properties and views before you have any content, you're doing a different project - the project of making a tool - and it competes with the one you meant to do.

The test is easy: can you start using it in the first minute? Make a thing, toss something in, look at it. If that takes an hour of setup, the setup will be the only part that ever gets finished.

And when you ignore it for two weeks

Which you will. Life gets in the way, the renovation stalls, the course goes quiet.

A good tool for one project just waits. Nothing breaks, no streak is lost, nothing needs cleaning up before you can use it again. You open it, and it's exactly where you left it - which is the entire reason you wrote things down in the first place.