Most wasted time at work is not idle time at all; it is re-decision time, and it looks exactly like work while you are doing it. Opening the same email for the fourth time. Reopening a document to remember where you left off. Asking a colleague something you already asked last Tuesday. This piece names seven places that cost sits in a normal week and gives the GTD mechanics that remove each one, with the list design and perspective rules spelled out rather than hand-waved. The honest conclusion, up front: willpower does not fix this, and neither does a time-tracking app. A system you trust does, and it takes about four weeks to bed in.

Where the hours actually go (it is not just your phone)

Three different things get lumped together as lost time, and they need different treatment.

Idle time is the obvious one: scrolling, waiting for a file to open, the ten minutes before a meeting that are too short to start anything. Interruption time is the colleague at your desk, the chat ping, the call. Both are real. Both are what every “top time wasters”list describes, because both are visible from the outside.

Re-decision time is the expensive one, and nobody counts it. Every time you look at an input and have to work out again what it means, what the outcome is and what you would physically do next, you pay the same thinking cost you already paid. An email you have read three times has not been processed three times. It has been deferred three times, with a full re-read each round.

Try a two-day audit before you change anything. Keep a tally, paper is fine, and mark a stroke every time you re-open an email you had already read, reopen a file to work out the next step, or re-ask someone something you have asked before. Most people are startled by the ratio of repeats to new work. That tally is your real target.

Discipline cannot touch this, because the problem is not that you are weak at 3pm. The problem is that the decision was never written down in a form your 3pm self can act on. A trusted system stores the decision, not the item. That is the whole trick, and the seven fixes below are just places to apply it.

Fix 1: One inbox instead of six places to check

Count your real capture points honestly. Email, work chat, a paper notebook, the notes app on your phone, sticky notes on the monitor, voicemail, a whiteboard, and the back of your mind. Six to nine is typical. Every one of them is a place you have to scan, and scanning is re-reading, and re-reading is re-deciding.

Job one: time to captured. From the moment a thought arrives to the moment it is safely in a place you will actually empty, how many seconds? If that is over about five seconds with your phone locked and your hands full, you will skip it under pressure, and the ideas you skip are the good ones you had walking out of a meeting. Five seconds is a practical working benchmark rather than an official rule, but it holds up.

Voice capture is usually the fastest route on a phone; paper is the fastest at a desk with a laptop lid down. Both are fine, provided they land in one inbox you empty rather than six you glance at. If you want the mechanics of getting voice, paper and app capture into a single funnel, the detail is in this guide to capturing anything in under five seconds with an AI assistant.

The mistake almost everyone makes: treating the email inbox as the master list. Email is a capture point, not an action list. A 40-message inbox used as a to-do list costs you a full re-read every time you open it, and you open it a lot.

Fix 2: Clarify once, so you never re-decide

David Allen’s clarify questions are the cheapest productivity upgrade available. Is it actionable? If yes, what is the outcome that means it is done? What is the very next physical, visible action?

Physical and visible is the part people skip. “Dave quote”is a reminder to think. “Ring Dave on 0161 496 0000 about the kitchen quote”is a reminder to act, and it costs zero thinking time at the point of use. You pay the clarification once instead of every time your eye crosses the line. Entries like “Mum”, “website”and “budget”are the main reason weekly reviews drag; each one restarts a conversation you already had with yourself.

The two-minute rule belongs here too, and it is more mercenary than people realise. A 90-second reply costs more to capture, tag, file, re-read and schedule than it does to send. So send it. Anything longer becomes a next action with a named outcome, written properly, and leaves the inbox.

On AI: it is genuinely useful for turning a woolly open loop into candidate next actions. Paste in “sort out the autumn mailer”and you will get a handful of plausible steps, some of which are usable. Do not let it decide what matters or maintain your lists. The jobs it does well and the ones it quietly ruins are set out in more detail in this breakdown of making ChatGPT work with GTD.

Fix 3: Context lists that match the tools and energy you actually have

A single flat list of 140 actions forces you to read 134 things you cannot do right now in order to find the six you can. That scan happens every time you look. It is the purest form of re-decision cost there is.

Contexts are not folders. The point is that the list in front of you contains only what you can genuinely do with the tools, people and energy available at that moment. The ones that still earn their place in 2026: Calls, Errands, Agendas (one per person), Low Energy, Offline, and anything tied to a physical location you visit rarely.

In OmniFocus, build it in the rule builder: tag is Errands, availability set to Available, grouped by project, sorted by due date. Your 140-item list becomes a six-item list you can work from the car park. Half a dozen views like that, properly set up, remove most daily scanning; there is a fuller walkthrough in this guide to custom OmniFocus perspectives.

Not on a Mac? Things reaches the same place with tags plus a saved filter inside Anytime, and Todoist does it with a saved filter such as @errands &!no date &!subtask style queries, adjusted to your tags. The app matters far less than the rule. One screen, only available actions, short enough to read in a breath.

Fix 4: A Waiting For list so chasing stops eating your week

Delegation without a Waiting For entry is the most expensive habit in office work. You pay once to delegate, again to remember you delegated, and a third time to reconstruct what you asked for, when, and of whom. That third payment usually happens in front of someone, which adds embarrassment to the bill.

Log it at the moment you send, with the date and the name baked into the text: “WF: Priya, signed-off copy for the autumn mailer, sent 15 September 2026”. No archaeology later. A Monday pass over that list surfaces the chase before it becomes a problem, rather than the chase occurring to you halfway through an unrelated meeting.

Pair it with an Agenda list per person. Five small questions saved for one conversation beat five interruptions, for both of you. Review Waiting For at the start of the week, not after something has already slipped.

Fixes 5, 6 and 7: support material, meeting prep and the weekly review

Fix 5: Keep project support material out of your action lists

Reference material judged on how pretty it looks is a beautiful shelf of software you never open. Judge it on retrieval speed instead: can you get to the brief, the contract and the last three emails in under ten seconds, from your phone, without remembering a folder path? If not, the structure is wrong, however tidy it looks.

Keep support material separate from the action list and linked to it. Mixing them means every scan of your actions drags you into reading notes, which is re-decision dressed up as preparation.

Fix 6: Apply the natural planning model before the invite goes out

Most recurring meetings exist because nobody ever wrote down their purpose. Run Allen’s natural planning model over one of yours: purpose, successful outcome, brainstorm, organise, next actions. Two things usually happen. The invite list gets shorter and the meeting gets shorter. A meeting with no defined outcome generates re-decision for every person in the room, multiplied by the room.

Fix 7: The weekly review is the maintenance slot, not a nice-to-have

Everything above decays without it. A repeatable checklist works: empty every inbox to zero, review the calendar two weeks back and four weeks forward, read the projects list, read Waiting For, read Someday/Maybe, and check for stalled projects.

That last one matters more than it sounds. A project with no next action is not a stalled project, it is a recurring interruption, because your mind will raise it again and again until something concrete is written down. OmniFocus has a Stalled Projects view built in; in Todoist or Things you can approximate it with a filter for projects with no available tasks. Catch them on a Friday review and they stop becoming Friday-afternoon emergencies three weeks later.

What to measure, and the traps to avoid

Measure completed next actions and finished outcomes, not hours logged. Productivity in the national statistics sense is output per hour worked, which is how the ONS measures labour productivity, and the same logic applies at a desk: more hours on the clock is not the number you want to move. If you are curious how the national picture frames individual work, we have looked at what the UK productivity figures mean for your own working week.

Surveillance-style monitoring tends to produce busier-looking work rather than better work. Keystroke counts and activity scores reward visible motion, and re-decision is extremely visible motion. Skip it.

AI assistants shift where the waste sits rather than removing it. Good at: breaking a vague open loop into candidate actions, drafting a short reply you then edit, summarising a long thread so you can clarify it once. Poor at: deciding what matters this week, and maintaining your lists, where it produces tidy-looking output that you then have to check line by line. Checking generated lists is a new daily admin tax. Watch for it.

Roll the fixes in one at a time, roughly a week each: week one, single inbox and capture speed; week two, clarify properly and apply the two-minute rule at triage; week three, build your contexts and one or two perspectives; week four, Waiting For plus the first real weekly review. Rebuild everything at once and you will abandon it by the second month. That pattern is the common thread in every productivity system that actually lasts.

Frequently Asked Questions

How much time is actually wasted at work each day?

Published figures vary wildly depending on who funded the survey and how they defined waste, so treat any single number with suspicion. The more useful measurement is your own two-day tally of re-opened emails, re-opened files and re-asked questions. Most people find repeats make up a surprising share of their switches, which is a figure you can actually act on.

What causes the most wasted time at work for office-based staff?

Unclear next steps, not distraction. When an item on a list says “budget”rather than “draft Q1 figures tab and send to Sam”, you re-make the same decision every time you see it. Multiple capture points make it worse, because each one gets scanned rather than emptied.

How do I stop wasting time on email without ignoring it?

Treat the inbox as a capture point and empty it on a schedule, two or three passes a day. Anything under two minutes gets answered on the spot; anything longer becomes a properly worded next action with the email filed or linked. The aim is an inbox you process, not a list you re-read.

Can time-tracking apps fix wasted time at work?

They diagnose, they do not cure. A tracker will show you that you spent 90 minutes in email and nothing about how many of those minutes were spent re-reading the same five messages. Use one for a fortnight to find the pattern, then change the system rather than the stopwatch.

How long does it take before a GTD system reduces wasted time?

Capture speed pays back in days. Context lists and Waiting For usually feel worth it within two to three weeks. The weekly review takes longer to stick, often a month or two, because it only proves its value once it catches something expensive before it goes wrong.

The post Wasted Time at Work: 7 GTD Fixes That Stick appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The best AI assistant GTD workflow is the one where the assistant never holds a single task. That is the honest conclusion, up front, and the rest of this piece is just the build: five stages, one handoff each, a prompt pattern where it helps, the failure mode that breaks it, and the one stage where the right move is to shut the window.

If you already run OmniFocus with custom perspectives, or Things, or Todoist, nothing here asks you to move. The assistant drafts and questions. Your task manager decides and holds. Get that boundary wrong and the system stops being trustworthy inside a fortnight.

Why most AI productivity advice breaks a GTD system

The common failure is quiet and quick. You start asking ChatGPT or Claude to “help me plan the week”, it produces a tidy list, you leave that list in the thread, and now you have two inboxes. One gets reviewed. The other sits in a conversation history nobody opens again.

GTD runs on completeness. The five stages David Allen sets out, capture, clarify, organise, reflect and engage, only work because every open loop lands somewhere you trust and every commitment appears on one set of lists. An assistant that keeps three of your commitments in a chat transcript has made your list incomplete. An incomplete list is one your brain stops believing, and once that happens you are back to holding things in your head while paying a subscription for the privilege.

So the working rule for this whole article: AI drafts and questions, your task manager decides and holds. Everything below is an application of that single line.

What has changed recently is worth naming, because it is what makes any of this viable. Persistent memory means the assistant can carry project background between sessions. Voice modes mean capture no longer requires typing. Shared, editable document surfaces such as ChatGPT Pages mean generated material can live somewhere with a URL instead of scrolling away up a thread. All three improvements help with reference material. None of them makes a chat window a list manager.

Stage 1: capture, where an AI assistant earns its place fastest

Job one: time to captured. Not how clever the tool is, not how good the transcription sounds in a demo video, just how many seconds pass between the thought arriving and the item sitting in the one inbox you actually process.

Under about five seconds, you will keep doing it under pressure. Over that, you will skip it while walking between meetings, which is precisely when the useful ideas turn up. Treat five seconds as a practical working benchmark rather than an official rule, but test yourself against it honestly. Phone locked, screen off, hands busy. That is the real test condition, not a calm desk.

Voice capture into an assistant works genuinely well, on one condition: the route ends somewhere else. A spoken note that triggers an email to your task manager’s inbox address, or fires a Shortcut on iOS, or drops through a share sheet into Things, has captured something. A spoken note that lives in the transcript has not. It has made a recording of an idea and then buried it.

Run the ten-item test. Over one working day, capture ten things by whatever mix of voice, phone and paper you normally use. At your next weekly review, count how many arrived in the single inbox. Fewer than ten and you have a broken route, not a discipline problem, and fixing the route takes twenty minutes once. The longer version of that build is in the piece on capturing with an AI assistant in under five seconds.

Stage 2: clarify vague open loops with the right prompt pattern

Clarify is where most inboxes rot. You have an item that says “website”. Six days later it still says “website”, because deciding what it means costs more thought than the two seconds it took to write.

This is the stage where an assistant does real work, provided you make it ask GTD’s questions rather than its own. The question set is fixed: is this actionable? If not, is it rubbish, reference, or someday/maybe? If it is, what is the successful outcome, and what is the very next physical, visible action?

A prompt pattern that holds up:

• “Here is a raw inbox item: [item]. Ask me whether it is actionable. If it is, ask me what done looks like in one sentence, then propose three possible next actions, each starting with a physical verb. Do not restate the item as the action. Flag anything you have assumed.”

That last clause matters more than the rest. Without it, the assistant will cheerfully invent plausible-sounding commitments you never agreed to, and they look exactly like the ones you did.

Worked through, “website”came out as “Draft the three questions for the designer about the pricing page”, under the project “New pricing page live”, tagged @Mac once it reached the task manager. Verb first, visible, doable in one sitting. The assistant proposed it. You approved it, line by line, and typed the context yourself.

For messier projects, the natural planning model makes a far better prompt skeleton than any “be my productivity coach”instruction: purpose, principles, outcome, brainstorm, organise, next action, in that order. Ask for the stages explicitly and the output stops being a generic project plan and starts being yours. Budget a few minutes per tangled project. Clarifying ten simple inbox items this way is slower than clarifying them yourself, so do not bother; save it for the three that have been staring at you for a fortnight.

