// WRITING / TAGS / LEADERSHIP
Technical leadership is the work of taking responsibility for outcomes you can't directly produce. It's making the call when the data is incomplete. Owning the consequences when the call was wrong. Creating the conditions for people around you to do work you couldn't have done yourself.
These posts are about what that actually looks like in practice. Not the org-chart version, the in-the-room version. How to disagree productively with someone who outranks you. How to hold a position you believe in when the room wants you to fold. How to know when you're in over your head and what to do about it. How to change your mind without losing credibility.
Most of what's here was learned by getting it wrong first.
The overnight evangelist is often the most motivated person in the room, responding to a real signal that something needs to change. The problem isn't that they found something. It's the leap from 'I got this working' to 'everyone must use this everywhere.' And the org's response is usually wrong in both directions.
Infrastructure work has a visibility problem baked into the nature of the work itself. When it's working nobody notices. When it fails everyone notices. That asymmetry shapes every prioritization conversation infrastructure teams ever have, and it doesn't fix itself with better communication.
You can delegate the work. You can use managed services. You can hire people who know the thing you don't. What you can't do is outsource the comprehension. When something breaks at 2am, the understanding either exists or it doesn't.
Good planning isn't about staying on schedule — it's about making better decisions in flight, taking on deliberate technical debt with clear eyes, and arriving at the right destination even when the route changes.
A home lab isn't a static thing. It grows through distinct phases. Wave one is making something work. Wave two is making it more complicated. Wave three is adding rigor. Wave four is building a true datacenter corollary. Most people stop at wave two. Wave four is where the interesting work is.
// RELATED TOPICS