In short
Decide out loud. Hand the transcript to the agent. It ships before the next call. Humans decide, agents implement, nobody writes a ticket.
The third practice. A meeting used to produce notes, and the notes produced tickets, and the tickets produced work weeks later. Now the meeting produces a transcript, the transcript goes to an agent with instructions, and the agent does the work.
This changes what a meeting is for. It is where decisions get made in plain language, by the people who own them. The implementation is not a separate phase. It starts when the recording stops.
It requires two things: connectors, so the agent can act on what was decided; and an instruction file that says what counts as a decision, what to do with one, and when to ask before acting.
Example
What it looks like.
A thirty-minute review call. Decisions: swap the hero photo, add the new show dates, fix the bio. The transcript goes to the site's agent. All three are live by the time the follow-up email is written.Related
Read next.
- connectorA link between an agent and a real system: email, calendar, files, the CRM, the site. Connecting your people to their systems is one of the first things we do in month one.Read the definition
- agentSoftware that reads its instructions, looks at the situation, takes actions with real tools, and reports back. Runs on a schedule or on a trigger, without being prompted.Read the definition
- workflowA piece of work from trigger to done, run by an agent under instructions. Not a flowchart. The agent handles the branches the chart never drew.Read the definition
- trust boundaryThe written line between what an agent may touch and what it never does. Set before anything runs. Autonomy and safety move together.Read the definition