Stage 3: organise without letting the assistant own your lists

Contexts, energy levels, waiting-for status, due dates: all of that stays in the task manager. AI output gets pasted in. It never syncs from.

Make the paste painless by asking for a paste-ready format. One action per line, verb first, project name in brackets, context tag at the end. Something like:

• Draft three questions for the designer about pricing [New pricing page live] @Mac
• Ring the accountant about the quarterly filing deadline [Q4 accounts filed] @Calls

A block in that shape drops into OmniFocus, Things or Todoist without re-typing, and more importantly it forces you to read each line as a commitment before it lands. Re-typing is not the enemy. Unexamined additions are.

The honest home for most AI output is project support material: briefs, research notes, meeting agendas, comparison tables, first-draft checklists. Reference you consult while working the project, stored next to the project, not scattered through the action list. Treat every generated bullet as a task and your lists inflate with work you never committed to, which is the fastest route to a list you avoid opening.

One rule on storage, and it matters more with AI than with ordinary notes, because generated reference piles up fast. If you cannot get it out as plain text or Markdown, it is not storage, it is rented memory. Evernote’s change of ownership and its tightened free tier were a reminder of how quickly a storage decision can be taken out of your hands, which is why the migration costs of the main alternatives are worth knowing before you accumulate three hundred generated documents, not after.

Stage 4: use AI to sharpen the weekly review, not to replace it

Reflect is where an assistant helps most and can quietly do the most damage.

What it can honestly do: read a week’s captured notes and meeting scribbles and pull out candidate open loops you wrote down but never turned into projects; scan a project list and flag the ones with no available next action; suggest the awkward question to ask about an item that has not moved in a month. All three are summarisation and pattern-spotting, which is what the technology is actually good at.

What it cannot do is feel the small flinch you get when you scroll past the project you have been avoiding. It will produce a neat, well-formatted summary and leave you feeling reviewed, which is worse than not reviewing at all, because you now have false confidence.

A pairing that works: open a custom perspective filtered to projects with no available next action, and run an AI pass over the week’s captured notes at the same time. The perspective catches structural stalls. The AI pass catches outcomes you mentioned in a note and never promoted to a project. Then you do the part neither of them can: decide what leaves the system. Dropping a commitment is a judgement call about what you are willing to disappoint people over. Keep it human, keep it in your own head, and do not outsource it to something optimising for a tidy answer.

Stage 5: engage, and the four moments to close the chat window

Doing the work is where AI costs you most. Every query is a context switch out of the action you chose, and the switch is cheap individually and expensive in aggregate.

Four jobs to keep off the assistant while you are engaged:

1. Choosing what to do next. Asking an assistant how to prioritise tasks produces a confident ordering based on none of the information that matters: your energy, the time you actually have, the person waiting on you, what you can live with not doing. Context, time, energy, priority. That is your call, made against your own lists.
2. Writing in your own voice to people who know you. They can tell. The relationship cost outweighs the eight minutes saved.
3. Anything with confidential or client data. Check your organisation’s policy and the tool’s data handling before pasting; the ICO’s guidance on AI and data protection is the sensible starting point for UK readers, and most enterprise agreements have their own line on this.
4. Anything whose accuracy you cannot check yourself. If you could not spot a wrong figure or an invented citation, you are not verifying, you are hoping.

The exception is low-energy list work. Twenty minutes left, nothing in the tank, a dull first draft due: that is the moment a generated starting point beats a blank page, because editing something mediocre takes less willpower than creating something from nothing. The longer breakdown of which jobs survive this test is in the piece on the six jobs ChatGPT does well in GTD and the four it ruins.

Then set a rule, the same way you set a context. The assistant is open during clarify, organise and review blocks. It is shut during execution blocks. Write it on the wall if you need to.

Putting the AI assistant GTD workflow together: a one-week setup plan

Build it in order, one piece a day. Skipping to the clever prompts before the capture route works is the standard mistake.

• Days 1 and 2: capture route only. Voice to assistant to email or Shortcut to your one inbox. Run the ten-item test on day two.
• Day 3: save your clarify prompt somewhere you can reach in two taps. Run it on the five oldest items in the inbox.
• Day 4: set the paste-ready output format and paste one block into your task manager. Check nothing arrived that you did not agree to.
• Day 5: move one project’s generated material into project support, wherever that lives for you, and confirm you can export it as plain text.
• Days 6 and 7: one weekly review with the stalled-projects perspective and an AI pass over the week’s notes. Do the clean-out yourself.

What good looks like at the end of the week: one inbox, one trusted list, and every piece of AI output sitting in reference rather than on an action list. If a generated bullet is on your next actions list and you cannot remember agreeing to it, the boundary has slipped.

Give it a fortnight. If a stage is not better than it was before, remove AI from that stage and keep the rest. That is a valid outcome, not a failure, and for a lot of people the honest result is that capture and clarify improve, organise stays manual and engage gets quieter. Fewer moving parts, wired together properly, beat a clever setup you stop maintaining by the second month.

If you want the next piece of the picture, read up on building a personal productivity system that lasts, because the boundary described here only holds inside a system you already trust.

Frequently Asked Questions

Can an AI assistant replace my task manager in a GTD workflow?

No. A chat history is not a complete, reviewable list, and GTD only works when every commitment lives in one place you check. The moment half your actions sit in a thread and half in an app, your brain stops trusting either. Keep the assistant as a drafting and questioning tool, and let OmniFocus, Things or Todoist hold the commitments.

Which GTD stages does an AI assistant actually help with?

Capture, clarify and reflect, with reflect the stage where it helps most, provided the decisions about what to drop stay yours. Capture gains from fast voice entry, as long as the route ends in your real inbox. Clarify gains because the assistant will patiently ask the outcome and next action questions on items you have been avoiding. Reflect gains from summarising a week of notes into candidate open loops, though the decisions about what to drop stay yours.

What prompt turns a vague open loop into a proper next action?

Give it the raw item and require three things: a yes or no on whether it is actionable, one sentence describing what done looks like, and three candidate next actions that each begin with a physical verb. Add “do not restate the item as the action”and “flag anything you have assumed”. That is how “website”becomes “Draft the three questions for the designer about the pricing page”.

Is it safe to put work projects into an AI assistant?

It depends entirely on the data and your organisation’s policy, so check both before pasting. Client information, personal data and anything under an NDA need a tool and a contract that permit it; the ICO publishes guidance on AI and data protection for UK organisations. For general planning and non-sensitive drafting, the risk is usually low, but verify rather than assume.

How do I stop the chat window becoming a second inbox?

Give every useful output a destination before you generate it. Actions get pasted into the task manager; reference gets saved into project support material; everything else gets closed. A short end-of-session habit works well: before you shut the window, ask yourself what in here is a commitment, move it, and then let the thread go.

The post AI Assistant GTD Workflow: A 5-Stage Build appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

If you want to know how to stop procrastinating, start here: procrastination, in most cases, is a wording problem wearing a psychological costume. The same item sits on your list for six weeks, you feel guilty every time you read it, and you conclude you are lazy. You are not. You are re-planning the same undecided commitment every time your eyes pass over it, and your brain quite sensibly refuses to do that work again.

So this piece does not cover rewards, shame-busting or timers. It gives you six diagnostic checks and six concrete edits, taken from working through David Allen’s Getting Things Done chapter by chapter, each one a change to the actual words on your list or the shape of your workflow. Pick the item you have been avoiding longest and repair it as you read.

Why You Procrastinate: Diagnose the Item Before You Fight Yourself

An item that survives six weekly glances is evidence. Not about your character, about the item. Something in it is undefined, misplaced or no longer true, and the cheapest fix is almost always an edit rather than a motivational intervention.

Run these six questions over the thing you are dodging:

1. Has anyone, including you, agreed what finished looks like?
2. Is the next physical, visible move written down, or just implied?
3. Is the item sitting where you will actually see it at the right moment?
4. Can it be done where you are, with the tools and people you have?
5. Have you reviewed it since the circumstances changed?
6. Is it honestly a commitment at all, or a wish you have never demoted?

Six questions, six fixes. Each section below handles one.

Resistance is a real feeling and a bad excuse

Steven Pressfield’s The War of Art (2002) gives the sensation its best name: Resistance, the force that gets stronger the more a piece of work matters to you. That is a useful vocabulary for what you feel at 9:04am when the important thing is open in front of you and the kettle suddenly needs attention. It is also why his book turns up in our round-up of the best motivational books that change what you do rather than just what you think.

But naming the feeling does not define the task. Resistance explains why you flinch at a properly worded next action. It does not explain why you have flinched at the word “insurance”for two months, because nobody can do “insurance”. The list edit does the work; Pressfield gives you the language for the ten minutes after the edit.

Why “just break it down”fails

Standard advice says break the task into smaller tasks. People then break one vague task into four smaller vague tasks and feel busier while nothing moves. “Plan the website”becomes “think about pages”, “research options”, “look at competitors”. None of those are things your body can start doing in the next sixty seconds. Granularity without physicality is still avoidance, just tidier.

Worth knowing: Piers Steel’s 2007 meta-analysis in Psychological Bulletin, The Nature of Procrastination, found task aversiveness and low expectancy of success among the strongest correlates of putting things off. Both of those are partly manufactured by your own list. A vague item is aversive because it is undefined, and undefined work feels unlikely to succeed. Rewriting it changes the inputs, not just the mood.

Fix 1: Rewrite the Item as a Physical Next Action

The clarify stage of GTD asks one question of everything: what is the next physical, visible action? Verb first. Something you could film someone doing.

Before and after, from real stalled lists:

• “Sort out tax return”becomes “download P60 from payroll portal”.
• “Mum’s birthday”becomes “text sister to agree a budget for Mum’s present”.
• “Website”becomes “email Sam the three pages I want changed”.
• “Car”becomes “ring the garage to book the MOT”.

Notice the pattern. Every “before”is a noun. Nouns on a list are the single most common cause of a skipped task, because a noun is a subject heading, not an instruction, and every time you read it your brain has to re-plan from scratch. Re-deciding is what procrastination actually feels like from the inside.

Use the ten-second test. Read the item, then try to picture yourself performing it. If you cannot see the hand, the phone, the keyboard or the door, the item is still a project and needs Fix 2.

Fix 2: Settle the Outcome With the Natural Planning Model

Big work rarely stalls at the bottom. It stalls at the top, because everyone is hunting for a first step before anybody has agreed what done means. Allen’s natural planning model runs purpose, outcome vision, brainstorming, organising, next action, in that order, and the first two are the ones people skip.

A five-minute project start-up fixes it. Write one sentence that describes the finished state in the past tense, then pull the first action out of that sentence. For example: “Done means the 2025/26 Self Assessment is submitted and the payment on account is scheduled.”The filing deadline for an online return is the 31 January after the tax year ends, and HMRC publishes the current dates on its Self Assessment deadlines page, so check it rather than trusting memory. Once that sentence exists, the first action writes itself: gather the figures, which starts with the P60.

Brainstorm on paper or in a notes app if the shape is genuinely unclear. Five minutes, everything out, no filtering. But be honest about the point where planning becomes the hiding place. If you are on your third mind map and still have no phone call to make, you are procrastinating in a more respectable font.

Fix 3: Empty the Open Loops Competing for Your Attention

An uncaptured commitment does not sit quietly. It resurfaces mid-sentence, usually while you are doing something else that matters, and it takes a slice of attention each time. Twenty of those circling and the task in front of you never gets a clean run.

Job one: time to captured. If saving a thought takes more than about five seconds with your phone locked in your pocket, you will stop doing it under pressure, and the thoughts you lose are the ones you had walking between meetings. Judge any tool against the five jobs a notes system has to do: time-to-captured, one trusted inbox, retrieval from half a memory, exit cost, and no daily admin tax. Most stalling systems fail on the first and the last. Capture is slow, maintenance is heavy, so the list quietly stops being believable and you go back to working from memory.

Voice dictation and AI assistants genuinely cut time-to-captured, which is why capturing straight into an AI assistant can be a reasonable route when your hands are full. One caveat, and it matters: a chat transcript is not an inbox. Unless the captured line lands somewhere you process weekly, you have relocated the open loop rather than closed it.

Analogue still wins for some people. An index-card Hipster PDA has near-zero start-up friction, no notifications and no settings screen, which removes the “I’ll just organise my app first”detour that eats the first hour of real work. A pocket notebook does the same job. The kit matters less than the rule: one inbox, emptied regularly, nothing else.

Fix 4: Stop Stockpiling Micro-Decisions

The two-minute rule is the least glamorous idea in GTD and the one that pays fastest. While you are clarifying, anything that would take under two minutes gets done there and then, because filing it, tracking it and re-reading it costs more than doing it.

An email inbox of 2,000 messages is a procrastination engine built from exactly this failure. Every unread message is an undecided commitment, and because the decision is deferred, the whole folder becomes a place you do not want to look. Opening it costs willpower, so you open it less, so it grows.

Process instead. One pass, four destinations: do it now if it is under two minutes, turn it into a next action if it is longer, log it as a waiting-for if someone else owes you something, file it as reference if it is just information. If your email client has been a list for years, our walk-through of GTD email and list swaps covers the tooling side.

The discipline is deciding once. Re-reading the same message on Tuesday, Thursday and Sunday is not diligence, it is three doses of the same avoidance.

Fix 5: Sort Lists by Context, Time and Energy

A single list of 97 items guarantees you pick the easiest thing on it. Scanning a mixed list means weighing calls against errands against two hours of deep work, and the brain resolves that comparison by choosing whatever requires least of it. Usually something involving tidying.

Context lists remove impossible options before you choose. Calls, errands, at computer, agendas for specific people. At 4.15pm with fifteen minutes before a school run, “calls”shows you three things you can actually complete; the undivided list shows you a feasibility puzzle.

