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.

The best self improvement books are the ones that survive contact with your inbox on a Tuesday afternoon. Everything else is reading, and reading is fine, but it is not change. This piece names seven books worth your time and, for each one, the single implementation step it demands: the next action, the calendar block, the card on your desk, the trigger you add to your weekly review. If a book on this list cannot produce at least one of those, it has no business being on it.

The honest conclusion, up front: two of the seven are parables you can finish in under an hour and are worth buying only if you are facing a change you did not choose, or need a values reset rather than tactics. One is a 500-page psychology book most people abandon. And the one that produces the most lasting change is the one nearly everybody reads halfway.

Why most self improvement books change nothing

Highlighting feels like progress. Your brain treats a yellow line through a good sentence roughly the way it treats a ticked box, which is the problem: you get the satisfaction without creating an open loop you ever have to close. A fortnight later you can remember the book was good and not a single thing you did differently because of it.

It helps to split the shelf in two. Idea books change how you see things. Method books change what you do on Monday morning. Both are legitimate, but mixing them at random stalls you, because an idea book read while your commitments are overflowing just adds a vague sense that you should be better, and a method book read when you have no direction at all gives you a beautifully organised list of things you do not care about.

The test applied here is deliberately narrow. Does the book generate a project with a defined outcome, a next action with a context, or a recurring trigger in your weekly review? If none of the three, it is entertainment. Good entertainment, sometimes. Still entertainment.

The seven below all pass, and all of them hold up to being reread, mind-mapped onto a single page and turned into a routine you are still running in month three.

The 7 picks and the habit each one builds

1. Getting Things Done, David Allen

The spine of the whole system: capture, clarify, organise, reflect, engage. Most readers get the first two. They do the big inbox sweep, they fall in love with the two-minute rule, they buy an app, and they stop. Six weeks later the lists have rotted.

The two chapters that actually produce lasting change are the natural planning model (chapter 3 in the editions on most shelves, titled around getting projects creatively under way) and the reviewing chapter that sets out the weekly review. Chapter numbering shifted slightly between the 2001 original and the 2015 revised edition, so check the contents page. On a reread, read those two first and skip the opening pitch entirely. The weekly review is the maintenance habit without which every other part of the method quietly degrades, and the natural planning model is the thing you use when a project is stuck and vague.

Best for

• Too many commitments and no trusted place to put them
• Anyone who has already tried three list apps and still feels behind

Skip it if

• Your problem is direction rather than volume
• You want a quick read: this is a manual, and it reads like one

2. Atomic Habits, James Clear

Clear’s useful contribution is habit stacking and environment design, and both sit early in the book (the chapters on starting a new habit and on environment mattering more than motivation). The rest is reinforcement. Rereading it twice is not the implementation step. Writing three stacks on an index card is.

A worked conversion, start to finish. On a card: “After I make the morning coffee, I process the inbox to zero.””After I close the laptop, I write tomorrow’s three actions.””After Friday lunch, I run the weekly review.”The card lives next to the keyboard, not in an app, and you look at it during the Friday review and mark which stacks actually ran. Two weeks of honest marks will tell you more than the book did. If you want a format for that, the Hipster PDA templates are deliberately crude and work fine.

Best for

• People who know what to do and do not do it consistently
• Rebuilding a routine after a holiday, a job change or a messy quarter

Skip it if

• You have already read two habit books this year
• You need to decide what matters, not how to repeat it

3. The War of Art, Steven Pressfield

Short, blunt and slightly aggressive about the fact that you are avoiding your own work. Pressfield calls the avoidance Resistance and spends the first section describing its behaviour with uncomfortable accuracy. The later material on the muse and the “higher area”loses a lot of readers, and that is fine; the first third is the part that works.

Use it as a reread rather than a read. When a project has been sitting at the same percentage for three weeks, forty minutes with this book plus one commitment (a start time, written down, for tomorrow) restarts more projects than another planning session will. That is the whole implementation: a time, a place, and the first physical action.

Best for

• Stalled creative or writing projects
• Freelancers who have stopped doing the unpaid work that generates paid work

Skip it if

• You want systems, templates or tactics
• Mystical framing irritates you more than it motivates you

4. Deep Work, Cal Newport

Published in 2016 and still the clearest argument for protecting long, uninterrupted blocks. It converts into a diary more readily than almost any other book here, which is why it earns its place among the books that change what you actually do rather than how you feel for a week.

The conversion, concretely: two 90-minute blocks booked in the calendar before Monday starts, a shutdown ritual at 17:30 that empties the inbox to a list and closes the laptop, and the next action phrased as “draft section 2 of the report, laptop offline”instead of “focus more”. The shutdown ritual appears at the end of Rule 1, in the section making the case for being lazy in the evening, and it is the part people quietly drop first.

The honest trade-off: if you work in a support role, a clinical rota or anything with a shared diary that other people fill, the 90-minute block is not available to you. Two 40-minute blocks before 10am is the version that survives. Newport does not really address that, and pretending otherwise sets you up to fail at his standard and blame yourself.

Best for

• Knowledge workers with some control over their calendar
• Anyone whose output is measured in finished thinking rather than replies

Skip it if

• Your diary is booked by other people and you cannot change that this quarter
• You already block time and the problem is what goes in the block

5. Who Moved My Cheese?, Spencer Johnson

A parable about mice, cheese and change, first published in 1998, readable in about 45 minutes. Anyone looking for a Who Moved My Cheese summary is usually trying to work out whether to bother, so here it is plainly: two mice adapt quickly when the cheese disappears, two little people argue about fairness and stay put, and the one who eventually moves finds new cheese. The frame is that the cost of waiting is usually higher than the cost of moving.

That is it. There is no method. As tactics it is worthless, and the condescension of the format puts some readers off within ten pages. But hand it to someone three weeks into a restructure consultation, or to a manager whose team has just been told their department is merging, and it does something no tactical book does: it makes movement feel normal rather than disloyal.

Best for

• Restructures, redundancy, forced career change
• Teams stuck arguing about a decision already made above them

Skip it if

• You want techniques, checklists or research
• Simple allegory reads as patronising to you

6. The Traveler’s Gift, Andy Andrews

Andrews’ 2002 novel sends a man who has lost everything to meet seven historical figures, each handing him one decision. It is sentimental and the dialogue creaks. The seven decisions, pulled out of the story, make a genuinely useful values exercise.

Treat it as input to the higher altitudes of your system rather than to your action lists. Read it, then spend twenty minutes writing what each decision would mean for your next two years, and park the output in your areas of focus and one to two year goals review. If those horizons currently hold nothing, this book is a cheap way to fill them.

Best for

• Readers whose lists are tidy but whose direction is blank
• Anyone doing an annual review and struggling to get past next quarter

Skip it if

• Fictionalised uplift makes you put books down
• Your bottleneck is execution, not purpose

7. Thinking, Fast and Slow, Daniel Kahneman

The pick for understanding why your plans fail. Kahneman, who was awarded the Nobel Prize in Economic Sciences in 2002 for his work with Amos Tversky, on judgement under uncertainty, sets out the planning fallacy and the outside view in chapter 23. That chapter alone justifies the purchase.

The practical output is a buffer rule. Take your estimate for any multi-week project, find two similar things you have actually finished, and plan against how long those really took rather than against your best case. Then add the gap to your deadline. Plenty of people bounce off the length and the density; if that is you, swap in Rolf Dobelli’s The Art of Thinking Clearly as a shorter substitute, not as an eighth pick.

Best for

• Chronic underestimators and anyone who manages estimates for a living
• Readers who want evidence rather than exhortation

Skip it if

• You need behaviour change this month
• You read on a commute in ten-minute bursts: this does not survive that

How to pick the right book for the problem you actually have

Diagnose before you buy. Four common bottlenecks, four different answers.

• Too many commitments: Getting Things Done, and nothing else until the weekly review is running.
• No follow-through: Atomic Habits, with the card.
• No direction: The Traveler’s Gift, or an annual review with a blank page.
• No energy for the work itself: The War of Art.

Reading three habit books in a row is procrastination wearing a respectable jacket. The second one will not tell you anything the first did not; it will simply postpone the uncomfortable moment where you commit to one change and watch yourself miss it on Wednesday.

Motivational books earn their place when you know what to do and have gone cold on it. They are a sugar hit when used as a substitute for a system, which is the classic pattern: an inspiring Sunday, a heroic Monday, and a Thursday that looks exactly like last Thursday. Order matters. If your inbox is the bottleneck, read the system book first and the mindset book second.

Turning a book into a working system in one sitting

Mind-map it onto one page, within a week of finishing. Centre is the title, three branches: principles, triggers, actions. The constraint is the point, because fitting a 300-page book on one sheet forces you to separate the method from the anecdotes padding it out. The War of Art reduces to maybe four triggers. Who Moved My Cheese? reduces to two. That is not a criticism of either book; it is what they are.

Then extract next actions properly. “Be more focused”is an intention, not an action. “Book two 90-minute blocks in Monday’s calendar, laptop offline”is an action with a context you can actually see. Each principle you keep should produce something physical and visible, and if you are running lists in an app, this is where tight views earn their keep: see the custom perspectives that cut a daily review for one way to keep new habits in front of you.

Give every change a review slot. New habits get a checkpoint line in the weekly review, and a 30-day date to decide whether to keep or drop them. Dropping them is a legitimate outcome. And keep the current rules on paper. One index card, one or two rules, visible on the desk. Running more than two behaviour changes at once reliably kills all of them, which is the single most expensive mistake on this page.

Mistakes that waste a good book

Buying the summary instead of the book, then applying neither, is the most common. Summaries give you the conclusions without the examples that make the conclusions stick, and nobody changes their Tuesday because of a bullet point.

Audiobooks are the second trap. Fine for parables and narrative, poor for method books, because you cannot flick back to the chapter you half remember when a project goes sideways in four months. Reference material wants a physical index.

And skipping rereads. The books that change behaviour are almost always the ones read twice, a year apart, when your situation has moved enough that different paragraphs light up. GTD read while drowning and GTD read while merely busy are two different books.

Where to find and read them in the UK without overspending

Start with the library. A council library card gets you free digital borrowing through Libby or BorrowBox, depending on which your local service uses, and that is the right way to try any title you are unsure about. Parables especially: borrow Who Moved My Cheese?, read it on a Sunday, return it Monday.

Buy the physical copy when you are going to write in it and read it twice. A new self-help paperback in the UK costs a good deal more than the same title picked up secondhand or in a charity shop, and the secondhand price is a reasonable one for a book you intend to deface with margin notes.

Sample the first chapter before you commit. It reveals almost immediately whether you are holding a method book or a 300-page magazine article with a cover price. Then set a rhythm you can keep: one chapter plus a ten-minute conversion step, four evenings a week, finishes most 250-page books inside a month and leaves a one-page map behind. Binge reading leaves you with a finished book and nothing on the card.

Pick one book for the bottleneck you actually have, run one change for thirty days, and judge the result by what changed in your week rather than by how the reading felt. That is the only useful test of the best self improvement books, and it is also why most shelves stay full of good books that never did anything. If you want to see what the finished version looks like in practice, the pieces on measuring output rather than activity and books that change habits for people running their own thing go further into the mechanics.

Frequently Asked Questions

What are the best self improvement books to start with?

Start with the one that matches your bottleneck. If you are overloaded, Getting Things Done; if you are inconsistent, Atomic Habits; if you have lost direction, a short values-led book such as The Traveler’s Gift. Starting with the most famous book rather than the most relevant one is how shelves fill up and weeks stay the same.

How many self improvement books should I read in a year?

Fewer than you think. Four to six, each converted into a one-page map and at most two live changes, beats twenty read and forgotten. The limiting factor is not reading speed, it is how many behaviour changes you can hold at once, which for most people is one or two.

Are book summaries as good as reading the full book?

For deciding whether to read something, yes. For changing behaviour, no. Summaries strip out the examples and caveats that make a method usable, and they leave you able to describe an idea you have never actually tried. Use them as a filter, not a replacement.

Which self improvement book helps most with procrastination?

The War of Art, if the problem is avoidance of work you care about and keep circling. Getting Things Done, if the problem is that your next actions are vague and your lists are not trusted. The two causes look identical from outside and need completely different fixes.

How do I actually apply a self improvement book instead of just reading it?

