Running programs with AI in the loop.
Field notes from inside live enterprise transformations — what AI actually changes about governance, reporting, and risk, and what still takes a human with their name on the outcome.
The confidence problem
A human who isn't sure sounds like it — and that hedge is information leaders have run on for decades. AI-drafted reports sound equally certain whether they read the record or guessed over a gap. Engineer the doubt back in, or lose your oldest early-warning system.
Read →Mind the seams
Programs don't break inside teams — they break at the seams between them: the handoff nobody owns, the dependency with two owners, the interface that drifted while both sides looked away. AI can map every dependency and still own none of them.
Read →Automation debt
Standing up an automation feels like deleting work. It isn't — you just converted visible manual work into invisible standing work that breaks silently and needs an owner. The build is the cheap part. The upkeep is the program.
Read →Pilot purgatory
Your AI pilot worked — that's the easy 10%. A demo runs on clean data, a willing user, and no consequences. Production runs on the real board, a skeptic, an integration nobody scoped, and a name on the output. That gap is where most AI programs quietly die.
Read →The rubber-stamp review
You kept a human in the loop, so you call the work supervised. But the better the AI gets, the less the reviewer actually reads — and a safeguard that has quietly stopped looking is the dangerous kind, because everyone still trusts it.
Read →The decision backlog
A program rarely dies because the work was too hard. It dies in the gap between when a decision was needed and when someone finally made it. You track the work to the hour — but nobody tracks the decisions, which is exactly where the schedule bleeds out.
Read →Shadow AI is already on your program
Your team already adopted AI — you just didn't approve it. A no-AI policy doesn't stop the usage; it removes your ability to see it. Bring it into the light, or govern nothing.
Read →Garbage in, gospel out
Point an agent at a dishonest Jira board and it won't tell you the board is lying — it will summarize the lie in executive-ready prose. Data hygiene isn't an admin chore anymore. It's the load-bearing wall under every AI capability you want.
Read →When the agent does the work, who signs?
AI drafts the report, flags the risk, moves the ticket. None of that changes who owns the outcome. You can delegate the labor — you cannot delegate the signature. The boundary that decides whether AI makes your program safer or just faster.
Read →The AI-augmented PMO: what actually changes
Gartner says AI could absorb 80% of project management tasks by 2030. That number is real — and the conclusion most people draw from it is wrong. The 20% that's left was always the entire job.
Read →Killing the status-report tax
Teams lose a person-week a month manufacturing reports nobody trusts. AI closes the gap — but only if you build it to tell the truth, not just to be fast. Automating a lie just makes it cheaper.
Read →AI won't save a failing program. It warns you sooner.
The expensive part of a collapse is the three months nobody admitted it. Early detection turned 45 days of warning into $4.7M saved on one program. The rescue is still human. The timing isn't.
Read →The delivery stack behind an AI-augmented program
Not a tool list — a division of labor. The model thinks, the automation moves, a human owns the boundary. Claude, Copilot, Power Automate, Make, n8n, and the governance layer everyone skips.
Read →Reading is easy. Delivering is the hard part.
If your program needs someone who can put AI to work without losing the discipline that makes it safe — let's talk.
Start a conversation