Every status, current
the second you ask.
I stopped holding status meetings.
I type one line and the answer is already true. Ken, named after Ken Norton, assembles it the moment I ask — from the live HR org, the locked quarter plan, and continuously-reconciled project state — and tells me where each piece came from. The status you read is provenance, not a snapshot someone built days ago and let go stale.
Slack
Where you ask — one line, any depth.
Notion
Reconciled project state — one of the live sources.
HR org + quarter plan
The other two live sources, each kept current on its own.
Proof from the readout.
A real exchange: a three-word ask, and the answer opening with where each slice came from — then day-precise facts a stale board gets wrong, then the offer of a deeper cut.
Live readout · 15 June 2026 · #coo · project names blurred, facts kept
A three-word ask, a multi-source answer that names itself.
I run this on my own projects.
The honest test: there's no status doc to maintain, because there isn't one. I ask where a project stands and the answer comes back current to the day — what shipped, what's late and by how many days, what's waiting on whom — assembled the moment I ask from sources each kept live on their own.
Slack is soft context, never a decision source. A status only changes through a confirmed update, not a passing comment. And Ken reports the current state, then ends with options — the call stays with a person.
Ask: three words in Slack. Source: the HR org refresh, the locked quarter plan, reconciled project state. Result: a total, current answer that cites its own provenance and carries day-precise facts a stale board gets wrong.
Questions an exec asks.
Because there's no doc to maintain. Ken assembles the answer the moment you ask, from sources each kept live on their own — the HR org refresh, the locked quarter plan, and project state that's reconciled continuously.
The answer tells you where each piece came from in its first line. You're reading provenance, not a last-edited timestamp.
Yes — the same live state, re-cut for the reader. A leadership one-liner or the full roster, a strategic cut or a tactical one.
No. It reports the current state and ends with options, never a verdict. The call stays with a person.
No. Slack is soft context, never a decision source. A status only changes through a confirmed update, not a passing comment.
Point it at the projects you want visible. As the record reconciles, "where does X stand" starts returning current answers — and the status meeting quietly stops being necessary.
Put Ken on the projects you need kept current.
A 30-minute walkthrough on real projects. A one-line ask typed in, the three live sources assembled, and the answer that names its own provenance — end to end. You don't manage the plan, and you don't hire for it.