Match energy honestly too. Trying to force the hardest item into a 4pm slot is how people learn to hate their own system. Low-energy slots get low-stakes actions: expense receipts, the two-minute replies, filing. Save the thinking work for whenever your good hours actually are.

App features help if you use them to cut work rather than add it. Saved filters or OmniFocus perspectives that open directly on “what can I do here, now, with this much energy”remove a daily decision. Building fourteen elaborate views you then maintain is just a daily admin tax in a nicer interface.

Fix 6: Rebuild Trust With a Weekly Review and an Honest Someday List

Here is the position most procrastination advice misses entirely: avoidance is rational when the list is out of date. If a third of your items are stale, you do not believe the list, so you work from memory instead, and memory serves you whatever is loudest rather than whatever matters. Trust is the actual product of a system.

Book an hour in the diary, weekly, and run four passes:

1. Empty every inbox, physical, digital and whatever you dictated to an assistant.
2. Review every project and confirm each has at least one next action.
3. Check waiting-for items and chase anything that has gone quiet.
4. Scan the calendar roughly two weeks back and four weeks forward.

Then do the uncomfortable part. Anything you have not acted on in a month and will not act on next month moves to Someday/Maybe. It is not failure, it is bookkeeping. Items you have silently decided against generate guilt every single time you open the list, and that guilt is what makes you avoid opening it at all.

Three signs the system has drifted: items you have read so often you no longer see them, a list you tend not to open on Monday morning, and capture happening in three places at once. Fewer apps, wired together properly, beat a beautiful shelf of software you never open. If the drift has gone deep, rebuild from the structure rather than the tools, which is what our guide to building a personal productivity system that lasts sets out.

Work the six fixes in order on one stalled item and you will usually find the fault in the first two. That is the honest answer to how to stop procrastinating: stop negotiating with yourself, and edit the words until the next move is obvious, visible and somewhere you trust.

Frequently Asked Questions

Why do I procrastinate on tasks I actually want to do?

Wanting the outcome and knowing the first move are different things. Enjoyable projects stall most often because nobody has agreed what finished looks like, so every attempt to start turns into planning. Write the one-sentence done statement first, then pull a physical action from it.

What is the fastest way to stop procrastinating on one specific task today?

Rewrite it as a verb plus the first visible move, then check you can do it where you are sitting. “Sort out insurance”becomes “ring Aviva to ask what the renewal quote covers”. If you cannot picture yourself doing it within ten seconds of reading it, it is still a project and needs an outcome, not more willpower.

Does the two-minute rule really help with procrastination?

It helps with one specific kind: the stockpile of small undecided items that makes your inbox and lists unpleasant to look at. Clearing those during processing keeps the system believable, which is the thing that keeps you using it. It will not touch a genuinely hard, multi-week piece of work, so do not expect it to.

Is procrastination a time management problem or a motivation problem?

Mostly it is a definition and trust problem, which is why both the time-management and the motivation camps get partial results. Piers Steel’s 2007 review points to task aversiveness and low expectancy of success as strong drivers, and both are reduced when an item is specific, current and visible at the right moment. Fix the wording first, then judge what is left.

How often should I review my lists to stop things being put off?

Weekly, with an hour booked in the diary, plus a quick daily glance at whichever context list matches where you are. Any longer than a week and items go stale, the list loses credibility and you drift back to working from memory. The review is what makes the other five fixes keep working.

The post How to Stop Procrastinating: 6 GTD Fixes That Work appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

A personal productivity system is not an app, a template or a methodology; it is six moving parts that have to keep working when you are tired, late and holding a coffee. Most of them fail in the same place, and it is almost never the place people think. The honest conclusion, up front: your app is probably fine, your clarify step is broken, and no amount of migrating to a new tool will fix a list full of vague nouns.

This piece names the six parts, gives you five jobs to score any tool against, marks the two things AI genuinely does well here, and ends with the weekly routine that makes the whole arrangement self-repairing. It assumes you have already tried Todoist, Notion, a bullet journal or Reminders, got three good weeks, and watched it go quiet.

Why most personal productivity systems quietly die by week three

Three failure modes account for nearly all of it.

The first is a daily admin tax. You built a setup with tags, statuses, areas, a dashboard and four database views, and now every captured thought costs forty seconds of filing before it counts as handled. That tax is bearable in week one, when the work is light and the novelty is doing the carrying. By the second month, with a genuinely bad week on, you stop paying it. The system does not announce its death. It just stops being updated.

The second is a second inbox. Captures land in your notes app, flagged emails, browser bookmarks, Slack saved items and a notebook in your bag. None of those places is complete, so none of them is trusted, so you keep a mental backup copy of everything. That mental copy is the thing you were trying to get rid of.

The third is the review that gets skipped once. Miss a weekly review and your lists quietly drift out of date. Open a stale list and you cannot tell which items are real, so you close it and work from memory and your inbox instead. One skip becomes permanent surprisingly fast.

Open loops are the symptom to watch

David Allen’s term for an unresolved commitment is an open loop, and the test is brutally simple: if your brain is still rehearsing the same task at 2am, that task is not in a system you believe. Nice dashboards do not stop the rehearsal. Only a complete, current, decided list does.

The ‘perfect setup’ trap

Rebuilding your tag taxonomy feels like work. It produces no finished outcomes. A useful rule of thumb is that if you have reconfigured your setup twice in a month and shipped nothing, you are using configuration as procrastination, which is also the honest answer to a lot of searches about how to stop procrastinating: the stall is usually an undefined next action, not a character flaw.

Diagnose before you migrate

Before you move anything, open your current list and read the first ten items out loud. Count how many are a physical, visible action you could start right now, and how many are nouns like “insurance”, “Mum”or “website”. If most are nouns, switching apps will carry the problem across intact, with a weekend of setup added for free.

The six moving parts every working system needs

1. Capture

One frictionless way to get anything out of your head, wherever you are. Phone locked, screen off, hands busy: that is the real test condition, not a calm desk. If getting a thought saved takes more than about five seconds, you will skip it under pressure, and the skipped ones are the good ones.

2. One inbox

Everything lands in a single processing point. Email, voice notes, web clips, photographed paper. You can have several capture tools; you cannot have several inboxes and still trust the result. Consolidating to one place beats any amount of clever tagging.

3. Clarify

Decide what each item is and what the very next physical action is. “Website”becomes “draft three homepage headline options in Obsidian”. “Mum”becomes “ring Mum about the hospital date”. This is the step people skip, and skipping it means every glance at the list costs a fresh decision. Lists that charge you a decision per glance stop getting opened. Teaching this chapter by chapter out of Allen’s book is where the difference shows, because the reasoning matters more than the template.

4. Organise

Next actions go on lists split by context. Projects (anything needing more than one action) go on a projects list. The calendar holds only things with a real date and time, never aspirational scheduling. One update on the original book: “at computer”is now meaningless, because everything is on your laptop. Rebuild contexts around genuine constraints instead: low energy, requires other people, offline, phone calls, errands, needs 90 uninterrupted minutes.

5. Reflect

A weekly review that reconciles the lists against reality. Without it, the lists are a record of what you intended a fortnight ago.

6. Engage

Choosing from a list you believe, filtered by context, time available and energy. If you trust the previous five parts, this is the easy one. If you do not, no prioritisation method on earth will rescue it.

Choose tools by the five jobs, not the feature list

Feature tables tell you which app has handwriting, backlinks and an AI summariser. They do not tell you whether it survives a busy Tuesday. Score candidates against five jobs instead.

Time-to-captured

Count the seconds and taps from thought to saved item with the phone locked. Lock screen widget, share sheet, watch complication, voice. Five seconds is a practical working benchmark rather than an official rule, but an app that wins on features and loses here will not last the month.

One trusted inbox

Can email, web clips, dictated notes and a photo of a scribbled card all arrive in the same place for processing? An inbox email address, a share extension and a scan function cover most of it. If the tool forces a separate holding pen for one input type, you have manufactured a second inbox.

Retrieval from half a memory

You remember the gist, not the title, folder or date. Test it: search for a phrase you half-recall from a note you wrote months ago, including text inside attachments and images. Full-text search across PDFs is the quiet differentiator here, not note linking.

Exit cost

Run an export today, before you commit years of reference material. Proprietary formats, two-way links and database views frequently flatten to plain text or lose attachments entirely, and you only discover it when leaving. The migration costs are covered in more detail in the comparison of Evernote alternatives and what their exports actually preserve.

No daily admin tax

How much tidying does the tool demand before it gives anything back, and how much can you switch off? If you cannot explain a field’s purpose in one sentence, delete the field. For a job-by-job scoring of the main contenders, the roundup of the best note taking app options for a GTD workflow applies exactly these criteria.

Where AI earns a place (and where it breaks trust)

AI is a capture and clarify assistant. It is not a list owner.

Good jobs: dictating a capture hands-free while walking, with the phone in your pocket; turning a four-minute rambling voice note into a tidy set of candidate next actions; producing a first-pass brainstorm for a project you have been avoiding. There is a working method for the first of those in the guide to ubiquitous capture with an AI assistant.

Bad jobs: letting a chatbot hold your authoritative action lists, and accepting invented deadlines or next actions you never agreed to. A model that confidently adds “submit by Friday”to a task where no Friday exists has just put a lie into the one place that needs to be true. The moment your list contains items you did not decide, you stop believing it, and you are back to the 2am rehearsal.

The practical rule: AI can speed up capture and clarify; reflect and engage stay yours. Treat every AI output as an inbox item to process, never a decision already made. The breakdown of which GTD jobs ChatGPT does well and which it ruins goes further into the line between the two.

Build it in one weekend: a start-up sequence

1. Mind sweep. Everything out of your head onto separate slips or lines. Paper is fine and usually faster. Expect something in the region of 80 to 150 items and an hour or two; that range is typical experience rather than a measured figure, but if you finish in fifteen minutes you have not finished.
2. Process the pile once. For each item: if clarifying it would take longer than doing it, do it now. That two-minute rule tends to finish roughly a third of a first sweep on the spot. Everything else becomes a next action, a project, reference, someday/maybe, or bin.
3. Set up only the lists you will read. Next actions by context, projects, waiting for, someday/maybe, calendar. Then stop configuring. Resist the dashboard.
4. Run the natural planning model on your two messiest projects. Purpose, outcome vision, brainstorming, organising, next actions. Apply it to “move house”or “launch the newsletter”and the stall almost always turns out to be a missing next action rather than missing motivation.
5. Empty email once. Down to zero, using the same clarify decisions. The point is not inbox zero as a lifestyle; it is starting the system from a known state. The two-minute rule clears a startling share of a 500-message backlog in one sitting.

Keep it alive: the weekly review and the paper hybrid

The review, same slot every week

Thirty to sixty minutes, Friday afternoon or Sunday evening, fixed checklist:

• Empty every inbox, including the physical one and the notes app.
• Scan the calendar two weeks back and four weeks forward.
• Read the projects list and confirm every single project has a next action.
• Check “waiting for”and chase anything stale.
• Skim someday/maybe and move one thing up or let it go.

The projects check is the load-bearing one. A project without a next action is where stalls hide.

Paper is not nostalgia

A Hipster PDA, which is a stack of 3×5 index cards and a bulldog clip for a couple of pounds, has an unbeatable time-to-captured in a meeting, on site, in a queue or with no signal. No open up, no app launch, no awkward phone-out moment while someone is talking. The discipline that makes it work is the nightly or weekly shuffle: captures get processed into the digital lists and the cards go in the bin. Skip the shuffle and you have two parallel systems, which is the second-inbox problem wearing a hat. There are printable hPDA card templates if you want the lined and project versions.

Healthy, repairable, or genuinely time to switch

Signals it is working: you recall fewer loops from memory, you finish outcomes rather than having busy days, and the weekly review is something you do rather than dread.

Most wobbles are repairs, not replacements. Lists gone stale means a missed review. Items being ignored means they are nouns, so rewrite them as actions. Captures going astray means your capture route is too slow. Switching tools is only justified by something structural: the product shuts down, sync breaks repeatedly, the price changes beyond what the job is worth, or the admin tax is baked in and cannot be switched off. Migration costs you a weekend and your reference history. Spend that rarely.

If you want the reasoning behind each part straight from the source, the official Getting Things Done site from the David Allen Company sets out the five steps the method is built on. And if you want to judge whether the system is paying off, measuring finished outcomes rather than hours logged is the right frame; there is more on that in the piece on what UK productivity figures actually mean for your work.

Frequently Asked Questions

What is a personal productivity system, and how is it different from a to-do list?

A to-do list is one component: a record of things you intend to do. A personal productivity system is the whole loop that keeps that list true, covering capture, clarify, organise, reflect and engage. The difference shows when you are under pressure, because a bare list goes stale and a system repairs itself at the weekly review.

How long does it take to set it up from scratch?

A focused weekend gets you running: an hour or two for the mind sweep, a few hours to process it, and one session to empty email. Expect the lists to feel rough for two or three weeks while you learn what a properly worded next action looks like. The system becomes trustworthy at around the third weekly review, not on day one.

Which app should I use?

Whichever one wins on time-to-captured and does not charge a daily admin tax. Score your shortlist against the five jobs above rather than the feature table, test an export before you commit, and accept that plain text files and a calendar beat an elaborate setup you quietly abandon. Apple Reminders plus a notes app is a legitimate answer for a lot of people.

Why does my system keep falling apart after a few weeks?

Almost always one of three things: the upkeep outgrew the payoff, captures scattered into a second inbox nobody processes, or the weekly review got skipped and never resumed. Check the wording on your lists first. Vague nouns instead of next actions is the most common root cause, and no new app will fix it.

