The 72 Degrees method
A method for Technology Enabled Transformation.
φ is the lowercase Greek letter Phi, the mathematical symbol for the golden ratio. The five points of the 72 Degrees pentagon are spaced at 72 degrees around a circle, derived from φ. The method is named after the geometry the firm itself is named after.
This page is the canonical home of φ: what it is, how we run it, how we price it, how we staff it, and where it has been earned.
Why φ exists
Closing the gap between strategy on a slide and change in the world.
Most organisations are not transforming. They are doing expensive change.
That is not a criticism. Expensive change, done well, matters. But the label creates a problem. When a programme is called a transformation, it carries expectations a standard change initiative does not. Different outcomes, different timescales, different leadership behaviour. And a fundamentally different answer to the question: what will be different about how we operate when this is over?
Most transformation programmes cannot answer that question clearly. The methodology was loaded before the destination was named. The pyramid was staffed before the outcome was contracted.
φ is the method we use to keep transformation transformational. It exists to close the gap between strategy on a slide and change in the world.
The five elements
Five elements, each necessary, none sufficient on its own.
The discipline is keeping them in step. AI threads through each one. It does not take the headline.
Strategy. What is being attempted, why it matters, and what will be different at the end. Specific enough that every decision downstream can be tested against it. Not a vision deck. A working answer to what changes, for whom, and how we will know. Where AI is part of the strategy, the same test applies: what changes, for whom, and how will we know, rather than which platform, which model, which vendor.
Technology. The estate has to support whatever the strategy commits to. Architecture, platforms, tooling, integration, security, performance. What is commonly sold as a technology-only programme is enabling work; it does not deliver business transformation on its own. The mistake organisations make is conflating the enabler with the outcome. That is why 72 Degrees does Technology Enabled Transformation. The estate gets refreshed in service of the change, not as the change.
Data. The signals the business runs on: ownership, lineage, quality, accessibility, governance. Data is where most transformation programmes either find their best leverage or trip over their worst hidden problem. We treat it as a first-class element, not a sub-stream of technology. AI raises the bar: models trained on poor data inherit the problem and amplify it. Critical data products need named owners, SLAs, lineage and access controls before they are exposed to AI consumption.
Delivery. How work moves from intent to live. Methods, ceremonies, ways of working, tooling, governance, flow. A strategy that cannot move through delivery is a wish list. Delivery without strategy is industrious drift. AI enters the delivery method as a capability inside the team rather than as a layer above it. It earns its place in routine engineering and the long tail of administrative effort that previously consumed senior time. It does not belong in contractual, regulatory and irreversible action: we are deliberate about that boundary.
People. The element that brings everything to life. Culture, capability, leadership, behaviour, trust. Change is delivered by people who feel heard, trusted and valued. No framework or tool compensates for disengagement. We design change with teams, not for them. When AI joins the workforce, the same rules apply: every agent gets a role and a contract before it gets credentials, in the same way a new hire would. The principle is human-centric whether the workforce is human, agentic or hybrid.
The technical stack
Four layers inside Technology and Delivery. Skip any one and the work fails.
Each layer fails on its own. Agile without DevOps means releases still take three months. Agile and DevOps without Team Topologies means nothing ships without a dependency negotiation. SAFe without the foundations means PI Planning is theatre.
SAFe attracts genuine criticism for its complexity, some of it fair. But the attempt it makes is the right one: a coherent operating model that connects team-level delivery, programme-level coordination, and portfolio-level strategy. We are SAFe Practice Consultant trained. We use it where the scale justifies the overhead, and cut it back where it does not.
Human-Centric Transformation
The cross-cutting axis around the technical stack.
The technical stack is necessary. It is not sufficient. Around all of it sits the human axis, treated with the same rigour as the technical components rather than as a communications plan with a launch event.
People-Centric. Change starts with what your people actually value, not what you assume matters or what an engagement survey suggests. Resistance is information: it tells you where alignment is missing, where trust has not been established, where communication has fallen short.
Capability-Led. Skills can be taught. Adaptability, curiosity and a genuine willingness to learn are harder to develop. We invest in capability with targeted training linked to the change being delivered, in the work rather than alongside it.
Enablement-Driven. Capability without enablement is frustration. The most skilled, motivated workforce will go unrealised if the tools, access or authority to act are missing. We close that gap deliberately.
This is the part of the method the market is least able to commoditise, and the part where 72 Degrees is most deliberate. Behaviour change, organisational design and senior judgment are what AI cannot do, and what most clients now value most.
AI in the method
The five elements still hold. What changes is who or what performs each role.
AI changes the operating model underneath the method more than the method itself. The four-layer stack still holds. What changes is throughput, quality and where the new failure modes sit. Two places where AI threads through the work, and one place where it changes the contract.
In diagnosis. Where AI is part of the question being asked, the honest first move is to establish where the organisation actually is. We use the AI Transformation Readiness Diagnostic: ten domains, five-level maturity, evidence over opinion. The output is a baseline a board can act on, not a recommendation to buy a platform.
Inside delivery. AI sits in the work, not on top of it. Code generation, test generation, documentation, evidence capture, decision support, regulatory mapping, and the long tail of administrative effort that previously consumed senior time. We use it to widen throughput without losing quality, and we measure the difference. We are equally deliberate about where AI does not belong: most contractual, regulatory and irreversible-action surfaces.
In the contract. With AI carrying the coordination, reporting and evidence work that used to require a programme office, an engagement no longer has to be priced in consultant-days against a leveraged pyramid. The contract can be priced against outcomes. How that works in practice is set out below under How we price and How we staff.
The four governance principles
The role-based model rests on four governance principles. They came out of how we run our own delivery. They hold up because most of the high-profile agentic AI failures of the last year were violations of one or more of them.
We apply them inside our own work before we apply them inside anyone else's.
The Strategy Execution Method
A modular workstream library, not a programme office.
Strategy without delivery design is a wish list.
A modular workstream library for major change, refreshed from heritage IT-enabled transformation work for current technology and AI-enabled delivery. Twelve workstreams organised across five groupings: Delivery Governance, Business Solutions, Technical Delivery, Business Engagement and Readiness, Implementation. Used end-to-end on enterprise transformation, or lifted in part to support a discrete piece of work.
The workstream library is the structure. The Golden Thread is the spine. The Strategy Execution Method is the Golden Thread realised in working artefacts: a strategic objective register, an execution design backlog, a delivery execution evidence stream, and an outcome measurement OKR pack. Every workstream contributes evidence to one of the four artefact streams. The artefacts are versioned, instrumented and queryable, not handed over as a one-time deck.
Programmes are sometimes necessary at enterprise scale, but they are an agile antipattern by design. The Strategy Execution Method delivers the same coverage as a heavy programme without forcing the work into a programme structure where a lighter pattern can do the job. AI inside the team carries the coordination, reporting and evidence work that previously required a separate programme office. We carry the workstream library; we do not carry the programme office overhead.
The mode of engagement
Four phases. Each one short, evidence-led, modular.
Organisations can engage the method end-to-end or pick the phase they need. The phases are not waterfall. We loop between them as we learn.
The Golden Thread
The auditable line from strategic objective to delivered outcome.
Most organisations struggle to trace a clear line from strategic objective to delivered outcome. The Golden Thread is the auditable, traceable connection that holds a transformation together. Where it holds, organisations move with clarity and confidence. Where it breaks, they lose pace, money and momentum without always knowing why.
The Strategy Execution Method, described above, is how the four stages turn into working artefacts the engagement actually produces.
How we staff
Two vectors. Enterprise reach without a leveraged pyramid.
72 Degrees is structurally a small consultancy. Headcount is intentionally small and senior-led. We scale through two distinct vectors that together produce enterprise-level reach.
The associates network is a flexible network of senior practitioner associates, brought into engagements where the work calls for additional hands or specific domain expertise. Associates are partners-in-engagement, not employees. They are engaged per engagement or per phase, with a clear scope, a clear outcome to land, and a clear time commitment. The network is curated: senior, sector-credible, aligned to φ.
The permanent agentic workforce is continuous. It does not leave for better packages. It scales linearly with the work. It carries the coordination, reporting, evidence and execution that previously required a programme office and a leveraged pyramid below it. By function, that means planning the work and writing the brief, implementing against the brief, auditing the implementation before it lands, and producing the evidence trail the Golden Thread depends on. The human practitioners set direction, hold the trust relationship, approve the high-risk decisions, and accept the consequences.
Together, the two vectors mean we can engage at scale without becoming a leveraged pyramid. We can run multiple workstreams concurrently. We can layer strategic, tactical and embedded work in the same engagement. We can deliver against an outcome rather than billing against a consultant-day rate card.
The broader market is calling this the obelisk shape: fewer layers, more leverage at each level. The obelisk is the destination, not the brand. We did not draw it on a slide and hire against it. We built it by running 72 Degrees on φ for six months, every day, on our own work first.
How we price
Outcomes by default. Consultant-days are not what a client buys.
We price for outcomes by default. The default contract structure for a φ engagement is a phase fee tied to evidenced outcomes, with a joint business case underwriting both upside and downside. Where the outcome lands ahead of the case, the engagement shares the upside. Where it falls short, the engagement carries part of the downside.
Two alternatives sit alongside the default.
Time-and-materials. Available where outcomes are genuinely diffuse, typically at the front end of Diagnose where the work is to determine what the right outcome is. T&M is a discovery instrument here, not the spine of a transformation contract.
Subscription and retainer. Available for embedded engagements where the work is continuous and the deliverable is a capability rather than a one-off outcome. Suited to Embed-phase work, role-library stewardship, and governance support after the main engagement closes.
We are explicit about this because the rest of the market is explicit about it. McKinsey reports approximately 25 percent of its global fees on outcomes-based pricing, with leadership expecting that share to rise. Source Global Research's 2025 buyer-side data shows 79 percent of senior executives now using outcomes-based elements in some or all of their consulting contracts, and 88 percent planning to expand the practice. The hourly rate is becoming a benchmark currency rather than the primary contract structure.
What a client buys from 72 Degrees is not consultant-days. It is whether the change landed. Outcome capability is what we sell. The permanent agentic workforce is what makes outcome pricing possible at our scale.
Where φ sits
Inside a recognisable methodology family. Smaller footprint. Senior-only staffing.
φ sits inside a recognisable methodology family. It does not invent a new genus.
The big-four and SI lineages (EY, Accenture, Deloitte, McKinsey, BCG, Bain, IBM) are all rebuilding around the same destination: a productised AI-native delivery layer on top of a senior-led judgment layer, with outcomes-based pricing alongside the day rate. φ is aimed at the same destination with a smaller footprint and a senior-only staffing posture. Thoughtworks AI-First Software Delivery and AWS AI-DLC are the practitioner-credible counterweights at the build layer. Shape Up, unFIX and FAST Agile are the counterweights at the team-of-teams layer. φ is positioned alongside them, not against them. The differentiator is that we run the firm on the method we sell, and we never had a pyramid to rebuild.
Why we run φ on ourselves
Earned before sold.
We will not sell a method we have not earned the right to sell.
φ has been in deliberate use at 72 Degrees for six months. We run it on our own work before we sell it. The Helm, ArcStudio, the methodology canon, the engagement assets and the firm-knowledge platform were all built using φ. The team that built them is two senior people, the associates network engaged when the work called for it, and the permanent agentic workforce running every day alongside.
That is the evidence. The four governance principles are not aspirational: they are applied to our own delivery first, where the consequences of getting them wrong land on us. Local-first by default. Cost-disciplined model routing. Evidence-quality audit trail. Role contracts before credentials.
Get in touch
If you are running a transformation that feels heavier than it should, or you are starting one and want a credible baseline before you commit, get in touch.