Mindset Playbook 1 of 5

How to Capture Commitments and Clear Mental Clutter

Every unresolved commitment, whether a follow-up you promised, a decision you deferred, or an idea you want to revisit, occupies working memory and creates background anxiety. The fix is not a better to-do list but a single external system your brain actually trusts to hold everything. This playbook walks you through building that system, developing the capture habit, processing what you collect, and using the mental clarity you gain to engage fully in whatever is in front of you.

Developing Start here. Build the foundation.
  • Choose one capture tool and commit to it for 30 days. It can be a notes app on your phone, a physical pocket notebook, or a task manager like Todoist or Things. The tool matters less than the rule: every commitment, idea, follow-up, and open question goes into this one place the moment it surfaces. Set a phone reminder three times a day for the first two weeks: at 9 AM, 1 PM, and 5 PM. Set the message to 'Have I captured everything since my last check?' After two weeks, the reminders become unnecessary because the habit is forming.
  • Schedule a 15-minute daily processing session at the same time every day. The last 15 minutes of your workday works well. Open your capture tool and go through every unprocessed item. For each one, answer three questions: (1) What is this actually about? (2) Does it require action from me? (3) If yes, what is the very next physical step I need to take? Rewrite vague entries like 'follow up with Sarah' into specific next steps like 'Send Sarah the pricing comparison spreadsheet by email.' Delete anything that no longer matters. This daily clearing is what builds your brain's trust in the system.
  • Organize your processed items into four simple categories: Today (must complete before leaving), This Week (needs attention in the next 5 business days), Waiting For (I did my part, someone else needs to act), and Someday (interesting but not committed). Use whatever structure your tool supports: folders, tags, or separate lists. Review the Today list first thing each morning and the Waiting For list every Friday to follow up on anything overdue. Start with just these four categories. You can add more later if needed, but most people never need to.
Proficient Build consistency and rhythm.
  • Add context tags to your next actions so the right tasks surface at the right time. Common contexts include @computer, @phone, @office, @home, @errands, and @low-energy. When you have 10 minutes between meetings and your laptop open, filter to @computer and pick a task that fits the time available. When you are mentally drained at 4 PM, filter to @low-energy and knock out simple tasks that still move things forward. This eliminates the wasted time of scanning your full list and deciding what to do next. The context filter has already made the decision for you.
  • Build a weekly review ritual every Friday afternoon. Block 30 minutes and protect it like a meeting with your most important client. Walk through every active project and ask: are the next actions still correct? Walk through the Waiting For list and follow up on anything overdue. Walk through your calendar for the past week to capture any commitments you made in meetings but forgot to log. Walk through your calendar for the next two weeks to identify preparation tasks you need to add. Write down your top 3 priorities for the following week. This single ritual is what keeps the entire system trustworthy.
  • Run a capture audit at the end of each week. Before your weekly review, scan through the last 5 days of your email sent folder, your meeting calendar, your chat messages, and any paper notes. For each item, ask: 'Did I capture everything I committed to?' Anything you missed goes into the system now. Track how many items you missed each week in a simple tally. Over four weeks, this number should decline toward zero. If it stays high, identify which source you keep missing (meetings, hallway conversations, email replies) and build a specific capture trigger for that context.
Mastered Operate at the highest level.
  • Integrate your capture system with your team's tools so nothing falls through the cracks at handoff points. When someone assigns you a task in Slack, email, or a project management tool, the item should reach your capture system within 5 minutes, either through an automation (Slack reminder to your task manager) or a manual habit (immediately adding it during the conversation). Test this by asking a colleague to send you three requests through different channels on a random day. If all three appear in your system within the hour, your integration is working. If not, identify the gap and fix it.
  • Develop a 'mental sweep' technique you can run in under 5 minutes during high-pressure periods. When stress spikes, whether before a big presentation, during a crunch week, or when you feel overwhelmed, sit down with your capture tool and dump everything on your mind in rapid-fire, one item per line, without organizing or processing. Set a timer for 5 minutes and write continuously. The goal is not to solve anything but to move every open loop from your head to your system. Process and organize the items during your next scheduled processing session. Most people report an immediate drop in anxiety after this practice.
  • Measure the impact of your system on focus quality. For two weeks, track two metrics daily: (1) How many times during focused work did you get pulled away by a nagging thought about something you need to do? (Score 0-5 per focus session.) (2) How many commitments did you miss or remember at the last minute? At the end of two weeks, review the numbers. If both are consistently low (0-1 per day), your system has earned your brain's trust. If either is high, identify whether the problem is incomplete capture, insufficient processing, or skipping your weekly review, and address that specific gap.

Unlock Skill Progression

Coaching Personalized to your current level
Progress Tracking Across every skill area
Mastery Validation Evidence-based, not guesswork