Four Pillars of Engineering Leadership

A few years ago Paul Ingham, a previous manager, laid out what he called the four pillars of engineering leadership. They’ve stuck with me because they cut through the usual management noise. Leadership isn’t about hierarchy or authority. It’s about shaping the parts that make a team work, and each pillar needs the one before it.

Engineering Artisanship

Start with the craft. Artisanship means writing code that someone else can understand, building systems you’d want to own in a year, fixing things properly instead of patching them.

This is your foundation. If you can’t show what good looks like, don’t expect it from your team. Your standards become everyone’s standards: what gets merged, what gets reworked, what you let slide.

Without artisanship, the rest is theory.

Engineering Strategy

Once you’ve built your craft, you earn the right to set direction. Strategy gives meaning to the daily grind by connecting today’s work to next year’s outcomes.

You shift from “doing things well” to “doing the right things”.

Without the craft underneath, strategy is just PowerPoint slides.

Culture

Culture builds on craft and strategy. It turns skilled individuals into a team that ships.

You need feedback that flows both ways, candour as the default, and standards the team actually believes in.

None of that happens by accident. It gets built through a thousand small choices about what you reward, what you ignore, and how you respond when things break.

Culture is what turns strategy and craft into momentum.

Stakeholder Engagement

Everything so far is wasted if it stays internal. Stakeholder engagement connects your work to the wider world. That means real collaboration with product, design, ops and users, rather than status updates in Slack.

This only works with the other pillars in place. Without culture, collaboration dies. Without strategy, you talk in circles. Without craft, nobody trusts you.

This is where engineering becomes visible and where it matters.

Each pillar needs the one before it. Skip one and quality drops, priorities drift, and engineering turns into the department nobody talks to.


Published on . Co-authored with AI.