Why Some Technical Professionals Cross Over — and Others Don't

Early in my career, I assumed the transition from technical to commercial was about personality. That the people who made it successfully were naturally more outgoing, more comfortable in a room, more at ease with ambiguity. What I've learned over 27 years is that it has almost nothing to do with personality. It comes down to a specific set of skills - ones that build on the engineering foundation rather than replace it. 

I've watched technical professionals cross over and thrive. I've watched others stall - not because they lacked the intelligence or the drive, but because they were missing one or two things that nobody had named for them. The difference, almost every time, comes back to the same patterns. 

Here are seven of them. 

1. Translating technical value into business outcomes 

This is the foundational crossing. Clients don't buy technical features - they buy what those features do for their business. The engineer who can move fluently between "what it does" and "what it means for you" is the one who gets invited back into the room. The ones who can't make that translation tend to get filtered out early, regardless of how strong their technical work is. 

2. Knowing your numbers - and where they came from 

Engineers are trained to trust numbers that come from a model or a calculation. Commercial numbers are different - they're often built on assumptions, market reads, and judgement calls. The technical professional who crosses over successfully learns to interrogate a figure: what's it resting on, how sensitive is it, and how much weight can it actually bear? This isn't scepticism - it's rigour applied in a new direction. Leaders notice it immediately. 

3. Building relationships based on value, not friendship 

The best client relationships in energy aren't built on rapport alone - they're built on being genuinely useful. The technical professional who consistently brings insight, connects people, or reframes a problem earns a different kind of trust than the one who's simply likeable. That trust is what gets you into the conversations that matter. 

4. Commercial structuring - understanding how deals actually work 

The technical solution is only half the equation. How the work is scoped, priced, and risk-allocated is often what determines whether a project is profitable - or even deliverable. Technical professionals who cross over successfully develop a feel for commercial structure: not just what you're delivering, but how you're working together. That understanding changes how they approach everything from proposals to negotiations. 

5. Opportunity qualification - knowing when to walk away 

This one takes time to develop and courage to act on. Not every opportunity is worth pursuing, and chasing the wrong ones is expensive - in time, resource, and morale. The technical professional's instinct is often to engage with the problem. The commercial skill is knowing when the opportunity doesn't justify it. The ability to say "this isn't the right one" - and mean it - is one of the clearest signals of commercial maturity. 

6. Communication that works in both directions 

Listening well in a commercial context means paying attention to what isn't being said - the hesitation, the emphasis, the question behind the question. Presenting well means leading with why it matters before explaining how it works. Both are learnable. Together they determine whether a technical professional can hold a room that includes both engineers and executives - which is ultimately what the crossing requires. 

7. Strategic thinking - seeing the bigger picture 

Business development isn't just about the current project. It's about understanding how this engagement fits into a client's three-to-five year horizon, and how your capability positions you for what comes next. Technical professionals who develop this instinct stop thinking about individual projects and start thinking about trajectories - their client's and their own. 

The pattern I've observed 

The technical professionals who cross over successfully rarely have all seven from the start. What they have is the self-awareness to know which ones they're missing, and the willingness to develop them deliberately. The ones who stall tend to either underestimate what the crossing requires, or assume it isn't for them. 

If you lead technical teams, these are worth knowing. Not as a checklist - but as a lens for spotting who's ready, and what they need to get there. 

If this is a capability gap you're looking to close, let's talk.