Create one open loop you have to close: a project with a defined outcome, a next action with a context, or a recurring trigger in your weekly review. Mind-map the book onto a single page within a week of finishing, write the one or two rules you are running this month on a card, and set a 30-day date to keep or drop them. If you can find a home for new habits in your existing capture and review setup, from an index card to an always-available capture channel, they tend to survive the month.

The post Best Self Improvement Books: 7 You Act On appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The best Atomic Habits summary is the one that tells you which parts of the book your system already does, which parts it genuinely cannot do, and where the two actively argue with each other. This piece gives you the full argument of James Clear’s book (four laws, identity, systems over goals, habit stacking, environment design, the two-minute rule, the plateau of latent potential) and then maps each idea onto a GTD setup: lists, weekly review, capture, horizons. The honest conclusion, up front: Atomic Habits is excellent on repeated behaviour and close to useless on one-off commitments, which is exactly the gap GTD fills. Run both. Just don’t let the two two-minute rules collide, because that is the mistake nearly every reader makes.

What Atomic Habits actually argues, in one page

Clear’s central claim is that outcomes are lagging indicators of systems. You do not rise to the level of your goals; you fall to the level of your systems. A goal is a direction, the system is the repeated behaviour that produces the result, and the result shows up late.

That lateness is the part people underestimate. Clear calls it the plateau of latent potential: effort accumulates invisibly for weeks before anything measurable changes, which is precisely when most people quit. A tiny daily improvement compounding over a year is the arithmetic he uses to make the point. Treat it as an illustration of compounding, not a measured rate of human improvement.

Underneath sits a four-stage loop borrowed from behavioural science: cue, craving, response, reward. Clear’s contribution is not the description but the reframing of each stage as a rule you can act on. Cue becomes “make it obvious”. Craving becomes “make it attractive”. Response becomes “make it easy”. Reward becomes “make it satisfying”. Invert all four and you have a method for breaking a habit.

The strongest chapter, for anyone already running a list system, is the one on identity. Clear argues that durable change comes from changing the evidence you hold about who you are, rather than chasing a target. Every action is a vote for a type of person. Write one page a day and you accumulate evidence that you are a writer, which is a sturdier motivation than a word count.

Who will find the book thin? Anyone whose problem is project chaos rather than behaviour. If your week is falling apart because you have fourteen commitments you have never written down, no amount of cue engineering helps. That reader needs a trusted capture system first and a habit book second.

The four laws of behaviour change, and their inversions

Make it obvious. Two tools here. Implementation intentions, phrased as “I will [behaviour] at [time] in [location]”, which research in social psychology has linked to higher follow-through than intention alone. And habit stacking: “After [existing habit], I will [new habit]”, bolting the new behaviour onto something already automatic. Inverted, for breaking a habit: make it invisible. Remove the cue rather than resisting it.

Make it attractive. Temptation bundling pairs the thing you should do with the thing you want to do. Clear also leans hard on social pull: you copy the normal behaviour of the group you belong to, so the fastest way to make a habit attractive is to join people for whom it is unremarkable. Inverted: make it unattractive.

Make it easy. The law of least effort says behaviour follows the path of lowest friction, so you reduce the number of steps between you and the action. This is where the two-minute rule lives: scale the habit down until the starting version takes two minutes. “Read before bed”becomes “read one page”. Inverted: make it difficult, by adding steps.

Make it satisfying. The brain prioritises immediate reward, and most good habits pay off late, so you attach a small immediate marker: a tick, a tracker, a visible streak. Alongside it sits the rule that does the most real work in the book, never miss twice. Inverted: make it unsatisfying, usually by adding a cost or a witness.

Worth knowing before you set a 30-day challenge: in a study by Phillippa Lally and colleagues published in the European Journal of Social Psychology in 2010, the median time for a new behaviour to reach automaticity was 66 days, with individual times ranging from 18 to 254 days. The 21-day figure you see everywhere has no basis in that data.

Six ideas from this Atomic Habits summary worth keeping

1. Systems over goals, because the weekly review is already a system

You do not need to be sold this one if you run GTD. The weekly review is a system: fixed, repeated, outcome-agnostic. A New Year resolution is a goal with nothing attached to it. The useful move is to notice which of your intentions currently have a system and which are floating. Anything floating either gets a cue or gets demoted to someday/maybe. It also pushes you towards judging your week by output rather than activity, which is Clear’s point made from the other direction.

2. Identity statements, pinned at Areas of Focus

This is the idea most summaries bury on a habit tracker, where it dies. Identity belongs at GTD’s Areas of Focus horizon, the level where you define the ongoing responsibilities you maintain. “I am someone who finishes what they start”is not a morning routine. It is a filter on which projects you agree to take on, which is where it changes your life. Stuck at the daily level, it becomes a slightly grander way of describing brushing your teeth.

3. Habit stacking onto anchors you already have

“Do a weekly review each week”fails because the cue is a vague intention. “After I shut the laptop on Friday at 16:00, I open my weekly review checklist”works because the cue is a fixed event that happens whether you feel like it or not. Same for the inbox sweep after the morning coffee, or the capture dump after you take your coat off. Stack onto anchors, not onto willpower.

4. Environment design, which is a context list in physical form

Clear’s “make it obvious”chapter is cue engineering, and the GTD community was doing it with index cards years before the book existed. The in-tray by the front door. The notebook in the jacket pocket. The Hipster PDA card in your wallet, which is just a capture tool positioned where the thought actually happens. Treat your physical spaces as context lists: each one should make the next action the easy action, and make the wrong action mildly annoying.

5. The two-minute starting ritual for resistance work

Some next actions sit on the list for weeks, and almost always they are badly defined in a way that hides a wall of resistance. “Draft client proposal”is a project pretending to be an action. Rewrite it as “Open the proposal document and type the client name”and it moves, because the barrier to entry is a keystroke. Use this sparingly, on the items that have slid down the list three weeks running.

6. Never miss twice, the rule that saves lapsed systems

Skipping one weekly review is a bad week. Skipping two in a row is the point at which the inbox has enough backlog that the third review feels like a clear-out rather than a review, and a clear-out is unpleasant enough that people quietly stop. Missing once is noise. Missing twice is the start of abandonment. Protect the second one.

The two-minute rule confusion: Clear and Allen do not mean the same thing

This is the single most useful thing a GTD reader can take from the book, and mainstream summaries skip it entirely.

David Allen’s two-minute rule is a processing decision, made at the inbox. While clarifying, if an item will take less than two minutes, you do it immediately, because tracking it costs more than doing it. The rule exists to keep your lists free of trivia. It applies during processing and nowhere else.

Clear’s two-minute rule is a scaling-down tactic, applied to recurring behaviour. Shrink the habit until the entry version takes two minutes, so the ritual of starting becomes automatic, then let it grow. The rule exists to beat resistance at the threshold.

Merge them and you get one of two failure modes. Either your next actions list fills with two-minute fragments you have deliberately shaved down, which means you are now tracking work that Allen’s rule says should have been done on the spot. Or you apply Clear’s version to one-off work and end up with a habit that never grows past the token version: two minutes of proposal writing a day will not deliver a proposal.

Run both cleanly. Allen’s rule lives in capture and processing. Clear’s rule lives on recurring behaviour and on the handful of resistance tasks that need a smaller first step.

What Atomic Habits does not cover, and GTD does

Atomic Habits has almost nothing to say about one-off commitments. A house move, a self assessment return, a product launch: dozens of non-repeating actions, no cue to stack them onto, no repetition to automate. That territory belongs to project lists and Allen’s natural planning model, which works backwards from outcome to principles to brainstorming to organising to next action. Repetition is not the problem there. Definition is.

Capture is the other gap. Clear’s framework assumes you will remember your intentions when the cue fires. A trusted inbox assumes you will not, which is the safer assumption at 22:40 on a Thursday. If your capture takes more than a few seconds, you will skip it when it matters; an always-available capture channel solves a problem the book never addresses.

Where the book beats GTD outright: maintenance behaviour. Exercise, reading, flossing, tidying the desk, the quarterly backup check. None of it has a deadline, so none of it ever surfaces on a list by force. Habits are the only mechanism that reliably handles work with no due date.

One more warning. Habit tracking is where most readers quietly fail, because a tracker is a second system to maintain alongside the lists you already have. A four-line habit check folded into the weekly review costs nothing extra. A separate tracking app adds a daily admin tax and gets abandoned inside a month.

Build it: four weeks to put the summary into practice

1. Week 1. Pick one identity statement and write it at your Areas of Focus level. Pick one habit that supports it. Stack the habit onto a fixed anchor and write the implementation intention out in full: behaviour, time, location. One habit. Not five.
2. Week 2. Redesign one physical space so the cue is unavoidable and the friction drops by at least one step. In-tray on the hall table, running shoes by the door, phone charging in another room. Measure it by steps removed, not by how tidy it looks.
3. Week 3. Add a short habit section to your weekly review: the habit, whether it ran, and a never-miss-twice check. Four lines. If it takes longer than two minutes to complete, it is too elaborate.
4. Week 4. Audit. Anything still failing is not a willpower problem; convert it into a project with a properly defined next action, or drop it. A habit that has failed four weeks running is telling you something about the design, not about you.

Reading Atomic Habits alongside other productivity books

Atomic Habits was published in October 2018, runs to roughly 320 pages across 20 chapters, and is structured so tightly that the whole argument fits on one side of A4 as a mind map. That is the format worth keeping. Four laws as branches, inversions on the opposite side, identity and systems in the centre. You will revisit a one-page map; you will not reread 320 pages.

Next to Getting Things Done, it is complementary rather than competing: Allen handles open loops, Clear handles repetition. Next to Steven Pressfield’s The War of Art, it is the engineering answer to the same problem, where Pressfield gives you the moral one. If you want more in this area, the list of motivational books that actually change what you do is a better starting point than a bestseller chart, and the entrepreneur reading list overlaps where behaviour meets business decisions.

At some point, stop reading about habits. The marginal return on a fourth behaviour-change book is close to zero if you have not run a weekly review in a month. Read the one, map it, then go and do Friday at 16:00.

Frequently Asked Questions

What is the main idea of Atomic Habits in one sentence?

Small, repeated behaviours compound into large results, so you should build systems and identity rather than chase goals. Clear’s phrasing is that you do not rise to the level of your goals, you fall to the level of your systems. Outcomes are lagging indicators of what you repeatedly do.

What are the four laws of behaviour change?

Make it obvious, make it attractive, make it easy, make it satisfying. Each maps to a stage of the cue, craving, response, reward loop. To break a habit you invert them: make it invisible, unattractive, difficult and unsatisfying.

How is Clear’s two-minute rule different from David Allen’s?

Allen’s is a processing decision at the inbox: if an item takes under two minutes, do it now rather than tracking it. Clear’s is a scaling-down ritual: shrink a new habit so its starting version takes two minutes and cannot reasonably be refused. Different stage, different purpose, and merging them clogs your next actions list with fragments.

Does an Atomic Habits summary replace reading the book?

For the framework, mostly yes; the four laws and the identity argument compress well. What a summary loses is the case studies and the worked examples that make the inversions click, which is a fair amount of the book’s practical value. Read a summary to decide whether the structure fits your problem, then read the chapters that do.

Can you run Atomic Habits and GTD at the same time?

Yes, and they fit together better than most pairings, because they solve different problems. GTD holds one-off commitments and open loops; Atomic Habits handles recurring behaviour that has no deadline and never surfaces on a list. Keep the habit check inside your existing weekly review rather than running a separate tracker.

The post Atomic Habits Summary: 6 Ideas That Fit GTD appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

UK productivity figures measure output per hour worked across the whole economy. They are a national accounting exercise, not a scoreboard for your team, and most of the trouble people get into with them starts by forgetting that. This piece does two things: explains what the Office for National Statistics actually publishes and how much weight the numbers will bear, then shows how the same measurement logic scales down to five people or one desk without turning into surveillance.

The honest conclusion, up front: the national series is useful as context and almost useless as a target. But the discipline behind it, one defined unit of output, one hours source, a fixed release date and published revisions, is exactly what personal and team productivity tracking usually lacks.

What the UK productivity figures actually measure

Labour productivity is output divided by labour input. ONS publishes it three ways, and the three can move in different directions in the same quarter.

Output per hour, per worker and per job

Output per hour worked divides gross value added by total hours worked. It is the measure economists quote because it is the only one that adjusts for how much time people actually spent producing the output.

Output per worker divides by the number of people in employment. Output per job divides by the number of filled jobs, which is a larger count because people hold second jobs.

