You've been told to adopt AI. Nobody handed you a map.

Playbooks

Every playbook is one real project from my own team. The situation, the constraint I was stuck with, what I actually did, what the numbers say, and what I'd do differently. If I didn't run it, I don't write about it.

• Measuring AI Adoption on an Engineering Team, Without a Leaderboard

  You cannot coach a hash. Picking one AI habit that leaves an artifact, and coaching the artifact instead of the usage count.

  Read it

• Tracking AI Spend Across Providers and Finding $8,000 a Year on the Floor

  What are we spending on AI? A cost lens that reconciles to the real invoice, and the $200 question that unraveled it.

  Read it

• Letting an AI Agent Ship Bug Fixes, and the Gates That Made It Safe

  57 fixes landed in twelve business days at about $7 of compute each. The human gates I kept, and the one I removed anyway.

  Read it

• Read-Only Access for AI Agents: The Guardrails That Made Production Possible

  I gave my agents hands that physically cannot write. That one habit is why I could point them at production at all.

  Read it

• A Team Dashboard for AI Usage: What Changes When a Tool Gets an Audience

  Going from tools-for-me to tools-for-the-team is a different kind of work. Trust boundaries, not features.

  Read it

• Retiring the Sprint: Moving My Team to Continuous Flow Once AI Changed the Constraint

  The constraint sprints managed had quietly disappeared. What I locked with my co-leads before the change reached a single engineer.

  Read it

Read the playbooks

Guides

The evergreen how-to layer. Rolling out AI coding tools to a skeptical team, measuring whether the tools are actually helping, proving ROI to a VP who has seen too many vendor decks. Written for the manager who has to make it work, not the vendor selling it.

• How I Roll Out AI Coding Tools to a Skeptical Team

  A rollout plan built around evidence and volunteers, not a mandate and a leaderboard.

  Read it

• Measuring Whether AI Is Actually Helping, Without a Surveillance Dashboard

  How to know if the tools land, without turning usage into a scoreboard people game.

  Read it

• Proving the ROI of AI Coding Tools to a Skeptical VP

  An ROI story that survives a VP who has seen too many vendor decks, with the assumptions on the table.

  Read it

Browse the guides

Tools

Calculators with the formula printed on the page. Vendor ROI math tends to hide its assumptions. Mine are the input fields, so you can argue with them.

See what's coming