There is something reassuring about a well-organised inbox.
You create a folder for each project. Another for clients. Another for colleagues. Perhaps you add folders for invoices, suppliers, management, newsletters and anything else that seems likely to arrive more than once.
It feels sensible. If an email is about a particular project, you know where it belongs. If you ever need it again, you know where to look.
For a while, this works.
Then the folders multiply.
A project gets renamed. A client changes. Two projects overlap. An email relates to several subjects at once. You create subfolders because the existing folders have become too broad. Eventually, the system that was supposed to make your email easier to manage becomes another thing you have to manage.
The problem is not that folders are inherently bad.
The problem is that we tend to organise email around what messages are about, even though that doesn’t necessarily tell us what the messages mean for us.
The subject of an email doesn’t tell you what to do
Imagine that you receive five emails about the same project.
One contains information you might need later. One asks you to make a decision. One requires you to send something to a colleague. One is simply keeping you informed. The last one is part of a conversation that has already been resolved.
All five emails have the same subject.
Yet they have completely different consequences for you.
If you organise them according to subject, they naturally end up together. That makes sense from an archival perspective. They belong to the same project.
But from a working perspective, the project isn’t the most useful thing they have in common.
What they have in common is their subject.
What they don’t have in common is what you need to do with them.
This is where a seemingly sensible filing system starts to work against you.
Filing answers the wrong question
Traditional filing is built around retrieval.
You put something somewhere so that you can find it again.
That makes perfect sense for documents. A contract belongs with the other documents relating to a particular client. A project plan belongs with the project it describes. A set of meeting notes belongs with the work they relate to.
Email is different because an email can have two lives.
First, it is a communication that requires some kind of response or decision.
Later, it might become useful as a record.
Those are different needs.
If you organise every message primarily according to its subject, you are solving the second problem before you have necessarily solved the first.
That creates an odd situation: you can have an extremely well-organised inbox and still have no clear idea what needs your attention today.
The filing system is working.
The working system isn’t.
When subject folders become a burden
You notice this when finding an email starts to require a small investigation.
You remember that someone sent you something about a particular project, but you can’t quite remember whether you filed it under the project name, the client, the department or the person who sent it.
So you search.
Search has become the safety net for the filing system.
There is nothing inherently wrong with searching. Modern email makes it remarkably easy. But relying on search can hide an underlying problem: you are storing information according to a structure that doesn’t necessarily correspond with the questions you ask later.
You rarely think:
“I need to see everything that has ever been communicated about Project X.”
More likely, the question is something like:
“Where is the information I need?”
Or:
“What was I supposed to respond to?”
Or:
“Which things am I still waiting for?”
Those are not subject questions.
They are questions about purpose and status.
That is why a folder structure can look perfectly logical and still fail at the moment you actually need help from it.
The strange comfort of categorisation
There is another reason subject-based organisation survives.
Categorisation feels productive.
You take a message, decide where it belongs and move it there. Something that was previously sitting in your inbox now has a home. The screen looks cleaner. The system appears more orderly.
That creates visible progress.
But moving an email does not necessarily change what the email requires from you.
If you still need to respond, the message hasn’t become less important because it now sits inside a beautifully named folder.
In fact, it may become easier to forget.
The inbox at least presented the unfinished matter to you. Once you file it away, you have to remember which folder contains it and remember that you put it there for a reason.
Organisation can therefore remove visual clutter while increasing mental dependence on the system.
That is a trade-off worth noticing.
The problem with organising around topics
Subject-based organisation also assumes that the subject will remain meaningful for as long as you need the information.
Work rarely behaves that neatly.
A single email can relate to a project, a person, a decision, a supplier and a future task. Which folder should it belong to?
You could create a more sophisticated structure that accounts for all of those possibilities. But every additional category introduces another decision.
And the more decisions your system requires, the more likely you are to postpone making them.
That is how an inbox can gradually acquire the characteristics of a filing cabinet designed by committee.
Everything has a place.
Nobody particularly wants to maintain it.
The irony is that the original intention was simplicity.
A more useful way to look at email
There is a more fundamental question beneath all of this:
Why are you keeping an email?
The answer is rarely simply “because it is about Project X.”
You might be keeping it because you need to act on it. You might need information from it. You might be waiting for something connected to it. You might need the record later. Or you might simply be keeping it because deleting it feels uncomfortable.
Those reasons have very different implications.
Once you start looking at email through that lens, the subject becomes less important.
The subject still matters. It helps you understand the context of the communication. It helps you find things later.
But context isn’t necessarily the same thing as purpose.
That is an important shift because it changes what “organisation” means.
Instead of asking how to build a better map of everything that has entered your inbox, you can start asking what information deserves your attention now, what needs to remain visible, and what can safely move out of your immediate field of view.
That is a much closer reflection of how people actually work.
Organisation should reduce decisions, not create them
A good organisational system should make future decisions easier.
If you have to repeatedly ask yourself where something belongs, whether you should create another folder, whether an email fits two categories, or whether you will remember where you put it, the system is demanding attention rather than saving it.
This doesn’t mean that simple systems are always better. Some work genuinely requires detailed classification. A legal department, a project archive or a regulated environment may have very different requirements from an individual’s working inbox.
But there is a useful test:
Does the organisation help you do the work, or does it mainly help you organise the evidence of the work?
Those are not the same thing.
A tidy archive can be valuable. It simply shouldn’t be confused with a system for managing attention.
That distinction becomes particularly important with email because messages arrive continuously. Unlike a filing cabinet, the inbox is not a static collection. It is a moving stream.
You don’t finish organising it once.
You have to keep organising it.
And that means every rule you introduce becomes a small recurring cost.
Perhaps the inbox doesn’t need better filing
The natural response to an overflowing inbox is to improve the filing system.
Create better folders. Rename them. Add categories. Develop rules. Automate the sorting. Spend an afternoon getting everything into the right place.
There is satisfaction in doing this because the result is visible.
But perhaps the more useful starting point is to question the assumption underneath it.
Maybe your inbox doesn’t primarily need to tell you what an email is about.
Maybe it needs to help you understand why the email still deserves your attention.
That doesn’t eliminate the need for organisation. It changes what you are organising around.
The subject of an email describes its context.
Its purpose tells you why it is still there.
And once you begin to see that difference, the familiar collection of project folders starts to look less like a solution and more like a record of how we have traditionally thought about information.
The challenge is not to create a perfect filing cabinet inside your email.
It is to create enough clarity that your inbox no longer requires you to think about every message from scratch.
That is a much more useful definition of organisation.