My operating manual.
How I think about leadership, decisions, customers, AI, technology, and staying current.
Leadership
“The best teams are built on trust, clarity, and the freedom to do great work.”
Great teams start with hiring for judgment and coachability, then trusting the people you hired.
My job is to make expectations clear enough that people can make good calls without me in the room, and to be the first person they call when they can't.
Skills can be taught. Judgment is the harder signal.
Ambiguity is the tax leaders pass down when they don't do their work.
Meetings should earn their place on the calendar.
Decision Making
“Every decision is a bet. The job is to make bets you'd take again with the same information.”
I try to name the signal, name the constraint, and then make the smallest reversible decision that moves us forward.
Reversible decisions get made fast. Irreversible ones get the room and rigor they deserve.
Speed up reversible calls. Slow down the ones that aren't.
What's the signal? What's the constraint? Everything else is noise.
Customers
“A go-live is a promise. Hypercare is when you prove you meant it.”
Customers don't buy software. They buy the outcome the software is supposed to produce.
That means the delivery organization owes them adoption, measurement, and iteration, not just a working install.
Deliverables are the receipt. Outcomes are the point.
The people using the product on Tuesday know things the exec sponsor doesn't.
AI
“AI is a leverage tool. Leverage doesn't relieve you of judgment, it amplifies whatever judgment you already had.”
I use AI to move faster on the mechanical parts of building software so I can spend more time on the parts that require human judgment: tradeoffs, taste, and accountability.
The team that ships with AI still owns every line that goes to production.
Scaffolding, tests, docs: where AI is already excellent.
Product direction, tradeoffs, and accountability stay human.
If nobody checks it, it will eventually hurt someone.
Technology
“Most product failures aren't technical. They're a wrong problem, a wrong time, a wrong team, or a wrong bet.”
The technology is almost never the thing that killed the product. Product failures are usually decisions that were wrong at the moment they were made.
The discipline is naming which of the four you're actually facing because the fix for each is different.
Wrong problem, wrong time, wrong team, wrong bet — pick one.
A rewrite rarely fixes any of the four.
Continuous Learning
“The half-life of what you know is shorter than it's ever been. Learning has to be a habit, not an event.”
I stay current by building, new products, new stacks, new workflows, and by writing about what I learn so it sticks.
The best executives I know are still curious. The ones who plateaued stopped being curious first.
Reading about it isn't the same as shipping it.
If you can't explain it, you don't understand it yet.