Can AI tools run my productivity system for me?

They can speed up capture and help you clarify a messy voice note into candidate actions. They should not own your lists or invent deadlines, because the moment the list contains commitments you did not make, you stop trusting it. Keep the authoritative lists human-readable and human-owned, and treat anything an assistant produces as an inbox item to process.

The post Personal Productivity System: Build One That Lasts appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The honest conclusion, up front: the Notion vs Obsidian question is not about features, it is about which set of running costs your week can absorb without you quietly abandoning the system. Both apps are good. Both are free to start. Both will happily sit on your machine as a beautiful shelf of software you never open, because the cost that kills a GTD setup is never the licence fee.

Every comparison you will find scores databases against backlinks, cloud against local, team against solo. Useful, and already well covered, including in the site’s own piece on which of the two fits a GTD workflow. This one does the opposite. It prices the switch: six costs your system pays daily, weekly or on the day you leave, including the cost of choosing wrong and moving back.

Cost one: how many seconds it takes to get a thought out of your head

GTD treats capture as a timed job for a reason. An open loop you cannot record in a few seconds goes straight back into your head, where it costs attention for the rest of the day. If capture takes more than about five seconds under pressure, you will stop doing it, and the thoughts you lose are the ones you had walking between meetings, not the ones you had at a tidy desk. Five seconds is a practical working benchmark rather than an official rule, but it holds up.

Notion’s natural capture route is a database row. Which means a picker: project, status, maybe a context, maybe a date, before the thought itself is even safe. That is processing dressed up as capture, and it breaks the rule that capture and clarify are separate steps. The fast Notion users all do the same thing: they keep a dumb inbox database with one field, title, and sort later.

Obsidian’s equivalent is appending a line to an inbox note, which is quicker on desktop and usually quick on mobile, with one condition attached. Sync has to be awake. Open the vault on a phone that has not synced for a day, type a line, and you are one conflict away from two versions of your inbox.

Run the arithmetic on your own week rather than trusting either marketing page. Count your captures for two days. If you log around twenty items a day and one app costs eight seconds more per capture, that is roughly two and a half minutes a day spent at the exact moment you are least willing to spend it, and several hours across a working year. The seconds matter less than the abandonment they cause.

The conclusion most comparisons miss: neither app has to be the catcher. A voice memo, a quick-entry task app or an AI assistant used purely as a capture channel can hold the thought, and Notion or Obsidian becomes the place it lands afterwards. One trusted inbox, emptied regularly. Where it lives matters far less than that there is exactly one.

Cost two: the daily admin tax

Both tools reward building. That is the trap.

Notion’s tax is view maintenance. Filtered views drift as projects change, rollups break when someone renames a property, relations need re-pointing, and the template you built in January needs editing in March because your process moved. None of it is hard. All of it is work that looks like productivity.

Obsidian’s tax is plugin upkeep. A community plugin updates and a Dataview query stops returning your next actions; the Tasks plugin changes how it reads a date format; your config on the laptop and the config on the desktop slowly diverge until one machine shows a different project list to the other. Also not hard. Also not deciding next actions.

There is a plain test for either tool, and you already have the slot for it. During your weekly review, note how many minutes went on repairing the system rather than deciding what to do next. Track it for a month. That number, not the feature grid, is the real price difference between Notion and Obsidian for you specifically.

The tax is worth paying when the structure answers a question you actually ask every week: what is waiting on someone else, what is due at this client, what has had no activity for a fortnight. It is not worth paying when you are colour-coding statuses nobody reads. Tidying feels like progress and produces none.

Cost three: licences, sync and the money side

The two pricing models have different shapes, and the shape matters more than the number. Obsidian is free for personal use, with paid add-ons such as Sync and Publish; licensing terms for work use have changed, so check Obsidian’s published pricing and licence page rather than relying on any article’s summary (checked 15 September 2026). Notion runs a free personal plan with paid plans charged per member, which means your cost scales with headcount rather than with features.

Check the figures yourself on the day you decide, on Obsidian’s pricing page and Notion’s pricing page, because both vendors have changed plans and add-on structures more than once. Any article quoting prices at you without a date checked is quoting history.

Self-hosted sync for Obsidian over a cloud drive or Git looks free and mostly is, in money. It costs setup time, and it costs conflict resolution on mobile, where background sync is least reliable and your vault is most likely to be half-updated. If you are the sort of person who enjoys that, it is close to free. If you are not, Sync is the cheaper option once you price your own Saturday morning.

The cost nobody budgets for is duplication. Your client’s team runs on Notion because someone else chose it, so you keep a personal Obsidian vault for your own lists, and every commitment made inside a Notion page has to be rewritten as a next action in the vault. The ones that do not get rewritten are precisely the ones that get missed. Two tools, two subscriptions, and a third cost paid in double entry.

Cost four: exit cost, which you should test before you commit

“Plain text means no lock-in”is half true, and the half people quote is the wrong half. An Obsidian vault opens in any editor, yes. Your prose is portable. Your system is not: Dataview queries become inert code blocks, Tasks plugin syntax becomes stray emoji and brackets, and canvas files become JSON that no other app will draw. The more cleverly you built it, the less of it travels.

A Notion export gives you Markdown and CSV, and it gives back the words honestly enough. What it does not give back is the machinery. Relations and rollups arrive as static columns, filtered views simply vanish because they were never content, and synced blocks come out as duplicated text in every page they appeared on. Anyone whose project list depends on rollups is exporting the sentences and leaving the logic behind.

Test this in an afternoon, before the decision, not after. Export one live project from Notion as Markdown and CSV, open it in a plain text editor, and write down what is missing: views, rollups, comments, the context a relation used to carry. Then zip an Obsidian folder containing a couple of Dataview blocks and a canvas, open it in something neutral, and do the same. The same discipline applies to any migration, which is why the piece on Evernote alternatives and their real migration costs starts in the same place.

Exit cost bites harder in a GTD system than in a wiki. A reference library can survive a messy move; you will find things eventually. Your project list and your next actions cannot. Lose those mid-migration and you spend a fortnight running on memory, which is the thing the system existed to replace.

Cost five: finding it again from half a memory

The retrieval test that matters is not “can it search”. It is this: you remember a fragment of a phrase, roughly which month, and nothing else. Go.

Notion searches across databases and nested pages, which is genuinely strong when your content lives in properly structured pages, and weaker when the thing you half-remember was typed into a database cell or buried in a toggle three levels down. Obsidian searches the files on disk, instantly, with backlinks and the graph to walk sideways from whatever you did find. Graph view is mostly theatre; backlinks are not, and they earn their keep when you capture the link at the moment of writing rather than during a tidy-up.

Offline is where the gap is widest, and it is a real scenario rather than a spec line. Forty minutes with no signal, and you need a note from three months ago. A local vault searches in full, every file, every time. A cloud workspace gives you what has been cached; Notion’s offline support has improved, but it still favours recent and explicitly saved pages over everything you have ever written. Decide how often your week looks like that train, honestly.

Habits beat engines either way. One inbox, dated notes, and links made at capture will outperform any amount of search tuning.

Cost six: AI add-ons, per seat or per API call

AI changes the cost model rather than the workflow, which is the part the launch posts skip. Notion AI is billed through the workspace, bundled into some plans and sold as an add-on on others, so it lands as a fixed line item per member whether you use it twice a month or forty times a day. Obsidian has no first-party AI; you install a community plugin such as Copilot, Smart Connections or Text Generator and point it at your own API key, or at a local model through something like Ollama. That spend scales with usage, and the local route costs nothing per call but costs you hardware and setup.

There is a quieter question underneath the invoice. A hosted model means note content leaves the machine, including from a vault you chose specifically because it was local. Read the provider’s terms on training and retention before you wire a plugin into client notes, and if the material is sensitive, run a local model or do not run one at all.

What AI actually earns its keep on in a GTD system is narrow and useful: drafting a project outcome in one sentence, turning a sprawling meeting note into candidate next actions you then edit, summarising reference material you already collected. The same split covered in the guide to the jobs ChatGPT does well in GTD and the ones it ruins applies here. What it will not fix: an unstructured vault, an inbox you have not touched since Tuesday, or a weekly review you keep skipping. Neither app enforces the review. That remains your job.

So which one, and when do you run both?

Choose Notion if the costs you most want to avoid are shared context ones: people asking where the brief is, status that lives in someone’s head, structured data you genuinely query. Choose Obsidian if offline access, file ownership, low exit cost and fast local notes matter more than anyone else seeing your work.

Better still, stop crowning a winner and map the tools to GTD phases. A Notion page template fits project start-up and the natural planning model cleanly: purpose, outcome, brainstorm, organise, next actions, all in one structured page a client can read. Linked notes in Obsidian fit brainstorming and reference, where the value is in connections you did not plan.

If you run both, there is exactly one rule, and it is not negotiable: next actions live in a single place. Notes can be everywhere. Commitments cannot. The moment your actions exist in two systems, your weekly review becomes a reconciliation exercise and your trust in both drops, which is the same failure mode as rebuilding an inbox after a tool disappears: not lost data, lost trust.

If you are still weighing the field rather than these two, the scored comparison of the best note taking app for a GTD workflow runs seven contenders against the same jobs used here: time to captured, one trusted inbox, retrieval from half a memory, exit cost and daily admin tax. Read that next, then run the export test on whichever two you are torn between.

Frequently Asked Questions

Is Notion or Obsidian better for a GTD system?

Neither is better in the abstract; they fail differently. Notion suits you if project context is shared with other people and you query structured data weekly, while Obsidian suits you if you work alone, offline, and want your files to outlive the app. The deciding factor is usually how many weekly review minutes each one costs you in maintenance.

What does it actually cost to move from Notion to Obsidian?

Money is the small part, because Obsidian is free for personal use and the export from Notion costs nothing. The real cost is rebuilding what the export does not carry: filtered views, rollups and relation logic, plus the hours spent re-pointing your project list and next actions. Budget a weekend for a modest workspace and more if your system leans heavily on databases.

Does a Notion export lose anything important?

It returns your words and loses your machinery. Markdown and CSV exports hand back page text and table data, but filtered views disappear, relations and rollups become static columns with no live connection, and synced blocks arrive duplicated wherever they appeared. Export one real project first and list what is missing before you migrate the rest.

Can you use Notion and Obsidian together without duplicating work?

Yes, if you give each one a different job and keep next actions in exactly one of them. A common split is team pages and shared project briefs in Notion, personal notes and reference in Obsidian, with actions in whichever system you review weekly. The duplication starts the moment commitments exist in both places.

Which is better offline, Notion or Obsidian?

Obsidian, clearly, because the vault is files on your device and search covers all of them with no connection at all. Notion’s offline support has improved, but it still leans on cached and explicitly saved pages rather than your whole workspace. If a long commute with no signal is a regular part of your week, that difference decides the Notion vs Obsidian question on its own.

The post Notion vs Obsidian: 6 Real Costs of Switching appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The best note taking app for iPad is the one that gets a thought out of your head before the thought gets bored, and still lets you find it three months later from half a memory. That is the honest test. Handwriting feel, template packs and how nice the ink looks on a 12.9in screen are all downstream of it.

Here is the conclusion up front, before the comparison. For most people running Getting Things Done, Apple Notes wins the capture job on an iPad and loses the archive job, so it works best paired with something file-based behind it. Drafts beats everything if you type more than you draw. Goodnotes and Notability are worth paying for only if ink is genuinely the work, and only if you accept a processing step after every meeting. Notion is support material, not capture. Obsidian is the cheapest long-term home for your reference, with the most fiddly setup day one.

This piece judges six apps against five jobs, with the iPad’s own problems kept in view rather than politely ignored.

Why most iPad note apps fail a GTD system

Every round-up ranks these apps on handwriting latency, PDF annotation and stickers. Almost none ask what happens to the note afterwards, which is the only part GTD cares about. A note that never becomes a next action, project support material or reference is just a tidier version of the pile on your desk.

Five jobs, applied consistently:

• Time-to-captured. Seconds from device asleep to words recorded. Under five is the practical working benchmark rather than an official rule, and it is the number that decides whether you keep using the thing.
• One trusted inbox. Everything lands in a single place you will actually empty, not four notebooks you sometimes check.
• Retrieval from half a memory. You remember “something about the invoice template, roughly February”. Can the app find it?
• Exit cost. What you get back on the day you leave, in a format another app can read.
• No daily admin tax. Tags, covers, folder trees and statuses that feel like progress and produce nothing.

Now the device problem, which comes first. An iPad lives in a bag. Your phone lives in your hand. So the real comparison is not Goodnotes against Notability, it is iPad against the phone you are already holding while walking between meetings. Unzip, wake, open up, open app, new page, pick pen: you have spent fifteen seconds before the first word. Marketing screenshots never show that queue. Your thumb does.

That reframes several of these apps. They are not your capture tool. They are the second capture point in a system, used when the iPad is already open in front of you, and they need to be judged on what they do with a thought once it has arrived.

Handwriting is the iPad’s selling point and GTD’s quiet failure mode

Ink is fast for thinking. Arrows, boxes, a rough org chart, a sketch of a pricing table: the Pencil beats a keyboard for all of it. The trouble is that writing “chase Jo re invoice template”in the margin of page four feels like you have captured a next action. You have not. You have buried one.

Handwriting recognition does not fix this, and better recognition will not either. An unprocessed ink page is still an open loop, however legible it is. The fix is a step, not a feature: after every meeting, spend two minutes reading your own page for verbs and moving each one somewhere searchable, leaving the drawing behind as reference. If you will not do that, buy a cheaper app.

The default, and why it is hard to beat on capture

Apple Notes

