Making technology teams work better
Making technology teams work better
"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.
He works with CTOs and technology leaders as a structural diagnostic and thought partner. Not a framework installer. Not a process coach. Someone who can see the system as it actually is, say what's true about it, and help build something more durable.
"Ten years of agile adoption produced ceremonies. It rarely produced structural change. Most organisations never completed the underlying work that any methodology assumes is already done. That's what Orchiture is for."
Why this work matters now ↓Sociotechnical Architect - the discipline, explored below.
30 years of experience across organisations including
"Ten years ago, everyone went down the agile route. Scrum. SAFe. Kanban. Coaches certifying coaches. And for most organisations, it didn't achieve the outcomes they were looking for. We're in a different world now."
The frameworks were real. The intent was real. But the structural conditions that determine whether those frameworks produce flow - team boundaries, architectural alignment, cognitive load distribution - were almost always left untouched. So the ceremonies ran. The retrospectives happened. And the velocity stayed flat.
What Orchiture offers isn't another methodology. It's the underlying structural work that methodologies assume is already done - but rarely is. That's why this work matters now, in 2026, more than it did when "just do agile" was still a plausible answer.
And with AI reshaping what teams are expected to deliver, the structural question has become even more urgent. More throughput from the same structure isn't possible without changing the structure.
The organisations that get this right don't just deliver faster. They stop having the same conversation every quarter about why delivery is slower than it should be. They build a system that sustains its own performance - and creates the conditions for growth that doesn't require doubling the team.
A significant part of the value for a CTO is having someone to think alongside before ideas go to the board. Not a sounding board who validates everything - someone with the structural depth and the candour to challenge what doesn't hold up, before it's exposed in a room where the cost of being wrong is higher.
The work protects delivery credibility. It means arriving at board conversations with a structural analysis, not just an intuition. And it means the uncomfortable conclusions - the ones about team design, technical debt, or delivery predictability - have been worked through before they need to be communicated upwards.
That's what a structural partner does. Not just the analysis. The confidence that goes with it.
"He uses systematic methods to gather data, analyse it statistically and come to sound, logical conclusions - even if the conclusions are sometimes uncomfortable for the business to hear."
"He partners with engineering and product leaders as well as cross-functional teams to improve ways of working and ultimately drive a culture of autonomous self-improvement. His partnership was invaluable."
Most interventions in technology organisations optimise one side and ignore the other. A new architecture deployed without accounting for the cognitive load it creates for the teams running it. A restructure that redesigns the human system without touching the technical boundaries that now cut across it. The result is a system where the human and technical components work against each other rather than amplifying each other's strengths.
The discipline that addresses this is called sociotechnical architecture - designing the human and technical structures together, as a single system, rather than treating them as separate problems with separate owners.
That's what the discipline produces in practice. The practical result is teams that can actually ship what they're designed to build, without structural overhead eating the throughput. Arriving at it from inside every part of the system, as engineer, architect, tester, operations manager, and delivery leader, means the design decisions are grounded in what each of those roles actually needs from the others.
The full career arc, from first principles to current practice.
Four career phases. Each one adds a layer. Together, they produce the systemic view that specialists can't replicate.
A decade of structural engagements across scale-ups, enterprise, and public sector organisations: Intuit, Gousto, Onto, the Office for National Statistics, Flock, NEBOSH and others. The work throughout: finding what is actually causing slow delivery, and fixing the conditions that produce it. Orchiture, established to give that practice a defined method and a proper home, formalised what the engagements had consistently been about: not installing frameworks, but repairing the underlying structure those frameworks assume is already right.
Seven years at the convergence of engineering management, operations, and technical leadership. As Development Manager at a loyalty and payments technology company, built and led a team that grew from five to thirty people: architects, developers, testers and business analysts. Formal test management responsibility and agile leadership sat within the role from the outset, including introducing Scrum and Kanban to the development department. Concurrently for the first eighteen months, managed a separate data centre operations team delivering loyalty and payments processing infrastructure for global oil brands and Tier 1 UK supermarkets across the UK and Europe. The clients on the other end of the SLA were organisations with no appetite for failure and the commercial weight to make that felt. PCI DSS Level 1 compliance throughout, passing audit four years in a row. That five-year period produced over 40% year-on-year growth in development revenues.
A year as Head of Systems Engineering at Siemens Traffic Solutions followed, responsible for real-time traffic management systems including the engineering infrastructure behind the London Congestion Charge Zone. Returning to the loyalty and payments company as a member of the executive team reporting directly to the CEO, product ownership and agile leadership operated at organisational rather than team level.
Fourteen years progressing through the full technical stack of a software organisation. Starting as a programmer and software engineer, moving into UI design, database architecture and DBA work across SQL Server and Oracle, then into software architecture, culminating as a systems integrations architect responsible for technical direction across an enterprise integration programme, including a US-based period following acquisition by a global workforce management company. By 2008, the view of a software system was end-to-end: from the interface a user touches to the data layer that persists it and the architecture that holds it together.
The career started not in technology but in finance and accounting: pensions administration and financial analysis, including a year of CIMA study. The work involved designing management information systems, automating accounting processes, and building the financial literacy that comes from working directly with the numbers a business runs on. That grounding shapes how structural findings are framed today. When a diagnosis needs to hold up in front of a CFO or a board, the ability to build that argument was formed here.
"James is calm, patient and deeply knowledgeable about team dynamics. He focuses on root causes of issues in teams in order to make long term improvements to ways of working."
"Helped every discipline across the technology org work smarter with better goal-oriented outcomes, in which open-communication and collaboration came first."
"A true guiding light in our company, always ensuring we delivered value with predictability and effectiveness."
"He uses systematic methods to gather data, analyse it statistically and come to sound, logical conclusions - even if the conclusions are sometimes uncomfortable for the business to hear."
"With James, we achieved a new team structure and way of working - which I really don't think we would have managed without him."
"He partners with engineering and product leaders to improve ways of working and drive a culture of autonomous self-improvement. In my time working with James I found his partnership invaluable."
"He is one person who knows how to make an impact just by influence."
"He has a knack for helping people see their strengths and navigate complexities, always with patience and good humour."
"His mentoring has been instrumental in helping me grow as a leader, especially in balancing technical depth with organisational strategy."
"Within a relatively short period of time, James has transformed the team, including many of the cultures and behaviours that existed beforehand."
"He helped and coached not only the engineering team but also our Design team, bringing collaboration among different areas of the company."
"He has made us self aware of our weaknesses and strengths with enthusiasm, really good character, and respect."
Let's find out whether a structural conversation is what your situation needs.
Start a Conversation