Your plan updates itself
when you talk.
The board was always a lie by Thursday.
The work moved; the record didn't. So I flipped it. The owner drops a plain comment in Slack or Notion — a date moved, an owner changed, a task done — and Ken, named after Ken Norton, classifies it and patches the structured row. Notion holds the plan; the working record is master, so the two can't drift. Nobody maintains the board.
Slack
Where the comment lands — said out loud, no form.
Notion
Where the structured row lives — the plan of record.
Record of truth
The master the board mirrors — so the plan can't drift.
Proof from the thread.
A real comment: one plain line typed the way you'd say it, and Ken's confirmation that the right row changed — status held In progress, due date moved out two weeks, owners tagged. Twenty-one minutes, end to end.
Live comment · 1 June 2026 · #projects · owners blurred
Six things a comment can mean — and the one Ken asks about.
I run this on my own projects.
The honest test: nobody on my team maintains the project board by hand anymore. Updates happen as plain comments, through Ken; the row stays current without anyone administering it. The conversation was always where the truth was — now the plan of record reflects it without the data-entry tax that used to make it a lie by Thursday.
And it asks before anything destructive — closing a task, deleting a row, re-dating a slip. A "mark it done" only lands after the owner confirms. Routine patches it applies on its own; the irreversible moves it checks first.
Input: a plain comment, no form, no fields. Control: Ken applies routine patches and asks before anything destructive. Result: one comment → the correct row mutation, confirmed in-thread, 21 minutes end to end.
Questions a project owner asks.
No. You write the way you'd say it out loud. Ken does the structuring — the date, the owner, the task, the status. There's no form and no required field.
Six things: a date change, an owner change, a new task, a completion, a dropped scope item, or something ambiguous. The first five it applies; the sixth it asks about.
It patches routine updates on its own, and it asks before anything destructive — closing a task, deleting a row, re-dating a slip. A "mark it done" only lands after the owner confirms.
It asks one clarifying question before touching a row, rather than guessing. The bias is to ask.
This runs on Notion today. The pattern — plain comment in, structured record out — isn't tied to Notion; that's just where our plan lives.
The working record is master and Notion mirrors it, so the two can't drift. Every write goes through one identity, so the history stays clean.
No. It updates the internal plan only. It never contacts a client or sends anything outside the team.
Put Ken on the projects you need kept current.
A 30-minute walkthrough on a real Notion plan. A plain comment typed in, the row classified, the date and status patched, and the confirm-before-destructive gate — end to end. You don't manage the plan, and you don't hire for it.