An AI Teammate Should Tell You What It's Waiting On

Most AI tools have one interface: you ask, they answer. Which means the entire burden of remembering what you asked for, what came back, and what still needs your judgment sits on you. An AI teammate worth the name inverts that. It keeps its own queue, names what it did, and tells you exactly which decisions it is blocked on before you have to go looking.

For a fractional CMO running four clients, that burden compounds. Four workspaces, four sets of half-finished AI outputs, four mental stacks of "did I ever approve that ICP draft?" The tool saves you drafting time and hands the cost straight back as tracking time.

The fix is not a better chat window. It is an AI system that keeps its own queue and reports what it needs from you.

The reader utility: build an "awaiting you" queue so no AI output dies waiting for a decision

Here is the thing you can act on after reading: every place your AI does work on your behalf should terminate in one aggregated list of open asks, sorted by what blocks the most downstream work. Below is how to construct that, whether you build it in your own stack or use it as a checklist for evaluating a tool.

Invisible background AI costs you trust, not just time

When an agent runs in the background and you cannot see it, three things happen, and none of them are neutral.

You stop believing the output. If a positioning draft appears in your workspace and you do not know which agent produced it, from what inputs, at what time, you will re-check it from scratch. The work was done twice. This is the "understanding, not just speed" problem: you can use the model to do it, but if you cannot see why it decided what it decided, you cannot defend it to a client.

You lose track of what is pending. Background work that finishes silently is indistinguishable from background work that never ran. So you build a shadow to-do list in Notion or your head, which is exactly the patchwork the AI was supposed to replace.

Decisions rot. An AI draft waiting on your approval is not free. It is a blocked dependency. If the ICP is not locked, every persona, every value prop, and every piece of content downstream of it is either stalled or built on sand.

The trust cost is the real cost. Time you can bill back. A deliverable you cannot vouch for in front of a CEO is worse than no deliverable.

How to make agent initiative legible: four requirements

In T2D3 OS, background agent work surfaces as named activity. Navigator handles strategy and research moves, Scribe handles writing, Sculptor handles structure and assets, and each run attaches the artifact it produced. That naming is not decoration. It is the minimum unit of accountability: which teammate did this, and what did they hand back?

If you are building or evaluating this pattern, require four things.

1. Every agent run is attributable by role. Not "AI generated this," but which agent, at what time, triggered by what. A run with no name is a rumor.

2. Every run attaches its artifact. The activity entry and the output it produced live together. If you have to go hunting in a different tab for what the agent actually wrote, the activity log is theater.

3. Open asks aggregate into one view, across every source. This is the part most tools skip. T2D3 OS pulls open asks from 26 distinct sources across the product into a single "awaiting you" view, surfaced on the dashboard, on home, and in the weekly digest. Twenty-six sources means twenty-six places a decision could have gone quiet. One view means zero.

4. Asks are ranked by what they block. An unapproved ICP outranks an unapproved social caption, because the ICP gates the personas, the value props, and every AI output that reads from them. Rank by downstream dependency, not by arrival time.

The inversion: your inbox reports to you

When agent runs are attributable, artifacts travel with their runs, open asks aggregate into one view, and that view is ranked by downstream dependency, the relationship flips. You open the workspace and the first thing you see is not a blank prompt. It is a list: three things need your vote, one ICP needs a lock, two drafts need a pass or a rewrite.

You stop being the one who remembers. The system reports its own blocked state, and your job narrows to the part only you can do, which is the judgment call.

That matters more across multiple clients than inside one. With a single org, you can hold the pending list in your head. At four clients, you cannot, and the daily re-entry cost of reloading which decisions are outstanding where eats hours you cannot bill. Four clients means four CRMs, four analytics stacks, four Drives, and one pending list you are keeping in your head instead of on a screen. An aggregated queue collapses four mental stacks into one.

What to do this week

Three steps, whatever tooling you are on:

1. Inventory your sources of open asks. List every place in your current stack where an AI output or a workflow can sit waiting on you. Most operators find more than they expect.
2. Force them into one list. One view, one sort order, ranked by what each decision unblocks downstream.
3. Require attribution on every AI output. If you cannot say which agent produced a draft and from what inputs, do not put it in front of a client.

There is a reason attribution belongs on that list. As Stijn puts it in internal training, what he is looking for is "both mastery, command, understanding, managing, quality, predictability, consistency, all while using, of course, every tool you can." You cannot claim command of work you cannot trace.

The test for any AI teammate is simple. Ask it what it is waiting on. If it cannot answer, you are still the one doing the tracking, and you are paying for the tool twice.