Why the split matters: if average hours fall, say through a shift to part-time working or a drop in overtime, output per worker can slide while output per hour holds up or rises. Same economy, two opposite headlines. During the furlough period this gap was severe enough that the per-worker series told you almost nothing about underlying efficiency.

Levels versus growth are different problems

A country can sit at a high level of output per hour and still grow slowly. The UK’s difficulty is mostly growth: the level is respectable by global standards, the growth rate since 2010 has not been. Headlines mix the two constantly. If a chart shows a percentage, check whether it is a percentage change on the previous year or a percentage gap against another country’s level. They are not the same claim and they imply different fixes.

Whole economy, market sector and the public services problem

ONS publishes a whole economy figure and a market sector figure. The difference is public services, where output is genuinely hard to measure because there is no price. ONS uses quantity indicators adjusted for quality in its public service productivity work, which is a separate release on a slower schedule. If your interest is business performance, the market sector series is the cleaner comparison. Quoting the whole economy number and blaming private firms for it is a common sleight of hand.

Where the numbers come from, and how often they change

The relevant publication is the ONS labour productivity series: a quarterly flash estimate first, then a fuller release with breakdowns by industry and by region. ONS’s main productivity outputs carry the accredited official statistics label, meaning they have been assessed by the Office for Statistics Regulation against the Code of Practice for Statistics. The flash estimate is the provisional one. Treat it as a first read, not a finding.

Here is the weak joint in the calculation, and it is on the hours side rather than the output side. Hours worked come from the Labour Force Survey. The LFS has had well-documented response rate problems, which pushed ONS to boost the sample and reweight the estimates, and ONS has publicly flagged the increased volatility of LFS-based figures while that work continues. Survey trouble flows straight into published productivity growth. That is one reason the series gets revised, sometimes by enough to change the story.

So the practical rule for anyone writing a board paper: cite the release and its date, every time. “ONS productivity figures published on [date of the release you are quoting]”is defensible. “UK productivity is X”is a hostage to the next revision. If you quoted a number last quarter, check it before you quote it again.

The headline picture: the productivity puzzle, regions and international gaps

The long-run shape is well established even as individual quarters bounce around. Before the financial crisis, UK output per hour grew at a far quicker pace than it has managed since. Growth since 2010 has averaged only a fraction of that earlier rate. That shortfall is what economists call the productivity puzzle. Check the current release for the latest reading before you put a figure in a slide.

On international comparisons, parliamentary briefings drawing on OECD data place UK output per hour below the United States, with France and Germany also ahead. The size of that gap is sensitive to two things people skip: the purchasing power parity conversion used, and each country’s hours estimates, which come from different survey designs. A gap of a few percentage points between two European economies is within the noise of the method. A gap against the US is not.

Regionally, London and the South East sit well above the UK average and pull that average up, which means the national number describes almost nobody’s actual region. Industry spread does the same job: finance, utilities and manufacturing show high output per hour, hospitality and social care do not, largely because of how much capital sits behind each worker and how the output is measured. If you run a care business, the whole economy figure is not your benchmark. The ONS regional and industry tables are.

Why growth stalled, and which causes you can act on

Most of the standard explanations are outside your control. Capital deepening, the amount of kit and software per worker, has been weaker in the UK than in peer economies, and no single firm fixes national investment. Diffusion is slow too: a long tail of lower-productivity firms sits well behind the frontier, and practice spreads sluggishly between them.

Two causes are within reach. The first is management practice and basic operational discipline, which costs a fraction of a machine and shows up in research on management quality as a real driver of firm-level performance. The second is job design. A surprising number of roles are built around coordination rather than output: chasing, status-checking, re-explaining. Those hours are counted as hours worked in the statistics. They produce nothing.

That is the part the national debate underprices. The figures count hours at work, not attention at work.

Build your own output per hour figure for a team of five

You can copy the method without pretending you have copied the rigour. Four steps.

1. Define one honest unit of output. Shipped deliverables, resolved cases behind a quality gate, invoiced projects, published pieces. One unit. Write the definition down, because the failure mode is redefining it in the quarter it looks bad.
2. Pick an hours source you will keep for a year. Timesheets, payroll hours, calendar time, whatever you will actually maintain. Decide now whether unpaid overtime counts. Both answers are defensible; changing your mind mid-series is not.
3. Set a quarterly cadence with a stated revision policy. Late sign-offs and holiday weeks will distort things. Allow yourself to restate the previous quarter and say so, exactly as ONS does.
4. Track headcount changes alongside the ratio. A new starter drags the number down for a quarter. That is onboarding, not decline.

A worked example. A five-person agency records 820 working hours in a quarter and signs off 41 client deliverables. That is 20 hours per deliverable. On its own it means nothing. Four quarters of the same pair of numbers, with headcount noted, starts to mean something.

Single desk, same logic: 12 hours of writing time producing three published articles gives four hours per article. Log email processing time separately so inbox activity never gets counted as output.

What to exclude, permanently: emails sent, messages read, hours logged in a tool, meeting counts, anything that rewards presence. There is a fuller case for measuring by output rather than activity, but the short version is that activity metrics are easy to game and people will game them within a fortnight.

Turning the figures into a working week

Open loops are the drag nobody measures. A commitment held in someone’s head rather than in a trusted system generates re-work, chasing and context switching, and every minute of that is counted as an hour worked in the national statistics. Clear the loops and output per hour rises without anyone buying anything. That is the cheapest lever in the entire productivity debate and it never appears in the investment argument.

Job one: time to captured. Unlike engagement or utilisation, you can time this with a stopwatch. Phone locked, screen off, hands busy, and you need to catch a commitment. If it takes more than five seconds, you will stop doing it under pressure, and the things you lose are the ones you thought of walking between meetings. Time it on your own setup this week; the result is usually worse than people expect. There are faster routes, including voice capture through an AI assistant when your hands are full.

Capital spending is not the only lever, and the analogue evidence proves it cheaply. A hipster PDA, index cards and a clip, costs pence and clears the five-second bar with no sync, no battery and no subscription. That is the personal-scale version of the national argument: process discipline explains a slice of the gap that capital alone does not.

Then process. Email gets turned into actions and reference, not read and re-read, so inbox volume stops standing in for work done. And run the weekly review like a statistical release: same day, same slot, same questions, revisions allowed. Most personal tracking collapses because the definition of output quietly changes every time the number disappoints.

One caution on tooling, because tooling is treated as free in these debates and it is not. Judge any new app on the same jobs this site applies to note-taking apps: time-to-captured, one trusted inbox, retrieval from half a memory, exit cost, and the daily admin tax in tags, statuses and tidying. Ten minutes of extra daily housekeeping across five people is roughly four hours a week of output gone. No dashboard will ever report that. Measure your output ratio for a quarter before the switch and a quarter after, and be willing to go back.

Five mistakes people make when quoting UK productivity figures

1. Comparing per worker with per hour. Quoting France on output per hour against the UK on output per worker is not a comparison, it is an artefact of different average hours.
2. Treating the flash estimate as settled. It is a provisional first read and it moves.
3. Using the national average as a sector or regional benchmark. London distorts the average upwards; hospitality and social care sit structurally below it. Use the ONS breakdowns.
4. Confusing hours worked with hours paid, or headcount with full-time equivalents. Four part-timers are not four workers’ worth of hours, and paid hours include time nobody worked.
5. Setting an individual target from a national statistic. The measure was built for economies. Applied to one person, it becomes an activity metric with a respectable-looking source attached.

If you want the reading rather than the statistics, the argument for changing what you actually do is made better in books than in briefings; the books worth the time are the ones that change behaviour rather than mood. The UK productivity figures will tell you where the country stands. What happens on your desk next week is a separate measurement, and it is the one you control.

Frequently Asked Questions

What do the latest UK productivity figures show?

Check the current ONS labour productivity release rather than any figure quoted in an article, including this one, because the series is revised. The established long-run picture is weak growth since 2010, markedly slower than the pace recorded before the financial crisis. Always cite the release date alongside the number.

How does the ONS measure labour productivity?

Output, measured as gross value added, divided by labour input. ONS publishes output per hour worked, output per worker and output per job, with a provisional quarterly flash estimate followed by fuller tables broken down by industry and region. Hours worked are derived from the Labour Force Survey, which is why survey response issues and reweighting feed directly into published productivity growth.

Why is UK productivity lower than in the US, France and Germany?

The usual explanations are lower capital investment per worker, slow diffusion of good practice from frontier firms to the long tail behind them, weaker training spend and variable management quality. The measured size of the gap also depends on the purchasing power conversion and the hours estimates used, so treat small gaps against European neighbours with more caution than the larger gap against the US.

Which UK regions and industries have the highest output per hour?

London and the South East sit above the UK average and lift it, which is why a single national figure rarely describes any given region. By industry, finance, utilities and manufacturing typically show high output per hour, while hospitality and social care sit lower, reflecting both capital intensity and how output is measured. The ONS regional and industry tables are the place to look for your own sector.

Can a small team measure productivity the way the national figures do?

You can borrow the method, not the precision. Define one unit of output, fix an hours source for a year, report quarterly and allow yourself to restate previous quarters. Track the same two numbers for four quarters before drawing conclusions, note headcount changes, and never convert the ratio into an individual target.

The post UK Productivity Figures: What They Mean for Your Work appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The Notion Mail shutdown is a workflow loss, not a data loss, and that one distinction decides how you should spend the next few weekends. Your messages are not in Notion. They are in Gmail, where they always were. What disappears on the day is the layer you built on top: the split views, the snippets, the auto-triage, the muscle memory in your right hand. This piece audits exactly what dies, tells you what to salvage before the lights go out, and rebuilds the same GTD processing loop somewhere that will still be there in three years.

Where the Notion Mail shutdown leaves you right now

Notion announced in late June 2026 that the Notion Mail inbox, across web, desktop and iOS, closes on 22 September 2026, with the company saying it is putting its effort elsewhere. That is roughly three months of notice, which is more than most wound-down clients give, and less than most people use properly.

Two layers, and they are not equally at risk. Layer one is your account: messages, threads, attachments, Gmail labels, contacts and calendar events, all sitting on Google’s servers because Notion Mail was always a client for Gmail and Google Workspace accounts rather than a mail host of its own. Nothing there is going anywhere on 22 September. Layer two is everything you configured inside the client, and that is the part that evaporates.

So the people in trouble are not the ones with ten years of archived mail. They are the ones who built their whole triage system inside Notion Mail’s views rather than in Gmail’s own settings. If your “Waiting on reply”list only exists as a saved view in a client that is being switched off, you do not have a system. You have a countdown.

Four jobs, in order: salvage what only exists in the client, pick a replacement against sensible criteria, rebuild the processing loop, then reduce your exposure so the next shutdown costs an afternoon.

What the shutdown actually takes with it (and what stays)

Stays, because it lives on Google’s infrastructure: every message and thread, attachments, Gmail labels and their colours, contacts, calendar events, and any filters you created in Gmail’s own settings rather than in the client.

Goes with the client:

• Custom views and split-inbox layouts, including the filter logic behind them
• Snippets and reply templates stored in Notion Mail
• AI-assisted labelling and auto-triage rules configured inside the app
• Anything sitting in the client’s scheduled send queue on the day
• Snoozes managed by the client rather than by a Gmail label
• The keyboard flow you memorised, which is worth more than you think

That last one is the loss nobody puts on the checklist. A processing routine tuned to one client’s shortcuts is a real asset. You built it over months, and it is the reason you can clear forty messages in twenty minutes without deciding anything twice. Rebuilding it is the expensive part of this migration, not exporting anything.

Check the crossover too. If you had mail flowing into Notion pages, task databases or meeting notes, work out whether the client created those links or whether the connection sits in Notion proper. Related reading on where Notion’s structure survives an export and where it quietly does not: what a Notion export actually loses.

Your salvage checklist before the inbox closes

Half an hour now, or a bad week in late September. Work down this list.

1. Copy snippets and templates out as plain text. Treat them as content, not settings. A Notion page, a text file or your new client’s template store all work. The wording is the asset; the storage format is not.
2. Recreate your triage rules in Gmail itself. Anything that sorts, labels or skips the inbox should live at the account layer, where it survives every client change. Then open Gmail Settings, go to Filters and Blocked Addresses, select all and export. You get a mailFilters.xml file you can import into any Google account later. Google’s own filter documentation covers the import and export steps.
3. Clear the scheduled queue. Send or cancel anything waiting to go out from the client. Do not assume a queued message survives the shutdown.
4. Check aliases, send-as addresses and signatures are set at Gmail account level. If you configured a signature only inside Notion Mail, it goes with it.
5. Screenshot every custom view you relied on, and write out the filter logic underneath. “From: anyone in the finance domain, unread, older than three days”is rebuildable in thirty seconds. A vague memory of a view you liked is not.
6. Pull a local archive if you want one. Google Takeout exports your mail as MBOX, which Apple Mail and Thunderbird will both import. Optional, but cheap insurance.

