I'm an enterprise coach. I help senior leaders redesign how their organizations work so strategy, product, and delivery actually pull in the same direction. The good ones already know the terrain; my job is helping them move on it with intent.
A four-skill Claude system that turns a generic chatbot into a personal nutrition and training coach. Methodology in skills, variables in memory.
A 2D pixel art browser game built with my two sons. Tactical cat with a machine gun, cucumber enemies, aluminum foil hazards. Vite, vanilla JS, HTML5 Canvas.
A print-ready scouting and practice priorities report for the Little League team I coach. Built from GameChanger data, refreshed each tournament.
Most of what's here started as something I built for myself and then realized other people might use. If something here sparks a question, I'd rather hear it than have it stay in your head.
Tell people what the outcome looks like and why it matters. Trust them to find the route. Micromanagement is for ground you've never walked and don't trust.
Liz Wiseman's framing is the right one. The work is making the people around you smarter and more capable, not proving you're the smartest one in the room.
Care personally, challenge directly. The version of you that won't have the hard conversation is not actually being kind. It's being convenient.
How teams are wired determines what they can produce. Skelton and Pais got this right. Most "process problems" are actually team-shape problems.
If I'm telling you something, you should be able to trace it back to a study, a researcher, or a named framework. Not "best practice." Not "research shows." A name.
Disagreement isn't conflict. If I'm working from evidence I won't fold because the room got uncomfortable. I'll change my mind when given a better argument.