I haven't updated a project board in months. It's never been this accurate.

Nobody on my team maintains the project board by hand anymore. This is the true story of Ken — the always-on AI that turns a plain comment into a clean plan, catches the slip before I would, and keeps one source of truth fresh and accurate for every project.

Ken is our project manager agent. Named after Ken Norton, the Google PM — a small nod, not a costume. He coaches the person first and lands the structure second. It is, obviously, not the real person.

A real Notion timeline of HKR's live projects, names blurred
A real view of our live project timelines in Notion. Project names blurred.

The work got done. The board never showed it.

Ten people gave updates ten different ways, and I never wanted to fix that — the version I needed as CEO was not the version the account manager needed, or recruiting, or the person actually doing the work. We had quarterly milestones and no project managers, so every plan was shaped differently, and I spent more time making the Notion board look right than moving the work forward.

And it always drifted. Something shipped on a Tuesday and the checkbox sat unticked until Friday, or forever. The plan and the reality slowly came apart, and the gap between them was where things quietly went wrong. Project management, it turns out, is the work most made for an agent.

I learned this trick before Ken existed.

Long before any of this had a name, I had an agent do one small thing: take each person's raw update and re-cut it into the version each reader actually needed — mine short, the account manager's detailed, recruiting's narrow. Same truth, shaped per audience. Nobody had to change how they wrote a thing.

That was the whole idea in miniature. I didn't make ten people write one way for the machine. I let the machine do the adapting. When it came time to fix the projects, I built on exactly that.

I never made my team fit the tool.

Every project tool I had ever used asked the people to conform — fill the field, tick the box, write the update in its format, on its schedule. The boxes went untouched and the truth lived somewhere else, in Slack, in someone's head.

So I flipped it. The owner just talks — drops a comment the way they'd say it out loud — and Ken does the structuring: the date, the owner, the next task, the status. The tool conforms to the people now, instead of the other way around. That's the entire difference.

A comment goes in. The whole plan stays true.

The first job was the unglamorous one: make the record true without anyone doing data entry. Someone comments on a project, and Ken reads what it means — a date moved, an owner changed, a task done, a scope dropped — and updates the plan in Notion to match. No form, no tab-switch, no "I'll update it later."

My favorite kind of catch is when the comment and the board disagree. On one project the demo had just landed and the board wanted to flip the whole thing to Done. I dropped one line saying hold it open — and Ken held it open, moved the date out, kept the status honest, and wrote down why. One comment. Ken did all the rest.

Sergiu9:42 AM

@Ken Don't mark done — hold it open and extend the due date ~2 weeks until the next phase is ready. Be aggressive with tagging until then.

KenAPP9:42 AM
📋Plan updated → •••••• · end date +2 weeks, status held In progress

Got it — kept the project In progress instead of closing on the demo win, moved the end date out two weeks, and logged the reason in the decision record so the history is clear. Tagging stays aggressive until the next phase lands. Want me to set a check-in for the new date?

Ken, Project Manager at HKR.TEAM
1
Live comment · 1 June 2026 · #projects

Then it stopped waiting for me to notice.

Ken watches the live projects on a clock — twice a day, every day. When an owner goes quiet past the point where quiet means something, he asks. When a date is about to slip with no reason behind it, he flags it. When a project's been still too long, he surfaces it before it shows up as a missed deadline.

I am not the one keeping the projects honest anymore. Something is always reading them, on a schedule, whether or not I remembered to look. The plan can't quietly come apart, because the gap gets named the moment it opens.

I ask where anything stands, and the answer is already true.

I don't hold a status meeting anymore, and I don't prep for one. I type one line — where do things stand — and the answer comes back current to the day: what shipped, what's late and by how many days, what's waiting on whom. It even tells me where each piece came from — this month's HiBob sync, the locked quarter plan, what's live this week.

That last part is the whole thing. The answer isn't a snapshot someone built on Friday and let rot. It's assembled the moment I ask, from sources each kept current on their own. I've stopped wondering whether what I'm reading is still true, because there's no version of it that's old.

Sergiu11:46

@Ken show me org and priorities for each.

KenAPP11:46

Org is from the 01 JUN HiBob refresh; priorities are the locked Q3 macros plus what's live this week.

  • •••••• — monthly report due 31 MAY, 15 days late.
  • •••••• closeout — confirm the internal walkthrough video was recorded so I can flip the row to Done; target was today, 15 JUN.
  • •••••• — go-live target 30 JUN; deploy goes the moment the owner confirms deploy-ready.

Want me to pull the full 150-person roster by department, or is the leadership cut what you needed?

Ken, Project Manager at HKR.TEAM
1
Live readout · 15 June 2026 · #coo

It coaches the person before it manages the work.

Every nudge Ken sends does two things in a fixed order. First it coaches — it affirms the right instinct and asks the better question. Then, and only then, it lands the structure: the owner, the date, the next move. A reply that's only the second half reads like a deadline bot. Ken does both, every time.

And the coaching is the opposite of looking over someone's shoulder. When that date slipped, Ken named the cause out loud — a client dependency, not a gap in the person doing the work. It takes the blame off my operator and points it at the real blocker. That's cover, not surveillance. It's the part my team actually likes.

No one was replaced. This is the always-on accuracy a PM would own — without the hire.

Costin runs operations, and he's the one who lives with Ken most. The way he uses it is the whole product in one habit: he asks Ken "what's next?" — and Ken hands back exactly one thing. Not a list to triage, not a dashboard to read. One next move. It forces him to work fast and iterate, and he never touches a checkbox to do it.

I'll say the honest version. There was no project manager here to replace — I was doing it myself, badly, in the cracks of everything else, and losing the thread. Without Ken I'd have eventually hired someone to keep the projects honest. I won't now. The accountability layer a PM would own just runs, and the people who do the actual work move faster because of it.

I don't open the board to update it anymore — I just say what happened, and it's already true. When I'm not sure what to do, I ask Ken what's next and it gives me one thing, not twenty. I move at least twice as fast, and I stopped losing time to admin I never wanted to do.

Costin Dinoiu, Business Operations, HKR
Costin Dinoiu
Costin DinoiuBusiness Operations, HKR

Everyone's in sync, and nobody's maintaining it.

There's one true version of every project now, and it stays true on its own. Anyone can ask Ken where a project stands and get it at their own depth — the one-line version or the full history — without chasing a person or reading a board nobody trusts.

The thing I built more boards to fix, I fixed by building fewer. The plan stopped being a thing we maintained and became a thing we just talked to.

An always-on AI that keeps every project fresh and accurate — not another hire.

That frees the people doing the work from the part that was never the work — the chasing, the reconciling, the box-ticking. Ken is the AI that keeps every project fresh and accurate on its own, so you can trust what you're looking at without asking anyone. It runs where you already are: Notion for the plan, Slack for the conversation.

If you're already an HKR client, the operators inside your business are right there. Point them at the projects you want kept honest, and we'll put Ken behind them. If you're not yet — that's the call.

Notion for the plan, Slack for the conversation.

Put an always-on AI on the projects you need kept accurate

I'll put Ken behind your operators — on your real projects, with receipts. You don't manage the plan, and you don't hire for it. You talk; the AI keeps it accurate.