Sent between signup and the Team intake. The goal is raw-material quality — not completion rate. A primed user gives Team better inputs, and better inputs produce briefs that actually move a career.
Most teams don't suffer from too few processes. They suffer from too few memories. Decisions get made in one meeting and forgotten by the next. Owners change without ownership transferring. The same conversation happens four times because no one remembers having it before.
I am not another project tool. I am the institutional memory that sits underneath your existing tools — capturing the small history that makes your team functional.
Over the next ten days I'll prepare you for the intake. By the end you should be able to see the coordination memory your team has been losing — and decide which projects you want me to start remembering.
Here is the diagnostic that catches almost every team off-guard.
Think about the last quarter. How many times did your team have substantively the same conversation about the same topic — pricing, hiring level, tech stack choice, customer segment, naming convention — and reach a decision that then quietly evaporated?
Most teams: between three and seven such conversations per quarter. That's three to seven decisions that ate meeting time, generated friction, and produced no durable outcome. Multiplied across the year, this is the single largest waste of senior time in most organizations.
The fix is not better facilitation. The fix is durable capture: every decision logged with rationale, owner, and reversal criteria. When the same topic resurfaces, the log surfaces too — and the team either confirms, revises with new information, or moves on.
First reflection. The most common coordination failure is not knowing which projects are still live. Half-dead projects consume attention without producing outcomes. Teams treat them as 'in progress' when they're actually 'in limbo.'
Second reflection. There's the place where decisions are supposed to be made — the weekly team meeting, the planning offsite, the formal review. And there's the place where they actually get made — the 1:1 with the lead, the Slack thread at 11pm, the hallway conversation, the chat after the chat.
If you don't know which one is real for your team, you can't capture decisions reliably. You'll keep documenting the official forum and missing the real one.
Third reflection. The most expensive coordination failure is when two team members both think they don't own something — or worse, both think they do.
This is rarely visible. Everyone assumes ownership is shared. The question 'who's driving X?' produces five different answers from five team members, none of whom realize they disagree.
If you've done the reflections, you've already mapped the ghost projects, located the real decision forums, and surfaced the ownership mismatches. The intake takes the data you've gathered and turns it into a working charter.
By the end of week one, you'll have a live decision log, a named ownership map, and a Friday status pulse routine. Week two, the friction point you flagged starts measurably easing. The contract: by week four, your team should be re-deciding decided things noticeably less often. If they aren't, the calibration is wrong and we adjust.
Open the Coordination intake →
Eight minutes · Your reflections are waiting inside
After the intake, Team takes over — operating in the background, surfacing only what needs surfacing, with no re-sequencing required from the user.