Why most people fail at decluttering
I started this whole thing about three years ago, when I realized I was spending roughly forty hours a month on administrative tasks that didn't actually move any projects forward. The traditional advice is always weekly reviews or daily check-ins, but I found that neither cadence worked for the kind of project portfolio I manage. A weekly review catches the small stuff but lets the structural problems accumulate. A daily review becomes a ritual of guilt rather than genuine planning. Monthly settled somewhere in between. The actual method is straightforward enough that you probably won't find anyone selling a course on it, and honestly that's the point. You pick one day each month, ideally the first or last, and you go through every active commitment you have and answer three questions: Does this still matter? Am I the right person to do it? What's the next concrete action?
Monthly Minimalism Step By Step
Here's how I actually run mine, not the polished version from blogs. Day one is preparation. I spend about twenty minutes printing or opening my current dashboard files — project list, task tracker, calendar export from the past thirty days, bank statement, and any inbox that hasn't been touched. I don't process the inbox. I just pull it out so I can see how much accumulated over the month. Then I close everything else. My phone goes in another room. This step takes about fifteen to twenty minutes for most people depending on how organized their tools are already. Day two is the audit. I go through each project one at a time and categorize it. The categories I use are active, paused, waiting on someone else, or dead. That's it. No priority levels, no urgency flags. If a project has been sitting in "active" for three months with no movement in the last thirty days, it doesn't automatically get moved to paused — I have to look at it and decide. This is where most people get stuck. They'll stare at a project and feel guilty about not finishing it, which means they don't actually make the decision and just leave it as active. Make the decision. Pause it, drop it, or commit to a concrete next action. There's no penalty for any of those choices. Day three is scheduling. I take all the projects I marked as active and assign them one concrete deliverable for the coming month. Not a habit. Not a goal. A deliverable. "Launch the landing page" is a deliverable. "Work on marketing" is not. I then block out calendar time for each deliverable in sixty-to-ninety-minute chunks. If a project can't fit into one of those chunks next month, it doesn't get scheduled. It stays active but gets flagged for review next month. The rule is simple: if it has no scheduled time, it doesn't exist for this month.
Day four is the cleanup. This is the part people skip and then wonder why they end up doing the same thing the next month. I go through my digital and physical spaces and remove anything that was used in the previous month but isn't needed going forward. That means unused templates, old drafts, redundant folders, physical papers from completed projects. I usually spend about an hour on this, sometimes two if I haven't done it in a while. There's a specific edge case I hit recently that I want to mention because it caught me off guard. I had a shared spreadsheet for a side project with three other people. The project was paused, but the file had seventeen revision histories and three separate comment threads from different months. I spent forty-five minutes going through the comments trying to figure out if any contained open questions. None did. Everything was resolved or irrelevant. I archived the sheet and shared a single summary document with the other people involved instead of leaving seventeen versions sitting in our cloud storage. The workaround was simpler than I expected — just a five-minute call to confirm nobody needed the old data, then archive and notify. Day five is reflection and reset. I write a short paragraph about what actually happened last month versus what I thought would happen. Not to judge myself, just to calibrate. This usually takes ten minutes. Then I set up the workspace for next month. One fresh folder for new files, one blank calendar sheet, and the three-question template copied from last month. I found that having a clean starting template actually makes the next month's review significantly faster because I'm not recreating the framework from scratch.
Get the Full Details
What nobody tells you about this approach
The biggest mistake I see people make is treating this as a decluttering exercise rather than a commitment audit. The physical stuff matters, but the real volume comes from open loops in your mind — half-finished decisions, projects you're maintaining by inertia, tasks you picked up from someone else without ever confirming you actually wanted them. The monthly review surfaces these faster than any other method I've tried. I've seen it cut the number of simultaneously active projects for my clients from an average of twelve down to about five, and the quality of work improved noticeably because there was less context-switching. Another thing: the sixty-to-ninety-minute calendar blocks are non-negotiable. I used to schedule thirty-minute slots and wonder why nothing got done. Thirty minutes isn't enough time to enter a focused state on most meaningful work. Sixty minutes gets you there. Ninety minutes lets you stay there. Anything shorter and you're mostly just starting and stopping, which is slower than working at all on complex tasks. There are scenarios where this method breaks down completely. If you manage a team of more than five people or have a job that requires real-time responsiveness — customer support, emergency services, live operations — the monthly cadence won't work because the feedback loop is too slow. You'd be better served with a weekly review or even a daily one. I tried applying this to a team of eight engineers for about six weeks and it created more confusion than clarity because people needed course-correction every few days, not once a month. The method works best for individuals managing their own project portfolios or small teams of four or fewer.
The other limitation is that the first three months tend to feel worse before they feel better. You'll discover commitments you had no memory of making, projects you're maintaining purely out of obligation, and calendar time you thought was reserved for deep work that was actually spent on low-value admin. That's not a failure of the method. That's just the lag between you not knowing the full picture and finally seeing it clearly. Give it four cycles minimum before deciding whether it's worth keeping. If you want to try this, you don't need any special software. A printed three-question template, a calendar, and a folder structure that makes sense to you is enough. I used to overthink the tooling — Notion setups, Obsidian vaults, dedicated productivity apps — and none of it lasted longer than two months because the system itself became another thing to maintain. The simplest version that survives is always better than the most feature-rich version that you abandon. The download link for the template I use is at the bottom of this page. It's just a PDF with the three questions, the four project categories, and a blank monthly calendar grid. Nothing fancy. I've updated it three times over the past year as I refined the layout, but it's never had more than those four elements. Use it or don't. The method works regardless of whether you use my template or draw something similar on a notebook page.
One more thing that seems obvious but deserves being stated directly: the review only works if you actually act on what you find. I had a client who completed six consecutive monthly reviews without ever scheduling a single deliverable. She spent the entire review time categorizing projects but never moved anything into calendar time. She was technically doing the method perfectly and getting zero benefit from it. The review is only useful when the output is a concrete plan for the next thirty days. Everything else is just expensive journaling. I've attached the template below. It's free, no email required, and it updates automatically if I find a better format later. If you use it and run into problems — say, a project falls into a gray area between paused and waiting — just reply here and I'll add it to the next version.