Apple Notes is the only app on this list that can be reached without unlocking the iPad. Tap the Pencil on the Lock Screen (you enable it under Settings, Notes, Access Notes from Lock Screen) and you are writing. Swipe up from the bottom right corner, or add Quick Note to Control Centre, and you get a floating note over whatever you were doing. Apple’s own walkthrough of these gestures sits in the iPad User Guide, and the routes do shift between iPadOS versions, so check yours.

Time-to-captured: roughly two seconds once the iPad is awake. Nothing paid beats that, because nothing paid is allowed to sit on the Lock Screen.

Search reads your handwriting, which matters more than it sounds. Quick Note also saves a link back to the Safari page or PDF you were looking at, so the note knows its own context when you process it on Sunday.

Where it falls down is structure and the exit. Folders and tags are fine for reference and thin for projects: no properties, no linked databases, no real way to hold a project’s support material together beyond a folder and good naming. Export is the bigger issue. You get PDF, or you select text and copy it, and there is no first-class “give me all of this as files”button. Your ink comes out as a flat image in a PDF. Readable. Not reusable.

Best for

• IPads that are a satellite of an iPhone and a Mac
• Anyone whose capture habit keeps dying because the app takes too long to open
• Mixed ink and typing, where the ink is thinking and the typing is the action

Pros

• Lock Screen and Control Centre capture, no open up, no sign-in
• Handwriting search that works well enough on normal handwriting
• Free, included, syncs across Apple devices without configuration
• Almost zero admin tax: there is very little to tidy

Cons

• Weak project structure for anything with many moving parts
• Export is PDF and plain text; no clean bulk file export
• Apple-only, so a future move to Android or Windows is painful

Ink-first apps and the retrieval problem

Goodnotes

Goodnotes treats the page as the unit, and for lectures, marked-up PDFs and long handwritten meeting notes that is the right model. Handwriting search is good on tidy writing and unreliable on scrawl, which is a problem specific to the notes you took fastest, which are usually the ones that mattered. Pricing has moved between a one-off purchase and an annual subscription depending on version and region, so check the current terms in the App Store before you commit.

Its admin tax is the highest here. Notebook covers, paper styles, nested folders, favourites. All of it feels like progress at eleven on a Sunday night.

Best for

• Students and anyone annotating PDFs for hours a week
• Pencil-heavy work where the page layout carries meaning

Pros

• Excellent ink feel and page handling
• Handwriting search across notebooks
• Strong PDF import and mark-up

Cons

• Slow to capture a single line compared with Quick Note
• Export is largely PDF or image, so structure and searchability do not travel
• Wrong for: anyone who mainly types, and anyone who wants one trusted inbox rather than shelves of notebooks

Notability

Notability’s one genuinely distinctive trick is audio recorded against the ink, so tapping a word jumps the playback to the moment you wrote it. In a client call where you missed a number, that saves a rewrite and occasionally an argument. Record people’s voices only with their knowledge and consent, which in the UK and EU is both basic courtesy and a data protection question.

Notability now runs a free tier plus a paid subscription for the fuller feature set, and the split has changed more than once, so verify before paying.

Best for

• Lectures, interviews and long meetings where the audio is the backup
• Note-takers who want one continuous scrolling page rather than fixed pages

Pros

• Audio synced to ink, which no other app here matches
• Clean, fast writing experience
• Reasonable handwriting search

Cons

• Subscription terms have shifted, so recheck what your tier includes
• Export produces PDFs and app-specific bundles, not portable text
• Wrong for: anyone wanting a reference archive they can grep in ten years

Structure, sync and exit cost

Obsidian

Obsidian is Markdown files in a folder you own. That is the whole pitch and it is the strongest answer to exit cost on this list: the files are readable in TextEdit, Notepad, Working Copy, anything. Nothing to export, because nothing was ever locked in.

The friction is day one on iPad. ICloud Drive sync works and occasionally sulks; the official Sync service is paid; setting up a vault on a cellular iPad takes a bit of patience. Capture speed is mediocre, because the app has to load the vault before it loads your cursor. We have compared the two platforms in more detail in this look at Obsidian vs Notion for a GTD workflow, including how each handles project support material. If the sync fees and sluggish capture here give you pause, the six real costs of switching between Notion and Obsidian are broken down in full.

Best for

• Reference and project notes you intend to keep for a decade
• People who want plain text, local files and no vendor

Pros

• Exit cost close to zero
• Fast search across everything, including old notes
• Free for personal use; plugins cover almost any workflow

Cons

• Sync setup is the least pleasant part of iPad life here
• No Pencil handwriting worth the name
• Wrong for: anyone who wants it to be their capture tool

Notion

Notion is the best of the six at holding a project’s support material: a brief, a client’s constraints, a shared table of deliverables, all linked. On iPad it is also the slowest to open and the weakest away from a decent connection, which is exactly the condition you are in on a train.

Its admin tax is databases and views. Powerful, and an easy place to spend a Sunday building something you will not maintain.

Best for

• Shared reference and client-facing project pages
• Teams that already live in it

Pros

• Genuinely good structure for projects and reference
• Collaboration that Apple Notes cannot match
• Markdown and CSV export available

Cons

• Slow cold start; poor offline behaviour on cellular iPads
• Export preserves text better than it preserves your databases
• Wrong for: capture, and for anyone who works offline often

The capture-first option

Drafts

Drafts opens to a blank cursor. Every time. No file picker, no notebook choice, no decision. It is the closest an iPad gets to a pocket notebook, and it is built around exactly the idea GTD starts with: get it down first, decide where it lives second.

Actions then route that line onward: into OmniFocus or Reminders as a next action, into an email, appended to a Markdown file. One inbox at the front, many destinations behind it, which is the shape of a system that stops fragments scattering across four apps. There is a free tier and a Pro subscription for the heavier automation.

Best for

• Keyboard-first writers with a Magic Keyboard or Smart Folio
• Anyone whose problem is scattered fragments rather than messy handwriting

Pros

• Fastest typed capture of the six
• Actions keep one trusted inbox while feeding task and note apps
• Plain text throughout, so exit cost is low

Cons

• Not a reference archive and not a PDF annotator
• No real Pencil story
• Wrong for: students who live in ink

Choosing between the six, by how you actually work

Time the loop before you choose. IPad asleep in the bag, thought arrives, start the clock: how long until the words are on screen? Then type the same thought into your phone from its Lock Screen. The gap between those two numbers decides more than any feature table, and for most people it says the iPad is the second capture point, not the first.

From there:

• Pencil-heavy student or meeting note-taker: Goodnotes or Notability for the page, Apple Notes or Drafts for the actions you pull out of it.
• Keyboard-first writer: Drafts at the front, Obsidian behind it. Skip the ink apps entirely.
• Mixed capture and reference: Apple Notes for speed, Obsidian or Notion for the archive.
• iPad is your only device: lean on Apple Notes plus one file-based archive, and keep the tag system thin.
• Still think on paper: photograph the index card straight into the same digital inbox. Our free Hipster PDA templates work well for this, as long as the photo lands in one inbox instead of starting a second pile.

Fewer apps, wired together properly, beat one app trying to be a notebook, a task manager and a wiki. Capture and reference want opposite things: one wants no decisions, the other wants structure. A pairing admits that. The broader version of this argument, across platforms rather than just iPadOS, sits in our comparison of the best note taking app options for a GTD workflow.

On AI: use it after capture, never in front of it. Summarising a messy meeting page or cleaning up handwriting is useful processing work. Anything that adds a prompt, a wait or a model choice before the thought is recorded makes time-to-captured worse, which is the one number you cannot afford to spoil. If you do want a voice assistant in the capture chain, the sensible setup is covered in this piece on capturing ideas in under five seconds with an AI assistant.

Setting it up so the weekly review takes minutes

Switch off every extra notebook until processing is a habit. One inbox, one place. Most abandoned systems died of three inboxes, not of a bad app.

Keep naming rules you will still follow in six months when you are tired and behind: date first, project second, three words of description. Tags only where search genuinely fails, which on an iPad is less often than you think.

Processing a page of ink is a specific job. Read it for verbs, write each one into your task list as a real next action (“ring Jo about the invoice template”, not “invoices”), mark the rest as project support material or reference, then archive the page. David Allen’s natural planning model doubles as a page template for the iPad: purpose, outcome, brainstorm, organise, next action. A brainstorm page with no next action pulled out of it is an open loop wearing a nice cover.

Last check, and do it before you pay for anything: open the export menu today. Export one notebook. Look at what actually comes out. A PDF of your ink is not the same as getting your notes back, and finding that out in year three, with 400 notebooks, is an expensive way to learn it.

Frequently Asked Questions

What is the best note taking app for iPad if you follow GTD?

Apple Notes for capture, because Lock Screen and Quick Note access beats everything else on seconds, paired with a file-based archive such as Obsidian for reference. If you type more than you write by hand, swap Apple Notes for Drafts and keep the same shape: fast inbox at the front, durable searchable store behind it.

Is Apple Notes good enough, or do you need a paid app?

For most GTD users it is good enough, and the free option winning is the unglamorous answer here. Pay for Goodnotes or Notability if you annotate PDFs daily or need audio synced to your ink; pay for Drafts Pro if you want captured lines routed automatically into a task app. Pay for nothing because a review called an app beautiful.

Can you search handwritten notes on an iPad?

Yes. Apple Notes, Goodnotes and Notability all index Apple Pencil handwriting, and results are good on neat writing and patchy on rushed writing. Treat it as a useful fallback rather than your retrieval system, and type the next actions you will need to find again.

Should you use one app for notes and tasks, or keep them separate?

Separate, in almost every case. Notes hold thinking and reference, which grows; tasks hold commitments, which need to be short enough to scan at speed. Mixing them is how task lists become unreadable, which is why many people run a notes app alongside something like OmniFocus with custom perspectives.

How do you move your notes out if you change app later?

Export before you need to, so you know what you are dealing with. Markdown or plain text files come out intact; proprietary ink formats come out as flat PDFs, meaning your annotations survive and your structure and searchability do not. Our breakdown of Evernote alternatives and their real migration costs shows how different those two outcomes feel in practice.

The post Best Note Taking App for IPad: 6 GTD Picks appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

A flexible working productivity system is the one that still works in the room you are actually in, with the tools you happen to have on you. That is the honest test. Most pages ranking for “flexible working productivity system”are written for employers: benefits, engagement, retention statistics. Useful if you run an HR policy, useless at 7.40am on a Tuesday when the action you need is sitting on a desktop in an office you will not reach until nine. This piece builds the personal version using GTD mechanics: contexts redrawn around place and energy, one trusted inbox, a capture tool judged on five jobs, and a weekly review pinned to the shape of your week. The conclusion, up front: you need fewer tools and one defended review slot, not a new app.

Why the office system stops working when the week splits

Nearly every task list assumes one desk, one set of tools, and a continuous block of hours to work through them in. Fine for a fixed five-day office pattern. On a 3-2 hybrid, a nine-day fortnight or flexi hours arranged around a school run, that assumption fails in three specific ways.

Open loops get stranded on the wrong device. A note scribbled in a meeting app on the work laptop is invisible from the kitchen table. Actions need a place you are not in: “file the signed contract”is a Thursday-in-the-office job, but it sits in your list all week nagging at you. And reviews simply stop happening, because nothing in a variable week prompts you to tidy up. A fixed commute used to do that job. Remove the commute and nothing replaces it.

Two failure modes follow. The first is a list you no longer trust, so you start running the week from memory and from whatever shouts loudest. The second is subtler: a daily admin tax in tags, statuses and tidying, which quietly eats the hours flexibility gave you back. If you are spending twenty minutes a day maintaining the system that is meant to be saving you time, the system has turned into the work.

Map the shape of your week before you choose any tool

Do this on paper before you touch an app. Write down the real week, not the one in the handbook. Anchor days in the office. The mornings where you can actually think. The 45 minutes lost to the school run. The hour that is always meetings, every week, without exception. The two train journeys.

Then label each block by what it can hold rather than what is scheduled in it:

• Deep work: uninterrupted, cognitively expensive, needs the good screen and a closed door.
• Shallow work: admin, expenses, form-filling, the stuff you can do while tired.
• Calls: anything that needs a voice and signal, including the walk to the station.
• Errands: physical, place-bound, often clustered around the office day.
• Dead time: commute, queue, waiting room. Short, interruptible, phone-only.

Run a dead time audit for one week and the numbers tend to surprise people. Two 25-minute train journeys and a 15-minute pharmacy queue are three usable slots. Not deep work slots. Three slots a well-built low-energy or calls list can genuinely clear.

Last step: decide what each location is actually good for, and then stop fighting it. If home gives you two quiet hours before the first call, home is where the writing happens. If the office is wall-to-wall people, the office is for conversations, signatures and the things that need other humans. Trying to do office work at home and home work at the office is where most hybrid weeks fall apart. The map, not the app, is the foundation here.

Redraw your context lists around place and energy

Classic GTD contexts of @work and @home were drawn when work had one address. On a split week they produce the worst possible outcome: you open a list and half of it is undoable from where you are standing. Do that three times and you stop opening the list.

Rebuild around what a block can hold:

• @deep: the three or four things that justify your best hours.
• @calls: short, voice-only, doable while walking.
• @errands: anchored to the office day or the high street.
• @low energy: expenses, filing, read-and-delete, the 8pm-on-the-sofa list.
• @online: anything that needs a browser and a login, from anywhere.
• @agenda-[person]: one short list per colleague.

Keep each list short enough to scan in the three minutes before a meeting starts. If a context list needs scrolling, it is a project list wearing a disguise.

The agenda lists are the ones hybrid workers underuse and the ones that pay back fastest. You lose corridor conversations when you are home three days a week, so the small questions pile up and turn into emails that turn into meetings. Hold them instead. On a 3-2 pattern with Tuesday and Thursday as anchor days, you empty @agenda-Priya and @agenda-Tom in person on those two days, and home mornings stay clear for @deep before the first call. Tooling helps here if you already use something capable: saved views make this trivial, and the custom perspectives approach for OmniFocus is the same idea applied to one app.