Notice what is not on that list: your emails. They are fine. Stop worrying about them and spend the time on the rules.

The five jobs your replacement inbox has to do

These are the same five jobs this site uses to judge note apps, and they transfer to mail almost unchanged. Feature comparisons will tell you which client has AI summaries and a unified sidebar. They will not tell you whether you can still empty the inbox on a Friday afternoon with a headache.

• Time-to-processed. How many keystrokes from open message to decided next action, filed, and out of sight? Three is good. Seven means you will start leaving things “for later”.
• One trusted inbox. Everything arrives in one place you actually empty. If the client creates a second queue (a “done later”pile, a separate AI tab) that you never clear, it has added a leak.
• Retrieval from half a memory. You remember the sender and four words of a phrase. Does search find it? Gmail’s server-side search is the benchmark here, and plenty of clients are worse.
• Exit cost. Does your setup live in open standards (IMAP, Gmail labels, server-side filters) or in the vendor’s own database? This is the job Notion Mail users just failed involuntarily.
• No daily admin tax. An inbox that looks tidy but demands a morning maintenance ritual in tags and statuses has failed. You will abandon it by the second month.

The same framework applied to capture tools is set out in the note-taking app comparison, if you want to see how it behaves on a different category.

Replacement email apps compared for a GTD workflow

There is a fuller breakdown in the Mac email app comparison. Here is the short version, judged against the five jobs rather than feature count.

Gmail on its own

The unglamorous answer, and for a lot of ex-Notion Mail users the right one. Zero lock-in, because the labels and filters are the product. Search is the best of any option here. Triage speed is the weak point, though multiple inboxes plus keyboard shortcuts gets you closer than people expect.

• Best for: anyone whose priority is never doing this migration again
• Watch out for: the interface is busy, and nudges and tabs can quietly become a second queue

Mimestream

A native client built specifically on the Gmail API, so labels behave like labels rather than being mangled into IMAP folders. Fast, quiet, and the closest thing to Notion Mail’s speed without the Notion Mail risk. Apple platforms only, so a Windows machine at work rules it out. It is a paid subscription; check the current pricing before you commit.

• Best for: Mac-and-iPhone users who want Gmail’s structure with a proper native client
• Watch out for: no Windows or Android, so it is a whole-ecosystem decision

Spark, Shortwave and Superhuman

The triage-first tier. All three are quick to process, all three snooze well, and all three store a meaningful chunk of your configuration on their own servers. Superhuman was acquired by Grammarly in 2025, which is a useful reminder that ownership changes and product direction changes with it. Run the lock-in test below before you rebuild your whole system inside any of them.

• Best for: high-volume inboxes where raw processing speed is the failing job
• Watch out for: exit cost. Ask what an export actually contains before you invest a month of habit

Apple Mail

The conservative choice. Standards-based, free, and it has outlived every fashionable client of the last fifteen years. Search is mediocre by comparison, and Gmail label handling is clumsy. But pair it with a real task manager and it does the job for decades rather than quarters.

• Best for: people who want the mail client to be boring and the task manager to do the thinking
• Watch out for: weaker search means you lean harder on good filing

How to choose: pick by the job that is failing for you now. Losing things? Fix retrieval, go Gmail or Mimestream. Drowning in volume? Fix time-to-processed, look at the triage tier. Been burned by this shutdown and want it never to happen again? Gmail or Apple Mail, and keep your structure at the account layer.

Rebuilding the GTD processing loop in an afternoon

Start with labels, created in Gmail, not in whichever client you land on. Four is enough: @Action, @Waiting For, @Someday and Reference. The @ prefix sorts them to the top of most label lists. Because they live on the account, switching from Mimestream to Spark to Apple Mail next year needs no rebuild at all.

Then the pass itself. Open, decide, move on. Anything under two minutes gets done there and then, as David Allen’s two-minute rule intends. Anything longer becomes a next action in your task manager, phrased as a physical action, and the message gets archived under Reference. Anything you have delegated or are waiting on gets @Waiting For and leaves the inbox. If you run OmniFocus, the custom perspectives guide shows how to surface those actions without a daily trawl.

One rule that will save a lot of people in September: snoozing is not a next action. Notion Mail’s triage features made it very easy to push a decision three days right, and when the client goes, so do the snoozes. Every deferred item should already exist as a next action or a @Waiting For entry outside the inbox. The snooze is a convenience on top of that record, never the record itself.

Wire the weekly review in three sweeps: run down @Waiting For and chase anything stale, empty the inbox to zero, and check anything the client has snoozed against your project list. If a snooze surfaces something your project list did not know about, that is a gap in the system, not a win for the inbox.

Finally, learn five shortcuts, not fifty. In Gmail with keyboard shortcuts enabled: e to archive, l to label, b to snooze, / to search, c to compose. Those five cover most of the day. Most clients either copy them or let you remap to them.

How to stop the next email client shutdown costing you a month

Email clients have form. Zenbe closed its mail service back in 2011. Sparrow, which a lot of Mac users loved, was bought by Google in 2012 and wound down shortly after. The pattern is consistent: users who kept their structure in IMAP folders and server-side filters lost an afternoon. Users who kept it in the client’s own proprietary views lost their system and rebuilt it from memory.

Run the one-hour lock-in test before you commit to anything. Time yourself recreating your triage setup in a second client, working only from your exports and screenshots. Under an hour, you are fine. Over an hour, that difference is exposure you are carrying, and you will pay it at the worst possible moment.

The structural fix is simple to state and mildly annoying to maintain. Commitments live in your task manager. Reference lives in your notes app or in labelled mail on the server. The mail client is a pipe, not the system of record. Never let a proprietary view be the only place a commitment exists, because the view is exactly what the shutdown notice takes away.

Handled this way, the Notion Mail shutdown costs you one afternoon of rebuilding and buys you a setup that is genuinely portable. Handled badly, it costs you a month and a few broken promises to clients. The difference is where your rules live, not which app you pick.

Frequently Asked Questions

When does the Notion Mail inbox shut down, and what happens on the day?

The Notion Mail inbox closes on 22 September 2026 across web, desktop and iOS, announced in late June 2026. From that point the client stops being a way to read or send your mail, and the views, snippets and in-app rules stop with it. Your Gmail or Google Workspace account carries on exactly as before, reachable through Gmail on the web or any other client.

Will I lose my emails, contacts or calendar in the Notion Mail shutdown?

No. Notion Mail was a client sitting on top of Google accounts, so messages, threads, attachments, Gmail labels, contacts and calendar events all live on Google’s servers and are unaffected. If you want a local copy anyway, Google Takeout will produce an MBOX archive that Apple Mail and Thunderbird can import. The things genuinely at risk are the settings you created inside the client.

Can I export Notion Mail snippets, custom views and label rules?

Not as a tidy settings file, which is why manual salvage matters. Copy snippet text into a plain document, screenshot each custom view and write the filter logic out in words underneath, then recreate the important rules in Gmail Settings under Filters and Blocked Addresses. Gmail will export those as mailFilters.xml, giving you a backup that works in any Google account and outlives any client.

Which email app should I move to if I run a GTD system?

Pick by the job that is failing for you now rather than by feature count. If retrieval and portability matter most, Gmail on its own or Apple Mail are hard to beat and cost nothing. If sheer processing speed is the problem, Mimestream on Apple platforms or one of the triage-first clients will be quicker, provided you check the exit cost before you rebuild your habits inside them.

Will the rest of Notion still work after the mail inbox closes?

Yes. The shutdown set for 22 September 2026 covers the mail inbox, not the Notion workspace or Notion Calendar, both of which will carry on as normal. If any of your pages or databases are populated by the mail client, check whether the automation sits in Notion itself or in the mail app, because only the second one will disappear.

The post Notion Mail Shutdown: Rebuild Your GTD Inbox appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

Zenbe is gone, and so is the app its list users were told to move to. That double shutdown is the whole story, and it is the part the old blog posts still floating around Google will not tell you: Zenbe Mail and Zenbe Lists were closed down in the early 2010s, there is no login screen, no archive and no successor from the original team. Zenbe Lists refugees were widely pointed at Wunderlist, which Microsoft then retired on 6 May 2020, pushing everyone to Microsoft To Do. Two forced rebuilds in under a decade.

This piece does two things. It gives you the honest status of Zenbe, then names six live replacements, split between the two very different jobs Zenbe was trying to do at once: a shared, commentable inbox and a stripped-back list app. The conclusion up front, so you can stop reading if you already agree: if you are the only person in your system, buy a plain standards-based mailbox and a separate list app. Do not buy a team inbox.

What happened to Zenbe (and which Zenbe you probably mean)

Zenbe launched around 2007 as a web mail client with a genuinely novel idea: one inbox that several people could work in, with comments attached to individual messages rather than buried in a reply-all chain. Zenbe Lists came later as a companion app, a simple shared to-do list that synced between browser and phone. Both were retired in the early 2010s. Accounts were closed, data was not migrated anywhere, and the company did not hand the product to a new owner.

The name collisions you will hit in search

Search “zenbe”today and the results are a mess. A Steam survival game, a Japanese ryokan, an anime character and an unrelated social media scheduling tool all share some form of the name. None of them is the email app. If you arrived here from an old bookmark, a 2010 forum thread or a link in a GTD blog archive, the product you remember is the one that no longer exists.

Why the old reviews still rank

Zenbe got real tech-press coverage at the time, and those pages still carry authority. They describe an interface, a pricing model and a sync behaviour that exist nowhere now. Age is not the only problem. Nothing has replaced those pages with a clear “this is dead”statement, so the reviews keep ranking and keep sending people to a landing page that no longer resolves to a product.

What Zenbe actually got right

Worth naming precisely, because it tells you what to shop for. One: a shared inbox where a message could be discussed inline by the two or three people who handled it. Two: a list app light enough that adding an item took a couple of seconds on a phone in 2010, on 3G, which was harder than it sounds. Most modern task apps are heavier than Zenbe Lists was.

And here is the design flaw that made the shutdown hurt twice. Zenbe merged two jobs into one vendor. In a working GTD system your email is a capture channel and your list manager is a separate thing entirely. Keep them apart and no single company’s closure can take out your action lists.

The five jobs a Zenbe replacement has to do

Feature tables are useless here. Score candidates on jobs instead.

• Time-to-captured. Seconds from thought to stored item, on a locked phone, without opening a project view first. If it takes more than about five seconds you will stop doing it under pressure. That is a practical working benchmark rather than an official rule, and it is the same test used in our guide to capturing ideas in under five seconds.
• One trusted inbox. A single place things land. Two inboxes means things hide in the one you are not looking at.
• Retrieval from half a memory. You remember two words and roughly when. Can you find it?
• Exit cost. How much of your data leaves in a format another app can read.
• Daily admin tax. How much tagging, status-setting and tidying the tool demands before it earns its keep.

Zenbe scored well on the first two and catastrophically on exit cost. Weigh exit cost first from now on.

Three swaps for Zenbe Mail: the collaborative inbox

1. Spark Mail

Spark is the middle option: a polished mail client with team features bolted on, rather than a support desk pretending to be a mailbox. Comments on threads, shared drafts, send later and a snooze model that pairs neatly with a weekly review, because a snoozed message returns to the inbox instead of rotting in a “starred”pile.

Best for

• Two to four people sharing a mailbox occasionally, not all day
• Readers who liked Zenbe’s inline comments but do not want per-seat pricing
• Anyone who wants snooze plus scheduled send in one client

Pros

• Free tier covers solo use; paid team plans are modest
• Connects to your existing IMAP or Gmail account, so switching clients later is cheap
• Fast capture of a message into a task via other apps’ share sheets

Cons

• Comments and shared drafts live in Spark’s own layer, not in the mailbox, so they do not survive a move
• Its built-in tasks are not a list manager; treat them as temporary
• Feature set has shifted several times across versions, so check what is current before committing

2. Missive

