I want to tell you about a system. Not a feature, not a workflow, not a hack — a system. It took three years to understand, and the understanding came not from building software but from watching how people actually work when nobody is measuring them.
Here is what I saw.
A person opens a task manager in the morning. She picks three things to do today. She closes the task manager and opens a timer. She starts a session. The timer has no idea what she picked. The task manager has no idea she's working. When the session ends, a third app plays a sound. A fourth app will ask her tonight how the day went — but it has no data, so it asks her to self-report, and she lies because she's tired and the truth is complicated. A fifth app tracks her goals for the quarter, but it has never seen a single session, a single task, a single reflection, so it shows her a number she entered three months ago and a progress bar she updates manually on Sundays when she remembers.
Five tools. Five closed worlds. The work moves through all of them, but the data doesn't. The insight doesn't. The feeling doesn't.
This is how most people work. Not because they chose it, but because nobody has built the alternative.
#The loop nobody owns
Every tool in the productivity space owns a piece of the process. Todoist and Things own capture and planning — brilliantly, in Things' case. Pomodoro apps own the twenty-five-minute countdown. Endel and Brain.fm own the sonic atmosphere. Daylio owns the evening mood check. Notion owns the quarterly review. Each tool is a room with no doors.
I spent a long time thinking about what would happen if the doors were open. If the task you chose this morning knew it was being worked on right now. If the timer knew which project it was feeding. If the sound adapted to where you are in the session, not just to your heart rate. If the evening reflection could show you what you actually did, not what you think you did. If the quarterly view could trace a line from today's forty-minute session all the way to the thing you said matters most in your life.
That is the Particle Loop. Six stages, one closed system, every stage feeding the next.
#The six stages
CAPTURE — "I need to do something."
A thought crosses your mind. You press a key. The thought becomes a task. It lands in the backlog. No decisions required. No project assignment, no priority level, no due date — unless you want one. The point is speed: the thought must leave your head before it costs you attention. Masicampo and Baumeister showed in 2011 that simply writing down a plan for an unfinished task provides cognitive relief nearly equivalent to completing it.1 The backlog is not a to-do list. It is a release valve for your working memory.
PLAN — "Today, this matters."
Morning. You open Particle. Yesterday's summary is there — what you did, what you didn't, how many particles you collected. Then the question: what is today's intention? You pull two or three tasks from the backlog into today. You order them. You have just built a playlist for your day. Not a schedule — schedules break before lunch. A playlist: this is the sequence in which I intend to move through the work. Gollwitzer's research on implementation intentions — "if situation X, then I will do Y" — shows that this act of planning switches behaviour from effortful conscious control to automatic cue-driven action.2 You don't have to decide what to work on next. You already decided. This morning.
EXECUTE — "I'm doing it now."
This is the particle itself. The timer starts. The sound starts. The world narrows. You are inside the work. The app disappears — not metaphorically but by design. Mark Weiser, the father of ubiquitous computing, said: "A good tool is an invisible tool. By invisible, I mean that the tool does not intrude on your consciousness; you focus on the task, not the tool."3 This is the standard we build to. When the timer is running, Particle should be the last thing on your mind.
Csikszentmihalyi's conditions for flow are met by structure: clear goal (the task you chose), immediate feedback (the timer, the sound shifting subtly), appropriate challenge (you set the duration), no distractions (the interface is gone).4 You are not using a productivity app. You are inside a room that holds your attention.
Some people count down. Some people count up. We built both, because the Flowtime movement taught us something the Pomodoro orthodoxy missed: rigid twenty-five-minute blocks break flow states as often as they create them. If you work until you naturally need a break, then break for a fifth of the time you focused, the rhythm matches your body — not a kitchen timer invented in the 1980s.5
COMPLETE — "I did it." Or: "Not today."
The session ends. Two paths. If the work is done: the particle counter increments. A quiet celebration — not fireworks, not confetti, not a tree that grew while you weren't looking. Just: one more particle, collected. The work of a life consists of many particles.
If the work is not done: it stays. No broken streak. No dead tree. No red badge. The task moves to tomorrow, or back to the backlog, or nowhere. You decide. The only thing Particle will never do is make you feel bad for stopping. We wrote seven thousand words about this in What Particle Refuses. The short version: guilt is not a productivity strategy. It is a retention strategy for apps that cannot earn loyalty through value.
REFLECT — "Was today meaningful?"
Evening. You trigger the closing ritual — not the clock, you. The day's particles appear. What you worked on. How long. Which projects moved. Then the triage: unfinished tasks go to tomorrow, back to the backlog, or away. Then, optionally, one line. How was today? Not for a dashboard. Not for a coach. For you, three months from now, reading back.
The Zeigarnik effect tells us that unfinished tasks occupy working memory like open browser tabs occupy RAM.6 The closing ritual closes the tabs. Everything is captured, triaged, put somewhere. The mind can rest — genuinely rest — because the system is trusted. Nothing fell through the cracks, because the system that holds them has proved, day after day, that it does not drop things.
ALIGN — "Am I closer to what matters?"
This is the stage no one else has built. It is also the one that makes everything else meaningful.
Every project in Particle belongs to exactly one vision — the thing you said matters most. Not a goal with a deadline. Not an OKR. A direction. The particles accumulate in projects. The projects feed the vision. Over weeks, over months, the shape of your work becomes visible. Not as a number. As a glow — how brightly a project shines is how strongly it serves the thing you care about.
Darwin did not track his hours. He worked four and a half hours a day for forty years — roughly sixteen thousand sessions — and produced the theory of evolution, plus fifteen books.7 He did not need a dashboard. He needed architecture: a wife who sorted his letters, a walk that structured his thinking, two games of backgammon that signalled the day was done, a study that nobody entered uninvited. The architecture held the work. The work, accumulated, changed the world.
Particle is the architecture. The loop is how the architecture breathes.
#Why the loop must be closed
An open system leaks. Data that lives in five apps is data that lives nowhere. The task manager doesn't know you worked for ninety minutes this morning. The timer doesn't know the session fed your most important project. The evening journal doesn't know what you actually did. The quarterly review doesn't know any of it.
A closed loop compounds. Every particle feeds a project. Every project feeds a vision. Every reflection informs tomorrow's plan. Every plan is better because yesterday's data is already there. The longer you use it, the more the system knows — not about productivity in general, but about you. How you work. When you work best. Which projects actually move when you give them attention. Which ones don't.
This is also why Particle's AI coach, Beam, can do things no other coach can. It has the complete picture — not self-reported, not approximate, but observed across every stage of the loop. It has seen your captures, your plans, your sessions, your completions, your reflections, your alignment. It can tell you, with evidence, that you are spending eighty percent of your energy on a project that serves two percent of your stated purpose. No coach who asks you to fill out a weekly form can do that.
#The loop and the Emma
We have written before about the Emma problem — the observation that every person who built a major creative life had a support structure, a holding architecture, an Emma who managed everything that was not the work so the work could happen. Darwin had Emma Wedgwood. Hemingway had the Finca. Murakami became his own monastery. Angelou rented hotel rooms. Most people have none of these.
The Particle Loop is the digital Emma. Not the emotional warmth — software cannot love you. But the architecture: the reliable, repeating, day-after-day structure that captures what needs capturing, plans what needs planning, holds the space while you work, celebrates what you finished, reflects on what the day meant, and keeps your life's direction visible even on the days when it feels invisible.
An Emma of Your Own described the principle. The Loop is the mechanism.
#What this means for you
If you are reading this and recognising pieces of your own workflow — the morning planning, the focused session, the evening reflection, the quarterly check-in — scattered across five apps that don't talk to each other, the loop is the answer to a question you may not have articulated yet: what if all of this was one thing?
It is one thing. It is six stages. It is a loop. And nobody else has built it, because building it requires believing that productivity is not about doing more. It is about knowing that what you did today is connected to what you care about most.
That is what Particle is for. Not sessions. Not timers. Not Pomodoros. Particles — small, meaningful units of focused work that accumulate into the shape of a life.
The work of a life consists of many particles. The loop is how they find their way home.
#References
#Footnotes
-
Masicampo, E. J., & Baumeister, R. F. (2011). "Consider It Done! Plan Making Can Eliminate the Cognitive Effects of Unfulfilled Goals." Journal of Personality and Social Psychology, 101(4), 667–683. DOI (opens in a new tab) ↩
-
Gollwitzer, P. M. (1999). "Implementation Intentions: Strong Effects of Simple Plans." American Psychologist, 54(7), 493–503. DOI (opens in a new tab) ↩
-
Weiser, M. (1991). "The Computer for the 21st Century." Scientific American, 265(3), 94–104. DOI (opens in a new tab) ↩
-
Csikszentmihalyi, M. (1990). Flow: The Psychology of Optimal Experience. New York: Harper & Row. ↩
-
Cirillo, F. (2006). The Pomodoro Technique. The technique was developed in the late 1980s using a tomato-shaped kitchen timer. The Flowtime method, documented by Zoe Read-Bivens (2015) and popularised by the Flowmo community, replaces fixed intervals with natural break points. ↩
-
Zeigarnik, B. (1927). "Über das Behalten von erledigten und unerledigten Handlungen." Psychologische Forschung, 9, 1–85. DOI (opens in a new tab) ↩
-
Pang, A. S.-K. (2016). Rest: Why You Get More Done When You Work Less. New York: Basic Books. Darwin's working hours and routine documented extensively in Chapter 1. ↩