Design an Email System With Few Enough Labels That You Actually Keep Using It
For an inbox that has turned into a shame closet: thousands unread and a newsletter folder you stopped opening a year ago. Works out first whether you have a volume problem, an attention problem or an organization problem, since those need completely different fixes. Then it declares amnesty on the backlog instead of making you process it, cuts inbound at the source, and caps the whole system at ten labels one level deep, with no new account and no folder tree to maintain. Pair the new system with our weekly review template so the inbox gets a standing check instead of another New Year's resolution. Sort what's actually urgent first with our task prioritization prompt if inbox anxiety is really a task-avoidance problem.

You are an email systems designer. Your job is to design ONE lean email system I will still be running in six months, not to hand me a folder tree. WHO YOU ARE TALKING TO: My inbox has become a shame closet. Thousands of unread messages, a newsletter folder I have not opened in a year, and a constant shuffling of messy digital objects from one place to another that never actually ends. I have already tried the obvious fixes and they backfired: - I set up extra email accounts to separate things. That just multiplied the problem and gave me two more places to check. - I created more categories and labels inside my mail client. That made me ignore messages and things I actually wanted to read, because every inbound message now cost me a filing decision. So assume my problem is too many moving parts, not too few. More folders is usually the wrong instinct here. Every label, rule and account you propose is a decision tax I pay on every single message, and you have to justify it. HARD RULES: - Never invent statistics, studies, or claims about how many hours email costs people. If a number matters, ask me for mine. - Maximum 10 labels or folders total, and never nested more than one level deep. If I already have more than that, your job is to tell me which ones to merge or delete, by name. - Never propose a new email account unless I already have a genuine legal or employment reason for one. Splitting work and personal is allowed. Inventing a third account for newsletters is not. - Do not propose any tool I have to buy, install or learn this week. Work with what my current client already does: labels, filters or rules, snooze, archive, search. - No inbox zero evangelism. Zero unread is not the goal. A trustworthy inbox is. - Ask questions in batches of five at most, then stop and wait for my answers. STEP 0 - FIND OUT WHICH PROBLEM I ACTUALLY HAVE (do not skip): Before designing anything, ask me up to five short questions and stop. You are sorting my situation into one of three, and they need different fixes: a) A VOLUME PROBLEM. More arrives than any system could hold. The honest framing is that I cannot have more attention than I have, so the fix is triage and cutting inbound at the source, not faster filing. b) An ATTENTION PROBLEM. The mail is manageable, but I keep reopening the inbox because cleaning it feels productive while the real work waits. If this is me, say so plainly in Step 7 instead of pretending a filter will fix it. c) AN ORGANIZATION PROBLEM. The volume is not mine to control: reply-all culture, being copied on everything as cover, approval bottlenecks where work stops until I respond. No client-side setup fixes this, so it needs boundary and process language, which you will write for me in Step 6. Most people are a mix. Tell me the proportions you think I am, in two lines, and which one we are fixing first. Ask me for: my rough unread count, my mail client, how many labels or folders I have now, how many accounts I check, and the last message I genuinely regret missing. STEP 1 - DECLARE AMNESTY ON THE BACKLOG: Do not ask me to process thousands of old messages. Give me a one-time cutoff move: select everything older than a date you pick with me, archive it in one action, and trust search to find anything that matters. Write the exact steps for my client. Say out loud that archived is not deleted and nothing is lost. If I am scared of that, give me the safety version: archive it into a single folder called Old, one level, never to be sorted. STEP 2 - CUT INBOUND AT THE SOURCE BEFORE DESIGNING ANYTHING: Filing faster is losing. Ask me to name the senders and types filling my inbox, then for each one tell me which action applies and write out what I actually do: - Unsubscribe outright, and be aggressive about it. If I have not opened it in a month, it goes. - Auto-archive on arrival, skipping the inbox entirely, readable later by search or label if I ever want it. Notifications, receipts and system mail belong here. - Turn the notification off in the source app rather than filtering the mail. - Ask a human to stop sending it or stop copying me, which is Step 6. Then estimate roughly how many messages a week each cut removes, based only on the numbers I gave you, never invented ones. STEP 3 - DESIGN THE SMALL NAMED TOOLKIT: Give me the whole system as ONE table, nothing more: Label or rule | What lands here | How it gets here (filter, snooze, or my hand) | When I look at it | What empties it Constraints you obey: - Aim for four to seven labels. Ten is the hard ceiling. Fewer is better. - Every label must be defined by what I DO with it, not what it is about. Action labels like Reply, Waiting and Read Later survive. Topic labels like Projects, Admin and Misc are where filing systems go to die, because a message can belong to three of them and I stall. - No label may exist without a named emptying trigger. If nothing ever empties it, it is a graveyard and you cut it. - If I already have labels, map each existing one to keep, merge into X, or delete, in a second short table. Be specific and use my label names. STEP 4 - WRITE THE TRIAGE RULE, INCLUDING URGENCY WINDOWS: Give me a decision I can make in under five seconds per message, written as a short ordered list I could pin next to my screen. Include: - The two-minute rule: if replying takes less than two minutes, reply now and archive. - Urgency windows instead of vague flags: needs me today, needs me this week, needs me after that. Tell me exactly how to express each in my client, and prefer snooze over a new label wherever snooze does the job. - What to do with a message I genuinely cannot decide about. Give it one home, not three. - An explicit rule for anything that is really a task pretending to be an email: where it goes, so my inbox stops doubling as a to-do list. STEP 5 - SET THE CHECKING SCHEDULE: Propose specific times, defaulting to twice a day unless my job genuinely requires otherwise, and ask what my real response-time expectation is before locking it in. For each session give me a timebox in minutes and what counts as done, which is never zero unread. Tell me what to turn off so the inbox stops interrupting me between sessions, and name the one exception channel people should use if something is truly on fire, so I can stop guarding the inbox for emergencies that arrive elsewhere. STEP 6 - IF THE VOLUME IS NOT MINE TO CONTROL, WRITE THE SCRIPTS: Where Step 0 found an organization problem, give me two or three short copy-paste messages, plain and not passive-aggressive, for the specific situations I described. Typically: asking to be taken off a recurring CC thread, replacing an approval that only happens over email with a standing rule or a shared channel, and setting a stated response window with my team or clients. Keep each under five lines. Name who I send it to. STEP 7 - THE HONEST CHECK: If my answers suggest I clean the inbox to avoid something else, say it directly and without softening. Ask me the uncomfortable version: once the inbox is empty, what is my excuse then? Then name the piece of real work the inbox is standing in front of, based on what I told you, and give me one concrete thing to do first tomorrow BEFORE opening email at all. If this is not my problem, skip this step entirely and say so in one line rather than inventing a psychological issue I do not have. STEP 8 - THE ONE-PAGE SUMMARY AND THE ANTI-SPRAWL RULE: Close with a summary I could tape to the wall: my labels, my triage list, my checking times, my cut-at-source actions. Then give me: - The first action to take in the next ten minutes, small and specific. - The anti-sprawl rule, stated plainly: I may not add a label without deleting one, and if I find myself wanting a new folder, the real answer is usually a filter or an unsubscribe. - A three-line monthly review: what leaked into the inbox that should have been cut, which label went stale, which unsubscribe I still owe. MY INPUTS Rough unread count and how long it has been building: [NUMBER, MESSY ESTIMATE IS FINE] Mail client and whether I can use filters and snooze: [E.G. GMAIL, OUTLOOK, APPLE MAIL] Accounts I currently check: [LIST THEM] Labels or folders I have now: [LIST OR SAY TOO MANY TO COUNT] What actually floods it: [NEWSLETTERS / CC THREADS / NOTIFICATIONS / CLIENTS / ALL OF IT] What I have already tried and how it failed: [DESCRIBE OR SAY NOTHING YET] Real response-time expectation in my job: [E.G. SAME DAY, WITHIN AN HOUR, NOBODY CARES] Am I using inbox cleaning to avoid something: [YES / NO / NOT SURE] Start at Step 0. Ask your questions, then stop.
How to use this chat prompt
Paste it directly into a new chat, replace anything in [BRACKETS] with your context, and send. Re-use it whenever the task comes up, or save it as a text-expander snippet.
Example output
Gmail, 8,800 unread built up over two years, 22 existing labels, two accounts, and a habit of reopening the inbox between tasks.
Set up folders for Work, Personal, Newsletters, Receipts and Projects, and move each email into the right one as it arrives.
Aim for inbox zero every day, unsubscribe from lists you do not read, and consider a separate email address for signups.
Filters and rules can help automate the sorting once the folders exist.
DIAGNOSIS: roughly 60 percent volume, 30 percent attention, 10 percent organization. We fix volume first.
AMNESTY: select everything before 1 March, archive in one action. Nothing is deleted and search still finds it.
CUT AT SOURCE: 4 newsletters unsubscribed, build and ticket notifications auto-archived. Around 140 messages a week gone before triage.
Label | What lands here | How | When I look | What empties it
Reply | Needs a real answer from me | My hand at triage | 11am and 4pm | Sending the reply
Waiting | Sent, awaiting someone else | My hand | Friday scan | Their reply or a nudge
YOUR 22 LABELS: keep 5, merge Client A, B and C into Reply, delete 14 including Misc and Projects.
ANTI-SPRAWL RULE: no new label without deleting one. Wanting a folder usually means you need a filter or an unsubscribe.
FAQ
Frequently asked questions
I have almost 9,000 unread messages. Does this make me go through them all?
No. Step 1 declares amnesty on the backlog: you pick a cutoff date and archive everything older in one action, which keeps it searchable without deleting anything. Being told to process thousands of old messages is how people quit a new system in week one.
I already tried making more labels and folders and it made things worse. Is this the same advice?
The opposite. The system is capped at ten labels, one level deep, and it tells you which of your existing labels to merge or delete by name. It also refuses topic labels like Projects or Misc, since a message can belong to three of them at once, which is exactly the filing stall that made you start ignoring messages.
Should I set up a second or third email account to separate things?
It will not propose one unless you have a real employment or legal reason. Extra accounts usually multiply the problem and give you more places to check, so splitting work from personal is treated as the ceiling, not the starting point.
What if the real problem is that my company copies me on everything?
Step 0 checks for exactly that, and when the volume is not yours to control it writes short copy-paste messages instead of more filters: asking to come off a recurring CC thread, moving an email-only approval into a standing rule, and stating a response window. No client-side setup fixes a reply-all culture.
What if I am using inbox cleaning to avoid actual work?
Step 7 asks you directly and names the work the inbox is standing in front of, rather than pretending another filter will help. Once that work has a name, sorting it with the Eisenhower matrix gives it a real slot in the week instead of leaving it parked behind email.
How often should I actually check email under this system?
It defaults to twice a day with a timebox on each session, but asks your real response-time expectation first rather than assuming. It also names one exception channel for genuine emergencies, so you stop guarding the inbox for fires that never arrive there.
Keep going
What's next
Guide
Effective Prompt Engineering for Daily Productivity
Prompt engineering for everyday work isn't secret syntax. It's context engineering in miniature: handing the model context, audience, format, and constraints, then iterating. Here's the full playbook.
Prompt
Prioritize a Task Pile With the Eisenhower Matrix Without Everything Landing in 'Urgent'
Fixes the two ways the Eisenhower matrix actually fails you: it makes you define what 'urgent' and 'important' mean for YOUR goals instead of guessing, sorts your whole task dump for you so working memory doesn't blur by task 12, and hands back a concrete next action per quadrant - plus it forces an impact-first re-rank when everything crashes into 'urgent and important.' Once the pile is sorted, protect time for the top quadrant with our deep work session planner so it doesn't just get re-sorted next week.
Article
The AI Productivity Paradox Is Mostly a Prompting Problem
Studies keep finding AI adds work instead of saving it. A surprising share of that hidden tax isn't the model's fault - it's how we prompt.