Systems thinking, applied with a keyboard in hand.
I'm not a strategy deck that leaves before the work starts, nor an engineer who ignores the organization around the code. The approach is the same in both: understand the whole, find the leverage, and build capability that stays with your team.
Six ideas I keep returning to.
Drawn from Deming, Senge, Meadows, and Schein, and tempered by nearly two decades of what actually holds up under delivery pressure.
See the whole
A team, a codebase, and a customer are one connected system. I start by mapping how the parts actually interact, including the parts no one drew on the org chart, before touching any of them.
Optimize the system, not the part
Local efficiency often hurts the whole. The goal is the performance of the system end to end, which sometimes means a part slows down so everything else can speed up.
Find the leverage points
Some changes barely move the needle; a few quietly move everything. I look for the structural shifts (in incentives, information flow, and rules) that produce outsized, durable change.
Build quality in
You can't inspect quality into a product at the end. It comes from the process that produces it, so I work upstream, on how the work is done, not just on catching defects late.
Make it a learning organization
The point isn't a one-time fix; it's a team that gets better at getting better. Tight feedback loops and shared understanding turn improvement into a habit.
Respect the people in the system
Almost everyone is doing their best inside the constraints they're given. Change the constraints with humility and curiosity (humble inquiry over blame), and people do remarkable work.
A loop, not a waterfall.
These phases overlap and repeat. We learn, adjust, and keep the feedback loops short, because the plan should change as the system teaches us about itself.
Listen & diagnose
Time on the ground with your people and your systems. I learn how value really flows, where it stalls, and what the data and the day-to-day actually say.
Map & locate leverage
We make the system visible together and identify the few changes with the highest leverage, so effort lands where it compounds.
Build & change
Hands-on work: shipping software, reshaping process, coaching leaders. Small, reversible steps with fast feedback beat big-bang rewrites.
Embed & hand off
I transfer the thinking, not just the artifacts. Success is your team carrying the improvement forward on its own.
Curious whether this fits your situation?
The best way to find out is to talk through what you're facing. No deck required, just the real problem.