Missive is the closest surviving relative to what Zenbe Mail was doing: a shared inbox with real conversation threads attached to messages, assignment, and rules for who handles what. Priced per user per month, so the bill scales with the size of your team. Check the current pricing page.

Best for

• A small team processing one address together every day, such as hello@ or bookings@
• Replacing internal forwarding and “did you reply to this?”messages

Pros

• Genuine inline discussion, the Zenbe behaviour people actually miss
• Clear assignment so a message has one owner
• Works over your existing mail provider

Cons

• Overkill for a one-person system, and you pay monthly for the privilege
• Adds a daily admin tax: assigning, closing and commenting only pays off with two or more people in the same mailbox
• The collaboration data is proprietary, even though the mail itself is not

3. Fastmail

The boring, durable choice, and the one most solo readers should take. A paid individual plan, full IMAP access, standards-based calendars and contacts, and no attempt to be your task manager. Your exit cost stays close to zero because any client can read it.

Best for

• Solo practitioners who want a mailbox, not a workflow product
• Anyone burned by a shutdown who wants their mail portable by default

Pros

• IMAP means you pick the client: Apple Mail, Thunderbird, Spark, whatever you like next year
• Thunderbird can pull the whole account down to mbox files for a local archive
• Search is quick and handles the “two words and roughly when”test well

Cons

• No shared inbox comments at all
• Paid only, with no free tier
• You supply the discipline; the app will not nag you into processing

Deciding between the three takes one question. Is anyone else reading this mailbox? If no, buy a mailbox and pair it with a client you like. If you want to compare clients properly, our comparison of Mac email apps for getting things done scores them on processing speed rather than feature count. And if you remember Sparrow, our Sparrow write-up is a second case study in the same lesson.

Three swaps for Zenbe Lists: simple shared task lists

4. Microsoft To Do

The direct heir to Wunderlist, built by the team Microsoft acquired, and free with a Microsoft account. If you followed the Zenbe Lists to Wunderlist path and then stalled in 2020, this is where that road ends.

Best for

• Shared household or small-team lists (shopping, packing, handover)
• Anyone who wants Wunderlist behaviour back at no cost

Pros

• Free, cross-platform, and shared lists work the way Zenbe Lists users wanted
• My Day view gives a daily short list without building a filter system
• Steps (subtasks) and file attachments included

Cons

• Weak review views; no proper contexts, so you improvise with lists
• Export is awkward compared with CSV-per-project tools
• Its history is literally a shutdown chain, so keep a plain-text backup of your next actions

5. Todoist

The fastest capture of the three. Type “call Dave friday 9am @calls”and quick-add parses it into a dated task with a label. Contexts live as labels, and filters rebuild GTD views. The useful version is a subscription, cheaper when billed annually; check the current pricing page.

Best for

• Practitioners running proper contexts and a weekly review
• Heavy keyboard users who capture by typing, not tapping

Pros

• Natural-language dates cut time-to-captured to a couple of seconds
• CSV export per project, which makes a future migration an evening’s work
• Filters give you context lists without a plugin ecosystem

Cons

• Free tier limits reminders and project count; the useful version is paid
• Labels and filters invite fiddling, which is a daily admin tax if you let it grow
• Attachments and comments sit behind the paid plan

6. Apple Reminders

Free on Mac and iPhone, and quietly the most standards-friendly list app on this page: it syncs over CalDAV, and dates follow the iCalendar conventions. Sensible if you already live in Apple Mail and Calendar.

Best for

• Apple-only households who want zero subscriptions
• Location and time reminders (“when I get to the office”)

Pros

• Capture via Siri with the phone locked, which is the real test condition
• Shared lists, subtasks, tags and smart lists included at no cost
• CalDAV underneath, so a third-party client can read your data

Cons

• No tidy CSV export; you script it or copy it out
• Windows and Android access is poor to non-existent
• Review views are basic next to a filter-driven app

Losses, plainly: Microsoft To Do gives up contexts and review views, Todoist gives up being free, Reminders gives up cross-platform and clean export. Pick the loss you can live with. If your lists are entangled with notes, the note taking apps scored for a GTD workflow piece covers where the boundary should sit.

Rebuilding your GTD setup after a shutdown

Start by separating the two jobs Zenbe merged. Email is an in-tray. It is not an action list. Processing a message means deciding the next action and writing that action in your list app, then filing or deleting the message. Starring is not processing; it is postponement with a badge.

A realistic one-evening rebuild looks like this: about 30 minutes choosing your mailbox and list app, 30 minutes creating a small set of contexts (@calls, @errands, @mac, @waiting), then 60 to 90 minutes taking the inbox to zero with the two-minute rule (do it now if it takes under two minutes, otherwise capture the action and file the mail). Finish by putting a recurring 45-minute weekly review in your calendar. Not a reminder. A calendar block. If Notion Mail’s shutdown is what’s forcing this rebuild, see the guide to rebuilding your GTD inbox for what to export first.

Resist the elaborate label tree. Four or five folders plus search beats forty nested labels, because search handles retrieval and folders only need to handle the handful of things you genuinely revisit. Reference material should leave email entirely and live in your notes app.

As for your old Zenbe data: it is unrecoverable. No archive, no export request, no support address. Rebuild from what you have now, which is your current inbox, your calendar and your head.

How to avoid the next migration chain

The Zenbe Lists to Wunderlist to Microsoft To Do chain shows where the cost really sits. Not the monthly fee. The repeated rebuilds, each one eating an evening and quietly losing the habits you had attached to the old tool.

So run the export before you commit, not after. Create three test items, export them, and open the file in Numbers, Excel or a text editor. Todoist hands you CSV per project. Apple Reminders syncs over CalDAV. Thunderbird will pull an IMAP mailbox down to mbox for archiving. If the export cannot be read outside the app, treat that tool as temporary however good the capture feels. Our write-up on what a Notion export actually loses shows how far a technically real export can still fall short.

Warning signs worth taking seriously: no paid tier at all (someone has to fund the servers), sync that only works between the vendor’s own apps, and a single funding round with no revenue story. None of those is proof of doom. All of them raise the odds.

Keep a fallback that no company can switch off. A text file of next actions in a synced folder costs nothing and opens in 2045. So does paper: an hPDA card in your back pocket has never once shown a retirement notice. The durable layer is the standards layer, and the standards layer is why a rebuild takes an evening rather than a fortnight.

Frequently Asked Questions

Is Zenbe still available, and can I log in to my old account?

No. Zenbe Mail and Zenbe Lists were shut down in the early 2010s and there is no working login, support channel or successor product from the original team. Any page promising a Zenbe sign-in today is either an old cached result or a different company that happens to share the name.

What happened to Zenbe Lists after it shut down?

Users were widely advised to move to Wunderlist, which was the obvious like-for-like at the time. Microsoft later acquired Wunderlist and retired it on 6 May 2020, directing people to Microsoft To Do. That is two forced migrations for anyone who started on Zenbe Lists.

Can I recover my Zenbe email or list data?

Realistically, no. The service closed without a migration path and there is no archive to request data from. If any Zenbe mail was collected over POP or IMAP into a desktop client years ago, check that client’s local folders, because that is the only place a copy could plausibly survive.

Which Zenbe alternative works best for a GTD system?

For most solo practitioners: a standards-based mailbox such as Fastmail paired with Todoist or Apple Reminders for lists. The mailbox handles capture, the list app handles next actions, and neither vendor’s closure takes out the other half of your system.

Do I need a shared inbox tool, or just a better email client?

If you are the only person reading the mailbox, a better client. Comments, assignments and internal threads are a daily admin tax that only pays off when two or more people process the same address. Add a shared inbox tool the day a second person starts replying, not before.

The post Zenbe Is Gone: 6 GTD Email and List Swaps appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The honest answer, up front: making money blogging around a full-time job is a scheduling problem wearing a marketing problem’s clothes. Every guide to how to make money blogging lists the same income streams and stops there, which is fine if you have forty spare hours a week. You have about six, some weeks four, and roughly none in December. So this piece does something different: it budgets the hours first, then scores each income route on how long it takes to pay you anything, how much weekly admin it drags behind it, and how badly it hurts when the platform changes its mind.

The conclusion, stated now so you can stop reading if you disagree: with a day job, pick one route, run it for six months, and treat the blog as a project with a defined next action rather than a hobby you feel guilty about.

What blog income actually looks like in year one

Close to nothing for months one to six. That is not pessimism, it is how the mechanics work. Display ad networks and most affiliate programmes only pay meaningfully once you have consistent monthly traffic, and search traffic to a new site builds slowly because pages need to be indexed, then tested by Google against incumbents, then held there for a few months before they settle.

“Passive income”is a misread of what is happening. Income compounds only while publishing stays consistent, and consistency on five spare hours is a calendar question, not a motivation question. The blogs that die did not run out of enthusiasm. They ran out of scheduled blocks.

So set your number before you pick a route. £50 a month of beer money, £500 a month to cover the car, or replacement income are three genuinely different projects with different routes, different traffic needs and different admin loads. Most people never say which one they want, which is why they pick the strategy that suits somebody else’s case study.

For the first year, count assets rather than revenue: indexed posts that still rank after three months, email subscribers who open, and a topic you can defend against every other person writing about it. Those are the things the money eventually attaches to.

Six ways to make money blogging, scored on hours

Score each route the way you would score an app: time to first pound, ongoing admin tax, and exit cost if the platform shifts. Most people pick on income potential alone, then quit the route the moment the admin turns up.

1. Display ads

• Time to first pound: slow, because it is gated on traffic, not effort.
• Weekly admin tax: near zero once the code is live.
• Platform risk: high. Rates, thresholds and Core Web Vitals impacts are outside your control.

Google AdSense and Ezoic will take small sites and pay small money. Mediavine’s Journey tier sits at around 10,000 monthly sessions and Raptive at roughly 100,000 monthly pageviews, though both have moved their requirements before, so check the current thresholds on their own sites rather than trusting a blog post. Treat those numbers as milestones, not promises.

2. Affiliate marketing

• Time to first pound: medium. Needs review and comparison content that ranks.
• Weekly admin tax: low to medium (link checking, price updates, dead programmes).
• Platform risk: medium. Commission rates get cut with a week’s notice.

Amazon Associates UK is the default choice and usually the wrong one: commission rates for most categories sit in low single-digit percentages, so you need a lot of clicks for very little. Software, hosting, insurance and service programmes typically pay far better per click. Check the current UK fee schedule before you build a whole category around it.

3. Sponsored posts

• Time to first pound: fastest of the six. A four-figure invoice is possible before your ad revenue buys lunch.
• Weekly admin tax: the highest. Pitching, briefs, revisions, disclosure, chasing payment at 60 days.
• Platform risk: low on tech, high on relationships.

This is the route people abandon, not because it fails but because the admin never stops. Every pound is re-earned from scratch next month.

4. Digital products

• Time to first pound: the worst of the six.
• Weekly admin tax: low after launch, spiky around support and refunds.
• Platform risk: low if you own the list and the checkout.

Templates, printables and short courses carry the best margin, and they need an email list before they need traffic. Build the list first or you are launching to nobody.

5. Services sold from the blog

• Time to first pound: very fast, second only to sponsored work, and often quicker in practice if you already have a sellable skill.
• Weekly admin tax: medium, and it is client work, not blog work.
• Platform risk: lowest. You need readers, not volume.

Twelve of the right readers a month beats 12,000 of the wrong ones. If you can do a thing people pay for, this is the unglamorous answer.

6. Memberships and paid newsletters

• Time to first pound: medium, once you have a list that trusts you.
• Weekly admin tax: permanent. You have sold a deadline.
• Platform risk: medium, depending on how easily subscribers export.

Predictable monthly revenue is lovely. A content commitment that does not care about your work trip is exactly what a day-job schedule breaks against.

Budget the hours before you pick the route

Write down your actual weekly capacity in evenings and weekend blocks, then halve it. The halved number is your real budget, because school plays, on-call rotas and flu exist.

Six hours is a workable week: two hours of keyword and topic research plus outlining, two hours drafting, two hours editing, publishing and promotion. That produces one solid post a week and a newsletter a fortnight. Four hours produces a fortnightly post. Both are fine. Pretending you have twelve is not.

Then apply the natural planning model to the post itself, because “write blog post”is a project, not a next action, and projects stall silently. Purpose (why this post exists), outcome (what a reader can do afterwards), brainstorm, organise into an outline, then the actual next action, which might be “open the outline and write the 300 words under heading two”. That single reframe is the difference between publishing weekly on five hours and owning fourteen drafts at 60 per cent and no revenue. The blocker is almost never writing speed.