A worked example: a project stranded between two locations

Say a supplier review has been sitting on your project list for six weeks. Every time you look at it you move on, because the next action is really “think about it”, and thinking about it needs a block you keep giving away.

Run the natural planning model once, at the kitchen table, twenty minutes. Outcome: a one-page recommendation agreed with Finance by the end of the month. Principles: no new systems, no renegotiation before the contract break date. Brainstorm: pricing comparison, the two complaints from Operations, the licence count nobody has checked. Organise: comparison first, then the Operations conversation, then the write-up. Next action: “draft the comparison table from last year’s invoices”(@deep, home, Wednesday morning), with “ask Tom which complaints were logged formally”sitting on @agenda-Tom for Thursday.

Projects that straddle two locations stall at the thinking stage, not the doing stage. Twenty minutes of planning buys you a next action that is doable from somewhere you will actually be this week.

Capture that survives commutes, kitchen tables and school runs

Judge a capture tool on five jobs, not on its feature list:

1. Time-to-captured: seconds from idea to saved, phone locked, screen off.
2. One trusted inbox: everything arrives in a single place you will definitely empty.
3. Retrieval from half a memory: can you find it when all you remember is “something about the invoice and a Tuesday”?
4. Exit cost: what leaving in three years costs you in formatting, attachments and links.
5. No daily admin tax: capture should not require tagging, filing or a status update.

Time-to-captured matters most on flexible hours, because your ideas arrive in motion rather than at a desk. Under five seconds is a practical working benchmark rather than an official rule, and anything slower gets skipped under pressure. The ideas you lose that way are the ones you had while walking to the station. If you want the longer comparison, the tested note taking app picks for a GTD workflow work through each of those five jobs app by app, and there is a separate piece on using voice and an AI assistant as one capture channel when your hands are full.

Paper has not been superseded. In a packed train, during a school pick-up, or in any room where pulling a phone out is rude, a pocket index card is faster and less conspicuous than unlocking anything. Write it, pocket it, then shuffle the cards into your digital inbox at the next processing pass. If you want the card stock ready-made, the free Hipster PDA templates cover the usual sizes.

One rule holds the whole thing together: everything from every device lands in the same inbox before it is processed. Email, voice notes, photographed scraps, index cards, the half-sentence you typed on the phone. Two inboxes means two systems and no trust.

A weekly review that keeps flexible hours honest

The weekly review is the first thing people drop and the thing a hybrid working GTD system needs most. Pick a slot and defend it. Friday late afternoon suits most office patterns, because you are finishing anyway. Sunday evening works better if your week starts hot and Monday 9am is already a meeting. Put it in the calendar as a recurring appointment and treat it as a meeting with yourself that you do not move for anyone below director level.

Budget 45 to 60 minutes and work through this:

• Empty every inbox: paper, notes app, voice memos, email, chat saves.
• Re-read the project list and confirm each live project has one defined next action.
• Check each context list is still actionable from where you will be, and that there is at least one action you can do from Monday’s location.
• Scan two weeks of calendar forward for travel, childcare clashes and anchor-day collisions.
• Review waiting-for items and decide which get chased on the next office day.

Email deserves its own pass. In hybrid roles it is the most common second to-do list: whatever room you are in, the inbox sets the agenda. Process it into actions, reference and waiting-for in one or two defined passes a day, and leave the rest alone. If your email tool recently changed under you, the rebuilding a GTD inbox after a shutdown write-up goes through the swap in detail.

You will know within two weeks whether this is holding. The tells: ideas you captured on Tuesday are still in the system on Friday, Monday morning does not start with a scramble, and you rarely hit an action you cannot do because you are in the wrong place.

Keeping colleagues and managers on side without performing work

Flexibility gets withdrawn quietly, not formally. It erodes when people cannot see what you are doing and fill the gap with assumptions. The answer is not performative presence or green dots on a chat tool.

Publish the shape of your week, not a minute-by-minute diary. Office days, focus mornings, the window you do not take calls in. That is enough for colleagues to plan around. Use your waiting-for list to chase people on a schedule rather than firing status pings across chat, which costs them attention and buys you nothing.

Report output, not activity. Presence is a poor proxy for work when nobody can see you, so give your manager finished things: decisions made, deliverables sent, the next actions you closed this fortnight. This site has a fuller argument on measuring productivity by output rather than activity, and the habit of keeping that record is worth more than any dashboard.

The UK backdrop matters for the paperwork. Since 6 April 2024, employees can request flexible working from the first day of employment, make two requests in any 12-month period, and must receive a decision within two months; the current rules are set out on the GOV.UK flexible working pages. Check the detail before you apply, as guidance does get updated. The practical point: if you may need to make a request, or defend one at review, a running record of what you shipped on home days is the evidence, and nobody can reconstruct it after the fact.

If flexibility is reduced anyway, most of the system survives. Energy-based contexts still beat location-based ones on a fixed five-day week, the agenda lists still save meetings, and the weekly review is the part you keep regardless.

Mistakes that quietly wreck a flexible working setup

Rebuilding everything in a new app every time the system wobbles is the big one. A wobble almost always means a missed review, not a missing feature, and a fresh app costs you a week and solves nothing. Migration has a real price too; the question of what an export actually loses is worth reading before you move anything.

Letting a chat tool, email and three notes apps each behave like an inbox is the second. Pick one, route everything there.

Over-engineering comes third: nested tags, saved filters, a dashboard that needs feeding. If maintenance costs more than the work it organises, delete the structure.

The last one is specific to compressed hours. A nine-day fortnight is not a normal fortnight with hours shaved off each task. Keep the same commitment load and you will simply work later on the nine days. Cut or renegotiate one project per cycle instead. That decision belongs in the weekly review, where you can see the whole shape at once.

Frequently Asked Questions

What does a flexible working productivity system actually include?

Five parts: a written map of your week by block type, context lists based on place and energy, one capture tool fast enough to use with your phone locked, a single inbox everything routes into, and a fixed weekly review. Tools come last and matter least. The map and the review do the heavy lifting.

How do GTD contexts work when your week is split between home and the office?

Drop @work and @home, because both are now ambiguous. Use @deep, @calls, @errands, @low energy, @online and one @agenda list per colleague, so every list you open contains things you can actually do from where you are. Anchor office days are for emptying agenda and errand lists; home mornings are for deep work.

Which tools suit capture on the move, and does paper still earn a place?

Any tool that gets an idea saved in a few seconds from a locked phone qualifies, which rules out most apps that open on a dashboard. Paper still earns its place: an index card in a pocket beats unlocking a phone on a crowded train or during a school pick-up, and the cards get processed into your digital inbox at the next pass.

How often should I review the system if my hours change week to week?

Weekly, at a fixed point in your pattern rather than a fixed day of the month. Forty-five to sixty minutes is typical once you are practised. If your hours genuinely change every week, review on the last working day of each week whenever that falls, and add a ten-minute check on Sunday evening to confirm Monday’s location matches Monday’s list.

How do I show my manager that flexible working is producing results?

Keep a running record of completed next actions and finished deliverables, then report those rather than hours or availability. Summarise fortnightly in a few lines: shipped, decided, waiting on others. If you need to make or defend a flexible working request, that record is the evidence you will wish you had started keeping six months earlier.

The post Flexible Working Productivity System: A GTD Setup appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The right to switch off is a capture problem dressed up as a legal one. Here is the honest position, up front: there is no statutory right to switch off in the UK today, the version that was proposed was never going to ban your boss from messaging you at 10pm, and even if a code of practice lands next year, it will not stop you lying awake remembering the thing you promised on Thursday. So this piece does two jobs. It states the legal position plainly, without the HR-consultancy hedging, and then builds the personal and team system that actually produces a switched-off evening: a shutdown routine, a weekly review, a response-time agreement and a short list of tools that help rather than quietly making it worse.

Where the Right to Switch Off Actually Stands in the UK

No UK employee currently has a legal right to disconnect. If a page tells you otherwise, it is describing a manifesto commitment, not a rule you can cite in a grievance.

The route the proposal took matters, because it tells you what protection would actually look like. Labour’s Plan to Make Work Pay (2024) set out a right to switch off delivered through a statutory code of practice, explicitly modelled on Ireland and Belgium, rather than through a hard prohibition on out-of-hours contact. Codes of practice work by tribunal weight: ignore one and it can be used in evidence against you, which is how Ireland’s Code of Practice on the Right to Disconnect (in force since 2021) functions in Workplace Relations Commission proceedings. France requires employers above a certain size to negotiate on digital disconnection; Belgium requires larger employers to agree deconnection arrangements. None of these models makes an evening message unlawful. They make a pattern of them evidence of something.

The switch-off right was not in the Employment Rights Bill when it was introduced in October 2024, and reporting at the time indicated it had been set aside for later work on a code. The Bill and its accompanying consultations have moved since, so check the current status on legislation.gov.uk and the government’s own pages before you rely on any of it.

A UK code, if it arrives, was expected to cover three things: no routine expectation of work outside normal hours, no detriment for declining out-of-hours contact, and contact windows agreed employer by employer rather than imposed nationally. Useful, eventually. Your Tuesday evening is happening now.

What UK Law Already Gives You Today

You have more than people assume, just not the thing you want. The Working Time Regulations 1998 give you an average working week capped at 48 hours (averaged over 17 weeks, and you can sign an individual opt-out, which many UK contracts ask for as a matter of course), 11 consecutive hours of daily rest, 24 hours of uninterrupted weekly rest, and a 20-minute unpaid break on a shift longer than six hours.

Read the 11-hour rule again, because it is the one with teeth. Answer a message at 23:30 and start at 08:00 and your employer has a rest problem, not a politeness problem.

Alongside that, health and safety law requires employers to assess and manage risks to health, and work-related stress is in scope. The HSE’s Management Standards for work-related stress cover demands, control and support, which is exactly the territory an always-on culture sits in. Acas guidance is the practical route for raising out-of-hours expectations informally before anything becomes a formal grievance, and informal is where almost all of these are resolved.

Two more places existing law bites. If unpaid out-of-hours work drags your total hours up enough that your pay divided by hours falls below the National Minimum Wage, that is a minimum wage issue regardless of what anyone agreed. And on-call arrangements that repeatedly interrupt rest can breach the daily and weekly rest entitlements, with compensatory rest owed.

What none of it covers: a single “quick question”on Teams at 22:00 from a manager who genuinely does not expect a reply. Technically nothing is breached. Practically, you have just reopened work.

Why You Still Cannot Switch Off at 9pm

Here is the part the policy articles never reach. People do not fail to switch off because their phone buzzed. They fail because they are carrying commitments their brain has not been able to hand to anything it trusts.

David Allen’s argument in Getting Things Done is that the mind keeps renegotiating any agreement it has made with itself and not externalised. It has no sense of time or priority, so it raises the thing at 03:00 with exactly the same urgency it would at 11:00. Shutting the laptop changes nothing about that, because the laptop was never where the loop was stored.

You know the symptoms. The 3am wake-up about a half-promised invoice. Sunday afternoon dread with no specific content. The shower where you suddenly remember you told a client you would check something by Friday. Those are all the same event: an open loop with nowhere to live.

Which is why a notification ban on its own fails, and why “just set better boundaries”stalls. The thought still arrives. With no trusted place to put it, your only options are to hold it in your head (rumination) or open the work app to deal with it (re-engagement). Ban the app and you have simply moved the rumination from the inbox to the pillow.

The trade-off nobody sells you: switching off costs a small amount of daily admin, done at a specific moment. Ten to fifteen minutes, before you log off, not after dinner.

A 15-Minute Shutdown Routine That Closes Open Loops

Do it in this order, every working day.

1. Sweep every inbox into one list. Email, chat mentions, your notebook, the pile on the desk, the photos you took of a whiteboard, the voice note you left yourself. Everything goes to one place. One inbox, not four.
2. Decide the next physical action on anything that would otherwise nag. This is the step people skip, and skipping it is why their shutdown routine does not work.
3. Park what is not this week. A someday/maybe list exists so your brain stops auditing twelve projects you are not touching until March.
4. Write the handover. Three lines for colleagues: what landed, what is blocked, who is covering what. Name a person for genuine emergencies.

On step two, language does the work. “Pricing review”is a thought generator; your mind has to re-plan it every time it surfaces. “Email Sam the two pricing options”is finished thinking. Nothing left to work out, so nothing left to raise at 9pm. Verb first, specific object, somewhere real to do it.

The handover matters more than it looks. If nobody is named for emergencies, the duty defaults silently to whoever answers, which is usually you, which is how ambient availability becomes permanent.

Sanity check for the whole routine: when a work thought arrives at 21:00, does it have an obvious home you can reach in under five seconds without unlocking a work device? If yes, the routine is working. If you find yourself opening Outlook “just to check”, it is not.

The Weekly Review Is the Real Off Switch

A weekly review beats any out-of-hours policy, and it is not close. An unreviewed system does not sit quietly; it runs a low-grade, never-finished review across your entire weekend instead. That half-review is precisely the state a switch-off code is meant to prevent, and no employer policy can reach it.

Sixty to ninety minutes covers it: inbox to empty, project list made current (add what started, delete what died), waiting-fors chased or dropped, calendar two weeks back and four weeks forward. Back, because last fortnight leaves loose ends. Forward, because next month is where the panic comes from.

Run it Friday afternoon, not Monday morning. Monday reviews mean you spend the weekend as the storage device. Friday reviews mean the loop closes before the weekend starts, which is the entire point. If Friday afternoon is sacred client time, Thursday late works; Monday does not.

