The Player-Coach Philosophy: Why Technical Context Makes Better Leaders
Why I reject the idea that engineering leadership means graduating away from the craft. Technical context drives better operational decisions.
The best architects still code. The best operational leaders still understand the tools.
There is a pressure in engineering leadership to trade the terminal for the spreadsheet. To “graduate” away from the craft and focus entirely on strategy, planning, and meetings.
I reject that.
I operate as a Player-Coach. I believe that to make high-stakes decisions about cloud-native infrastructure and operational systems, you need to understand the friction required to build them.
My Philosophy
1. Outcomes Over Outputs
Shipping features is not the goal. Moving business outcomes is. I connect OKRs to product roadmaps so teams know why they’re building what they’re building.
2. Systems Over Heroics
Sustainable excellence comes from well-designed operational systems. Resilience, in software and in teams, is the result of consistent standards and strong feedback loops.
3. Automate and Multiply
If we do it twice, we script it. If we do it three times, we build a system for it. I want my teams solving interesting problems, not fighting fires. AI-assisted workflows are the force multiplier.
I bridge the gap between business strategy and technical execution. I speak “Executive” and I speak “Engineer.” But my focus is making the entire organization more effective.
I’m Keith. I build the operational systems that let engineering organizations scale.
Let’s get to work.