A capture-to-publish pipeline that survives a busy week

Ideas arrive in the shower, on the 07:42, and three minutes into a meeting you cannot leave. Then they evaporate. Idea capture is the cheapest lever a part-time blogger has, and the test is the same as for anything else: can you get a headline out of your head and into a trusted inbox in under five seconds, phone locked, hands busy? If it takes longer, you will not do it under pressure. Set up fast capture on your phone or a card in your pocket and a blank-screen evening turns into an editing evening.

Bloggers who stall at month four almost always stalled at idea supply first.

Run a weekly review on the blog itself, not just work: ideas move to outlines, outlines to drafts, drafts to scheduled, and anything untouched for two reviews gets killed. Deleting an idea is a decision, and decisions cost less than open loops. Batch the work too: outline three posts in one sitting, draft in another. Restarting cold every evening is where the hours go.

Keep the editorial calendar somewhere you will genuinely look. A project app works; so does a printed index card in your back pocket. Whichever you can see without unlocking anything.

What it costs to run a UK blog for a year

The predictable lines are a domain renewal, hosting, a theme, an email platform, and images. Domains are small money annually. Shared hosting runs from a few pounds a month, managed WordPress hosting considerably more, and email platforms are the sneaky one: free tiers typically end somewhere between 500 and 1,000 subscribers, after which the price steps up with list size. Price all of these yourself at the time you buy, because the numbers move.

Free tiers do genuinely work at the start. The point where they start costing you is when they block a custom domain, restrict ad code, or cap sends.

Platform exit cost is a monetisation decision, not a technical one. Some hosted platforms limit display ads, affiliate links or how cleanly your posts and subscriber list leave. Check the export before you publish fifty posts, because a migration is a weekend of link fixing, image re-uploading and redirect mapping that produces no new content and no revenue. Self-hosted WordPress is dull and portable. Dull and portable wins.

Where beginners overspend: premium plugins, a paid course, and a redesign, all before a single post has earned anything. Darren Rowse made the same point about assets over aesthetics years ago, and it holds up; there is more on that in our ProBlogger book review.

Tax and disclosure rules UK bloggers keep getting wrong

HMRC’s trading allowance lets you receive up to £1,000 of gross trading income in a tax year without reporting it. Above that, you register for Self Assessment by 5 October following the end of the tax year in which you started, and file online by 31 January. The details and current rules are on the gov.uk trading allowance guidance. Check it yourself, since allowances change at Budgets.

Keep records from day one: income by source, and hosting, domain and tool costs as allowable expenses. Gifted products sent for review can count as income at their value, which surprises people the first time an accountant mentions it. The VAT registration threshold is a long way off for most, but know it exists, and check the current figure in the VAT registration guidance on gov.uk.

On disclosure: sponsored content and gifted items need to be clearly labelled, and the ASA expects an identifier such as “Ad”up front, where a reader sees it before engaging with the content. The ASA’s influencer guidance is the source to read. Affiliate links need disclosure too under consumer protection law. Burying it in a footer is not disclosure.

Then the plumbing: a working cookie consent banner and a privacy policy once analytics or ad networks are live, real opt-in for email (no pre-ticked boxes), and an eye on US affiliate payouts, where currency conversion and minimum payout thresholds can leave a small balance sitting in an account for months.

Mistakes that keep blogs at zero

Counting posts and word totals is measuring activity. Revenue per published post, email signups per month and posts holding a top-ten position are output, and with six hours a week the distinction is the whole game. If ten posts in a category have earned nothing in six months, that is data telling you to change route, not to write harder. Our guide to measuring output rather than activity goes further into how to set those measures.

The other four, briefly. Choosing a niche with no commercial intent, so traffic arrives and nothing sells. Bolting on a second income route before the first works, doubling the admin for the same money. Rebuilding the site instead of publishing, which is the most respectable form of procrastination there is. And quitting at month five, which tends to be the month before search traffic starts compounding.

Work out how to make money blogging in that order: hours first, one route second, admin tax third. Six months of that beats three years of good intentions and a beautiful theme.

Frequently Asked Questions

How long does it take to make money blogging?

First pounds commonly arrive somewhere between month three and month twelve, depending entirely on route. Sponsored work or services sold from the blog can pay within weeks if you already have a skill and an audience of any size. Display ads and affiliate income are gated on search traffic, which usually takes six to twelve months of consistent publishing before it means anything.

How much traffic do you need before a blog earns anything?

Less than you think for services and digital products, far more for ads. Google AdSense and Ezoic will accept small sites at low rates; Mediavine’s Journey tier sits around 10,000 monthly sessions and Raptive at roughly 100,000 monthly pageviews, though both have changed requirements before, so verify current figures with the networks. Affiliate income depends on intent rather than volume, so 2,000 well-targeted readers can out-earn 20,000 casual ones.

Do I need to tell HMRC about income from blogging?

If your gross trading income stays under HMRC’s £1,000 trading allowance for the tax year, you generally do not need to report it. Above that, register for Self Assessment by 5 October after the end of the tax year you started, and file online by 31 January. Gifted products received for review can count towards that total, so record them at value, and check the current gov.uk guidance because allowances change.

How many hours a week does a blog need if I have a full-time job?

Around six hours a week supports one solid post plus a fortnightly newsletter: two hours research and outlining, two drafting, two editing, publishing and promotion. Four hours a week works at a fortnightly publishing pace. The trick is protecting named blocks in the calendar rather than hoping for spare evenings, and halving your optimistic estimate before you commit to a schedule.

Which way of making money blogging works best for a brand new blog?

Selling a service you can already deliver, because it needs readers rather than traffic volume and pays within weeks. If you have no service to sell, affiliate content on genuinely commercial topics is the next best start, with display ads added later purely because they cost almost no admin once installed. Avoid launching digital products first; they have the longest time to first pound and need an email list you do not have yet.

The post How to Make Money Blogging Around a Full-Time Job appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

Notion lock-in is not about whether there is an export button. There is one, it works, and it will hand you a zip file. The real question behind every Notion lock-in export argument is narrower and more useful: do the exported files still run your GTD system on Monday morning, or do you now own a folder of readable text and a broken machine?

The honest conclusion, up front. Your words travel fine. Your structure does not. Databases flatten into CSVs, relations become page-title strings, formulas export as whatever number they happened to show on the day, and the graph you spent two years building is the part you rebuild by hand. That rebuild time, measured in hours, is your actual exit cost. Licence fees are a rounding error next to it.

What people actually mean when they worry about lock-in

Lock-in gets argued in the abstract on Reddit and Hacker News, and explained mechanically in Notion’s own help docs. Neither helps you decide anything. A GTD system holds the open loops you have agreed to stop carrying in your head, so the question is a trust question: if this workspace disappeared on Thursday, would you still know what you had committed to?

Notion’s position is reasonable enough. Import and export both exist, and the company documents the process in its help centre guide to exporting content. What most people miss is the other half of that page: a workspace owner can switch export off entirely under Settings then Security. If you keep your personal GTD system inside your employer’s workspace, you may have no export route at all, and no warning until you need one.

Worth knowing, and worth not over-claiming: the UK GDPR right to data portability, explained by the ICO, covers personal data you provided to a controller. It is not a legal lever for prising your team’s project notes out of a company workspace. Assume the technical route is the only route.

The three export formats, and which one you actually want

Notion offers Markdown and CSV, HTML, and PDF. They are not interchangeable.

Markdown and CSV is the one to use as your working archive. Plain text pages, tables as CSV rows, attachments in folders. Every serious note app imports Markdown, which makes it the sane base for a move to Obsidian, Apple Notes, Bear, Craft or anything else on a shortlist of Evernote alternatives with real migration costs.

HTML preserves more of what you see: callouts, toggles, columns, and internal page links that still resolve between the exported files. Lovely to read, miserable to edit. Take it as a second, read-only archive, not as the thing you migrate into.

PDF is presentation only. It is also the format with a plan dependency: whole-workspace PDF export sits behind paid plans, per Notion’s documentation at the time of writing. Do not build a backup strategy on it.

Three toggles decide whether your hierarchy survives: include sub-pages, create folders for sub-pages, and include databases (choose everything, not just the current view). Miss the sub-pages toggle and you export the top of your tree and none of the branches. People do this, notice six months later, and by then the workspace has moved on.

What survives the export, and what quietly does not

Survives in usable shape

Page text, headings, bullet and numbered lists, checkboxes as Markdown checkboxes, tables as CSV rows, most file attachments, and the folder hierarchy if you ticked the right box. Read the export and you can still tell what you were thinking. That matters more than people give it credit for.

Degrades

Databases become flat CSV files. One file per database, one row per page, columns for properties. Everything you built on top of that data (views, filters, sorts, grouping, board layouts, calendar overlays) does not exist in a CSV. A GTD workspace with an Inbox database, a Projects database and a Next Actions database exports as three unrelated CSVs plus a folder tree of Markdown files. Your single trusted inbox is now three spreadsheets that no longer talk to each other.

Breaks outright

Relations and rollups are the real lock-in, not the text. Take a freelance consultant with a client database of 40 rows, each client linked to project pages, with a rollup showing invoiced totals. The export gives you 40 rows of plain text, a rollup column showing numbers with no live source underneath them, and client-to-project links reduced to page titles. The numbers are a photograph. The links are a suggestion.

Formulas behave the same way: they export as their computed value. That looks completely fine on export day and is dead the moment your data changes. If you run formula-driven “due today”or “available now”views for your next actions, assume those views do not travel. Not degraded. Gone.

Also on the casualty list: synced blocks, which duplicate their content into every location rather than staying one source; database templates; button automations; and anything driven by Notion AI.

The forgotten stuff

Comments, page history, reminders, and @mentions of people. Meeting notes where the decision lives in a comment thread export as a page with the decision missing. Internal links inside Markdown exports frequently point back at notion.so URLs rather than at your local files, so your carefully cross-referenced reference library becomes a set of dead ends the day your access ends.

Score the export against the five jobs your system has to do

This is the part nobody runs. Do not ask “did everything export”. Ask whether the export can do the five jobs a GTD system exists to do, the same five used to compare note-taking apps for GTD.

• Time-to-captured. In the target app, on your phone, locked screen, one hand: how many seconds from intent to saved? Under five is a practical working benchmark rather than an official rule, and it is the one that decides whether you keep using the thing. The mechanics of hitting it are covered in this guide to capturing an idea in under five seconds.
• One trusted inbox. Does the archive leave you with a single processing queue, or fifteen scattered CSVs and a folder tree? If you have to remember which file a loop lives in, you do not have an inbox.
• Retrieval from half a memory. This is where technically complete exports fail hardest. Every byte can be present and you still cannot find the thing, because you used to find it by scanning a board grouped by client, and now it is row 212 of a CSV with a filename like Untitled 3c8f2a.md. Test with three real items you half-remember, never with tidy demo content.
• Exit cost. Count the hours to rebuild relations and views. Then ask whether you would ever willingly do it twice. If the answer is no, you are not portable, you are just told you are.
• No daily admin tax. If the new home needs weekly tidying, tagging and status hygiene to stay trustworthy, the migration failed even if every file arrived.

Old lesson, still true: the system you trust is the one that survives changing tools. Index cards and plain text files have a zero exit cost, which is why hybrid paper setups like the hPDA keep outliving whichever app is fashionable that year.

The export and verification drill you can run this weekend

1. Run a full-workspace export as Markdown and CSV, with sub-pages included, folders for sub-pages on, and databases included in full.
2. Run a second export as HTML and keep it as your readable archive. Two formats, one afternoon.
3. Anything sizeable arrives as an emailed download link rather than an instant file, and that link expires. Check the current window in Notion’s help centre before you plan around it, and download it the same day.
4. Spot-check ten pages, chosen badly on purpose: one heavy database, one project page full of relations, one reference page with attachments, one meeting note where the substance is in the comments, and six at random.
5. Open the CSVs in a spreadsheet. Confirm relation columns, dates, checkbox fields and multi-select values came through in a shape you can actually use. Date formats are a common nasty surprise.
6. Then the real test: work from the archive for a week. Process one genuine inbox to zero using only the exported files. You will find the breakages in an hour instead of during a forced migration at the worst possible moment.
7. Set a repeat. A quarterly export, filed alongside your weekly review routine, takes minutes: one Markdown and CSV archive, one HTML archive, both dated, both dropped into cloud storage.

