Ending the Methodology Wars
In organisations everywhere, a quiet turf war is being fought. On one side, project thinking: plans, milestones, defined scope, delivery to a date. On the other, product thinking: continuous evolution, customer value, iterate and learn. Both are right. Both work. And when teams holding each worldview have to deliver together without a shared understanding of when to use which, the result is friction, inconsistent decisions, and initiatives that slow down precisely when they need to speed up.
Cambridge University Press & Assessment, part of the University of Cambridge and a world leader in educational assessment, qualifications and academic services for learners and institutions globally, found itself living this tension. Project-led and product-led ways of working were converging across the organisation, different teams held genuinely different views on how work should be delivered, and a key initiative was feeling the drag. Leadership didn't want a winner declared. They wanted a shared understanding, and a practical way forward.
That framing matters, because the consulting industry is full of methodology evangelists who arrive with the answer already decided. Fluxion deliberately took the opposite stance: no side, no dogma. Our job wasn't to convert anyone. It was to help capable leaders see both approaches clearly enough to choose well.
We started by listening, running stakeholder discovery sessions to understand where each perspective was coming from and where the real points of friction lay. Only then did we design a tailored workshop for senior leaders, and we built it around something deliberately concrete: a live delivery challenge from within the organisation, rather than abstract theory. Participants explored the genuine strengths of both project and product approaches, tested where each was most appropriate, and applied that thinking to work that actually mattered to them, right now.
The session ended not with a methodology mandate but with agreed actions: practical recommendations to improve collaboration and delivery alignment that leaders had shaped themselves.
What Cambridge University Press & Assessment gained was a shared language. Project and product stopped being tribal identities and became tools, with far less ambiguity about when each should be applied. Leadership alignment strengthened, decision-making sharpened, and the organisation moved towards a more balanced delivery model, one capable of flexing to support whatever its strategic initiatives demand next.
The methodology wars are rarely won by either side. The organisations that thrive are the ones that stop fighting them, and learn instead to ask a better question: not which approach is right, but which is right for this.
