<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by FacileThings on Medium]]></title>
        <description><![CDATA[Stories by FacileThings on Medium]]></description>
        <link>https://medium.com/@facilethings?source=rss-4c17513083b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*5spoREXCzrSKbSjP.png</url>
            <title>Stories by FacileThings on Medium</title>
            <link>https://medium.com/@facilethings?source=rss-4c17513083b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:38:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@facilethings/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Weekly Review: The Habit That Keeps Your Entire GTD System Running]]></title>
            <link>https://facilethings.medium.com/the-weekly-review-the-habit-that-keeps-your-entire-gtd-system-running-05d107a32d04?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/05d107a32d04</guid>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[stress]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[self-awareness]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 19:12:55 GMT</pubDate>
            <atom:updated>2026-11-04T19:12:55.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Na27mHQKqxdqnhXu.png" /></figure><p>You may have noticed that, throughout this series of articles, <strong>the Weekly Review</strong> has come up time and time again. We introduced it when discussing the “reflect” step; it came up again as one of the four essential habits for implementing GTD; and we also noted that it’s the way to get yourself back on track after a falling off the wagon. This is no coincidence. David Allen considers it <strong>the key to success for the entire methodology</strong>, and in this final article, we’re going look at it in the detail it deserves.</p><h3>Strategic, not functional</h3><p>During the week, your relationship with the system is functional: you capture what comes up in your life, clarify the contents of your inboxes, choose the next action, and take it. You work at ground level, tackling what’s right in front of you. <a href="https://facilethings.com/learning/en/tutorial/the-weekly-review">The weekly review is something else</a>. It’s the time to look up and take a look at the big picture, your personal and professional life at the same time, to check three things:</p><ol><li>That <strong>everything is in the system</strong>,</li><li>That <strong>everything is up to date</strong>, and</li><li>That <strong>the system remains 100 percent usable and reliable</strong>.</li></ol><p>That last condition is fundamental. GTD works because the mind stops carrying the burden of commitments when it trusts that they’re stored in an external location. But that trust isn’t automatic or permanent. All it takes is for the system to fall out of sync for a couple of weeks for you to start doubting it, and as soon as you have doubts, your mind takes over again and tries to remember everything. The weekly review is the recurring maintenance that prevents that from happening.</p><p>And when it’s already happened, when you’ve had a chaotic week and the system has fallen behind, this is also the way to get back on track. It’s the step that gets you back on the wagon. You don’t have to start from scratch or reorganize everything; a quick review is all it takes.</p><p>Allen suggests setting aside about two hours at the end of the workweek, although everyone eventually finds their own time and pace. The important thing is to treat it like <strong>an appointment with yourself</strong>, with its own slot in the calendar, and not as something you’ll do if you have extra time, because you never have extra time.</p><p>The review is organized into three phases, and the order matters.</p><h3>Phase one: gaining clarity</h3><p>The goal of the first phase is to <strong>clear out the inboxes</strong>, and it begins with a sweep up on three fronts. The physical cleanup involves gathering loose papers, notes, receipts, cards, and anything else that’s been piling up on your desk, in your wallet, or in your backpack. The digital cleanup involves going through your email, notes on your phone, saved messages, the downloads folder, or your computer’s desktop. And the mental cleanup involves sitting down for a few minutes to clear your mind of everything that’s still swirling around in there, using a <a href="https://facilethings.com/blog/en/the-mind-sweep">list of triggers</a> like the one we saw in the previous article, in case you’re having trouble getting started.</p><p>During the sweep, you only <a href="https://facilethings.com/gtd-dictionary/en/capture">capture</a> items. Nothing is analyzed nor organized: everything goes into the inbox without having yet decided what it is or what to do with it. Mixing these two activities slows down the sweep and causes things to slip through the cracks, for the same reason we discussed when talking about capturing items in day-to-day life.</p><p>Then it’s time to <a href="https://facilethings.com/gtd-dictionary/en/clarify">clarify</a>, but <strong>you should only clarify what you’ve just captured</strong>. One of the most common mistakes is turning the weekly review into the session where you clarify everything that wasn’t clarified during the week. Clarifying is a daily habit, so you should arrive at the weekly review with an empty inbox or very few items. If you arrive at the review with a hundred pending items, processing them will eat up all your available time and energy, and you’ll never get to the phases that truly make the review valuable. If that’s the case for you, dedicate a different session to catching up on that backlog before the review, and save this one for what it’s truly meant for.</p><h3>Phase two: updating</h3><p>With the inboxes empty, it’s time to <strong>go through the system list by list</strong>. This is the longest phase, and the one that ensures that what your lists say matches reality.</p><p>Start with your <a href="https://facilethings.com/gtd-dictionary/en/calendar">calendar</a>, looking both ways. Look back to review the days that have passed since your last review and catch up on any follow-ups you may have missed: the email you promised to send after a meeting, the task that was left unfinished. Look ahead to anticipate what’s coming in the next few weeks and give yourself plenty of time to prepare for anything that requires advance planning.</p><p>Next up are the <a href="https://facilethings.com/gtd-dictionary/en/next-actions-list">Next Actions</a> and the <a href="https://facilethings.com/gtd-dictionary/en/agenda">Agendas</a>. Check off what’s already been done and make sure each action is still relevant and clearly written, meaning it starts with a verb that describes a physical, visible action. “Think about vacation” isn’t one; “Look for flights to Lisbon for the first week of August” is. This review is also an invitation to reflect. If there are actions that have been on the list for weeks without you touching them, ask yourself why you’re procrastinating on them. Sometimes the answer is that they’re poorly defined and need to be made more specific. Other times, it’s because you don’t actually have a real commitment to them, and in that case, the most honest thing to do is to move them to the <a href="https://facilethings.com/gtd-dictionary/en/someday-maybe-list">Someday/Maybe list</a>. A list full of tasks you know you’re not going to do loses its value, because you get used to ignoring it.</p><p>Review the <a href="https://facilethings.com/gtd-dictionary/en/waiting-for-list">Waiting For list</a> to make sure deadlines are being met. If something you were expecting is taking longer than is reasonable, it’s time to follow up on it, or make a note to do so.</p><p>The <a href="https://facilethings.com/gtd-dictionary/en/project-list">list of Projects</a> is handled in a similar way, also starting with the wording. A project must be described using a result verb, and the question that helps you formulate it is: What needs to happen so you can check it off? “Website” doesn’t answer that question; “Launch the store’s new website” does, because you’ll know exactly when you’re done. Next comes the most important question: Are you still committed to each project? Pay special attention to the ones that no longer have a next action, because those are the ones that have stalled without you realizing it. You need to reassess each one. Either you decide to continue (in which case you define the next action that gets it back on track) or you acknowledge that now isn’t the right time and set it aside for now. What you shouldn’t do is leave it on the list as if it were moving forward.</p><p>This phase ends with <a href="https://facilethings.com/gtd-dictionary/en/checklist">checklists</a>, the lists you use as recurring reminders. Going over them acts as a trigger. You often discover an area you’ve been neglecting for some time or a recurring task you’ve overlooked, and that leads to new actions or projects.</p><h3>Phase three: applying creativity</h3><p>Once you get here, you have a complete, up-to-date, and usable system, and that puts you in a rare state of mind, with <strong>a high degree of perspective and mental clarity</strong>. There’s nothing in the background pulling your attention anymore, and you know exactly what you’re dealing with. It’s the best possible time to think beyond the immediate, and you have to take advantage of it.</p><p>The main tool in this phase is the <strong>Someday/Maybe list</strong>, but the goal isn’t to go through it as a mere formality, it’s to review it creatively. Is there anything that’s now worth pursuing? Anything you’re no longer interested in and can cross off? Any idea that, when combined with another, gives rise to something new?</p><p>This is also the time to reassess your commitments as a whole, to ask yourself whether what you’re currently working on reflects what you truly want to do, and to capture new ideas, no matter how ambitious or far-fetched they may seem. Allen encourages you at this point to be creative and bold: with a clear head, ideas have room to emerge, and the system ensures they won’t get lost.</p><h3>A reminder system, not a storage system</h3><p>Some people, when they start using GTD, complain about having to duplicate things that already exist in other systems, such as the team’s project management tool, the CRM, the shared folder, or the incident manager. If all that already exists, why copy it? The answer is that <strong>in GTD, nothing is duplicated</strong>. What you keep in your system aren’t the items themselves, but reminders of them. Your project “Present the proposal to the client” doesn’t reproduce the content of the proposal or the team’s tasks; it simply reminds you that there’s an outcome you’ve committed to and what’s your next step toward achieving it.</p><p>What you do need is to be able to <strong>quickly access information when you need it</strong>. A good system doesn’t force you to search; instead, it takes you directly to the document, conversation, or folder you need to take action. The Weekly Review is a great opportunity to improve in this area. If, while reviewing a task, you have to stop and think about where the contract was or which email thread discussed the budget, add the link or the missing information. Week by week, the system becomes more accessible, and the easier it is to use, the more you’ll use it.</p><h3>The habit that sustains everything</h3><p>With this article, we conclude the series. We began with an introduction to the methodology, walked through its five steps, and saw how to implement it in our daily lives. The Weekly Review is the piece that ties everything together. Capturing, clarifying, organizing, and engaging are habits you can practice imperfectly for a while without the system falling apart; but if you stop reviewing, it will. Without a review, lists become outdated, confidence disappears, and your mind ends up shouldering the burden again.</p><p>That’s why it’s worth protecting. You don’t need it to be perfect or to last two hours. <strong>You need it to happen, week after week, because that’s what turns a collection of lists into a system you can rely on</strong>. And it’s that trust that allows you to give yourself fully to what you’re doing, knowing that everything else is waiting for you exactly where it should be.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/the-weekly-review-habit"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05d107a32d04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Get Started with GTD: Set up a System That Works and Make It a Habit]]></title>
            <link>https://facilethings.medium.com/how-to-get-started-with-gtd-set-up-a-system-that-works-and-make-it-a-habit-14f838bb87fc?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/14f838bb87fc</guid>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[system-design-concepts]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 18:09:09 GMT</pubDate>
            <atom:updated>2026-10-14T18:09:09.725Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*QZNZ0mLmD7fYO2kn.png" /></figure><p>In the previous articles, we’ve gone over <a href="https://facilethings.com/blog/en/basics-workflow">the five steps of the GTD workflow</a>: <strong>capture, clarify, organize, reflect, and engage</strong>. Understanding them is relatively simple. The challenge is incorporating them into your daily routine and not giving up on them after a few weeks, when the initial enthusiasm fades and old habits creep back in. In this fourth installment, we’ll focus on exactly that: how to put GTD into practice.</p><h3>First the habits, then the system</h3><p>The most common mistake when starting out with GTD is spending too much time trying to design the perfect system: comparing apps, defining dozens of contexts, building a flawless tag taxonomy… and never actually putting the methodology properly into practice.</p><p>That’s why our advice for getting started is to <strong>focus on habits and settle for a minimally functional system</strong>. A few lists that you check every day are worth much more than a sophisticated structure that you’ll abandon within a month. The system will become progressively more refined as you use it, and <a href="https://facilethings.com/learning/en/tutorial/the-weekly-review">the weekly review</a> is the natural time to do this: you’ll see which lists you never check, which contexts are unnecessary, and which ones you’re missing.</p><h3>Customize your system</h3><p>Even if it’s minimal, your system needs to show your real life-even if it’s not a complete picture. <strong>Start with projects</strong>, meaning all the tasks that require more than one action to complete. One or two lists are enough: a single list if you prefer to see all your commitments together; or two, one personal and one professional, if your two spheres are clearly separate.</p><p><strong>Next come the contexts</strong>, which answer a very specific question: What do I need in order to perform this action? Sometimes it’s a tool, sometimes a place, and sometimes a person. It’s often helpful to think of them in groups. Communications give rise to contexts such as #calls, #phone, or #whatsapp. Tools lead to contexts such as #computer, which you can break down into personal and work-related if you use different devices. Workplaces generate contexts such as #office or #company, and fixed locations in your personal life generate others such as #home or #home2 if you have a second residence. Finally, there are temporary locations: #errands for everything you do outside, or contexts for places you visit fairly often, such as #town or #Madrid. The idea is that, when you&#39;re in one of those situations, you&#39;ll see only what you can do there. If a context is always empty or you never check it, delete it without hesitation.</p><p>There’s one type of context that deserves special mention: <strong>agendas</strong>. It involves creating a context with the name of each person you interact with frequently and share certain activities with, such as your manager, your partner, or a close colleague. Whenever something comes up that you need to discuss with that person, instead of sending them a message or walking over to their desk right then and there, you write it down in their agenda. When you talk, you go over the list and address everything at once. In practice, it’s an anti-interruption tool: you stop interrupting others, and over time, your example encourages others to do the same with you.</p><p><strong>Tags</strong>, which resemble contexts in appearance, serve a different function. They don’t tell you where or how to take action; instead, they’re used to organize reference material and items in the “Someday/Maybe” list. You can have an #ideas tag to save thoughts you don&#39;t want to forget, topic-based tags like #programming or #design, and collections like #movies you want to watch, #places you want to visit, or #beers you want to try. When properly labeled, the &quot;Someday/Maybe&quot; list stops being a jumble and becomes a catalog you&#39;ll want to browse from time to time.</p><p>There’s one practical question left: how to link each action to its project. The easiest way is through the wording itself. An action like “Call the management company to ask about the tax return” makes it clear which project it belongs to without needing anything else. You can also use tags for this, but you run the risk of them getting mixed up with contexts and other tags until you no longer know what each one means. If you choose to use an app to implement GTD, it will usually allow you to link each action directly to its project.</p><h3>Mind sweep</h3><p>With the lists prepared, it’s time to fill them out. A <a href="https://facilethings.com/learning/en/tutorial/mind-sweep">mind sweep</a> is a <strong>systematic and exhaustive recording of everything that demands your attention</strong>: commitments, unfinished tasks, ideas, concerns, and things you should have done but haven’t. The problem is that none of this comes to mind on its own, because memory works by association and needs stimuli. That’s why the sweep relies on a <a href="https://facilethings.com/blog/en/the-mind-sweep">list of potential unfinished items</a>, a reference list with categories that trigger memories. In the professional sphere, this includes things like projects you’ve started but not finished, commitments to your manager or coworkers, pending calls and emails, meetings to prepare for, or administrative tasks. On the personal front, it covers the house and home repairs, family, health, finances, travel, hobbies, or things you need to buy.</p><p>The process has three steps. First, you capture ideas by going through the list at a leisurely pace and jotting down everything that comes to mind, without evaluating anything just yet. Next, you clarify and organize what you’ve captured, just as we saw in the previous articles. And finally, you cross off the categories you’ve already reviewed from the “triggers” list. This last step is what allows you to <strong>tackle the mind sweep in several stages</strong>: the first time you do it usually takes a while, so it’s okay to spread it out over several sessions as long as you know where you left off.</p><p>We’ve already seen in other articles that pending tasks lead to intrusive thoughts that interfere with other tasks. By combining the mind sweep with the clarification phase, you don’t complete everything on your to-do list, but each item ends up with a defined next step and an proper reminder, and your mind will stop reminding you of it every few moments. It’s normal to feel a bit overwhelmed when you see the volume of what you’ve captured, but that volume was already there; the difference is that now you can see it.</p><h3>The initial goals</h3><p>Don’t try to master it all from day one. <strong>The initial goal boils down to four habits</strong>:</p><ol><li>capture everything that catches your attention as soon as it appears;</li><li>clarify and organize everything you’ve captured on a daily basis;</li><li>choose your next action by filtering based on the criteria we discussed in the previous article;</li><li>and do your weekly review.</li></ol><p>With these four habits in place, you already have a minimally functional system. Everything else can wait.</p><p>You’ll probably also have to re-educate the people around you. The people in your life are used to interrupting you when they need to and to expecting an immediate response. Setting aside blocks of uninterrupted time, grouping communications together, or starting to use agendas takes time, but people adapt quickly once they realize that, even if you don’t answer right away, you’ll always get back to them.</p><h3>Tips for improving your personal effectiveness</h3><p>The first key is to recognize that <strong>sustainable change is built on habits, and that habits are adopted gradually</strong>. A study by Phillippa Lally and her team, published in 2010 in the <em>European Journal of Social Psychology</em>, found that it took participants an average of 66 days to make a new behavior automatic, with huge variations between individuals and between habits: ranging from 18 to 254 days. The same study noted that skipping a single day did not derail the process. The practical takeaway is twofold: patience, and not trying to adopt all habits at once.</p><p>The second key is to <strong>make the work clear</strong>. Much of the stress doesn’t come from the amount of work, but from not knowing exactly what it implies. That’s why GTD emphasizes turning the unknown into something known, breaking down each outcome into a visible next action, and making the wording of each task as specific as possible. “Prepare a budget” forces you to rethink it every time you read it; “Ask Lewis for the estimated hours for the client’s budget” doesn’t. That specificity helps you when it’s time to take action, because you don’t have to decide anything, and also during your weekly review, because you can see at a glance where each item stands.</p><p>The third key has to do with <strong>attention</strong>. We can work with <em>reactive attention</em>, responding to whatever comes our way, which is inefficient and shouldn’t be the rule. We can work with <em>proactive attention</em>, which we use to analyze and make decisions: it doesn’t cause stress, but it does require effort, and it’s the kind of attention suited for moments like clarifying tasks or conducting the weekly review. And we can work with <em>receptive attention</em>, in which, since everything has already been decided, you simply flow from one action to the next without stressing. Much of the beauty of GTD lies in the fact that it helps you invest your proactive effort at the right moments so you can spend the rest of your time in receptive mode.</p><p>Related to this is the principle of <strong>being present in what you’re doing</strong>. Work that requires concentration needs continuous, uninterrupted blocks of time. In 2009, researcher Sophie Leroy described what she called “attention residue”: when we switch tasks, part of our attention remains tied to the previous one, and our performance on the new task suffers as a result. Constantly jumping from one thing to another comes at a cost, even if we don’t realize it.</p><p>It’s also a good idea to <strong>make the most of your energy</strong>. Knowing yourself means knowing when you’re at your most productive during the day and setting aside those times for demanding tasks, while saving routine tasks for when your energy levels decline.</p><p>And finally, <strong>start and finish</strong>: completing what you start brings a sense of satisfaction that your brain appreciates, while letting things remain half-finished creates the feeling that you’re never making progress, even if you’re working nonstop.</p><h3>The surfboard effect</h3><p><strong>You’re going to fall</strong>. There will be chaotic weeks when your inbox overflows, you don’t get anything sorted out, and you skip your weekly review. It’s inevitable, and it’s good to know this from the start so you don’t see it as a failure. It’s just like learning to surf: falling is part of the process, and in fact, it’s a sign that you’re using the method, because you can only fall off a board you’ve actually gotten on. The important thing is to realize it and get back on. A quick mind sweep, clarifying everything that’s piled up, and a weekly review, is enough to get back on track in a matter of hours, without having to start from scratch.</p><p>David Allen uses an image drawn from martial arts to describe the state that GTD aims for: <strong>the mind like water</strong>. If you throw a stone into a pond, the water responds exactly in proportion to the force applied and then returns to calm. It neither overreacts nor underreacts. That is what a system you trust enables: responding to each thing with the attention it deserves (no more and no less) rather than reacting to the loudest stimulus of the moment.</p><h3>The path towards GTD mastery</h3><p>None of these practices happen on their own. You have to work on them every day and reinforce them until they become habits. Once you achieve that, you’ll be able to maintain focus, or quickly regain it when you lose it; eliminate distractions and focus on what really matters. In short, you’ll keep your world in balance.</p><p>That’s why, beyond simply getting more done, effectiveness has a lot to do with well-being: with the peace of mind that comes from knowing everything is under control and that what you’re doing at any given moment is what makes sense to do. Of all the habits we’ve discussed, there’s one that underpins the others and makes the difference between those who practice GTD for years and those who give it up after just a few months: the weekly review. We’ll cover this in the next and final article in the series.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/how-to-get-started-with-gtd"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14f838bb87fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Organize, Reflect, and Engage: The Three Steps That Complete the GTD Workflow]]></title>
            <link>https://facilethings.medium.com/organize-reflect-and-engage-the-three-steps-that-complete-the-gtd-workflow-c95ca57fe620?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c95ca57fe620</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[gtd]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 18:03:15 GMT</pubDate>
            <atom:updated>2026-09-30T18:03:15.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*J14zF_ProYwCWKrI.png" /></figure><p>In <a href="https://facilethings.com/blog/en/capture-and-clarify">the previous article</a>, we looked at <strong>how to capture</strong> everything that demands our attention and <strong>how to clarify</strong> each matter until it becomes a decision. But every decision we make needs a place to be stored, a time to revisit it, and, finally, an opportunity to carry it out. That’s what the three steps that complete <a href="https://facilethings.com/blog/en/basics-workflow">the GTD workflow</a> are all about: <strong>organizing, reflecting, and engaging</strong>.</p><h3>Organize</h3><p>Our brains are unreliable when it comes to remembering to-do lists, but they’re surprisingly good at <strong>associating places with meanings</strong>. We know instinctively where our keys are if we always leave them in the same spot, and just seeing a package by the door is enough to remind us that we need to return it. <a href="https://facilethings.com/gtd-dictionary/en/lists">GTD lists</a> are based on that ability: when each type of task has its own place, knowing where to locate something is equivalent to knowing what it is and what needs to be done with it. The mind stops wasting energy on remembering and reclassifying the same things over and over again, and that freed-up energy is, to a large extent, what makes us more effective.</p><p><a href="https://facilethings.com/gtd-dictionary/en/organize">Organizing doesn’t require inventing anything</a>. The categories are already determined by the decisions we make as we clarify things, and each answer from the previous step has its corresponding list.</p><p>The actions we need to do go on the <strong>Next Actions</strong> list, and they should be done as soon as possible, whenever circumstances allow. If, on the other hand, they need to happen on a specific day or at a specific time, they belong in the <strong>Calendar</strong>, which also includes events and information that’s only relevant on a specific date. It’s important to protect the calendar: if it fills up with things that “would be nice to do that day,” it stops reflecting what actually needs to happen, and we lose confidence in it.</p><p>Some tasks can only be completed when we’re with a specific person, and that’s where <strong>Agendas</strong> come in: lists of pending matters to discuss with each person or at each regular meeting, so that when we meet with them, we have everything we wanted to talk about right at our fingertips. And when what’s missing depends on others, the task goes to the <strong>Waiting For</strong> list. The key here is to note three things: what we’re waiting for, from whom, and since when. Without the date, it’s impossible to know if a delay is normal or if we should follow up. An item doesn’t come off this list until what we were waiting for comes back to us.</p><p><strong>Projects</strong>, on the other hand, are the list of pending outcomes. They don’t contain the complete plan, but rather a commitment to an outcome that requires more than one step, and every active project should have at least one next action in one of the lists above. If it doesn’t, the project is at a standstill even if we continue to believe it’s moving forward.</p><p>Things that aren’t actionable also have their place. What we decide not to decide just yet goes to <strong>Someday/Maybe,</strong> where it sits until we revisit it. Information that might be useful to us later goes to <strong>Reference</strong> as reference material. And what’s no longer needed goes to the <strong>Trash</strong>, which is also a legitimate way to organize.</p><p>To sum up:</p><ol><li><strong>Next Actions</strong> → actions I need to do myself, as soon as possible</li><li><strong>Calendar</strong> → actions I need to do myself, with a specific date and/or time, and events and information that are relevant on a specific date and/or time</li><li><strong>Agenda</strong> → next actions that require me to meet with someone to complete them.</li><li><strong>Waiting For</strong> → next actions that other people need to do</li><li><strong>Projects</strong> → pending outcomes</li><li><strong>Someday/Maybe</strong> → items I’ll evaluate later</li><li><strong>Reference</strong> → supporting material</li><li><strong>Trash</strong> → items I don’t need</li></ol><p><strong>The way each item is worded matters</strong> just as much as where we place it. The next action must be able to be carried out without any obstacles. When we read it, we should know exactly what to do, without having to think again about what it meant. That’s why actions are written using specific verbs (“call Marta to request a quote,” “draft the contract”), while projects can use more generic verbs that describe the result (“renovate the kitchen,” “launch the new website”). A list of vague actions forces us to go back and clarify them every time we consult them, and it ends up being a list we avoid looking at.</p><p>Ultimately, the system that replaces our memory is nothing more than that: <strong>reminders organized into lists</strong>. Actions and projects take place in real life, not within GTD. What the system stores are the cues that allow us to keep track of everything.</p><h3>Reflect</h3><p>If I had to choose the most important step in the entire workflow, it would be <a href="https://facilethings.com/gtd-dictionary/en/reflect">reflect</a>, and it takes the form of a specific habit: <strong>the Weekly Review</strong>. Its purpose is to maintain trust in the system. A system that isn’t reviewed becomes outdated, and when we stop trusting it, our minds take over and try to remember everything on their own. In other words, we’re back to square one.</p><p>The Weekly Review is not the time to catch up on everything we didn’t do during the week, nor some heroic session to make everything perfect. It’s just a review, and any review-no matter how brief or incomplete-is better than none at all. Given its importance, we’ll devote a separate article to it later; here, I’m simply showing you its basic structure.</p><p>David Allen breaks down the weekly review into three objectives. The first is to <strong>gain clarity</strong>, which usually takes between five and ten minutes: clearing out your inboxes and sorting through whatever has piled up, including loose papers and anything that’s still on your mind.</p><p>The second step is to <strong>get up to date</strong>, which is the most time-consuming part, taking about thirty to forty-five minutes. This involves removing what’s already been done, filling in any missing information, and going through the lists one by one. The <em>Calendar</em> is reviewed in two directions: backward, from the last review, to identify commitments or follow-ups that may have been overlooked; and forward, four or five weeks, so that nothing catches us off guard with little time to react. The <em>Next Actions</em> and <em>Agendas</em> are reviewed to confirm that they’re still valid. The <em>Waiting For</em> list requires active management: if following up on something takes less than two minutes, it’s done right away; otherwise, a reminder is set to handle it later. Finally, in the <em>Projects</em> section, we look for those that no longer have a next action so we can reactivate them, and we review their supporting materials to see if they contain anything we may have overlooked.</p><p>The third goal is to <strong>get creative</strong>. With the system up to date, the mind finally has room to look further ahead: to review the <em>Someday/Maybe</em> list to see if anything is worth pursuing, to capture new ideas, and to consider which projects we want to get off the ground. It’s the reward for the work we’ve done, because it’s hard to think ambitiously while part of your mind is still preoccupied with what might be slipping through the cracks.</p><ol><li><strong>Gain clarity</strong> → 5–10 minutes</li><li><strong>Get up to date</strong> → 30–45 minutes</li><li><strong>Get creative </strong>→ 0–?</li></ol><h3>Engage</h3><p>The goal of all of the above is very simple to articulate: to feel good about what we’re doing at any given moment. And that’s only possible when we know that what we’re not doing is accounted for elsewhere. <a href="https://facilethings.com/gtd-dictionary/en/engage">In GTD, engaging</a> isn’t simply about executing tasks; it’s about <strong>filtering and choosing</strong> from a set of tasks that have already been defined.</p><p>Throughout the day, we work in three different ways. Sometimes we tackle <strong>work as it shows up</strong>: unexpected events, requests, and urgent matters that pop up without warning and that, at times, are rightfully the most important. Other times (most of the time), we <strong>work on tasks that have already been defined</strong>-those listed in our reminders: the <em>Calendar</em>, <em>Next Actions</em>, and, optionally, the <em>Waiting For</em> list. And other times we work on the system itself, <strong>defining the work</strong>: capturing, clarifying, and organizing. This third approach is the one most easily neglected, and when we devote little time to it, the rest of the work becomes poorly defined, and everything ends up turning into work that just pops up.</p><p>When it comes down to <strong>choosing between tasks that have already been defined</strong>, the decision goes through a series of filters. The first is <em>context</em>: where we are, who we’re with, and what tools we have available; because it doesn’t make sense to consider making a call if we don’t have a phone handy. The second is the <em>time available</em>: twenty minutes before a meeting isn’t enough to start a report, but is enough to wrap up three pending tasks. The third is <em>energy</em>: some tasks require a fresh mind, while others can be done just fine late in the afternoon. Only after applying these filters, among the remaining options, do we ask ourselves which one makes the most sense to do right now.</p><ol><li><strong>Context</strong> → place, person, tools</li><li><strong>Available time</strong></li><li><strong>Available energy</strong></li><li><strong>Which one makes the most sense?</strong></li></ol><p>For this to work, we need to develop the habit of returning to our lists every time we finish something and it’s time to choose the next action. If we don’t, the natural tendency is to do whatever comes up, and the day becomes reactive even if the system is flawless. And if we have trouble deciding when consulting our lists, the problem almost always lies in the fact that we haven’t clarified things well enough. A list of specific actions practically chooses itself; a list of vague intentions paralyzes us.</p><h3>A cycle, not a sequence</h3><p>Capturing, clarifying, organizing, reflecting, and engaging aren’t five phases that you complete once and then forget about; rather, they’re a cycle that repeats daily and is readjusted each week. None of the steps is difficult on its own; what makes the difference is practicing them consistently enough that they no longer require effort. When that happens, the question of <strong>what to do next</strong> ceases to be a source of anxiety and becomes a calm choice, because everything else is exactly where it needs to be.</p><p>Knowing the five steps is just the beginning; the real challenge lies in putting them into practice in our daily lives without giving up on them after just a few weeks. We’ll discuss how to implement GTD in the next article in this series.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/organize-reflect-and-engage"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c95ca57fe620" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Capture and Clarify: The First Two Steps of the GTD Workflow]]></title>
            <link>https://facilethings.medium.com/capture-and-clarify-the-first-two-steps-of-the-gtd-workflow-5c79482e1c6b?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c79482e1c6b</guid>
            <category><![CDATA[gtd]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[workflow]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 17:33:16 GMT</pubDate>
            <atom:updated>2026-09-16T17:33:16.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*_sFtwgem2LKT19KX.png" /></figure><p>In <a href="https://facilethings.com/blog/en/the-perfect-storm">the previous article</a>, we looked at what GTD is and why so many people adopt it as their go-to system for staying organized. Now it’s time to dive into the workflow itself, starting with its first two steps: <a href="https://facilethings.com/gtd-dictionary/en/capture">capturing</a> and <a href="https://facilethings.com/gtd-dictionary/en/clarify">clarifying</a>. These are the foundations on which everything else rests, and they’re also the hardest to turn into a habit.</p><h3>Capture</h3><p><a href="https://en.wikipedia.org/wiki/David_Allen_(author)">David Allen</a> sums it up with a phrase worth keeping in mind:</p><blockquote>The mind is for having ideas, not holding them.</blockquote><p>When we use our minds as a storage place for pending tasks (that meeting we need to schedule, the call we mustn’t forget, the idea that came to us in the shower), our minds never stop going over them, even if we can’t do anything about them at that moment. Every unresolved commitment consumes background attention, even when we think we’re focused on something else. Capturing is the first step towards closing that loop.</p><p>The sources from which these “stuff” arise (as GTD calls them, precisely because at the moment we capture them we don’t yet know what they are or what we’re going to do with them) are varied: your own mind, loose papers, email, voicemail, a casual conversation in the hallway. Some things get captured almost automatically, like emails or notifications; others require us to pause for a second and write them down somewhere before they get lost.</p><p>The real goal of this step isn’t so much to <strong>prevent forgetfulness</strong>, though that’s part of it, as much as to <strong>retrain how we manage our attention</strong>. Every time we capture something instead of trying to hold onto it mentally, we teach our mind that it can safely let go and continue paying attention to what it was doing, because there’s an external, reliable place where it will be stored. We teach it to be present, to stay focused.</p><p>For this to work, you have to <strong>get used to capturing stuff without hesitation</strong>: anything, no matter how small or vague it may seem, has a place. You shouldn’t filter or make any decisions at the moment of capture; that evaluation comes later, during the clarifying step. Filtering at the moment of capture is what usually breaks the habit. You have to capture everything.</p><p>Having <a href="https://facilethings.com/blog/en/capture-tools-and-best-practices">the right tool for capturing stuff</a> in every situation is essential. The easier it is to capture information, the more automatic the behavior becomes. It doesn’t matter if it’s a notebook, an app, or a voice memo; what matters is that it’s always at hand when the need arises and allows you to capture with minimal friction.</p><p>That said, capturing alone has limited value. If the items we capture pile up without us doing anything with them, we’ve ended up with a backlog of unresolved tasks, not a clear and uncluttered mind. The value of capturing depends entirely on the second step that follows: clarifying.</p><h3>Clarify</h3><p>In practice, clarifying and organizing go hand in hand, and it’s best to do them all at once: <strong>empty your inboxes completely</strong>, without leaving anything half-done. For those who haven’t practiced GTD before, this step involves <a href="https://facilethings.com/blog/en/the-ultimate-skill-clarifying-precisely-what-is-what">a mental process</a> that doesn’t come naturally at first, so it’s a good idea to force yourself to go through the questions consciously until they become second nature.</p><ol><li>The first question is simply <em>what it is</em>. Before deciding anything, we need to <strong>understand what that issue is all about</strong>, what it really means to us.</li><li>The second question is <em>whether it’s actionable</em>: Do we want to do something about it, and, furthermore, is there anything we can do? “Painting the wall” isn’t actionable if we don’t have paint at home; there’s a preliminary step that needs to be taken first.</li><li>If the answer is that <em>it’s not actionable</em>, there are three options: simply <a href="https://facilethings.com/gtd-dictionary/en/trash">trash</a> it, <a href="https://facilethings.com/gtd-dictionary/en/reference-material">file it away for future reference</a> if it’s information that might be useful down the road (a contract, a warranty, meeting notes), or <a href="https://facilethings.com/gtd-dictionary/en/incubate">incubate</a> it, that is, consciously set it aside because we’ve decided not to make a decision just yet.</li><li>If the matter <em>is indeed actionable</em>, the key question is <em>what the next action is</em>. In GTD, <strong>the next action</strong> is the next concrete, visible step that moves the matter forward; something that is started and finished in one go, without depending on any intermediate steps. “Prepare for the meeting with the client” isn’t a next action; “send an email to Ana asking for the meeting agenda” is. Defining the action with that level of specificity is precisely what most people fail to do, and it’s the reason why so many tasks get stuck without anyone really knowing why. Once you’ve identified the next action, there are three ways to handle it: <em>do it right away</em> if it can be completed in less than two minutes (the well-known <a href="https://facilethings.com/gtd-dictionary/en/two-minutes-rule">two-minute rule</a>, designed for tasks that can be resolved immediately); <a href="https://facilethings.com/gtd-dictionary/en/delegate">delegate</a> it if you’re not the right person to carry it out; or <a href="https://facilethings.com/gtd-dictionary/en/defer">postpone</a> it, setting a reminder to return to it at the appropriate time. When we’re going to delegate a task, we often need to prepare something beforehand. In that case, the next actual action is that preliminary preparation, and only then comes the step of delegating.</li><li>Finally, if the matter requires more than one step to complete, clarify it by asking a broader question: <em>What is the end result we are seeking?</em> If step 4 is sufficient to resolve the matter, the process ends there; if not, <strong>we are dealing with a project</strong> (any outcome that requires more than one step and can be achieved in less than a year), and it should be defined as such. Defining the action first and then the project seems counterintuitive. That’s because we tend to do it the other way around-planning the entire project before taking the first step-and that’s precisely what leads to overplanning. <strong>Clarifying involves thinking and deciding</strong>, not designing a complete plan before taking action. When the issue to be clarified is an email (a common scenario) it almost never involves just a single issue. It’s common for a single message to contain several different stuff within the same email, and each one needs to go through its own clarification process.</li></ol><p>Capturing without clarifying simply shifts the noise from your head to a list; clarifying is what truly clears your mind, because each item is transformed into a decision you’ve made. With these two steps complete, the system is ready for the next one: organizing each item in its proper place, which is what we’ll discuss in the next article in this series.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/capture-and-clarify"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c79482e1c6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Perfect Storm: Why Modern Work Overwhelms and How to Deal with It]]></title>
            <link>https://facilethings.medium.com/the-perfect-storm-why-modern-work-overwhelms-and-how-to-deal-with-it-053021de8db0?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/053021de8db0</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[stress]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 18:33:17 GMT</pubDate>
            <atom:updated>2026-09-02T18:33:17.489Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*gvpIQ50PA_BVcQIe.png" /></figure><p>It’s Monday morning. You open your laptop and already feel the weight of it before you even read the first email. The feeling that there’s too much to do, that no matter how much you get done today, you’ll still have a lot left to do tomorrow. You’re hard-working and disciplined, so something must be slipping through the cracks.</p><p>That’s right. What’s happening is the natural result of two forces that have collided predictably: the nature of work has changed radically, and our brains continue to function according to the same design as always.</p><h3>Work isn’t what it used to be</h3><p>Throughout most of human history, work meant producing something tangible with one’s hands. It was obvious, predictable, and its output was proportional to the time invested. Economist <a href="https://facilethings.com/blog/en/peter-drucker-self-management">Peter Drucker</a> was the first to point out, in the late 1950s, that this was changing. A new class of worker, the <a href="https://facilethings.com/gtd-dictionary/en/knowledge-work">knowledge worker</a>, was beginning to dominate the economy. Unlike the manual laborer, who performs tasks already defined by someone else, <strong>the knowledge worker must define his or her own work</strong> before being able to do it.</p><p>That detail shifts the paradigm of work. It’s no longer enough just to “do”; you have to decide what to do, in what order, and what to leave undone, because there’s never enough time for everything. Knowledge work is unpredictable by nature, and there’s always something left undone at the end of the day. Performance no longer depends solely on execution, but on the quality of thinking and the decisions that are made. Drucker called it the greatest management challenge of the 21st century, and rarely has a prediction aged so well.</p><h3>A brain that wasn’t designed for this</h3><p>We’re the result of millions of years of evolution, and our brains operate using two very distinct thinking systems. Daniel Kahneman, a Nobel laureate in Economics for his work on the psychology of decision-making and behavioral economics, popularized them as <a href="https://facilethings.com/blog/en/self-control-and-productivity">System 1 and System 2</a>. System 1 is automatic, fast, emotional, and impulsive; it operates in parallel with everything else and cannot be turned off. System 2 is manual (it must be consciously activated), single-tasking, rational, and energy-intensive. According to Kahneman’s own estimates, the vast majority of our mental activity takes place in System 1: System 2 comes into play only a small fraction of the time, and it does so reluctantly, because it takes effort.</p><p>Over time, some processes migrate from System 2 to System 1. What initially requires total concentration-driving, typing, applying a new methodology-eventually becomes automatic. This is great news, because it means the initial effort isn’t permanent. But while that process is underway, we rely on System 2, and System 2 has very real limitations: limited mental energy and decision-making capacity, and a memory that becomes overloaded much sooner than we’d like to admit.</p><p>Let’s add one more ingredient: our brain developed, purely for survival, an “alert mode” that treats the unknown as a potential threat. That mechanism made sense when the unknown was a predator lurking in the bushes. Today, that same alert mode is triggered by an unprocessed inbox, by a half-formed idea swirling around in your head, by a commitment that exists nowhere but in your memory. The result is stress, even when there’s no real danger, just <strong>unresolved information</strong>.</p><h3>The perfect storm and its consequences</h3><p>When these two forces combine -work that constantly demands thinking and decision-making, and a brain with limited resources that interprets pending tasks as a threat- the result is what David Allen, who had spent decades closely observing how top-performing professionals work, named <em>the perfect storm</em>, and its consequences are all easy to see in today’s society.</p><p>We <a href="https://facilethings.com/blog/en/procrastination">procrastinate</a> because putting things off is the brain’s natural response to uncertainty. <strong>We choose instead of deciding</strong> because, when everything is competing for the same limited attention, we tend to do what’s easiest to check off the list, not what’s most important. <strong>We rely on our memory</strong> more than we should, and that unfounded reliance creates underlying stress that we often don’t even recognize as such. When under pressure, System 1 takes over and System 2 shuts down: stress makes us less competent just when we need to be at our best. <strong>We overplan</strong> in response to the need for control, achieving a false sense of mastery over something we don’t actually control; and <strong>we constantly interrupt ourselves</strong>, jumping from one thing to another, because the mental noise of pending tasks pushes us to check, review, and start over.</p><p>To a greater or lesser extent, this happens to all of us. It’s the logical response of a brain that was designed for a different kind of world and is now faced with a reality for which it hasn’t yet evolved.</p><h3>Effectiveness: The Missing Skill</h3><p>If the problem is structural, the solution must be as well. It’s not about “trying harder” or finding more discipline; both of these rely on System 2, precisely the one that runs out of steam first. It’s about developing a new skill: <a href="https://facilethings.com/blog/en/effectiveness-can-be-learned">effectiveness</a>, understood as the combination of efficacy and efficiency. This isn’t just an aspirational idea; it’s backed by evidence and works for anyone who applies it consistently. It rests on three pillars: <strong>proactively managing interruptions</strong> rather than suffering through them; <strong>adaptive planning</strong> that assumes the plan will change (“we’ll see how it goes”) rather than forcing a rigid script; and what is often called the <strong>extended mind</strong> -that means letting go of the expectation that memory can handle a task it isn’t designed for.</p><p>This last idea is simpler than it looks. Instead of relying on your memory, you place a visible external reminder where it makes the most sense. It’s exactly the same idea as leaving something by the front door so you don’t forget it when you leave. Externalizing is a way to relieve your brain of a task it’s not very good at, freeing it up for what it does well: thinking, deciding, and creating.</p><p>When this is applied systematically, what we might call the <strong>productive experience</strong> emerges: you feel in control, stress-free, focused, and fully present in what you’re doing. It’s a state we’ve all experienced at some point, almost always by accident. Our challenge is to get there most of the time, rather than having it happen only occasionally and by chance.</p><h3>Five steps towards getting back in control</h3><p>David Allen developed <a href="https://facilethings.com/blog/en/ultimate-guide-to-gtd">the Getting Things Done methodology</a> precisely to address this perfect storm. Essentially, it’s a five-step process that, once internalized as a habit, allows you to take control of your own workload. <strong>Capture everything that demands your attention</strong>, without leaving anything solely in your memory. <strong>Clarify what each item really means</strong> and what specific action it requires. <strong>Organize the result</strong> into a system you can rely on. <strong>Reflect regularly</strong>, reviewing the big picture so you don’t lose perspective. And take action, <strong>choosing what to do at every moment</strong> with the confidence that it’s the right choice, because everything else has already been captured, clarified, and organized elsewhere.</p><p><a href="https://gettingthingsdone.com/2009/02/when-productivity-is-low-getting-things-done-makes-at-least-a-20-difference/">A study by Productivity Scan</a>, conducted in collaboration with the David Allen Company, documented a minimum 20% improvement in personal productivity in low-performance settings following the implementation of GTD. But perhaps the most significant finding isn’t the percentage itself, but rather the mechanism: it’s not about working faster, but about stopping wasting mental energy on managing what an external system can manage for you.</p><h3>There are no shortcuts, but you don’t have to wait years either</h3><p>There’s one thing you should know: making these five steps second nature doesn’t happen overnight. <a href="https://onlinelibrary.wiley.com/doi/abs/10.1002/ejsp.674">Research on habit formation</a> (the benchmark study is by psychologist Phillippa Lally of UCL) shows that it takes an average of 66 days for a new behavior to become automatic, although the actual range varies between 18 and 254 days depending on the person and the habit. It’s not two years, but it’s not three weeks either. It’s a real process, with its own pace, and it’s best not to get discouraged if it requires conscious effort at first.</p><p>The good news is that the benefits don’t wait until the habit is firmly established. From the very first day that something leaves your head and enters a system you trust, that “alert mode” which used to perceive pending tasks as threats, eases up a bit. You don’t need to master the methodology to start noticing a difference, you just need to start.</p><p>The perfect storm isn’t going away. Knowledge work will remain unpredictable, and our brains will continue to have the same limitations they’ve always had. But that doesn’t mean we have to navigate it without tools. The question isn’t how to avoid the storm, but what system we build to weather it with a clear head.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/the-perfect-storm"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=053021de8db0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The New FacileThings: Rethinking the Tool from the Ground Up]]></title>
            <link>https://facilethings.medium.com/the-new-facilethings-rethinking-the-tool-from-the-ground-up-852cdbac3c68?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/852cdbac3c68</guid>
            <category><![CDATA[getting-things-done]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 00:00:14 GMT</pubDate>
            <atom:updated>2026-08-19T07:06:55.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*8T4-fzdlnEXDbKi3.png" /></figure><p>A little over a year ago, we made a decision that wasn’t easy: instead of continuing to add layers to the app you’ve been using for years, we were going to build a completely new one from scratch. Taking advantage of a short summer break, I wanted to tell you why, where we’re headed, and what technology is behind that decision.</p><p>Our motivation came mainly from listening to you. We conducted a survey to get a better understanding of what you truly value about FacileThings, and the overall response was quite clear: <strong>adherence to the GTD method</strong> and the feeling that this was a tool specifically designed to implement it effectively, without having to build your own system from scratch on top of a generic app. But you also told us, just as clearly, where the friction points were: an awkward mobile app, a somewhat outdated and cluttered web interface, and processes that required too many clicks to do something simple.</p><p>We came to the conclusion that we should keep the GTD structure intact, but redesign a significant portion of the interface.</p><p>At the same time, a series of specific circumstances arose, which also pushed us to make significant changes. The provider that supported our mobile app ceased operations, leaving us with no room to continue evolving. The technological infrastructure we had built up over the years had become outdated, and it was becoming increasingly difficult to maintain, adapt, and scale it. Moreover, infrastructure costs had risen to the point where continuing to patch the old system no longer made sense, neither technically nor financially.</p><p>Rebuilding the application from scratch, with <strong>an architecture designed both to significantly improve the user experience as well as to facilitate innovation</strong>, seemed like the most reasonable solution. Shifting to a <em>local-first</em> architecture is the most significant technical decision we’ve made in FacileThings’ 15-year history.</p><h3>What exactly is “local-first”?</h3><p>Most apps in the cloud work by requesting permission and information from a server-which can be located anywhere in the world-for every action the user takes. You save a task, the operation is sent to the server, you wait for the response, and you see the result. Every data exchange generates a brief delay, which results in loading indicators everywhere: animated icons spinning until the response arrives, loading skeletons simulating data until the actual data arrives, and so on.</p><p>In <strong>a local-first app</strong>, a complete copy of your data is stored locally on your own device, so that all operations (creating an action, completing a project, or clarifying an item in the inbox) take place on that local copy. The result is virtually instantaneous interaction, indistinguishable from a native app, and the ability to keep working even if your internet connection is lost, something that simply wasn’t possible in the classic version of FacileThings.</p><p>The component that enables the “local-first” approach is the <strong>synchronization engine</strong>, a piece of software that runs in the background and keeps your copy of the data on your device in sync with the copy stored on the server, even when you don’t have an internet connection. The synchronization engine is responsible for sending changes to the server and retrieving updates that have occurred on other devices, ensuring that both copies remain identical.</p><p>Although <a href="https://www.inkandswitch.com/essay/local-first/">the local-first architecture has existed conceptually for some time</a>, it has only become practical in recent years thanks to the evolution of browser storage APIs and the emergence of new tools that simplify data synchronization. By allowing data to remain on the client device and synchronize with a server or other nodes only when necessary, local-first applications can deliver a fast, reliable, and privacy-friendly user experience.</p><h3>The technology behind it</h3><p>On the front end, we’ve opted for React, React Router, and Vite. The component that enables the “local-first” behavior is Replicache, a software that manages the local copy of data and handles synchronization with the server optimistically, meaning it applies your changes immediately locally, and reconciles them with the server later. The backend remains a Ruby on Rails server that stores all the business logic and accumulated knowledge about GTD, although communication now takes place through an API optimized for sharing data with the new synchronization engine.</p><p>This synchronization engine has been, by far, the component that has required the greatest amount of engineering work on our part. At first, it worked well, but as we began incorporating beta testers with real-world data, some with many thousands of items accumulated over years of use, we started encountering use cases where performance degraded to an unacceptable degree. We’ve redesigned and optimized entire sections of that engine more than once to ensure it remains fast no matter how much historical data you carry with you.</p><h3>One single code, many entry points</h3><p>This architecture has an additional advantage that is essential to our vision and long-term sustainability. By separating the application’s logic from the device on which it runs, the same code that runs in your browser today will serve as the foundation on which we will later build <strong>desktop and mobile applications</strong>, without having to rewrite the product from scratch again. The idea is to build a single system and multiple ways to access it, all synchronized with each other in real time.</p><p>That same architecture also opens the door to something that still seemed far off just a year ago: <a href="https://facilethings.com/blog/en/new-mcp-server">the possibility of AI agents working directly within your GTD system</a>. It’s no coincidence that, alongside the development of this new app, we’ve started building <strong>an MCP server</strong> that allows models like Claude or ChatGPT to capture, clarify, and, in the future, help you with your weekly review, by speaking the same API language that powers the app.</p><h3>What’s Next</h3><p>The new app is currently in beta with invitation access, but it will be fully open next month. It covers the entire GTD workflow (capture, clarify, organize, review, and act), but some important pieces are still missing: the weekly review, routines, and, later on, the packaged versions as mobile and desktop apps that I mentioned earlier.</p><p>We’re releasing a new update every week, and we’ll keep doing so, fine-tuning each feature based on your feedback, <strong>until this app truly becomes the best way to implement GTD that you can have</strong>.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/the-new-facilethings"><em>https://facilethings.com</em></a><em> on August 18, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=852cdbac3c68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Talk to Your GTD System: How FacileThings New MCP Server Works]]></title>
            <link>https://facilethings.medium.com/talk-to-your-gtd-system-how-facilethings-new-mcp-server-works-de15a1e4d5a3?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/de15a1e4d5a3</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[gtd]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 00:00:07 GMT</pubDate>
            <atom:updated>2026-08-26T15:20:34.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*9arm1a5r3NC4ck7Nf0ypKQ.png" /></figure><p>Can you imagine telling Claude, without opening any app: <em>“note that I need to call Marta to talk about her new contract,”</em> and having that thought land exactly where it should, in your FacileThings inbox? Or asking it mid-morning: <em>“what’s pending on the website project?”</em> and getting your actual next actions back? Or sitting down on a Sunday afternoon and letting your assistant walk you through your weekly review, conversationally?<em>(1)</em></p><p><strong>FacileThings’ new MCP server</strong> is a bridge that connects your GTD system directly to Claude, ChatGPT, or any other LLM compatible with the <a href="https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro">Model Context Protocol</a>, so you can capture, organize, and review your life and work using natural language.</p><p>This isn’t just a connection to your data. The server comes with a set of instructions on how an assistant should behave inside a GTD system managed with FacileThings: what capturing means, what clarifying means, how the tickler file works, what sets an action apart from a project, how areas of focus and goals relate to whatever you’re working on, and so on. That way, before telling you which list something belongs in, or whether something is an action or a project, the assistant can consult these guidelines instead of improvising <em>(2)</em>.</p><p>We’ve also built in safety instructions, such as never permanently deleting anything without your explicit confirmation, always choosing to move something to trash rather than delete it, and asking rather than guessing when it isn’t clear which list a captured item belongs in.</p><p>The goal is <strong>an assistant that knows FacileThings and respects the GTD methodology</strong>, rather than one that simply executes literal commands against a database.</p><p>We’re launching this first version straight into public beta, which means every FacileThings user already has access.</p><p>This first version includes a good number of tools for capturing, reviewing, and organizing your system, but it doesn’t yet cover all of FacileThings’ capabilities <em>(3)</em>. We’ll keep filling it out based on how you actually use it. So we encourage you to try what we already have and tell us what’s missing or what could be improved through the app’s Support system.</p><p>Here’s an <a href="https://cdn-ft-site.nyc3.cdn.digitaloceanspaces.com/blog/en/mcp-claude.mp4">example of a session with Claude</a>. On the right, you can see how the new Beta app reacts automatically to the changes.</p><p><em>(1) This last question is the most ambitious one, but in upcoming versions we’ll add specific prompts to guide you through clarifying your inbox and doing your weekly review, so conversations like these turn into a step-by-step guided flow.</em></p><p><em>(2) Important note: the fact that these guidelines exist doesn’t mean the assistant always consults them on its own initiative. Depending on the LLM you’re using, it may not turn to them automatically and may only do so when you explicitly ask it to. So at first, you’ll likely need to be the one telling it how you want it to do things (for example, asking it to check FacileThings’ guidelines before deciding which list something belongs in, or telling it what you exactly expect from specific requests). Usually, once you tell it, the assistant will remember that way of working for future conversations, so you won’t need to repeat it.</em></p><p><em>(3) This first version has tools to access lists, capture items, move items between lists, review and edit tasks, manage projects and sub-projects, access context and person tags, and manage the perspective horizons (purpose, principles, vision, goals, and areas of focus).</em></p><h3>How to connect FacileThings MCP to Claude</h3><p>Connecting your FacileThings account to Claude takes less than a minute and requires no technical knowledge. The steps are the same whether you’re using Claude in the browser or the desktop app:</p><ol><li>Open <strong>Settings → Connectors</strong> from Claude’s customization menu.</li><li>Click the <strong>Add</strong> button and choose <strong>Add custom connector</strong> .</li><li>Fill in the details:<br> — Name:FacileThings<br> - Server URL:https://mcp.facilethings.com/mcp<br> - OAuth Client ID:Cc-IyQWv97tXc_Kn6TRvFPCRihEXHShzaEhgfI0ykLU</li><li>Click <strong>Add</strong>, then <strong>Connect</strong> to authorize access to your account. You’ll be taken to a consent web page where you’ll need to enter your FacileThings login credentials.</li></ol><p>Once connected, there’s no need to do anything special to “activate” it each time: just write naturally <em>“capture this…”</em>, <em>“what’s pending on project X?”</em>, <em>“help me review my waiting-for list.”</em></p><h3>How to connect FacileThings MCP to ChatGPT</h3><p>ChatGPT only allows adding custom MCP servers on certain plans. On the free plan, you’ll need to enable “developer mode” to do this:</p><ol><li>Open <strong>Settings → Plugins</strong>, from the menu under your name in the bottom left.</li><li>Turn on <strong>Developer mode</strong> (if needed).</li><li>Open <strong>Browse plugins</strong> and click the <strong>(+)</strong> button (if that button isn’t there, you’ll need to enable “developer mode” first).</li><li>Fill in the details:<br> — Name:FacileThings<br> - Connection:https://mcp.facilethings.com/mcp<br> - (Click &quot;Advanced OAuth settings&quot;)<br> - OAuth Client ID:L7xgxiTwTkHMO3Upnva2lygRjzqrQFDnyIspLO2xR3A<br> - (Check &quot;I understand and want to continue&quot;)</li><li>Click <strong>Create</strong>, then <strong>Connect</strong> to authorize access to your account. You’ll be taken to a consent web page where you’ll need to enter your FacileThings login credentials.</li></ol><h3>How to connect FacileThings MCP to Gemini CLI</h3><p>Gemini only allows you to connect MCP servers if you have a Business/Enterprise plan, and it has to be through the Gemini CLI tool:</p><p>Type /mcp auth facilethings in Gemini CLI. The data to establish the connection is:</p><ul><li>URL: <a href="https://mcp.facilethings.com/mcp">https://mcp.facilethings.com/mcp</a></li><li>OAuth Client ID: djZDQ4rfvH7GWPgmmkwGdVM1dCdihwqR3yrwZwjwVvE</li></ul><h3>How to connect FacileThings MCP to Hermes</h3><ol><li>Add to ~/.hermes/config.yaml an mcp_servers section. If it already exists, just add the facilethings section in it:</li></ol><pre>mcp_servers:<br>  facilethings:<br>    url: https://mcp.facilethings.com/mcp<br>    auth: oauth<br>    oauth:<br>      client_id: &quot;djZDQ4rfvH7GWPgmmkwGdVM1dCdihwqR3yrwZwjwVvE&quot;</pre><p>2. Connect to FacileThings through:</p><p>$ hermes mcp login facilethings</p><ul><li>Copy the URL and paste in the browser.</li><li>Enter your FacileThings credentials and authorize.</li><li>When your browser shows a connection error after authorizing, copy the full URL from the address bar and paste it at the prompt below.</li></ul><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/new-mcp-server"><em>https://facilethings.com</em></a><em> on August 4, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de15a1e4d5a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Do We Leave a Meeting with More Questions than Answers?]]></title>
            <link>https://facilethings.medium.com/why-do-we-leave-a-meeting-with-more-questions-than-answers-f639878c60e3?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f639878c60e3</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 17:35:51 GMT</pubDate>
            <atom:updated>2026-07-22T17:35:51.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*_I7cX1F1saUukvKu.png" /></figure><p>You leave the room or end the video call, and for a moment you feel like something has been resolved. There was a conversation, ideas were put on the table, and even a verbal agreement was reached. But twenty minutes later, as you’re already focused on another task, you still don’t feel entirely at ease: What exactly was decided? Who was responsible for what? And what did that comment about “we need to take our time” really mean?</p><p>Does this sound familiar? Meetings aren’t necessarily bad, but we often confuse two things that are similar but not the same: having discussed a problem and having solved it. And there’s a fairly specific explanation for that confusion; it has to do with how our minds work when switching from one activity to another.</p><h3>The meeting doesn’t end when it seems to end</h3><p>In 1982, researchers Doyle and Straus first described what organizational psychology would later call <strong>meeting recovery syndrome</strong>: the time we need to “cool down” and regain our focus after a meeting, especially if it was confusing or poorly managed. It’s not simply fatigue. It’s that the brain doesn’t “wrap up” the meeting when the meeting ends.</p><p>Joseph Allen, an organizational psychologist who has studied this phenomenon extensively, says that <strong>switching from one task to another requires active cognitive effort</strong>. You have to “detach” from the previous task before you can focus on the next one. Under normal circumstances, that transition can take ten or fifteen minutes. But when a meeting hasn’t left a clear sense of closure-when it’s unclear what was decided or what happens next-that disengagement process can take up to forty-five minutes. During that time, even if you’re physically engaged in something else, <a href="https://facilethings.com/blog/en/you-are-what-you-pay-attention-to">part of your attention</a> continues to process the previous meeting, trying to figure out a meaning it never quite had.</p><p>Steven Rogelberg, author of one of the most comprehensive studies on the science of meetings, points out that the problem is almost never the meeting itself. It’s meeting without it being clear, by the time it ends, what has actually changed outside that room. When a meeting ends without that clarity, it’s not just the time the meeting took that’s wasted. It also contaminates the time that follows.</p><h3>Where are the decisions and commitments?</h3><p>There’s a second, even more subtle problem that occurs even in meetings that do end with clear agreements. Someone says, “I’ll take care of that” or “I’ll send it to you this week,” everyone nods in agreement, and the conversation moves on. And that commitment, spoken aloud and seemingly accepted by everyone, fades away somewhere between the meeting room and the following Monday.</p><p>This problem has to do with <strong>prospective memory</strong>, a type of memory we use constantly and that often fails us. It’s not the memory that recalls what has already happened, but the one that has to remember to do something in the future. Early research in this field, such as that by Crovitz and Daniel in 1984 , estimates that at least half of everyday forgetfulness doesn’t come from general memory failures, but specifically from failures of this type: we knew we had to do something, but when the time came to do it, that “reminder to remember” simply didn’t kick in.</p><p>Researcher Key Dismukes, who has studied these failures in high-risk contexts such as aviation, describes a mechanism that explains very well what happens once the meeting is over . When we’re focused on the task at hand, we become vulnerable to what he calls <strong>cognitive tunneling</strong>. We become so immersed in what we’re doing right now that <strong>we lose sight of the commitments</strong> we made an hour, a day, or a week ago, even though at the time they seemed obvious and impossible to forget. The commitment doesn’t disappear because we don’t care; it disappears because it never had a place outside our heads where it could survive the shift in attention.</p><p>The busier we are and the more complex the meetings are (the more people participate in a meeting, the greater the number of topics discussed, the quicker we jump to the next task), the more likely this is to happen. It’s not a problem of a lack of commitment or a poor memory. It’s a predictable characteristic of how human attention works under stress.</p><h3>The problem isn’t the meeting</h3><p>A meeting can be well-prepared, well-run, and full of good intentions, and yet still fall short in the most important way, because what really matters doesn’t happen during the meeting, but afterward. It happens the moment each person returns to their seat, and that verbal agreement has to survive the transition into the rest of their week.</p><p>This suggests that the question we usually ask ourselves, <em>how can we make meetings more efficient?</em>, may not be the most useful one. A more interesting question would be: What happens to the decisions made in the meeting as soon as the meeting ends? Is there a reliable place where they are documented, or do they depend entirely on each person remembering them on their own?</p><p>No meeting, no matter how well conducted, solves anything if the outcome doesn’t go beyond the minds of those sitting at the table.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/why-do-we-leave-a-meeting-with-more-questions-than-answers"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f639878c60e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Do You Feel Anxious at Work Even When You Don’t Really Have Much to Do?]]></title>
            <link>https://facilethings.medium.com/why-do-you-feel-anxious-at-work-even-when-you-dont-really-have-much-to-do-2d766e221b21?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d766e221b21</guid>
            <category><![CDATA[stress]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[anxiety]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 08 Jul 2026 18:11:20 GMT</pubDate>
            <atom:updated>2026-07-08T18:11:20.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*EI_BpaAaAzesY1W7.png" /></figure><p>There’s a form of <strong>work-related anxiety</strong> that’s particularly unsettling because it doesn’t quite fit our understanding of <a href="https://facilethings.com/blog/en/stress">stress</a>. I’m not referring to the typical anxiety of an overwhelmed professional-someone with many ongoing projects, some of which are in crisis mode, and an inbox that just keeps growing.</p><p>Sometimes anxiety creeps in when, in theory, you have the situation under control, when there’s no active crisis and your workload is reasonable. Even so, something inside you remains on high alert, and your mind seems unable to fully relax. On Sunday afternoon, before the week begins, that shadow appears. You walk out of a meeting that went perfectly well, but you feel a vague unease that you can’t quite put your finger on.</p><p>If this sounds familiar, you’ve probably come to the conclusion that you’re the problem. That you’re too anxious, that you worry too much, and that you should learn to unwind. It’s an understandable reaction, but research points to something much more specific and, above all, much less personal.</p><h3>The brain doesn’t distinguish between a tiger and an unanswered email</h3><p>To understand why we feel anxiety without a proportionate, objective reason, it’s helpful to briefly review how <strong>the brain’s alarm system</strong> works . The amygdala, a subcortical region that has been evolving for millions of years, plays a central role in detecting threats and triggering the stress response before the rest of the brain has had time to analyze the situation. It’s an early-warning system designed for speed, not accuracy.</p><p>The problem is that the amygdala doesn’t properly assess the nature of the threat: it responds with the same urgency to a real physical danger as it does to uncertainty about whether a project is going well or if a message has been left unanswered. When the amygdala detects something ambiguous or unresolved, it activates the hypothalamic-pituitary-adrenal axis, triggering the release of cortisol and adrenaline, the same mechanisms that once helped us escape from a predator. Except that now there is no predator to run away from, and cortisol builds up with nowhere to go.</p><p>Studies have also shown that elevated cortisol, in addition to preparing the body for a threat, increases the sensitivity of the amygdala itself and skews perception toward the negative, causing ambiguous situations to be interpreted as more threatening than they actually are. In other words, stress creates a greater predisposition to stress. It’s not weakness or hypersensitivity, it’s your nervous system doing exactly what it was designed to do.</p><h3>Ambiguity as a source of chronic stress</h3><p>Modern <a href="https://facilethings.com/gtd-dictionary/en/knowledge-work">knowledge work</a> has a characteristic that is rarely analyzed honestly: it’s structurally full of ambiguity. Not clear threats, but constant vagueness.</p><p>In the 1960s, psychologist Robert Kahn and his colleagues published one of the seminal studies on <strong>organizational stress</strong> , identifying two main sources of workplace stress that remain as relevant today as they were then. The first is <strong>role conflict</strong>: when a single employee faces incompatible demands from different people or parts of the organization. The second, and more subtle, is role ambiguity: a <strong>lack of clarity</strong> regarding exactly what one’s responsibilities are, how one is expected to act, or the criteria by which one’s work is evaluated. Kahn documented that this <strong>ambiguity is consistently associated with stress, anxiety, and reduced performance</strong>, regardless of the objective workload.</p><p>What is significant about this finding, confirmed by numerous subsequent studies, is that <strong>stress doesn’t require an excessive workload to arise. It only requires uncertainty</strong>. And in contemporary knowledge work, uncertainty is the default state: projects with vague success criteria, priorities that shift without anyone explicitly communicating them, commitments made in informal conversations that no one wrote down anywhere, expectations that are taken for granted without ever having been articulated. It’s not that the workload is excessive; it’s that it isn’t defined clearly enough for the brain to relax.</p><h3>The cost of what remains unresolved</h3><p>Added to this is a mechanism I already mentioned in <a href="https://facilethings.com/blog/en/decision-fatigue">the article on decision fatigue</a>: <strong>the Zeigarnik effect and its impact on cognitive load</strong>. Unfinished tasks, unresolved commitments, conversations left hanging, issues on which no decision has yet been made-all of these remain active in the mind even when we aren’t consciously thinking about them. Not as a passive memory, but as a monitoring process that consumes mental resources in the background and keeps the alert system slightly activated.</p><p>Dugas and Freeston’s research on <strong>uncertainty intolerance</strong> adds another layer to this picture. These researchers found that one of the most predictive variables of chronic worry isn’t the number of actual problems a person faces, but rather their ability to tolerate the fact that some things remain unresolved. For those with low tolerance for uncertainty, any ambiguous situation triggers rumination and worry as a coping strategy: if I think about this long enough, perhaps I can anticipate all possible scenarios and be prepared. It’s an illusion of control that comes at a very real cognitive and emotional cost.</p><h3>Where does this anxiety come from, with no apparent cause?</h3><p>Returning to the scene at the beginning: the vague tension of a Sunday afternoon, the unease that lingers after a meeting that apparently went well, the feeling that something is unresolved even though you can’t pinpoint what it is. These experiences don’t usually mean that you’re overly anxious or that you have a clinical problem. They usually indicate that your nervous system is responding rationally to a significant amount of ambiguity and unresolved issues that haven’t been processed, decided, or brought to a close.</p><p>To put it another way: the problem is rarely the amount of work. <strong>It’s the lack of clarity about that work</strong>. A professional with a heavy workload but complete clarity about what needs to be done, in what order, and what constitutes success experiences far less chronic stress than someone with a lighter workload but a list of vague commitments, blurred priorities, and pending decisions that never seem to get resolved.</p><h3>Three principles suggested by current research</h3><p>None of the findings above point to a magic solution, but they do converge on some fairly consistent ideas.</p><p>The first one is that <strong>reducing active ambiguity has a more direct impact on stress than reducing the workload</strong>. Even if the amount of work doesn’t change, there are many things that can help reduce the burden that your brain’s alert system keeps active in the background, such as clarifying what “done” means in a project, agreeing precisely on who is responsible for what, turning verbal commitments into something written and reviewable, and so on.</p><p>The second point, derived directly from the research by Masicampo and Baumeister that we mentioned in the previous article , is that <strong>it isn’t necessary to resolve an issue or complete it in order to close it out</strong>. It’s only necessary to have a reliable place where that issue is recorded, along with a decision about when or how it will be addressed. The mind stops monitoring what it perceives that it has been handled, even if it isn’t finished yet.</p><p>The third, perhaps the least intuitive, is <strong>realizing the difference between being busy and having clarity</strong>. Constant busyness can itself be a source of ambiguity: if you’re always reacting, there’s never any room to decide what deserves real attention and what doesn’t. The anxiety this creates doesn’t go away by working faster. It goes away, to a large extent, when the system surrounding your work (the decisions, commitments, and priorities) is structured enough so that your brain can finally let its guard down.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/anxiety-at-work"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d766e221b21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decision Fatigue: Why You Feel Exhausted Without Having “Done” Anything Physically]]></title>
            <link>https://facilethings.medium.com/decision-fatigue-why-you-feel-exhausted-without-having-done-anything-physically-e570f369c62b?source=rss-4c17513083b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e570f369c62b</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[brain]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[FacileThings]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 17:35:08 GMT</pubDate>
            <atom:updated>2026-07-01T17:35:08.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HT3TsXeQ5YZptGJX.png" /></figure><p>It’s seven o’clock in the evening. You haven’t moved a single box, you haven’t run, and you haven’t carried anything heavier than a cell phone. And yet, you feel that heavy, almost physical exhaustion that you normally associate with a day of house moving or a long workout. You sit down on the couch and don’t even have the energy to decide what to have for dinner. Why are you so tired?</p><p>The answer has to do with <strong>how many times you’ve had to make a decision throughout the day</strong>.</p><h3>The brain is just like any other muscle. It gets tired</h3><p>In the late 1990s, social psychologist Roy Baumeister proposed an idea that changed much of the subsequent research on self-control: that <a href="https://facilethings.com/blog/en/self-discipline">willpower works like a muscle</a> . It can be trained, but it also becomes fatigued with use. In one of his most frequently cited experiments, he asked a group of hungry participants to resist the temptation to eat freshly baked chocolate chip cookies, while another group was allowed to eat them. Afterward, everyone was given an impossible puzzle to solve. Those who had had to resist the cookies gave up much sooner than those who hadn’t had to exercise any self-control beforehand. He dubbed the phenomenon <strong>ego depletion</strong>: the idea that resisting an impulse, making a difficult decision, or maintaining concentration all draw on the same limited mental resource, and that once that resource is depleted, less of it is available for the next task.</p><p>It’s important to note that this theory, despite its enormous influence, isn’t a settled matter. A large-scale replication study published in 2016, involving more than two thousand participants across various laboratories, failed to reproduce Baumeister’s original results, and since then, the academic debate over whether <em>ego depletion</em> exists as initially described has remained open . What does seem to hold true, even among the harshest critics of the original model, is the phenomenon itself: that <strong>the quality of our decisions deteriorates as we accumulate previous decisions</strong>, regardless of the exact mechanism that explains it.</p><h3>Judges who made decisions based on the time of day</h3><p>One of the most frequently cited examples of this decline comes from a study published in 2011 in the journal <em>PNAS</em> , which analyzed more than 1,000 parole decisions made by Israeli judges over the course of several months. The researchers found a striking pattern: the probability that a judge would grant parole dropped progressively throughout each work session, falling from about 65% at the start to nearly 0% at the end, only to rise sharply back to 65% immediately after each lunch break. It wasn’t the case, the prisoner’s record, or any legal factor that best predicted the decision: it was, quite simply, how many decisions the judge had made since their last break.</p><p>The study wasn’t free from criticism. Other researchers pointed out that part of the effect could be explained by a statistical bias related to the order in which the cases were presented, rather than by actual mental fatigue. But regardless of the exact explanation, the general pattern-that the quality of our decisions deteriorates the more we make-has been observed in very different contexts, from medical committees to shopping environments. And it ties in with something that anyone who spends their days making decisions recognizes immediately: <strong>deciding something at 9 a.m. is not the same as deciding it at 6 p.m.</strong></p><h3>Every decision counts, not just the important ones</h3><p><strong>The brain doesn’t seem to distinguish very well between the magnitude of a decision</strong>: deciding whether a task is a priority, whether to reply to that email now or leave it for later, in what order to do the three things you have pending, or whether that meeting could have been handled with a message. None of these decisions is dramatic on its own. But they pile up, one after another, for hours, and each one consumes a small portion of the same limited resource.</p><p>There’s a common belief that we make about 35,000 decisions a day. It’s a statistic that sounds compelling, but when you trace its origin, it falls apart amid loose estimates, misattributed quotes, and, in some cases, research that was later retracted. But we don’t need an exact (and likely made-up) figure to support the central idea: in a modern <a href="https://facilethings.com/gtd-dictionary/en/knowledge-work">knowledge work</a>, the number of microdecisions we make every day is high, constant, and almost always invisible to us.</p><h3>The Real Cost: Cognitive Load</h3><p>This brings us back to the original question. If no one would say that deciding what to write in an email is exhausting, why is the accumulation of hundreds of microdecisions so exhausting?</p><p>The answer lies in how working memory functions-that mental space where we keep information active while we process it. Psychologist John Sweller, who developed what is now known as <strong>cognitive load theory</strong> in the 1980s, demonstrated that working memory has a very limited capacity: it can hold only a few items at a time before becoming overloaded . Every pending decision, every unresolved task, every “I’ll decide this later” occupies a small portion of that limited space, even when we aren’t actively thinking about it. The system doesn’t completely let go: it continues to process in the background, keeping that information “open” in case it’s needed.</p><p>That “background processing” has a name and nearly a century of research behind it. In 1927, <a href="https://facilethings.com/blog/en/zeigarnik-effect-gtd">psychologist Bluma Zeigarnik</a> observed that waiters accurately remembered the orders for tables that had not yet been paid for, but forgot those same details as soon as the bill was settled. In the lab, she confirmed that interrupted tasks are remembered better than completed ones: something in the mind keeps the unfinished “open” . Decades later, psychologists E. J. Masicampo and Roy Baumeister took this idea to a more practical level . In a series of experiments published in 2011, they found that having an uncompleted goal generated intrusive thoughts during completely different tasks and impaired performance on problem-solving exercises. <strong>The simple fact of having something pending (unresolved, undecided, or not written down anywhere reliable) consumed mental resources that should have been available for something else</strong>.</p><p>Here is, perhaps, the most useful finding in this entire area of research: in those same experiments, all the participants had to do was formulate a concrete, specific plan for tackling the pending task (not to complete it, but simply to decide when and how they would do it) for the intrusive thoughts to disappear and their performance to return to normal. <strong>The mind did not need the task to be completed. It needed it to be decided</strong>.</p><h3>Recognize the signs</h3><p><strong>Decision fatigue</strong> rarely presents itself as such. It manifests as the feeling of being unable to choose what to eat after a day’s work, even though you’re hungry. Like the irritability that appears out of nowhere at six in the evening for no clear reason. Like systematically choosing the easiest option, or the one you’re already familiar with, over the one that would probably be better, simply because evaluating alternatives requires an effort you no longer have. Like that small, almost trivial task you’ve been putting off all day, not because it’s difficult but because deciding how to tackle it is, in itself, yet another decision your brain would rather postpone.</p><p>Recognizing these signs is a valuable exercise in self-awareness. It’s the first step toward understanding that the exhaustion you feel at the end of the day, that “I can’t take it anymore” feeling with no obvious physical cause, has a fairly specific explanation and, above all, is quite manageable.</p><h3>What the research suggests</h3><p>None of these studies points to a magic solution, but they do, quite consistently, point in the same direction.</p><ul><li>The first is to <strong>reduce the number of trivial decisions</strong> we make without realizing it: the more routines and default settings we have for repetitive tasks, the fewer resources we spend on decisions that add no value simply because they are deliberate.</li><li>The second is to <strong>get pending decisions out of our heads and put them somewhere external and reliable</strong>: not because writing something down solves the problem, but because, as Masicampo and Baumeister demonstrated, the mind stops actively monitoring what has been captured and decided elsewhere.</li><li>And the third, perhaps the easiest to overlook, is to <strong>avoid making the same decision over and over again</strong>: every time we revisit a decision we’ve already made, we pay the full cognitive cost all over again, as if we’d never resolved it in the first place.</li></ul><p>None of these three principles requires a complex methodology or a specific tool. It simply requires understanding that the mind is not designed to juggle hundreds of open decisions at once, and that much of the exhaustion we feel at the end of the day doesn’t come from what we did, but from everything we had to decide at some point.</p><p><em>Originally published at </em><a href="https://facilethings.com/blog/en/decision-fatigue"><em>https://facilethings.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e570f369c62b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>