Engineering leadership · London

In the work,
not above it.

"When you've written the code, designed the database, managed the testers, run the infrastructure, and sat in the board conversation about why delivery is slow - you stop seeing silos. You start seeing the whole system."

Over 30 years building and leading technology organisations. James has spent his career at the structural edge - the moments where rapid scale-up meets structural friction, where the design of the human system begins to actively hinder what the technical system can do.

Not a framework installer. Not a process coach. Someone who goes in alongside your teams, says what's actually true about what's happening, and builds something that holds when the engagement ends.

Organisations bring me back. Contracts get extended. The reason, in both cases, is that the team is doing something at the end that it could not do at the start.

James Thomson, engineering leadership consultant, London

50+

product teams

10+

years independent practice

200+

people coached
1-2-1


30+ years across organisations including

Intuit
Gousto
Onto
Flock
Office for National Statistics
Siemens

Three ways I engage.

01

Embedded practitioner

Three to five days a week. High autonomy. I go in alongside the teams, establish delivery discipline, and fix the structural problems that are visible from the outside but resistant to change from within.

Learn more →

02

Fractional

One or two days a week. The same delivery leadership as the embedded model — at the scale and cadence an early-stage organisation can actually absorb. Works well alongside a fractional CTO.

Learn more →

03

1-2-1 coaching

For heads of engineering, delivery leads, and technically strong people navigating organisational complexity. Monthly rhythm, outcome-led. I've coached over 200 people this way.

Learn more →


From the people who've worked with me.

Every engagement is structural work done alongside people trying to find their way through something that is not working, and what the people I have worked with describe about that, is more useful than anything I could say about it myself.

"James has an exceptional ability to listen deeply and offer insightful feedback, which has consistently helped me refine my ideas and approaches. He has a knack for helping people see their strengths and navigate complexities, always with patience and good humour."

Oliver Andrews

Head of Engineering · Flock

"James quickly assessed the team, our processes and delivery approach, and proposed a set of improvements. He then led the delivery teams through implementation in a collaborative, learn by doing way. That transformation was achieved alongside continued delivery of the project."

Callum Foster

Senior Project Manager · Office for National Statistics

"James developed our teamwork to the point where each team ran itself and operated in a genuinely autonomous way. He developed strong relationships and made a great impact on our culture and ways of working, which always felt gentle and well-observed, and never rushed or top-down."

Carenza Harvey

Product Manager · Onto

Read more recommendations →

The work, with the numbers.

All case studies →

Case study 01 · Global SaaS · ~9 months

Scaling Without Breaking

A UK engineering team scaling from one to three. Zero sprints hitting committed scope in the preceding eight weeks. The structural conditions for growth were not in place — and the business knew it.

90%

delivery vs commitment

−55%

cycle time

0→42%

sprints hitting plan

Case study 02 · Global SaaS · ~16 months

Unwinding the Feature Factory

Output obsession without outcome ownership. Teams shipping continuously but solving nothing. The diagnostic identified the structural source — and the path back to delivery that mattered.

+72%

business value time

−92%

waiting time

−56%

context switching


Thinking in public.

All writing →

Performative Scrum Syndrome · 01

Performative Scrum Syndrome: when the ceremonies run but the team does not.

orchiture.com →

Performative Scrum Syndrome · 02

Performative Scrum Syndrome: when you measure activity instead of value.

orchiture.com →

Scaling

The structure that made your engineering team fast is making it slow.

orchiture.com →

It starts with
a conversation.

Tell me briefly what you're dealing with and what you're looking for. If it sounds like something I can help with, we'll arrange a call.

Let's talk →