Engineering Management: Leadership and best practices

How I Decide Which Technical Debt to Fix

|Engineering Management

Every engineering team keeps a list of code it hates: the deployment script nobody dares touch, the service with the four-thousand-line class, the test suite that fails on Tuesdays. Dislike is a signal worth hearing, but it is not a measurement, and if I fixed everything my teams complained about we would spend years rewriting working systems while dangerous debt waited in the queue. In this guide, I share the five factors I score – operational risk, security exposure, delivery friction, maintenance cost, and probability of change – how I sort every item into fix now, defer with a trigger, or accept in writing, and why the debt a team hates most is sometimes the debt worth keeping.

How I Explain Engineering Trade-Offs to Executives

|Engineering Management

Most good engineering ideas do not die because they are wrong. They die in a meeting, presented in a language the room does not use to make decisions. In a regulated enterprise the gap is wider: an untranslated technical risk is an audit finding waiting for a date. In this guide, I share how I translate reliability, security, technical debt, delivery speed, and cloud costs into money, time, and risk, the four-part structure I use for every trade-off conversation, and how I present ship now versus build it right so the consequences are visible and the risk lands with a named owner.

How I Handle Underperformance on My Team

|Engineering Management

Every manager eventually has a conversation they would rather postpone: someone on the team is not delivering what the role requires. The instinct is to wait another sprint and hope the problem resolves itself. It rarely does, and the waiting quietly becomes a management decision of its own. In this guide, I explain the process I follow from the first signal to the final decision: diagnosing the cause, auditing my own contribution, setting measurable expectations, matching support to the problem, documenting progress, and knowing when improvement is not happening.

How I Give Difficult Feedback Without Losing Trust

|Engineering Management

Difficult feedback can feel like a choice between honesty and trust. It is tempting to believe a careful manager has to choose between saying the hard thing and preserving the relationship. In this guide, I explain how I decide whether a conversation is warranted, prepare with observable facts, describe the impact, and invite the other person's perspective. Then I agree on a clear next step, offer support, and follow up so the conversation leads somewhere.

How I Set Priorities When Everything Is Urgent

|Engineering Management

By mid-morning you will have been told four different things are urgent, and at most one of them will be true. Urgency is a claim someone makes on your attention; priority is an allocation of finite capacity. In this guide, I share the filters I use to tell real emergencies from loud stakeholder demands, how I communicate what will not get done, and what disappointing a senior stakeholder to protect something bigger taught me.

What I Learned From Managing Former Peers

|Engineering Management

The promotion email goes out on a Tuesday. By Wednesday, the people who reviewed my pull requests last week report to me. Nothing has changed about the people, yet everything has changed about the structure around them. In this guide, I share what managing former peers taught me: how to hold authority without arrogance, handle the friend and the rival, set boundaries that protect both sides, and resist the pull back to the individual work that got me promoted.

The Biggest Mistakes I Made as an Engineering Manager

|Engineering Management

Management has a nasty habit of punishing the instincts that made me a great engineer. When I stepped into the role I brought years of technical experience and almost no people skills, and I got most of it wrong before I got any of it right. In this guide, I share the mistakes that cost me most, in roughly the order I made them: staying the hero engineer, solving instead of coaching, avoiding hard conversations, saying yes to everything, and what each one taught me to do instead.

How I Hire, Onboard, and Develop Great Engineers

|Engineering Management

Great engineers are rarely found. They are built, through intentional hiring, thoughtful onboarding, and consistent development. I hire for trajectory over current output, onboard for momentum in week one, and develop by giving people problems slightly bigger than they think they can handle. In this guide, I share the system I actually use: how I define the role before I post it, how I run a structured interview loop, how I onboard so new engineers ship early, and how I develop them long after they are productive.