Value Optimisation · EST. 2011 · APAC

Agile wasn't just for IT. Origin Energy's data and contracts teams doubled their productive output.

The Situation

Origin Energy’s data management and contracts teams were running project and operational work without a shared system for managing flow, priorities, or reporting. Origin engaged ZXM to design and embed a business agility approach across two business units — approximately 25 people spanning legal, data research, and contract management.

The challenge was structural. The work arriving into both teams was a mix of planned project deliverables and high-volume unplanned requests. The team had no mechanism for distinguishing between the two, no way to protect planned work from ad hoc interruption, and no visibility of lead time or cycle time that would allow the programme manager to set realistic expectations with stakeholders.

What the diagnostic found

Before any training was designed, ZXM mapped the flow of work through both teams. The primary finding was that the teams were not underperforming — they were absorbing a volume of unplanned demand that made planned delivery structurally impossible. Three conditions made this worse: there was no visual system distinguishing planned from unplanned work, the programme manager had no real-time signal of what was actually in flight, and the Sprint cadence had never been applied to non-technology work in this context, so the teams had no inspect-and-adapt rhythm.

The pattern held across both teams. Legal and data research were experiencing the same flow breakdown by different mechanisms. That confirmation pointed to a shared cause: the operating system, not team performance.

What changed

ZXM trained both teams on Lean, Kanban, and Scrum — delivered through simulations on flow, value stream mapping, work-in-progress limits, and batch theory rather than theory-first instruction. The training was designed to create shared mental models, not just shared vocabulary.

Once the foundations were in place, ZXM helped Origin design a hybrid operating model using Scrum’s two-week Sprint cadence to structure planned work, with Kanban overlaid to make unplanned work visible and manageable within the same system. Epics were mapped on a Kanban planning horizon for upcoming months and quarters, giving the programme manager a forward view that had not previously existed. The Sprint Review gave stakeholders a regular, structured mechanism for understanding actual delivery versus expectation — which directly reduced the pressure to escalate unplanned requests.

What held

Within three months, both teams reported a 200% increase in measured output. The gain was not from working harder — it came from removing the structural conditions that were absorbing productive capacity: unmanaged unplanned demand, no flow visibility, and no shared cadence for planned work.

The programme manager gained real-time visibility across both teams for the first time. Lead time and cycle time became measurable, which allowed realistic commitment dates to be set and met. Customer satisfaction inside the programme improved because expectations were no longer set informally or reset constantly under pressure.

The model transferred. After ZXM disengaged, the team leads continued running the Scrum-Kanban hybrid without external facilitation. The operating system was embedded, not installed.