September 8, 2025
Summary: This is the third post on our series on the pillars of the Delivery 360. 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.
In this post we look at Control & Optimisation. We examine why it's important to understand how an organisation governs what enters the delivery system, how it allocates engineering investment, and how honestly it connects product decisions to commercial reality. These are the control mechanisms that determine whether the organisation builds the right things, at the right cost, for the right return. When this pillar is weak, organisations can ship continuously and still underperform commercially.
When we look at Control & Optimisation in an organisation, we analyse it through four lenses: Demand Management & Roadmap, Capacity Allocation & Investment, Commercial Performance & Positioning, and Pricing & Packaging.
Let's start with context. Control & Optimisation is what turns delivery from activity into investment. In the Viable System Model, System 3 is the optimisation function. It is the part of the organisation responsible for making sure internal operations are efficient, coordinated, and aligned to the overall purpose. In a technology company, that translates into a harder set of questions: Is the work entering the system the right work? Is engineering capacity being allocated deliberately or by default? Do revenue, retention, and market position shape product decisions in practice? And does pricing capture the value being delivered, or leave it on the table?
Most technology companies have strong views on how to build. But many have weaker mechanisms for deciding what to build, how much capacity it should consume, and whether it delivered a commercial return. The result is a delivery system that can look operationally busy and even locally efficient, while still producing poor outcomes at a company level. That failure usually shows up in familiar ways:
Each of these issues reduces return on engineering investment. Together, they create a delivery system that works hard without enough commercial precision.
The diagnostic question: Is work interrogated and prioritised on evidence and strategic intent before engineering receives it, and does the roadmap communicate intent rather than simply listing features?
The delivery system is only as good as what enters it. If demand flows directly from stakeholders to engineering without interrogation — if requirements are vague, verbal, or already framed as solutions — the system ends up executing work that is poorly defined and often unnecessary. Engineering is downstream. It can only work with what it receives. Poor demand management is one of the most controllable sources of delivery waste.
In organisation where Demand Management is immature, the roadmap is a moving feature list shaped by urgency, internal politics, or the loudest voice in the room. Prioritisation is weakly evidenced. Engineers receive tickets that describe what to build, but not why it matters. PMs struggle to point to recent examples where they challenged or reframed stakeholder requests. Rework is common, and its root cause is usually poor problem definition upstream.
As organisation mature, demand is interrogated before it enters the system. Every significant item has a problem statement, a user need, and a defined success measure. The roadmap is structured around outcomes and strategic themes rather than a flat sequence of features. Prioritisation decisions can be traced to evidence — customer research, usage data, strategic bets, or commercial need. PMs can describe a recent request they pushed back on, reframed, or rejected.
When looking at Demand Management & Roadmap in client companies we look for clear data and signal:
The message here is that what separates strong Demand Management & Roadmap capability from weak is not process alone. It is the operating posture of the product management function. Product Managers who act as intake administrators are not managing demand. They are processing it. PMs who interrogate demand, ask why, test evidence, and resist premature solutioning are doing the governance work the function exists for. Weak demand management creates expensive waste before delivery even begins. When low-quality work enters the system, capacity is consumed on features that require rework, solve the wrong problem, or produce little measurable value. The cost is not only slower delivery. It is lower return on every engineering hour committed.
The diagnostic question: Does the organisation actively manage how engineering capacity is distributed across strategic work, maintenance, defect management, and technical debt, and is that distribution deliberate rather than accidental?
Engineering capacity is usually the company's largest delivery investment. And often is also one of the least explicitly governed. Leadership teams will often scrutinise a software contract worth tens of thousands, while having limited visibility into how a multi-million-pound engineering function is actually spending its time. That is a control failure, not a reporting inconvenience.
The core problem is that capacity allocation is rarely treated as an active investment decision. Work accumulates. Unplanned interruptions erode planned capacity. Technical debt grows because it is never explicitly prioritised against feature work. Features are launched and left in place, generating a permanent maintenance long tail cost. Over time, the organisation believes it is funding strategic progress while in actually turns out that over time mostof its engineering effort is actually absorbed by maintenance, defects, compliance overhead, and debt service.
Visibility is key here. At lower maturity levels, there is little reliable or actionable visibility into the investment profile. Leadership cannot state how engineering time is currently split. Maintenance and unplanned work remain invisible at portfolio level. Features are rarely retired. Build-versus-buy decisions are inconsistent or absent. At maturity improves levels, capacity is tracked across work types — feature development, defects, risk and compliance, maintenance, and technical debt. That distribution is used as an input to planning. Leaders can describe the current investment profile in quantified terms. There may also be a keep-kill discipline around features. And significant new capabilities trigger a real build-versus-buy assessment rather than an automatic decision to build. At the highest maturity levels, capacity allocation is treated as a strategic lever. It is discussed in terms of business outcomes, visible at board or investor level, and adjusted dynamically as commercial priorities shift.
When looking at Capacity Allocation & Investment in client companies we look for clear data and signal. We typically look for :
The diagnostic question: Does the product have a clear, evidence-based market position, and does product leadership own and actively manage the commercial outcomes its product produces?
This is where the gap between product/technology and commercial functions can become expensive. In many technology companies, revenue, retention, and expansion are treated as commercial metrics rather than product metrics. Product leadership knows what has been shipped. It is less clear whether it knows what is working commercially, for which segment, and why. That disconnect creates predictable problems. Churn is discussed anecdotally. Win-loss evidence rarely shapes roadmap decisions. Positioning is improvised or varied by sales teams to compensate for weak product narrative or commercial demands.
For organisations were Commercial Performance & Positioning rigour is immature, there is no durable position in the market. Sales teams adapt the message in the field. Product is distant from retention and revenue metrics. Net Revenue Retention and Gross Revenue Retention are treated as finance outputs rather than operating signals.
That matters because aggregate churn hides actionable truth. Current 2026 SaaS benchmarks suggest annual NRR around 101 to 105% for the median B2B company, with enterprise businesses often materially higher. When a company sits below those levels, the important question is not simply whether churn exists. It is which customer cohorts are churning, when in their lifecycle, and what product or value gap is driving it.
At higher maturity levels, product leadership owns the commercial story. Positioning is documented as explicit competitive differentiation. This is not simply a catalogue of features, but a defensible account of why the product wins against specific named alternatives. Win-loss patterns are reviewed on a defined cadence and translated into product decisions. PMs can cite a specific roadmap change driven by commercial evidence. Churn is analysed by cohort, segment, and timing, which makes intervention possible before revenue loss becomes normalised.
At the highest levels, product is not only protecting retention it is may also be actively managing expansion. Differentiation is maintained deliberately. The boundary between product and commercial is intentionally porous.
The diagnostic question: Does the pricing and packaging model actively capture the value delivered, or is it a legacy structure that nobody has meaningfully revisited?
Pricing is one of the highest-leverage decisions in a technology business. It is also one of the least frequently governed with discipline. The reason is structural. Pricing requires real coordination across product, commercial, finance, and often legal. It forces the organisation to test what the product is actually worth, rather than what it has historically charged. This is uncomfortable, which is why many firms leave it alone for too long.
This inertia can result in price structures persisting long after customer value, competition, and buying behaviour have changed. Discounting then becomes the real pricing mechanism. Packaging tiers reflect internal feature grouping rather than distinct customer needs. The relationship between price and value remains largely untested.
For companies with lower maturity levels, pricing is often just legacy or cost-plus. Discounting is weakly governed. Packaging is arbitrary. Few people in the organisation can explain what customers are genuinely willing to pay, because the question has not been tested properly.
At higher maturity levels, pricing rationale is explicit. The organisation can explain how price points relate to customer value and segment willingness to pay. Discount governance is enforced. Packaging tiers map to segment needs rather than arbitrary bundles. Pricing is reviewed at least annually, and willingness-to-pay research has been completed in the previous twelve months.
At the highest levels, pricing is treated as a product and commercial lever rather than an annual finance exercise. Significant changes are tested. LTV by pricing tier is visible. Leaders discuss pricing in terms of value capture and market position, not only target revenue.
When looking at Pricing & Package in client companies we look for clear data and signal:
When we look at Control & Optimisation pillar through all these dimensions, we see that weak governance most often turns into measurable financial underperformance. Poor demand management creates rework and weak roadmap quality. Poor capacity management leaves engineering functions spending large portions of their time on maintenance and debt without making that trade-off explicit. Weak connection between product and commercial performance allows churn signals to arrive too late. Poor pricing and discount governance leaves value uncaptured, often at larger scale than leaders first expect.
Individually, each of these looks like a separate issue. Together, they describe the same underlying problem: the organisation lacks deliberate control over where delivery investment goes and what it is expected to produce.
That is why this pillar matters. Delivery performance is not only shaped by how effectively teams execute. It is shaped by whether the business governs demand, capacity, commercial learning, and value capture with enough discipline to make execution worth funding in the first place.
Next in the series: Pillar 4 — Coordination. We focus our attention on process, tooling, cross-functional collaboration, team structure, and design capability. We are getting into the weeds of how teams and processes work together and the mechanisms through which the organisation stays coherent. Read more.
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.
