The 90-day value window every technology program ignores
There's a window at the start of every program where its trajectory gets set. Here's how to use those 90 days, and what a healthy program should be able to show at day 30, 60, and 90.
Writing
The Blog
Notes on tech, business, politics, ideas, and AI.
I Don't Write Code. I Ship Software Anyway
Three apps, a website and a set of automations, built by a technology leader without a programming language. What it took, what it changes for your programs, and how to put it to work.
You bought a transformation but funded a project
Post-mortems blame scope creep, requirements, and vendors. The real cause is usually simpler: the organization funded a transformation like a project, and the money ran out at go-live.
Hi Ho its off to actually Build Ideas
Every couple now has its own page, whole casts are loaded the day a season starts, and email alerts tell you when the tea drops. Plus this blog, where you can comment, reply and settle every Hot Take.
Most technology failures aren't technical. They're decision failures.
The programs that struggle most aren't underfunded or under-resourced. They're under-decided. Here's what slow decisions really cost, and how to design governance for speed.
I used 6% less electricity this year. I still paid $444 more.
My usage fell 6% and my Dominion bill still rose $444. Thirty-two bills show how much of that was me, and how much was the rate.