Build Notion so the exit stays cheap

You do not have to leave Notion to benefit from this. You have to build as though you might.

Keep projects and next actions in a simple structure and reserve relations and rollups for the places where they genuinely earn their keep, which is usually client work and money, not your reading list. Store real reference as files and plain text rather than as formula output or linked views of somewhere else. Name pages the way you would name a file on your hard drive, because that is exactly what they become: “2026-03 Acme rebrand scope”survives the export, “Untitled”does not.

Three signals it is time to move. The daily admin tax is rising and you are maintaining the system instead of using it. Search keeps failing you on things you know are in there. The whole thing only works when you are sat at a desk with two monitors.

Where people land varies, and the honest currency is rebuild hours rather than licence fees. Moving reference notes into a Markdown-native app is cheap, often an afternoon. Moving a project and action system into something like OmniFocus costs more, because you are recreating logic, though custom perspectives tend to replace the filtered views you lost. Moving everything to plain text and folders costs the least to maintain and the most in features you will miss for a fortnight and then forget.

Run the export this weekend. Work from it for a week. Whatever the Notion lock-in export debate says in the abstract, an hour spent finding the breakages now is the difference between a system you trust and a very tidy archive of things you used to be committed to.

Frequently Asked Questions

Does Notion’s export give you all your data?

It gives you all your page content, and not all of your system. Text, lists, tables and attachments come through; comments, page history, reminders, synced-block relationships, database templates and automations generally do not. Treat the export as a readable archive of what you wrote, not a working copy of what you built.

What happens to Notion databases, relations and rollups when you export?

Each database becomes a flat CSV file: one row per page, one column per property, no views, filters, sorts or grouping. Relations export as page-title text rather than live links, and rollups export as static numbers with nothing feeding them. Formulas export as whatever value they showed at the moment of export, so they are accurate that day and stale immediately afterwards.

Should you export as Markdown, HTML or PDF?

Markdown and CSV for anything you might migrate, because almost every note app imports it. HTML as a second archive if you want the visual structure and working internal links preserved for reading. PDF only for documents you intend to share or print, and note that whole-workspace PDF export is tied to paid plans.

Can a workspace owner stop me exporting my Notion data?

Yes. Notion’s documentation describes a “Disable export”setting under Settings then Security that a workspace owner can switch on. On a company workspace, that can leave you with no export route for anything you have stored there, which is a good argument for keeping your personal GTD system somewhere you control.

How often should I back up a Notion workspace I rely on for GTD?

Quarterly is enough for most people, tied to a weekly review you already do so it never becomes a separate chore. Export in Markdown and CSV plus HTML, date the folders, and keep at least the last two in cloud storage. If your work is client-billable or contractual, monthly is the safer cadence.

The post Notion Lock-In: What the Export Actually Loses appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The best books for entrepreneurs are the ones that change what you do on a Tuesday morning, not the ones that change what you think on a Sunday night. That is the honest test, and most reading lists never apply it. This piece picks eight, pairs each with one specific practice you install the week you finish it, then gives you a reading order and a six-week cycle so the practice survives past the point where the motivation wears off.

Short version of the conclusion: read a capture-and-review system first, read everything else second, and buy books more slowly than you read them.

Why most entrepreneur reading lists never change your week

You finish a good business book somewhere around 11pm, full of intent. The next morning you do one thing differently. By the second Monday, you are back to whatever you were doing before, with a new set of highlights you will never open again. Call it the second-week collapse. Motivation peaks at the final page and drains away before the new practice has had time to become automatic.

Business books fail founders in three predictable ways. Some are written for companies with a finance team and a head of people, so the advice assumes resources you do not have. Some are entertaining memoirs where the lesson is “be the sort of person this happened to”. And some are genuinely well argued but hand you no repeatable action at all, which is the sneakiest failure because it feels like learning.

The test used throughout this article comes straight out of GTD: what is the successful outcome, and what is the very next physical action? Apply that to a chapter and it splits fast. A chapter that produces “email five past customers this week with these three questions”is installable. A chapter that produces “think bigger about your market”is opinion, however good the opinion is. Read with a capture tool open and ready in under five seconds, and every idea lands as a next action instead of a yellow stripe on a page.

How these eight books were chosen (and what got cut)

Four criteria. The book has to hand you one repeatable practice. It has to survive contact with a one-person business, or translate cleanly into one. It has to still be accurate now, not just influential in 2011. And it has to reward a second read, because you will read it once for the ideas and once for the method.

Cut deliberately: hustle memoirs, billionaire biographies, and anything whose central mechanism is delegating to a team of twenty. Also cut, and this is where people disagree with me, most of the big corporate strategy titles. Good to Great is a fine book about large American companies and a poor book about your two-person consultancy. Measure What Matters sells OKRs, a quarterly goal ritual built for organisations big enough to need alignment between departments; run it alone and you have invented a slower to-do list.

Memoirs are not worthless, they are just a different job. They give you nerve, not process. If you want one that earns its place on that basis, our review of Duncan Bannatyne’s Anyone Can Do It goes through what a business memoir can install and what it cannot. If you are reading mainly for drive, the round-up of best motivational books that change what you do covers that ground properly.

On formats: paperback for anything you intend to mind-map, because flicking back across chapters is how you find the structure. Audiobook for narrative and mindset titles on a commute, with a voice note app for the three ideas worth keeping. Summaries are fine for deciding whether to buy, useless for installing anything, because the implementation detail is exactly what a summary strips out.

The 8 best books for entrepreneurs and the habit each one installs

1. Getting Things Done by David Allen

Capture, clarify, organise, reflect, engage. Read this one first and every book after it has somewhere to go. The habit you install is the weekly review, a fixed block where you empty every inbox and look at every project, plus one trusted capture point for open loops. The natural planning model (purpose, outcome, brainstorm, organise, next action) also works on books themselves, which is how “improve my sales calls”becomes “draft five past-behaviour questions before Thursday’s call”.

Best for

• Founders holding more commitments in their head than they can list on demand

Pros

• The only book here that gives you a filing system for the other seven
• Method is tool-agnostic, so it works on paper or in software

Cons

• Even the 2015 revision carries tickler files and filing cabinets you will translate
• Initial setup realistically costs you a weekend

2. The Mom Test by Rob Fitzpatrick

Published in 2013 and still the most efficient book on this list per page. The habit: a customer conversation script that bans pitching entirely and asks only about past behaviour. Swap “would you pay for this?”for “what did you do the last time this problem came up, and what did it cost you?”Run it across five conversations before you build anything. Compliments stop being data and start being noise.

Best for

• Anyone about to build a product, service or course on the strength of encouraging feedback

Pros

• Short enough to read in an evening and use the next morning
• The scripts are transcribable more or less verbatim

Cons

• Covers research, not selling, pricing or closing
• Examples skew towards software founders

3. The E-Myth Revisited by Michael Gerber

Gerber’s 1995 argument is that most small businesses are run by technicians who accidentally bought themselves a job. The habit: write down one repeatable process a week. Solo, the delegation chapters become documentation chapters, which is the translation exercise that makes half the books on this list usable. After a year you have fifty documented processes and a business that can be handed over, sold, or survive your flu.

Best for

• Freelancers and owner-operators who are the bottleneck on everything

Pros

• The systems-over-heroics point lands harder every year you stay small
• Process documentation pays off immediately, not just at hiring

Cons

• The pie shop narrative is repetitive and dated
• Franchise framing irritates plenty of service businesses

4. The Lean Startup by Eric Ries

Take the core loop and leave the rest. The habit: every new offer gets written as one testable assumption with a deadline attached. “Local accountants will pay £300 for a monthly bookkeeping review, tested by three signed clients by 30 June.”Not a plan, a claim with an expiry date. That framing alone kills more doomed side projects than any amount of strategy.

Best for

• Pre-revenue founders and anyone tempted to build for six months before selling

Pros

• Assumption-plus-deadline is genuinely portable to any business type
• Makes the cost of being wrong small and quick

Cons

• Written for funded software startups, and it shows
• Cohort analysis chapters are noise when you have eleven customers

5. Deep Work by Cal Newport

Newport’s 2016 case is that concentrated work is both rarer and more valuable than it used to be. The habit: two protected blocks a week, phone in another room, defended in the calendar like a client meeting. Not the phone face down on the desk. In another room. That detail is the whole practice, and the part people quietly skip.

Best for

• Founders whose important work only ever happens after 7pm

Pros

• Specific enough to schedule this week
• Pairs neatly with a weekly review that decides what goes in the block

Cons

• Written from a tenured academic’s diary, which you do not have
• Client-facing freelancers will halve the recommended block lengths

6. The War of Art by Steven Pressfield

Pressfield names the thing that stops you starting and calls it resistance. The habit: hardest task first, before email, and a one-page mind map of the book pinned where you actually start work, with branches for resistance, turning pro, and the first task of the day. Cheesy? A bit. It works because it gives the avoidance a name, and a named thing is easier to notice at 9:04am.

Best for

• Anyone doing creative or sales work they keep rescheduling

Pros

• Two-page chapters make it easy to reread in five minutes
• Condenses to a single page better than anything else here

Cons

• The final section on muses and angels loses a lot of readers
• Almost no method, just diagnosis

7. Atomic Habits by James Clear

The most quoted and least implemented book on most shelves. Habit stacking is the bit worth installing: attach the admin you avoid to an anchor that already happens daily. Invoices go out while the Friday kettle boils. Expenses get photographed when you lock the office door. Small, specific, tied to something physical you already do without thinking.

Best for

• People whose systems fail on consistency, not on design

Pros

• Habit stacking transfers directly onto business admin
• Clear writes plainly, with usable worked examples

Cons

• Examples lean heavily towards personal life, so you translate
• Little on multi-step work, which is most of what a business is

8. Profit First by Mike Michalowicz

Take your profit and tax out first, run the business on what is left. The habit: separate current accounts, one fixed transfer day each month, and a tax pot you never dip into. In the UK that means sizing the pot against a self assessment bill with payments on account due on 31 January and 31 July, dates set out on GOV.UK’s guidance on payments on account. Challenger banks make the multiple-account part trivial now, which was the main practical objection when the book came out.

Best for

• Sole traders and directors who find out what they owe in January

Pros

• Behaviourally clever: it uses constraint instead of discipline
• Bank-account mechanics take an hour to set up once

Cons

• Tax and banking detail is US-centric throughout
• The suggested percentages are a starting point, and your accountant is the one to confirm them

A reading order that builds instead of scattering

Reading order matters more than which titles you pick. Start with Getting Things Done, because everything you read afterwards needs a trusted place to land. Read mindset books first and the good ideas evaporate within days, since there is nowhere to put them.

After that, sequence by stage. Pre-revenue: The Mom Test, then The Lean Startup. First customers: Deep Work, because delivery is now the constraint. Approaching a first hire or a plateau: The E-Myth Revisited and Profit First. The War of Art whenever you notice yourself rescheduling the same task for the third week running.

Pace it at one book per six weeks. Four weeks reading roughly 30 to 40 pages a day, then two weeks running only the extracted practice with no new book started. That gives you eight books a year, all implemented, which beats twenty-four books and nothing changed. Book the implementation weeks in your calendar before you start reading, not after you finish, because after you finish you will be too excited to protect them.

When two books contradict each other, and they will, pick one operating principle and run it for a quarter. Newport wants fewer, longer blocks; Clear wants tiny daily repetitions. Both work. Running both at once works for nobody.

How to make a business book stick past week two

Mind-map the book to a single page. Chapters as branches, one action per branch, nothing else. Highlighting feels productive and produces an unprocessed inbox, which is just more open loops wearing a costume. A one-page map is retrievable months later from half a memory, which is the actual job of book notes.

Then apply the one-action rule: one next action per chapter, everything else goes to someday/maybe. Run the natural planning model on the survivors so each one becomes a small project with a defined outcome rather than a vague intention. At 30 days, make a call on each practice. Keep it, adjust it, or drop it and note why, because “this book did not work for my business”is useful information you would otherwise re-learn in two years.

Keep the maps somewhere searchable. A tagged notebook in whichever note-taking app fits your GTD system works; so does a wall of index cards if you prefer paper, and the hPDA templates are fine for that. For ongoing input between books, a handful of good productivity blogs to follow beats another purchase, because blogs give you one idea at a time and one idea at a time is the rate you can actually absorb.

Mistakes founders make with business books

