Other Side Of Leadership

What Nobody Tells You About Managing People

The title says it all, really. Most leadership content focuses on vision, empowerment, strategic thinking, the stuff you read about in books with glossy covers. The Other Side Of Leadership is what actually happens after the offsite retreat and before the next quarterly review. It's the Tuesday afternoon when two senior engineers who've been friends for eight years suddenly can't stand each other over a pull request, and you have to decide whose architecture approach the team will commit to. I learned this the hard way early on. I got promoted because I was good at delivering software, not because I understood people. My first six months as a team lead, I spent maybe four hours actually thinking about technical direction or product strategy. The rest was damage control. Missed deadlines caused by personal conflicts I didn't see coming. A developer who quit because they felt unheard during a performance review that I'd rushed through in twenty minutes while checking my email. A project I championed that failed because I hadn't factored in that the operations team had zero bandwidth to support it.

The Uncomfortable Math of Leadership Decisions

Here's something that doesn't get discussed much. You're going to make decisions that are technically correct but emotionally wrong, or vice versa, and often there's no reconciling the two. I once had to choose between promoting a developer whose code was solid but who actively made the team worse to work with, and passing over someone whose code was mediocre but who elevated everyone around them. The promotion committee wanted the better coder. The team would've preferred the better collaborator. I gave it to the collaborator. Two years later, the coder left for a competitor where they were obviously happier. The collaborator became a staff engineer. Did I make the right call? Yes. Was it the easy call? Absolutely not. Another thing people don't prepare you for: most of your authority is theoretical. You can't actually force anyone to do anything. You can ask, you can negotiate, you can threaten with consequences that ultimately require upper management to enforce, and you can hope that your track record and relationships give you enough capital to get buy-in. When that capital runs dry, you're just another person in the room with an opinion. This hits hardest during crunch periods when everyone's exhausted and you need extra effort but have nothing left to offer in exchange.

How to Actually Do This Work

The practical side of the Other Side Of Leadership breaks down into a few habits that aren't glamorous but compound heavily. First, schedule one-on-ones and treat them as immovable. Not status updates. Status updates belong in a chat channel or a shared document. One-on-ones are for the things that would otherwise never get discussed. Budget two weeks of buffer between meetings so you can actually process what was said instead of sprinting into the next conversation. Second, document decisions, not just outcomes. When the team asks why a particular approach was chosen, having a written record of the tradeoffs considered, the alternatives rejected, and the reasoning behind the final call saves enormous time and trust. I keep a simple wiki page for each major decision. Three sections: what we're deciding, what options we considered, and what we chose and why. Takes fifteen minutes to write. Saved me approximately two hundred hours of the same explanation over three years. Third, learn to separate problems that need solving from problems that need tolerating. Some issues will improve with time, context, or the departure of a specific person. Trying to fix everything creates the impression that nothing is actually wrong and that you're the source of all the friction. I've learned to categorize issues into fixable, manageable, and accept, then communicate that categorization to whoever's affected. It's not heroic. It's honest.

Where This Approach Completely Fails

Let me be blunt about the limitations because nobody else is. This style of leadership requires a certain level of organizational maturity and psychological safety that simply doesn't exist everywhere. If your company treats managers as enforcers rather than facilitators, if the culture rewards loudness over thoughtfulness, if promotion decisions are made by people who've never managed a team, then everything I just described becomes performative. You're going through the motions while the actual power dynamics operate on a completely different plane. It also requires time that organizations consistently fail to allocate. A proper one-on-one with a direct report, done well, takes forty-five minutes to an hour. Most companies expect managers to have six to ten direct reports and still produce shipping code or manage projects. The math doesn't work. You end up doing everything poorly instead of doing some things well. I've seen excellent leaders burn out and leave because the system demanded they be everywhere at once. The biggest failure mode I've encountered personally involves cross-functional dependency. No amount of good leadership on your side of the org chart matters if the team you depend on has its own leadership problems. I spent three months trying to build rapport with a counterpart in the security team who was chronically unavailable, constantly changing requirements, and blocking shipping for reasons that weren't documented anywhere. I tried the right approach: scheduled regular syncs, escalated appropriately, found their pain points, offered trade suggestions. It didn't matter. They were being squeezed from above in ways I couldn't influence. The workaround was to stop trying to fix the relationship and instead build a mitigation plan that reduced our dependency on them. Took longer upfront but saved months of frustration.

There's also a ceiling to what one person can absorb. If you're leading six or more reports and your organization expects you to be deeply involved in technical decisions, code reviews, and architectural guidance, you will not have the bandwidth to do any of that well. I've taken on too many reports twice. Each time, the quality of my relationships deteriorated noticeably within the first quarter. The team felt it. I felt it worse. The only sustainable fix is either reducing headcount or accepting a more delegatory management style, which most organizations punish career-wise unless you're already at a senior enough level that nobody questions your judgment. The Other Side Of Leadership isn't a method you adopt. It's the accumulated set of unglamorous choices that determine whether a team functions or fractures. There's no certification for it. No framework that guarantees results. Just experience, a growing list of mistakes you won't repeat, and the slow realization that most of what you do is spent making sure the people around you have the context and support to make their own decisions without you.