How I Work About James Case Studies Insights
Orchiture

Making technology teams work better

Prior Work

Results that speak for themselves.

Anonymised case studies from prior engagements. The numbers are real. The structural problems they document are the ones that show up repeatedly in engineering organisations at growth stage.

Outcomes across engagements
90% Delivery against commitment
−55% Average cycle time reduction
+72% Business value time
Global SaaS / FinTech · UK engineering centres

These engagements were delivered prior to Orchiture's founding, by its principal — James Thomson. They document the diagnostic approach and delivery methodology that Orchiture's service offer is built on.

About James →
Case Study 01

"The business wants to grow. We are not in a position to do that — none of the structural elements are in place."

90% delivery vs commitment −55% cycle time 0% → 42% sprints hitting plan
Scaling Team structure Global SaaS · ~9 months

Scaling Without Breaking

A global cloud accounting platform needed to triple its UK engineering capacity without breaking delivery in the process. One team, scaling to three. Engineering managers newly promoted from individual contributor roles. Zero sprints in the preceding eight had delivered their committed scope. The structural conditions for growth were not in place — and the business knew it.

The diagnostic identified a near-absent product ownership function as the primary driver — developers were filling the product management vacuum while also being expected to ship. Fixing that single structural problem, alongside standing up three focused product teams, moved delivery against commitment from 58% to 90% and cycle times by more than half.

Read the case study →
Case Study 02

"All external engagements were suspended. An exception was made for this one."

+72% business value time −56% context switching −92% waiting time
Delivery speed Team culture Global SaaS · ~16 months

Unwinding the Feature Factory

A return engagement, commissioned by specific exception during a COVID-19 freeze on all external work. Two Payroll product teams operating as a feature factory — engineers assigned to features rather than product areas, decisions flowing from Engineering Management rather than Product Management, individuals measured on personal throughput rather than collective output.

Less than a third of engineering time was on business value work at baseline. Context switching and waiting together consumed the equivalent of one and a half working days per engineer per week. Four structural and cultural interventions over sixteen months moved business value time from 30.6% to 52.6% — a 72% relative increase.

The structural problems had a cultural shadow. Engineers felt told what to do rather than trusted to use their judgement. Changing the structure without addressing that belief would not have held. Both had to move together.

Read the case study →

These engagements inform how Orchiture works today.

The diagnostic frameworks, operating model principles, and coaching approaches documented here are the foundation of Orchiture's current service offer — not historical artefacts. If the problems above look familiar, the methodology is the same.

Recognise the problem? Let's talk about the fix.

Most conversations start with one of these scenarios. Most of them end with a clearer picture of what's actually going on — and what to do about it.

Start a Conversation