The common failure is treating the review as a tidy-up. Renaming lists, recolouring tags, admiring the structure. A review is a decision session: what gets dropped, what gets renegotiated with an actual human, what you are deliberately not doing until the quarter turns. If nothing was dropped, you tidied. Custom views help here, and a well-built set of OmniFocus perspectives cuts the mechanical part of the review so you spend the time deciding instead of scrolling.

Agreements, Not Apps: Setting Out-of-Hours Expectations

Write a response-time agreement, not a contact ban. Contact bans fail the first time someone needs to send a thought at 22:00 so they do not lose it, and then the whole policy is a dead letter.

A worked version you can copy into a team channel:

• Messages may be sent at any time. Sending is not asking.
• Replies are expected between 09:00 and 17:30 on the next working day.
• A phone call means genuine urgency. Nothing else does.
• One named on-call person per week, with a written escalation route.
• Anyone writing late uses scheduled send.

Separate real on-call from ambient availability. Real on-call has a rota, an escalation path and either payment or time back. Ambient availability has none of those, which is why it spreads: it is free to the organisation and expensive to you.

Raising it without sounding difficult is mostly a framing problem. Bring a proposal and a measure, not a complaint. “I will commit to these three deliverables by Thursday, and reply to anything non-urgent by 10:00 the next working day”is a better conversation than “I would like fewer evening messages”. It also puts the discussion where it belongs, on output delivered rather than activity visible online.

If you manage people, your send times set the norm no matter what the policy says. Nobody believes the document; they believe the timestamp. Use scheduled send, and say out loud, in writing, that no reply is expected before morning. Managers who reward responsiveness rather than output manufacture out-of-hours work that no code of practice will ever fix.

Tools That Help You Disconnect, and Ones That Quietly Make It Worse

Judge any off-hours capture tool on five jobs: time-to-captured, one trusted inbox, retrieval from half a memory, exit cost, and whether it imposes a daily admin tax in tags, statuses and tidying. If capture takes longer than about five seconds, you will stop doing it under pressure, which is a practical working benchmark rather than an official rule. The under-five-second capture test is the whole game here.

The usual self-inflicted wound is two inboxes. You install a work-only capture app so evening thoughts stay “contained”, and now there is a work inbox at home that you check to make sure nothing is in it. One inbox, personal, always.

Capturing on a work phone defeats the purpose entirely. You open up it to note six words and you are looking at nine unread messages, two of which look like they matter. Twenty minutes gone. For a shortlist of apps that handle a single trusted inbox without the tag maintenance, see the note-taking app comparison.

Which is why paper still earns its place. An index card and a pencil by the bed, or in a back pocket, catches the 23:00 thought without unlocking anything at all. It feeds the main inbox the next morning in about ninety seconds. The hPDA templates are built for exactly this, and the exit cost is zero.

Settings worth five minutes tonight: turn on scheduled send in Outlook or Gmail, set a notification schedule so work apps go quiet at a fixed hour, drag Teams and Slack off your home screen (the icon is the trigger, not the badge), and if you use separate work and personal profiles on one device, write down when the work profile is allowed to open. “When I decide”is not a rule.

Whatever happens to the right to switch off in Parliament, the evening is won or lost in the fifteen minutes before you log off.

Frequently Asked Questions

Is there a legal right to switch off in the UK?

No. There is no statutory right to switch off or right to disconnect in UK law at the time of writing. Labour’s Plan to Make Work Pay (2024) proposed one delivered through a statutory code of practice, modelled on Ireland and Belgium, but that is a proposal rather than an entitlement. Check the current status of the Employment Rights Bill and any accompanying code before relying on it.

Can my employer require me to answer emails outside my working hours?

Generally your obligations are set by your contract, so if it specifies your hours, routine unpaid evening work sits outside them. Where it bites legally is through the Working Time Regulations 1998 (11 hours’ daily rest, the 48-hour average week) or through National Minimum Wage rules if unpaid extra hours push your effective hourly pay below the minimum. For a one-off genuine emergency, most contracts allow for reasonable flexibility.

What is the difference between the right to switch off and the right to disconnect?

Practically none. “Right to disconnect”is the term used in Ireland, France and Belgium and in EU-level debate; “right to switch off”is the phrasing used in recent UK policy documents. Both describe protection against an expectation of routine work outside normal hours rather than an outright ban on out-of-hours messages.

Do the Working Time Regulations stop out-of-hours contact?

Not directly. They regulate rest and working time, so they catch patterns of evening work that break the 11-hour daily rest period, the 24-hour weekly rest or the 48-hour average week. A single late message that does not interrupt rest breaches nothing. Repeated late work that cuts your rest short is a different conversation.

How do I stop thinking about work in the evening when the messages have stopped?

Capture and decide, rather than trying to suppress the thought. Run a ten to fifteen minute shutdown that empties every inbox and defines the next physical action on anything live, hold a sixty to ninety minute review on Friday rather than Monday, and keep one personal capture inbox you can reach in seconds without opening a work device. The thought will still arrive; it just stops needing you to do anything about it.

The post Right to Switch Off: How to Do It Without a Law appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

Obsidian vs Notion comes down to this: the better note tool for GTD is the one that gets a loop out of your head in a few seconds, shows you every one of them in a ten-minute weekly review, and lets you walk away in three years with your writing intact. That is the honest test, and it is not the test either vendor’s feature page is designed to pass.

So here is the conclusion, up front. Neither Obsidian nor Notion is a next-action list out of the box, and trying to make either one into your action system is where most GTD rebuilds quietly fail. Obsidian wins retrieval and exit cost. Notion wins structure, sharing and the weekly review view. Most people reading this will end up running both, with next actions somewhere else entirely.

The real difference: plain files on your disk vs blocks in a hosted database

Obsidian is a text editor sitting on a folder. Your notes are Markdown files with a.md extension, stored wherever you put them, openable in TextEdit, Notepad, VS Code or anything else on the machine. Notion stores blocks in its own hosted database, which you reach through the app, the browser or the API. You do not have a folder of Notion files. You have an account.

That single architectural choice decides almost everything else in Obsidian vs Notion. Local files mean search runs on your disk instead of over a network, which is why Obsidian’s search feels instant and Notion’s sometimes does not. Hosted blocks mean genuine multiplayer editing, granular permissions and database relations, none of which a folder of text files can fake. Offline behaviour, mobile cold start, sharing, and what survives when you stop paying all trace back to the same split.

Table stakes, stated plainly so we can move on: both do internal links, nested pages, web clipping, decent iOS and Android apps, and both have shipped AI features. Both are perfectly capable of holding your reference material. The arguments about dark mode and template galleries are not worth your time.

The GTD framing matters more. A notes tool holds reference material and project support material. It is not automatically your list of next actions, and the two jobs have opposite requirements: reference wants depth and richness, context lists want a view you can trust at a glance without reading anything. If you have already worked through our tested picks for a GTD note taking app, this piece goes deeper on the two that generate the most arguments.

Time-to-captured: how fast an idea gets out of your head

Job one: time to captured. Run the test on the vault or workspace you actually have, with the notes, attachments and half-finished databases already in it, not a clean install. A new empty vault is fast in every app ever made.

The test: phone locked in your pocket. Take it out, get a sentence of text saved somewhere you will see it again, and count the steps. If it needs more than a handful of taps and a few seconds, you will stop doing it when you are busy, and the ideas you lose will be the ones you had walking between meetings.

Obsidian has one well-known weakness here: cold start on a large vault. The mobile app indexes your files, and the bigger the vault and the more plugins you load, the longer you stare at the splash screen. The fix is to never open the app to capture. On iOS, build a Shortcut that appends a line to a single Inbox.md (or to today’s daily note) and put it on the lock screen or in the Action button. Text goes in, the app stays closed, the file is waiting when you next sit down. Quick Add plugin does the same job on desktop.

Notion wants a network. Capture into a synced workspace while you are on a train through the Chilterns and you get the spinning state that makes people distrust the inbox entirely. Notion’s quick-add widget and share-sheet extension are genuinely better than opening the full workspace, because they skip the sidebar and drop straight into a database row. Still slower than appending a line to a text file, and still dependent on getting a signal eventually.

Both lose to paper. A card in your back pocket needs no open up, no face scan and no sync, and a biro works in the rain. Keeping a paper capture layer is not an admission that your software failed, it is just acknowledging the real test condition: standing on a platform, hands full, phone locked. Our printable hPDA templates exist for exactly that gap, and there is a longer treatment of the speed problem in the piece on capturing an idea in under five seconds.

One trusted inbox: where open loops land and get processed

Trusted, in GTD terms, means one place. Everything arrives there, you empty it on a schedule, and nothing is hiding in a second workspace you built with enthusiasm in March and abandoned in April.

Notion makes a decent inbox if you keep it to one database with a status property and a relation to projects, then process into filtered views. The failure mode is specific and very common: five dashboards, each with a little inbox section, each holding three stray loops. The workspace looks impressive. Nothing is trusted.

Obsidian’s version is an Inbox.md or a daily notes folder, processed into project notes during the weekly review. The failure mode here is the opposite sort of mess: captures scattered across whichever file happened to be open, with no review trigger to collect them. Obsidian will not nag you. It has no concept of a stale item.

On email and web capture, Notion is ahead if you want things arriving automatically, because it accepts clipped pages, file attachments and forwarded material into the same database, and the API means automations can create rows. Obsidian clips to Markdown cleanly enough, but attachments land as files in your vault and you have to decide where. If your inbox problem started with email in the first place, the rebuild advice in rebuilding a GTD inbox after the Notion Mail shutdown applies regardless of which of these two you pick.

Finding something from half a memory, weeks later

Here is the retrieval test that matters. You remember two words and roughly when. You do not remember the title, the folder, the parent page or what you called the database. Go.

Obsidian is strong here and it is not close. Full-text search runs locally and returns as fast as you can type. Backlinks and unlinked mentions surface connections you never made on purpose. Best of all, because the notes are files, Spotlight, grep, ripgrep and any editor on the machine search the same content without Obsidian running at all. For a reference archive you expect to open in ten years, that is the whole argument.

Notion wins the other half of retrieval, the half Obsidian handles badly. When the thing you remember is a property rather than a phrase, a filtered database view answers in one click: every client project at “awaiting feedback”, every meeting note tagged to one account, everything created last quarter with an empty owner field. Relations and rollups give you structured metadata that no text search can guess at.

Where each one lets you down: Obsidian’s graph view is decoration, not retrieval, and anyone who tells you they find notes by rotating a constellation of dots is performing. Notion’s search degrades as the workspace grows and the nesting deepens, and deeply buried pages in a shared workspace can be genuinely hard to surface when you cannot remember the parent.

Exit cost: what actually survives when you leave

Notion’s export is the quiet trap. Markdown and CSV come out, and the words and images are fine. What does not travel as working structure: relations, rollups, formula outputs, saved database views, synced blocks and comments. You get the writing. You rebuild the system. Everyone underestimates which half took the effort, and the detail is worth reading in full in what a Notion export actually loses.

Obsidian’s exit cost on files is close to zero, because the files were never inside anything. Copy the folder. Done. But there is lock-in people miss, and it is the kind you built yourself: Dataview queries, Tasks plugin syntax, Kanban boards and.canvas files render as intended in Obsidian and as inert text or JSON anywhere else. A vault stuffed with clever queries is portable in the way a car with no engine is drivable.

Plan a move of a few thousand notes like this. The export itself takes minutes. Then budget hours, not minutes, for re-linking internal references, checking image and attachment paths and spot-checking a sample of pages, plus proper rebuild time for the handful of databases that carried relations and rollups. Roughly ten per cent of a mature workspace tends to need hands-on work. Treat that as a planning estimate rather than a measured rule, and scale it up if your workspace leans heavily on formulas. Anyone who has done an Evernote migration with the real costs counted will recognise the shape of it.

Lower your exit cost in whichever tool you choose: keep the structure flat, keep text as text, keep properties few and simple, and schedule an export you have actually opened and looked at. An untested backup is a feeling, not a file.

The daily admin tax: plugin maintenance vs database upkeep

Obsidian’s tax is plugins. Community plugins update on their own schedules, an app update can break one, and the dashboard that only you understand is the dashboard only you can repair. Sync across Mac, Windows, iPhone and iPad needs a decision too: paid Obsidian Sync, iCloud, or a third-party folder service with the conflict files that come with it.

Notion’s tax is upkeep of a different sort. Template drift, databases nobody has written to since last spring, permissions to tidy when a freelancer leaves, and the strong gravitational pull towards building the workspace instead of doing the work. Notion is unusually good at making procrastination look like progress.

The weekly review is the honest test, not the feature list. Sit down and try to see every open loop in one view within ten minutes. No fixing a broken query first. No “I just need to add a status to these”. If you cannot do it, the system has become the project. Notion passes this test more often, because filtered database views are its native strength. Obsidian can match it, but only once you have set up Dataview or Tasks and kept them working, and that maintenance is a real cost you should price in before you commit.

How to choose between Obsidian and Notion (and when to run both)

Choose Obsidian if your material is mostly personal reference and research, you want it fast and offline, and you care about owning the files. Obsidian is free for personal use, with Sync and Publish sold as paid add-ons and a separate commercial licence required for business use. Prices are set in US dollars and change, so confirm on Obsidian’s pricing page before you budget.

Choose Notion if the material is shared, structured and tracked with other people. The free personal plan covers a surprising amount for one person, with paid per-user tiers above it; again, check Notion’s current pricing rather than trusting a figure in any article, including this one.

