Team Pulse

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

• Pulse sweep runs weekday mornings · 8am and keeps the Pulse dashboard fresh. Weekday mornings — reads the channels you named, updates what still needs you, and redraws the board.
• What is captured lands in the Pulse log record, which lives at Data/Pulse Log in your vault — yours to open, search, and edit like any other file.
• The Pulse dashboard reads from the record and shows, at a glance: needs you · mentions needing you · questions nobody answered · decisions this week · channel activity · where each one stands · the pulse log.

The wiring, in one breath: Yarrow holds Decision capture · Yarrow holds Pulse catch-up · Pulse sweep writes to Pulse log · Pulse catch-up writes to Pulse log · Decision capture writes to Pulse log · Pulse log shown by Pulse · Pulse kept fresh by Pulse sweep · Pulse sweep run by Yarrow.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

• Open Pulse once, after the Pulse sweep has run in the morning. Mentions needing you and Questions nobody answered are the honest signal — both are ordered oldest first and carry how long the thing has sat, so the top of each list is the item most likely to have gone cold. Everything else on the board is context.
• Say what you have handled in passing and the board stays true: "I replied to Alice about the release date", "the import error is sorted". Pulse catch-up closes that row and nothing else on it. Without that, the sweep can only close what a reply in the thread proves — which misses every conversation you finished in a call or a corridor.
• Ask before you scroll. "What did I miss in #product?" reads the channel and tells you, and files nothing unless you ask it to — which makes it the cheap way back in after two days away, rather than opening Slack and starting at the top.
• Spend the calibration on the channel list and give Yarrow the negative rules too. "Never read #random" is worth as much as "watch #product": every channel you rule out is noise the sweep will never bring you, and a board that cries wolf is a board you stop opening.
• Say a decision out loud the moment it lands — "we’ve decided to hold the pricing change". Decision capture puts it on the shared Decision log, which the Meetings & Actions Kit keeps too, so a decision made in a channel and one made in a meeting end up on the same record and neither Kit asks you for it twice.
• Read Decisions this week before a status update or a planning call. It is the one panel that answers "what changed while I was not looking" without you having to reconstruct it from threads.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, records and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

• Which channels are watched, and which are never read — said once, in your words, and respected from the next sweep.
• What makes a mention yours: an @-mention by name, a mention of your team, a question in an area you own, or only a direct ask.
• Who counts as your team — the handles whose questions you want to see even when they were not addressed to you.
• How long a question should sit before it counts as unanswered, and whether you want a card at all on a quiet day.
• When the Pulse sweep runs, or pausing it and keeping the log by hand.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

1. Adding the Kit ends at the first sweep’s own screen. Start it and Yarrow reads the last two weeks of the channels you are already a member of, plus a search for your own handle, and builds the log: the messages that named you and got no answer from you, the questions nobody picked up, the decisions that got made. It reads only what you can already see, never a DM, and it has no way to post, react or message anyone. Slack is asked for when the sweep starts rather than before it: the first run pauses on one permission card and carries on the moment you say yes. It is a real run and uses credits like any other.
2. When that first sweep finishes, Yarrow leaves one card with what it found — how many things, across how many channels — and invites a few minutes on the three things only you know: which channels are actually worth watching, which mentions deserve you, and who counts as your team. That is also where you strike out anything already settled and say how long a question should sit before it counts as unanswered. This first run is the one time the sweep reads a channel nobody has named; from then on it reads only the ones you kept.
3. Skip the sweep and the log still works by hand: tell Yarrow what you are waiting on, what you asked and never heard back about, or what got decided, and it keeps the log and the board from that. Nothing in that conversation touches Slack, and the Pulse sweep waits on your Routines screen until you choose to run it.
4. After that the sweep runs every weekday at eight, reads only what is new in the channels you kept, closes a row the moment a reply lands, redraws the board, and raises one short card only when something genuinely needs you — or nothing at all, which is what a normal day looks like.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits