A wall of green status can hide drifting programs, stale updates, and investments that no longer match their business case. Here's what delivering portfolios do differently, and two programs that turned around without changing the technology.
Read post →I rebuilt the home screen of Yes or Mess while real players kept using it. Fourteen small releases, one stable preview link, and a launch date I moved on purpose. Here is the operating model, and what it means for any program that has to change a product people already depend on.
Read post →If the technology is in the title and the ROI came from the vendor, your business case was built to justify a decision, not guide one. Here's how to write it forward, and what to cost that usually gets missed.
Read post →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.
Read post →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.
Read post →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.
Read post →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.
Read post →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.
Read post →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.
Read post →