July 6, 2025
Summary: In this first article in our series looking at key pillars within our Delivery 360 framework for assessing technology companies we look at how to answer a most fundamental question: Does the organisation know what it is building, why, and for whom? And, importantly, does that knowledge extend beyond the leadership team? In our experience, failure here is the one of the most common root causes of technology delivery underperformance.
The Delivery 360 is an independent, evidence-based diagnostic that investigates the full system around technology delivery — not just engineering in isolation. It aims to provide a clear picture of where the issues sit, why they exist, and what to do about them. The Delivery 360 assesses across five key pillars: Identity & Direction; Intelligence & Adaptation; Control & Optimisation; Coordination; and Operations. In this post we examine Identity & Direction: what good looks like and what poor performance in this area typically signals.
Our Delivery 360 framework draws from thinking in Stafford Beer's Viable System Model, in which the identity function is the part of the organisation responsible for ultimate purpose, direction, and values. It answers the question: what are we, and why does it matter? We include it in our assessment because it conditions everything downstream. Weakness here does not just create strategic ambiguity at the top, it creates delivery issues all the way down into teams. An organisation can have amazing engineers, brilliant product managers, and a well-instrumented delivery pipeline but still consistently underdeliver because the direction being set at the top is unclear, or is inconsistently communicated, or is simply not trusted by the people expected to execute against it.
In our assessment we typically examine Identity & Direction through three lenses or dimension: Strategy & Intent, Leadership, Governance & Culture, and Product Operating Model & Empowerment. Together these help to validate whether the organisation has a clear and executable sense of itself and whether that sense is genuinely shared.
The diagnostic question: Does the organisation have a clear, trusted, and executable product and technology strategy ? And is it understood and used at every level, not just the top?
Strategy is one of the most overused words in business but also one of the most underdelivered realities. In most companies leadership can articulate a strategy. The question is whether the articulated strategy functions as a strategy and actually shapes decisions made by teams who are three levels down.
Each organisation is different and on a different journey, but all share common elements depending on where they are in their maturity. In technology companies at low maturity levels for Strategy & Intent, direction is set by the most recent request or the loudest voice. Engineering has no strategic context for the work it is doing. Roadmap items are built because someone important asked for them. Prioritisation is politics.
At higher maturity levels, a strategy actually exists and is written down, it names specific intents for markets and bets, and it is explicitly connected to the priorities the business is working toward. Roadmap items are traceable to documented strategic bets. Trade-off decisions are made against strategy.
At the highest levels, Strategy & Intent acts as a living operating tool that is reviewed on a defined cadence with structured inputs from market, customer, and outcome data, and revised when those inputs demand it. Additionally, teams are empowered to make autonomous decisions aligned to strategy without escalation. Engineering and commercial leaders are co-owners of strategy, not recipients of it.
When looking at Strategy & Intent in client companies we look for clear data and signal. Alongside the decks, we look for how it acutally happens in the organisation:
One of the most common findings in our assessments is a gap between articulated strategy and functional strategy. Leadership believes the strategy is clear. Middle management has a vague sense of it. Individual teams are working from last quarter's roadmap and their own interpretation of what matters. The strategy exists; it just does not function.
The diagnostic question: Do product, engineering, design and other leaders create the conditions for good work? Is decision-making clear, distributed, and appropriately exercised?
Leadership, Governance & Culture are often the most consequential variable in any delivery system and, honestly, the hardest to assess. In our methodology we we're looking for three things here: the quality of leadership; the clarity of governance and decision rights; and the health of organisation culture as an operating environment. Most leadership teams believe they are creating good conditions. The evidence too often tells a different story.
Starting here, we're looking to validate whether leaders across product, engineering, and design are building their teams well, providing clear direction, and governing effectively. Or are they, on the otherhand, individually reactive, each managing their own domain under pressure with no coherent leadership model? The latter is more common than one would expect and it produces common behaviours: decisions escalate to the top because nobody is confident in their authority; problems surface only when they become crises; and mistakes are attributed to individuals rather than examined as system failures.
Ambiguity in governance and decision making can be very expensive. When it is not clear who owns a decision, decisions either get stuck at the top or get made inconsistently at team level. And both create delivery issues by slowing things down. In our work, we look for evidence that decision rights are explicit, understood, and exercised at the appropriate level. It's not about the org chart, it's about where things actually happen.
This is not about perks or values statements. Rather we are looking to see whether the culture or operating environment allows people to do their best work. When things are poor here we see high turnover, chronic disengagement, or a pattern of strong people leaving. Signals like this indicate an environment where the conditions for sustained high performance do not exist, regardless of what the strategy says.
When looking Leadership, Governance & Culture we are searching for answers to key questions:
This dimension is where the impact of the first two above becomes most visible. A weak strategy produces a feature-list roadmap because there are no outcome goals to work back from. Weak leadership produces disempowered teams because nobody has been given the authority or context to make decisions. The product operating model is the mechanism through which both pathologies express themselves in delivery.
The diagnostic question: Are teams empowered to solve problems against outcomes? Or are they executing a pre-defined feature list? Does the product operating model support genuine product ownership?
In companies with low maturity for product operating model and empowerment, we see teams are told what to build. Product managers administer backlogs and simply translate stakeholder requests into Jira tickets. Engineers are story-point machines. Designers are brought in at the end to make things look presentable. Funding may be project-based and reshuffled per initiative, which means teams are constantly being rebuilt and nobody develops deep ownership of a problem space.
In more mature companies product, engineering, and design operate as a genuine unified trio. Or if not the trio something as tight. Teams own problems, not features. Teams have the authority to determine how to solve the problems they are given. Funding is team-based and persistent, creating stability and the embedding of learning. And the Product Manager role is about understanding customers and setting direction, not just backlog management.
At the highest levels, empowerment is structural. Teams can articulate the outcomes they are responsible for. They run their own discovery. They make build decisions without escalating. Leadership sets the direction and gets out of the way of the execution.
The shift from feature factory to empowered product team is one of the most impactful transformations a technology organisation can make. It's also one of the most difficult. It requires real changes in leadership behaviour, in how strategy is communicated, and in how performance is measured.
When examining product operating model and empowerment in client companies, we look for answers to key questions:
Rolling up the learning from the dimensions, we visibility of what Identity & Direction looks like in the organisation. To be frank, we rarely end up with neutral findings. Organisations either have a functioning sense of strategic identity that reaches all the way into teams. Or they do not. We find that there is limited middle ground. This is mainly because the absence of clear direction tends to get filled by the next loudest signal, whether that is a sales request, a competitor move, or a CEO's instinct.
When these are weak, the downstream effects are predictable:
When Identify & Direction score well, it tends to create a flywheel or a virtuous cycle that improves all levels of the organisation:
While Idenity & Direction may appear to be a long way from engineering and delivery performance. I'ts not. It is one of its primary material influences of delivery performance. When Identiry & Direction is functioning, the rest of the system has somewhere to point. When it is not, everything else is working against a headwind. Fix this, and the rest of the system has somewhere to point.
Next in the series: Pillar 2 — Intelligence & Adaptation. How does the organisation sense what is happening in its market, with its customers, and in its data — and does that intelligence actually change what it does? Read now
A 30-minute call is usually enough to know whether a Delivery 360 would be useful — and what it would look at in your situation.