Buying faster than you read. Six unread books on a shelf become a guilt-generating open loop, and that guilt quietly reduces how much you read, exactly the way an overflowing inbox reduces how much email you process. Buy in slower batches than you read. Clear the shelf by giving away anything you have not opened in a year, without ceremony.

Confusing highlights with decisions. An unprocessed highlight is not knowledge, it is a deferred judgement.

Importing corporate playbooks wholesale: OKRs, org charts, quarterly planning offsites for a business of two. Translate or skip. And the most common one of all, reading about productivity instead of running the weekly review you already know you should be running. If you have skipped it twice this month, close the book and go and do it. Then pick one of these titles, and read the whole thing with the next action question in your hand.

Frequently Asked Questions

Which book should an entrepreneur read first?

Getting Things Done, unless you already run a reliable capture and weekly review system, in which case start with The Mom Test if you are pre-revenue or The E-Myth Revisited if you are the bottleneck. A system book first gives every later book somewhere to put its ideas. Mindset first tends to produce a good fortnight and nothing after it.

How many business books should I read in a year?

Eight is a sensible target on a six-week cycle: four weeks reading, two weeks implementing with no new book started. Reading thirty and implementing none is a hobby, which is fine, but do not confuse it with running a business. Fewer books, properly installed, beat a long finished list.

Are audiobooks as useful as print for business books?

For narrative and mindset titles, yes, and a commute is otherwise dead time. For method books you intend to mind-map, print wins, because flicking back across chapters is how you find the structure worth mapping. If you do listen, capture the actions as voice notes at the time; retrospective recall a week later gets you almost nothing.

Why do business books stop working after a couple of weeks?

Motivation is at its highest on the final page and fades before the new practice has become automatic. Nothing is wrong with you or the book. The fix is structural: schedule the implementation week in your calendar before you start reading, and cut the book down to one action per chapter so there is less to sustain.

Are the best books for entrepreneurs different for solo founders?

The titles are mostly the same, but you read them as a translation exercise. Delegation chapters become documentation chapters, team rituals become a weekly review block you run alone, and anything requiring a department gets skipped without guilt. Judge every chapter the same way: does it turn an open loop into a defined next action, or is it just well-argued opinion?

The post Best Books for Entrepreneurs: 8 That Change Habits appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.

The only productivity number worth keeping is the count of loops you closed this week. Everything else measures intent.

This piece shows you how to measure productivity by output, not activity, inside a working GTD system rather than in the abstract. The conclusion, up front: define each project’s done-condition as a past-tense sentence someone else could verify, count four things during your weekly review (projects closed, deliverables shipped, decisions settled, loops reopened), and turn off every completed-task total and streak your apps are showing you. That is the whole method. The rest is the detail that stops it going wrong.

Ticking Off Tasks Is Not Producing Anything

Next actions in GTD are inputs by design. A next action is the smallest physical, visible step you can take, which makes it a brilliant unit for getting started and a useless unit for measuring delivery. When you count completed next actions you are counting how many times you intended to move something forward. Intent is not output.

The measurable unit is the closed loop. David Allen’s framing of open loops is the sharpest test available: a loop is anything you have committed to that is not yet where it belongs. It closes when the result leaves your hands. Sent, filed, published, signed, handed over, decided and communicated. Not “nearly ready”. Not “drafted and sitting in a folder”.

Take a freelancer whose task app proudly shows 312 completed tasks across a month. Look at what actually left their hands: one proposal sent, two articles filed with the client, one invoice raised. Four outputs. The 312 is motion, and the gap between the two numbers is where the feeling of being busy and broke lives at the same time.

False signals get treated as productivity every day:

• Inbox zero. A processed inbox means you have made decisions, which is good. It does not mean anything shipped.
• Completed-task counts. Rewards granularity, punishes people who write bigger actions.
• App streaks and productivity scores. Measure app usage. Nothing else.
• Hours logged. Measures availability.
• Meetings attended. Measures presence, and often measures other people’s loops.

Then there is the rework trap. Fast activity frequently opens more loops than it closes: the hurried reply that triggers three clarifying emails, the deliverable shipped at 80 per cent that comes back with comments, the decision made without the one person who then reverses it. High activity with negative net loop closure is entirely possible, and it feels like the busiest week of your year.

Define Your Outputs Before You Measure Anything

You cannot count what you have not defined. GTD’s project start-up gives you a free test: write the successful outcome as a sentence in the past tense that a colleague could verify without asking you how it went.

“New pricing page live.””Q3 budget approved by the board.””Supplier contract signed and filed.”Those are verifiable. If you cannot write that sentence, the project is not measurable, and in my experience that is usually why it has been sitting on your list for five months. It stalls because it has no finish line, not because you lack discipline. Motivation gets blamed for a definition problem.

Three kinds of output, and why the distinction matters

• Deliverables: things handed over. A report issued, code released, an invoice sent, a client call delivered.
• Decisions: things settled and communicated, so nobody has to think about them again. Choosing the supplier counts only when the other two have been told.
• Artefacts: things that now exist and did not before. A documented process, a template, a tested backup, a hiring brief.

Vague projects produce none of the above. “Sort out the website”is a permanently open loop pretending to be a project. Split it and you get three countable outputs: new pricing page live, contact form tested and receiving enquiries, old blog posts redirected. Same work. Three finish lines instead of nought.

Try this before you measure anything. Open your project list and read each entry. Mark every one where you cannot name the thing that will exist, move or be settled when it is done. Those marked projects are your real backlog, and they are the reason your output count will look thin in week one.

The Weekly Output Count, Bolted Onto Your Review

Do not build a reporting habit. Build a column. The weekly review already exists in your system, you are already looking at your project list, and that is the natural moment to count what closed. A separate tracking ritual fails for the same reason a note app with a daily admin tax in tags and statuses fails: anything that costs maintenance time gets quietly abandoned inside a fortnight.

Record four numbers, nothing more:

1. Projects closed. Done-condition met and verified.
2. Deliverables shipped. Things that physically left your hands this week.
3. Decisions settled. Decided and communicated.
4. Loops reopened. Work that came back, was rejected, or needed redoing.

Keep it to one page. Analogue wins here and it is not nostalgia: a single index card or one notebook page holds a week’s tally with no syncing, no configuration and no temptation to spend Sunday evening building a dashboard instead of doing the work. If you want something pre-ruled, the printable hPDA cards on this site take a four-column tally without modification. A digital note is fine too, as long as it stays one note.

Now the discipline that most people skip. Run it for four weeks before you conclude anything. Four rows, four columns, no interventions, no new system, no changing your project list to make the numbers look better. One good week and one wiped-out week tell you nothing. A four-week baseline tells you your realistic rate, and a realistic rate is what makes next quarter’s commitments honest.

Activity Metrics Worth Keeping, and the Ones to Switch Off

Not all activity data is rubbish. A few leading indicators protect output rather than impersonate it.

Time to captured. How many seconds from having the thought to it being safely in your system, with your phone locked and your hands full. Under five seconds is a practical working benchmark rather than an official rule. Slow capture means lost commitments, and lost commitments are lost output later. If you want to see how much that varies by tool, the comparison of note apps scored on capture speed covers it properly.

Cycle time. Date captured to date the loop closed. It shows you where work stalls without counting effort at all, and it is brutally informative on projects you thought were “nearly done”six weeks ago.

Waiting-for list length. The honest measure of work you cannot finish alone. A growing waiting-for list with flat output is not a personal performance problem, and it is the single most useful thing to take into a conversation with a manager or a client.

What to delete: completed-task totals, streaks, badges, productivity scores, screen-time dashboards. Task apps push these hard because churn looks like engagement. Turning those displays off is a measurement decision, not a cosmetic one, and if your app lets you build custom views, spend that effort on views that show stalled projects instead. The custom OmniFocus perspectives guide is one way to do that.

Keystroke logging and presence tracking deserve a blunter verdict. Skip them. Beyond the fact that they measure nothing you can ship, UK employers monitoring staff have obligations under data protection law, and the ICO’s guidance on monitoring workers sets out that monitoring must be lawful, fair and proportionate. Check the current version before anyone installs anything.

Measuring Output When the Work Is Invisible or Shared

The objection to output counting is always the same: my work does not produce widgets. Fair. It still produces something.

Thinking and planning work. Run the natural planning model (purpose, outcome, brainstorm, organise, next actions) and treat the finished plan as a genuine output. A written plan that someone else could act on is an artefact. A decision made and communicated is a deliverable. The David Allen Company’s own material on the methodology is worth reading if you have only ever met GTD through blog summaries.

Teams. Count at the boundary where work leaves the team, never per person. Releases shipped, client reports issued, cases resolved. Per-person ticket counts reward people for picking easy tickets and punish the person who spent three days unblocking everyone else. If you want individual data, use cycle time on the team’s shared work, not volume on individuals.

Email-heavy and support roles. Messages handled is the classic vanity number. Do the GTD inbox pass properly, deciding for each item whether to do it now, delegate it, defer it into your system, file it as reference or delete it, then measure resolved threads and reference filed. Two hundred messages touched and forty threads resolved is a real week. Two hundred messages touched and eight threads resolved is a warning. Your mail client affects how fast that pass runs more than most people expect.

Long projects. A three-month build with one output at the end gives you eleven weeks of zeroes and one week of triumph, which is useless as feedback and corrosive when you are already feeling overwhelmed at work. Define interim outputs at roughly fortnightly intervals: schema agreed and documented, staging environment live, first module reviewed and signed off. Each one has a verifiable past-tense sentence. Each one counts.

Where Output Measurement Goes Wrong

Gaming the count. Split “quarterly report issued”into nine sub-projects and your tally triples overnight. The done-condition test is the defence: if the outcome sentence is not something a colleague could independently verify as a real result, it is a next action wearing a costume.

Punishing quality. Ship fast, ship broken, count the win, absorb the complaint next week as new work. Record reopened loops honestly in that fourth column and the pattern surfaces immediately. Otherwise a high output count hides a high rework rate, which is precisely the failure that activity metrics get accused of. A week of six shipped and four reopened is worse than a week of three shipped and none.

Ignoring maintenance. Backups tested, dependencies patched, the invoice chased before it went bad. No new artefact, no obvious output, but the absence of it produces very expensive loops later. Keep a short maintenance line on the card rather than pretending it did not happen, and never let the tally become an argument for skipping it.

The honest answer. Sometimes four weeks of data show one or two closed projects a month and nothing hidden. That normally means your projects are too big, not that you are lazy. Split them, rewrite the done-conditions, count again. The numbers usually move within a fortnight, and the feeling of being permanently behind moves with them.

Measure productivity by output, not activity, for one quarter and you will lose the comfort of a large green number in an app. What you get instead is a small, true one, plus a rate you can plan against. Start at your next weekly review with four columns and an honest count of what actually left your hands.

Frequently Asked Questions About Measuring Output Instead of Activity

What does it mean to measure productivity by output rather than activity?

It means counting finished results that left your hands, not the steps you took towards them. In GTD terms, you count closed loops: projects whose done-condition has been met and whose result has been delivered, decided or filed. Tasks ticked, hours worked and emails answered are activity, however satisfying the totals look.

How do I count output if my work is thinking, planning or decisions?

Run the natural planning model and treat the finished plan as the output. A documented plan someone else could act on, a decision made and communicated, or a recommendation written up all pass the done-condition test. Write the outcome as a past-tense sentence (“pricing approach agreed and circulated”) and it becomes countable.

Are completed-task counts in a task app a useful productivity metric?

No. They reward whoever writes the smallest next actions and tell you nothing about delivery. Productivity metrics that track output need a verifiable result behind them, so switch off completed-task totals, streaks and productivity scores and count shipped deliverables instead.

How often should I measure output, and how long before the numbers mean anything?

Weekly, during your existing GTD weekly review, on one page. Give it four weeks before you draw a conclusion, because a single strong or ruined week says nothing about your rate. After a month you have a baseline honest enough to plan commitments around.

Can you measure output for a small team without individual tracking?

Yes, and it works better. Count deliverables at the boundary where work leaves the team, such as releases shipped or client reports issued, rather than tickets closed per person. Add cycle time and the length of the shared waiting-for list, and you can see where work stalls without monitoring anybody’s keystrokes. The same output-per-hour logic sits behind the UK productivity figures, which explain why national growth stalled despite longer hours worked.

The post Measure Productivity by Output, Not Activity: A GTD Guide appeared first on Getting Things Done GTD with Personal Development and Motivation for Success.