Writing. The method, given away.
Notes from two decades of building automation people can run: what works, what fails, and what to measure. One piece at a time, no schedule promised.
Replace the busy work, not the people
What the research says about where your team's week actually goes
Most of a team's week goes to work about work, while judgment, leadership and creativity get the leftovers. What the studies show, and how to swap that.
Read the piece
The three fears every team has about AI, and what the research says
For the people rolling it out and the people expected to use it
AI isn't erasing jobs, but the fear is real and it slows adoption. The three fears behind it, what the data says, and what leaders and teams can do.
Read the piece
Autonomy is earned, not granted on day one
A practical guide to automation adoption
Why the tools that scale fastest start read-only, the four stages of earned autonomy, the evidence required to promote a tool, and the safety nets that make a step back routine.
Read the pieceThirty minutes. Worst case, you lose half an hour.
Bring one process. You leave knowing which level it's on, what to fix first, and whether it's worth doing anything at all.