A story about tools that gather, and people who decide

Hi. If you are reading this, there is a fair chance your day is currently spread across three places that do not talk to each other: a calendar other people have been writing in, an inbox that fills up whether or not you open it, and a list you quietly stopped trusting some time last month.

None of those is the problem on its own. The problem is that holding them together in your head is a job, and it is a job nobody assigned to you.

You have probably tried the fix. A new app, a clean board, a system with a name and a diagram. It works for a fortnight.

Then the setup becomes the work. Groom the backlog, re-sort the labels, keep the streak alive. The tool that was going to carry the weight starts asking you to carry it instead.

This is older than software. The pocket diary and the wall calendar did the same two things every planner since has done: they held what you had promised, and they showed it back to you.

That was an enormous invention, and it is also the whole trick. A page cannot read your mail. It holds what you wrote down, and nothing else — which means the remembering, the checking and the deciding all stayed with you.

Then the page moved onto a screen and gained new abilities. It could remind you. It could repeat. It could sit on every device you owned and agree with itself.

What it still could not do was read anything. It knew the meeting was at two because you had told it. It had no idea the meeting had moved, because that was in a thread you had not opened yet.

What changed recently is not that computers got faster. It is that software can now read ordinary language — a thread, an invitation, a half-written note — and act on what it finds there.

That is a genuinely new material to build with. For the first time the tool can go and look, instead of waiting to be told.

Most of what has been built with it answers immediately. You stop typing and it starts. Whatever happened to be on the screen is what it knows, and for about a week that speed reads as intelligence.

It is the wrong trade. An answer produced before anything was read is a confident guess, and a confident guess about your Thursday is worse than no answer at all.

Drift takes the other side of that trade. Ask for something and it goes and reads first — the thread, the day, the list, and the twelve months of your own mail sitting behind them — then comes back once it has something worth saying.

It is a little slower to start. It is considerably more useful when it arrives.

Drift stops and asks before anything reaches another person, and before it deletes something. Everything else — reading, and work inside your own account that you can undo — runs without interrupting you.

The card shows the whole thing before you approve it: every recipient, and the body in full. Approving a subject line is not consent to words you have never read. There is no setting that turns this off, because a safety boundary with an off switch is a preference.

Today Drift reads across Gmail, Google Calendar, Google Tasks, and Notion, and reaches further through connections you choose to add — Slack, Asana, Todoist, and Linear among them.

Inside, there are three places to stand and no dashboard. Chat is where you ask. My Drift is one vertical view of what is actually in front of you. Focus holds a single task and softens everything else away. You can also just text it, the way you would text a person who happens to keep track of things.

That is the shape of it. Drift gathers, does the work, and hands the decision back. No streaks, no scores, nothing engineered to pull you back in — it is there when you open it and quiet when you do not.

A wealth of information creates a poverty of attention. — Herbert A. Simon, 1971