A personal tech blog
See the system. Shape the reaction.
Field notes from two decades of cloud architecture, solutions design, and leading engineering teams — with a running obsession over how design thinking and gamification shape the systems we build and the journeys we ship.
Gamification is not points and badges
The best gamified experiences never mention games. They borrow the one thing games do better than anything else: making progress legible.
Default to boring technology
Every team gets a small budget of novelty. Spend it on the problem that is actually your competitive edge — and pay full price for everything else.
The cost of a meeting that should have been a diagram
Most architecture debates are not disagreements. They are two people holding different pictures in their heads. Draw the picture first.
Designing for the second day
Onboarding gets all the attention. But the product is really judged on day two, when the novelty is gone and only the workflow remains.
Reliability is a product feature
Users do not experience your uptime as a percentage. They experience it as trust — earned slowly and lost in a single bad afternoon.
About the author
I'm an associate director of software development — a former cloud and solutions architect, a technology advocate, and a long-time problem solver. I care most about intuitive business design, design thinking, and the craft of turning a messy customer journey into something people actually enjoy moving through.
This is where I think out loud. No sponsors, no growth hacks — just the ideas I keep coming back to.