The hybrid that holds up in practice is boring and it works. Notion for anything a client or colleague opens: shared briefs, trackers, meeting notes. Obsidian on iCloud or Dropbox for the personal reference archive you expect to keep for a decade. Next actions in a dedicated task app, organised by context, which is where OmniFocus, Todoist or Things earn their keep. The reason is simple: a context list has to be trustworthy at a glance, and neither of these two gives you that without you building it. If you want a working example of what a list tool does that a notes tool cannot, the custom perspectives walkthrough shows the difference in practice.

Four questions, then decide:

• How many people touch this material? More than you means Notion.
• Does it need to work on a train with no signal? That means Obsidian.
• Is the data structured, with statuses and relationships that need querying? Notion.
• How fast could you get out with your writing intact? Obsidian, by a wide margin.

Fewer tools, wired together properly, beat a beautiful shelf of software you never open. Pick on the two jobs you do most, not on the comparison table.

Frequently Asked Questions

Is Obsidian or Notion better for GTD?

Neither is a complete GTD system, because neither gives you trustworthy context lists by default. Notion is better for the weekly review and anything shared, since filtered views can show every open loop in one place. Obsidian is better as a personal reference archive, thanks to instant local search and files you own outright.

Can you use Obsidian and Notion together without duplicating work?

Yes, if you split them by audience rather than by topic. Anything a client or colleague opens lives in Notion; your private reference, research and drafts live in the Obsidian vault. The rule that stops duplication is having one home per item and linking to it, instead of copying the text across.

What does Obsidian or Notion cost for a single user in the UK?

Both have a free option that a single user can live on. Obsidian is free for personal use, with Sync and Publish as paid subscriptions and a commercial licence needed for business use; Notion’s free personal plan is generous, with per-user paid tiers above it. Both price in US dollars and revise their tiers, so check each vendor’s pricing page at the time you buy.

How much of a Notion workspace survives an export to Obsidian?

The writing mostly survives. Pages come out as Markdown, databases as CSV, and images and files come with them, though paths often need fixing. Relations, rollups, formula results, saved views, synced blocks and comments do not arrive as working structure, so expect to rebuild those by hand.

Does Obsidian work offline better than Notion?

Yes, and the gap is not subtle. Obsidian reads and writes local files, so editing and search work with no connection at all, and sync catches up later. Notion has improved offline access, but it is still a hosted database at heart, so a flaky connection shows up as the one thing an inbox cannot afford: doubt about whether your capture saved.

The post Obsidian vs Notion: Which Fits a GTD Workflow? appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

ChatGPT Pages are a document surface, not a website builder, and getting that straight in the first thirty seconds saves most people a wasted afternoon. A page is an editable document that sits alongside your chats: notes, a plan, research, a shared reference you keep coming back to. ChatGPT Sites is the other thing, the one that builds and hosts a website, web app or small game from a prompt. Different problems entirely. The official pages explain the buttons and leave the conflation intact, which is why so much of the search traffic for this term arrives confused.

The honest conclusion, up front: Pages can carry real weight in a GTD system, but only on the reference side. They make decent project support material and a decent place to run a planning session. They make a poor inbox and a worse next-action list, mostly because of where you can and cannot create one. This piece puts Pages through the five jobs any notes tool has to do, then gives you a setup that does not collapse in month two.

What ChatGPT Pages Are (And What They Are Not)

Think of a page as a working document the assistant can read, draft and revise with you, held outside the scroll of a conversation. You can type into it yourself. You can ask ChatGPT to restructure a section, pull out the open questions, or turn twelve rambling paragraphs into a table. The result stays put instead of disappearing four hundred messages up a chat thread.

That persistence is the whole point. Chats are a transcript. Pages are an artefact.

Pages versus Sites, settled

Sites generates and publishes something for other people to visit. Pages produces a document for you (and anyone you share it with) to read and edit. If your search was really “how do I get ChatGPT to build me a landing page”, you want Sites and you can stop reading here. If you want somewhere to keep the spec, the quotes, the decisions and the half-formed plan for a project you are actually running, Pages is the right surface.

Where a page actually lives

Pages sit in the same account furniture as everything else in ChatGPT: your chat history, Projects for grouping related conversations and files, Spaces where shared work happens, and Canvas as the side-by-side editing view you may already have used for drafting. The practical question is not “what is it called”but “who can see it and will I find it in six weeks”. Before you commit anything you care about, open the sharing controls once and read them properly. Features move quickly here, so check the current behaviour in OpenAI’s own help centre rather than trusting a blog post, including this one.

The platform caveat that decides everything

At the time of writing, creating and editing pages is a web and desktop experience. On mobile you can find them, read them and share them. That is not a small footnote. It is the single fact that determines where Pages can sit in your system, and we will come back to it in about four hundred words.

The Five Jobs Any GTD Notes Tool Has to Do

Feature lists are useless for this decision. These five jobs are not.

1. Time-to-captured. Seconds and taps between the thought arriving and the text being stored, measured on the device actually in your hand. Phone locked, screen off, walking. Under five seconds is a practical working benchmark rather than an official rule, and it holds up: past that, people quietly stop capturing under pressure.
2. One trusted inbox. Everything lands in one place. The second you have two queues, you trust neither, and the weekly review turns into archaeology.
3. Retrieval from half a memory. You remember two words and roughly the month. Not the title, never the title. Can you still find it?
4. Exit cost. How much work it takes to leave, and what does not survive the journey.
5. No daily admin tax. How much tagging, status-setting and tidying the tool demands each day just to stay useful.

Pages passes three of those comfortably, struggles with one, and fails one outright. Retrieval is reasonable, because you can search and because the assistant will find a page from a vague description better than most keyword searches manage. The admin tax is genuinely low: no required tags, no board columns, no properties to maintain. Exit cost is the open question. Time-to-captured is the failure, and it is the one that matters most, because GTD collapses at capture long before it collapses at filing.

Where ChatGPT Pages Genuinely Earn Their Place

Project support material, in the proper GTD sense

David Allen draws a hard line between action lists and project support material: the specs, quotes, measurements, meeting notes, decisions and links that are not things to do but must be to hand when you do them. Pages sits naturally on the support side.

A home extension, say. One page holds the purpose, the outcome you are after, three builders’ quotes, the measurements, and the notes from every site meeting. The three live next actions (chase the party wall letter, book the surveyor, email the planning query) live in your task manager under phone and email contexts, where you will see them in a queue. The page is what you open when you sit down to work the project. It is not what tells you what to do next.

Running the natural planning model on one page

The five phases of David Allen’s natural planning model (purpose and principles, outcome vision, brainstorming, organising, next actions) map onto a single page almost too neatly. Write the purpose yourself. Dictate or type the vision. Then use the assistant for the brainstorm phase, where volume beats quality and your own judgement is the bottleneck anyway. Ask it to group the mess into themes. Pull the next actions out by hand, because that is the bit requiring an opinion about your actual week.

Twenty minutes, one page, a project that is no longer vague. Then the actions leave.

Turning noise into a short reference note during processing

Forty-minute client call. You take six lines on an index card while listening, because typing during a call makes you a worse listener. During processing, four minutes: paste the card’s contents in, ask for a page structured as Decisions, Open Questions and Reference, edit the wording so it is actually true, then move the two commitments you made onto the right context lists. The thread is closed. Nothing is left sitting in an inbox pretending to be a task.

That workflow sits alongside the other jobs ChatGPT does well inside a GTD system, and it shares their limit: the assistant is good at shaping material you already have, poor at deciding what matters.

Reusable checklists and start-up templates

Project start-up checklists, client onboarding steps, the pre-launch list you rebuild badly every time. Ask for a pre-filled draft, then edit by hand until it reflects how you really work. Checklists are where generated first drafts earn their keep, because the cost of a missing item is high and the cost of an irrelevant one is deleting a line.

Where Pages Break a GTD System (And What Breaks First)

Capture breaks first

You cannot create a page from a locked phone in under five seconds. With creation restricted to web and desktop, Pages cannot be your ubiquitous capture tool, and anything that cannot catch a thought at a bus stop cannot be your inbox. Keep a five-second phone inbox (voice note, widget, a single text file, whatever you will actually use) and promote items into Pages during processing. If you need to build that layer, start with capture under five seconds using an AI assistant, then let Pages take the material afterwards.

Action management is not there

No contexts. No due dates, no defer dates, no single scannable list. A next action buried in the third paragraph of a page is invisible on a Tuesday afternoon with nine minutes free. Keep your actions where you can filter them, whether that is a set of OmniFocus perspectives or a plain list per context. Two action systems means you trust neither.

A document the assistant can rewrite is not a stable record

This one catches people out. Ask for a tidy-up and the agreed price can come back paraphrased, the date softened, the caveat gone. For anything recording a decision, a price, a commitment or a deadline, paste the agreed wording in verbatim, mark it as fixed, and do not let it near a “make this clearer”prompt. Better still, keep that line in your task manager or your email archive, where nothing regenerates it.

Review friction

Pages scattered across chats, Projects and Spaces turn a weekly review into a search session. A 20 to 30 minute review should be a scan, not an investigation. If you have to go hunting, you will skip it, and a skipped review is how the whole system quietly stops being trusted.

A Working Setup: Pages for Reference, Lists Elsewhere

The split that holds:

• Phone: one capture tool, five seconds, no decisions required.
• Task manager: every next action, by context, in a list you can scan.
• Pages: one page per active project, plus reference material.

Name pages so they sort and search: area, project, outcome. “Home, Extension, Planning approved by March”. Put a single next-action line at the top that mirrors whatever your task manager says, and accept it will sometimes be a day stale. It is a signpost, not the source of truth.

The processing habit is the one that keeps this honest: anything actionable leaves the page in the same sitting. Same sitting, every time. Let actions accumulate in paragraphs and the page becomes a to-do graveyard that you stop opening because opening it feels bad.

If you capture on paper, the flow runs one way. Index cards or notebook feed the page during processing, never the reverse. A Hipster PDA and a web-only document tool actually pair well, because the paper covers exactly the gap Pages leaves: capture away from a keyboard.

In the weekly review, touch three things. Project pages, looking only for outcomes with no next action. One someday/maybe page. Nothing else. Resist opening the chat history. That is where twenty-five minutes becomes an hour and nothing gets decided.

Exit Cost, Lock-In and the Mirror-Out Habit

Run the exit test before you migrate an archive, not after. Take a 2,000-word page with two tables and ten links, copy it into a plain.md file, and count what survived: headings, table structure, link targets, images, nested lists. Fifteen minutes of work that tells you more than any feature comparison.

Chat-native documents tend to lose the surrounding material rather than the body text: comments, version history, the embedded chat context, and the link back to the conversation that produced the page. That context is frequently the part you wanted. Anyone who has run a Notion export and read the output properly knows the pattern, and the lesson transfers.

So mirror out. Keep the authoritative copy of anything you would be upset to lose in plain files or your existing notes app, and treat Pages as the working surface. One account change, one pricing shift, one feature retirement, and your reference layer is still on your own disk.

Pages is the wrong choice outright for three things: client deliverables, anything with a retention or compliance requirement, and shared team documentation that needs real permissions and an audit trail. Use a proper document system for those.

Should You Move Your Notes Into ChatGPT Pages? A Short Decision Checklist

Six questions. Answer them honestly rather than aspirationally.

1. Do you capture mostly on mobile? If yes, Pages is a reference layer only, permanently.
2. Does anyone else need to read these notes, and do they need permissions?
3. Would losing comments and version history on export actually hurt?
4. Do your notes record prices, dates or commitments that must not drift?
5. Are you at a desk when you do your weekly review?
6. Does your current system already pass the five jobs?

On that last one: if it does, stay put. Migration cost is real and tool-switching is not progress.

Compared with the usual alternatives, judged on retrieval and exit cost rather than feature counts: Obsidian wins exit cost outright because the files are already Markdown on your disk, and loses on effortless cross-device sync unless you pay or configure it. Notion wins structure and sharing, and its export is the thing to test first. A dedicated AI note taking app built for notes usually beats Pages on mobile capture, which is the job Pages cannot do. If you are leaving an old system behind, the real migration costs of the Evernote alternatives are worth reading before you move a single note.

Run a two-week trial on one live project. One page, real material, your actual weekly review. If at the end of a fortnight you are opening it during work sessions without being reminded to, keep it. If not, you have lost two weeks instead of an archive.

Frequently Asked Questions

What are ChatGPT Pages used for?

Pages give you an editable document that lives alongside your chats, for notes, plans, research and reference you return to rather than a one-off conversation. You can write in it yourself or ask ChatGPT to draft and restructure sections. In a GTD system the natural fit is project support material: specs, quotes, meeting notes and decisions you need to hand while working a project.

Are ChatGPT Pages the same as ChatGPT Sites?

No, and the two get confused constantly. Sites builds and hosts websites, web apps and small games from a prompt, so other people can visit what you made. Pages is a document surface for you and anyone you share it with. Completely different jobs.

Can you create and edit ChatGPT Pages on mobile?

At the time of writing, creating and editing is a web and desktop experience, with mobile limited to finding, reading and sharing. Check OpenAI’s current help documentation, because this is exactly the kind of limitation that changes. Until it does, keep a separate five-second capture tool on your phone and move material into Pages when you process.

Can you export ChatGPT Pages, and what gets lost?

You can copy content out to plain text or Markdown, and body text generally survives fine. What tends not to survive in any chat-native document is comments, version history, embedded conversation context and the link back to the chat that produced the page. Test one long page with tables and links before you move anything you care about.

Can ChatGPT Pages replace Notion, Obsidian or Evernote for notes?

For the reference layer of a single-person system, possibly. As a full replacement, not yet, mainly because of the mobile create gap and the absence of permissions, retention controls and an audit trail. Keep the authoritative copy in plain files or your existing notes app, and use ChatGPT Pages as the working surface rather than the vault.

The post ChatGPT Pages Explained: Where They Fit in GTD appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.