Proactive Brief

Every tool that holds what your team knows waits to be asked. Proactive Brief comes to you instead, and takes what changed to the one person it concerns.

August 17, 2026 7 min read

Every tool you use to hold what your team knows is passive. The wiki, the doc, the decision log, the channel history: each one sits and waits for you to come and ask it. They all rest on the same assumption, that at the moment you need something, you will remember it exists and go get it. That assumption is where all of them quietly fail.

The problem was never writing things down. Teams write plenty down. The problem is that a record you have to remember to retrieve is worth almost nothing at the one moment it matters, because that is exactly the moment it does not occur to you to look. Picture the situation precisely. You are about to ship a change that quietly reverses a decision the team made in the spring. You are not going to open the decision log to check, because as far as you know there is nothing to check. Passive knowledge only ever helps the person who already suspects the answer is there. Everyone else walks straight past it.

The agent that comes to you

Which is why one of the sixteen agents behind Brief, Proactive Brief, is built around this. It watches the decisions your team has on record and the signals moving around them, and when a change bears on a commitment you already made, it does not broadcast a note to the whole team and hope the right person notices. It works out who the change concerns, usually the person who owns the affected decision, and takes it to that one person. You do not have to know to ask. That is the whole point of it: it closes the gap between "the answer was on record" and "the answer reached the person who needed it."

The instant objection is that this is just more notifications, and it would be, except that the difference is the entire design. Three rules govern every time it opens its mouth, and each one is there to make it a colleague rather than a feed.

It earns the interruption. It does not fire on activity, it fires on meaning. A change becomes a message only when it touches a decision you actually made, and even then it is rationed: at most a couple of interruptions in a week, and several related items collapse into one note instead of arriving as five. A team that has decided nothing hears nothing. Silence is the default, and an interruption has to be paid for out of a small budget, which means the ones that arrive are worth the tax they charge on your attention.

It does the work, you make the call. When something changes, it does the reading. It finds the decision the change bears on, works out whether the two are genuinely in tension rather than merely similar, and brings you the short version. That distinction is most of the job and the easy thing to get wrong: a new piece of work that implements a past decision looks, on the surface, almost identical to one that contradicts it, and telling those apart is what separates a useful nudge from noise. What is left for you is the single thing a person should keep, the judgment. "You decided this because of that. Since then, this changed. Still true?"

Every message is a next action. It never arrives just to inform you. Each one carries a specific decision and a link to act on it, confirm it, dismiss it, or let it wait, rather than something to read and file. Anything you defer is not turned into per-item homework; it waits in a review queue that stays yours to clear, and the nudge to come back is about the queue as a whole, never a peck for each candidate. You can let any single one wait, which is the only honest way to ask for someone's attention.

What it actually catches

In practice it surfaces the things you would never have gone looking for, because you had no reason to think they were there. A decision whose deadline or condition is coming up, worth a second look before it lapses on its own. A customer theme that has quietly started to build against an assumption one of your live decisions depends on. A change someone just shipped that sits at odds with a call the team made months ago and reproduces the very thing you had moved away from. Each one taken to a single person, usually the owner of the decision it affects, with the context already assembled and a clear thing to do next.

It ends up feeling less like software and more like the one colleague who has been at the company long enough to say, in the meeting, "we tried that in the spring, and here is why we stopped," except that this one never leaves, never forgets, and never makes remembering your job.

Why you actually need it

Everything else about a record is capture and storage, and those matter. But a decision you wrote down and were never reminded of at the moment it counted is a decision you effectively made twice: once on purpose, and once by accident, when you undid it without knowing it was there. The writing was never the point. The point was to have the thing come back to you, on its own, at the moment you would otherwise walk past it.

So the question worth sitting with is not whether your team's decisions are written down somewhere. Plenty of them are. It is whether anything is going to bring the right one back to you at all, without your having to remember it exists, or whether that, still, is a thing you are quietly left to carry on your own?

Frequently asked questions

What is Proactive Brief? Proactive Brief reaches out when a change bears on a decision your team has made, instead of waiting to be asked. It watches the decisions and signals a team has on record, works out who the change concerns, and takes it to that one person rather than posting it to the whole team.

How is this different from notifications? Notifications fire on activity; Proactive Brief fires on meaning. It only speaks when a change touches a decision you actually made, it limits how often it can interrupt, it collapses several related items into a single message, and every message lands on a decision you can act on rather than information to file away. Silence is the default and an interruption has to be earned.

Why isn't storing decisions enough? Because a record you have to remember to look up is worth little at the moment it matters most, which is exactly the moment you have forgotten it exists. The time you are about to contradict a past decision is the time it will not occur to you to check for one. The value is realized only when the right decision reaches you unprompted and in context, rather than waiting in a log for you to think to query it.

What kinds of things does Proactive Brief surface? Things you did not know to look for: a decision whose deadline or condition is approaching and may be worth re-confirming; a customer or research theme that has started building against an assumption a live decision depends on; and a change someone has shipped that sits in tension with a call the team made earlier. Each goes to a single person, usually the owner of the affected decision, with the context and a clear next step attached.