Nobody prepares you for this part.

You build the technical foundation, you lead the architecture decisions, you drive the modernisation. And then you realise that the thing standing between you and real progress isn’t a system problem. It’s a people problem.

That’s when the real work starts.

The Myth We Carry In

Early in my career I believed that if the solution was good, it would speak for itself. Get the technical execution right and everything else follows.

It doesn’t work that way.

Technical excellence gets you to the door. Relationships get you through it. And when you’re leading teams, driving platform change, and aligning technology to business outcomes, the relationships aren’t a nice to have. They are the work.

Two Different Languages

A developer thinks in logic, systems, and cause and effect. A business stakeholder thinks in outcomes, risk, and what does this mean for my team. Neither is wrong. They just speak different languages, and if you can’t translate between them, you will constantly talk past each other.

I’ve sat in meetings where the technical case was airtight and the room still didn’t move. Not because the solution was wrong, but because the trust wasn’t there yet. Nobody buys into what they don’t understand, and nobody opens up to someone they don’t trust.

Learning to bridge that gap, to speak both languages fluently, is one of the most important things I’ve done as a leader.

The Real Work

Cross-team relationships don’t build themselves. You have to show up consistently and follow through on the small things. People notice when you do and they notice even more when you don’t.

With stakeholders it goes deeper. There is almost always a gap between what someone asks for and what they actually need. The only way to close that gap is trust, and trust only comes from listening properly. Not listening to respond. Listening to understand.

When people feel heard, they open up. They share the real constraints, the real concerns, the context that changes everything. That’s when the work gets better.

How This Shapes the Way I Lead

This thinking doesn’t stay in stakeholder meetings. It runs through everything, how I lead my team, how I create space for people to own their work, how I build a culture where problems surface early instead of quietly becoming crises.

Strong teams aren’t built on process and delivery boards alone. They’re built on trust. On people knowing that their leader is in their corner, that their voice matters, and that growth is part of the deal. When that foundation is solid, the technical execution takes care of itself.

The Honest Truth

Keep sharpening your technical skills, that foundation matters. But if you want to lead at the level where technology actually drives organisational impact, invest in your relationships. Learn to listen. Learn to translate. Learn to earn trust slowly and protect it carefully.

The problems that will keep you up at night won’t be the technical ones. You’ll figure those out. The ones that linger are the ones where a relationship wasn’t built or trust was lost somewhere along the way.

That’s where the real work is.