Our Story
Our ProductsAI
One Portal Client access
ContactInsight
·

Outcomes, not deliverables. Why we measure what moves in the business.

The consulting industry trades in deliverables. A deck that lands at the steering committee. A workshop that ends with a flipchart of priorities. A maturity report that sits on a shelf. We trade in outcomes. A line in the profit and loss statement. A decision shipped. A KPI that moves in the direction the leadership team agreed it should move. This article explains the operating discipline that makes outcomes possible and what changes when the conversation moves from scope to results.

The deliverable trap.

When an engagement is framed around deliverables, the firm and the client end up optimising for the production of the document rather than the change the document was supposed to drive. The deck becomes the artefact, the workshop becomes the event, the report becomes the receipt. The leadership team can point to what was produced. They cannot always point to what was changed.

We have seen this dynamic on both sides of the table, and the diagnosis is rarely that the document was bad. The diagnosis is usually that the document was not the right unit of value for the work. The leadership team needed a decision, a trajectory shift, an operating change. The firm produced the document because the document was what the contract specified, and the conversation moved on.

The trap is structural rather than malicious. Consulting contracts are easier to write around deliverables because deliverables are tangible, schedulable and chargeable. Outcomes are harder to write, harder to measure and harder to defend in a procurement conversation. The path of least resistance produces deliverable-led engagements, and the industry has built around that path for forty years.

How we define outcomes upfront.

The engagements we run start with an outcomes conversation before the scope conversation. We sit with the leadership team and the operating sponsors and we ask the same three questions in the same order. What is the change in the business you expect from this work. How will we know it has happened. By when does it need to be visible.

The first question forces the leadership team to articulate the change rather than the activity. The most common honest answer is that the team has not yet agreed what change they expect, and the first value of the conversation is to make the disagreement visible before money is spent. The second question forces the team to commit to a measurement method, which is where most outcome conversations break. The third question forces a trajectory rather than an indefinite ambition.

The outcomes are written into the engagement letter, named explicitly, and tied to a measurement method. They are not the only thing in the engagement letter, because the work also has a scope and a method, but they are the part that frames everything else. When the partner running the file looks at the work three months in, the question they are answering concerns the outcomes rather than the deliverables. The deliverables track themselves once the outcomes are clear.

Outcomes are harder to write, harder to measure and harder to defend in a procurement conversation. Once written, they change everything that comes after. The deliverables organise themselves around the outcome rather than the other way round.

How we instrument tracking.

Outcome tracking does not require a new analytics platform in most cases. It requires three things. A shared definition of the metric that is being moved. A shared dashboard, accessible to both the client and the partner, that updates on the cadence the metric actually changes. A scheduled conversation, monthly or quarterly depending on the engagement, where the trajectory is read together and the work is adjusted if the trajectory is off.

The shared definition is the part that most engagements skip and most engagements regret. The metric the client uses internally is sometimes calculated differently from the metric the firm uses in its tracking, and the gap surfaces six months in when the numbers do not agree. The version of the definition that holds is the one written down before the work starts and signed off by the team that owns the metric in the business.

The shared dashboard is less about the technology than about the access. The firm and the client see the same numbers, at the same time, with the same context. There is no firm version and client version of the truth. The simplicity of that arrangement removes a whole class of disagreement that consumes time in deliverable-led engagements.

The scheduled conversation is where the value of the tracking compounds. The dashboard does not change behaviour by itself. The conversation that interprets the dashboard is what produces the adjustment that moves the outcome. Skip the conversation, and the dashboard becomes another receipt.

What we do when the outcome does not land.

Outcomes do not always land, and the discipline of how a firm handles a missed outcome is what determines whether the relationship survives. The version that works is to own the miss openly, diagnose the cause honestly, and adjust the work. The version that ends the relationship is the one where the firm hides the miss, presents the deliverables as evidence of effort, and asks for the next phase of work.

When we miss an outcome on a file, we tend to bring three things to the next steering committee. A clear statement of where the trajectory is versus where it should be. A diagnosis of why, written in plain language without softening the explanation. A revised plan that addresses the diagnosis, with the cost implications explicit if there are any.

The conversations are sometimes uncomfortable. They are also the ones that build the trust that produces the next engagement. Clients who have seen a firm own a miss honestly tend to come back. Clients who have seen a firm dress a miss up tend not to.

Outcomes change the conversation.

The longer effect of outcome framing is that the conversation between the firm and the client moves from scope to results, and from effort to trajectory. The debate at the steering committee is no longer whether the engagement is producing the work that was contracted. It is whether the work is moving the business. The two questions look similar from the outside. From the inside, they produce different engagements.

Clients we have worked with on outcome-framed engagements describe the same shift in posture. The firm is held to a harder standard, the work is harder to do, and the relationship is more useful. The work that lands well in this framing tends to come back as further work, not because the firm is upselling but because the trust is genuine and the conversation about the next bet is easier when the previous bet was honest.

If your organisation is preparing a consulting engagement and the conversation is framed around deliverables, the move we recommend is to flip it. Ask the firm what change they expect to produce in the business, how they will know it has happened, and by when. The firms that can answer those three questions clearly are the firms worth engaging. The firms that struggle to answer are usually the firms whose model depends on deliverable framing. The Consulting and Tech Factory teams in our Paris, Dubai, Singapore and Bali offices are reachable from the brief form below.

Frequently asked questions.

How is outcome-based work contracted?

On engagement letters that name the outcomes, the measurement method and the cadence of review, alongside the scope and the price. The pricing is not contingent on the outcome in most cases, because outcomes depend on the client's execution as much as the firm's. The accountability is shared, not transferred.

What do outcomes look like in transformation work versus tech build?

In transformation work, outcomes are usually about decisions shipped, operating-model changes adopted, or capability metrics moved. In tech build, outcomes are usually about features in production, users adopting them, or business metrics changing as a result. The framing is the same, the metrics differ by engagement type.

How do you handle multi-stakeholder outcomes?

By naming each stakeholder's outcome separately and explicitly. The shared dashboard reflects the multiple outcomes, and the steering committee discusses each one. The temptation to roll all outcomes into one composite metric is one we resist, because the composite hides the trade-offs that actually matter.

What if an outcome needs to change mid-engagement?

We rewrite the outcomes openly. Business conditions change, and an outcome that made sense at kickoff sometimes becomes the wrong outcome by quarter three. The discipline is to discuss the change at the steering committee, agree the revised outcome in writing, and continue. The version that fails is the one where the outcome is quietly abandoned and a new deliverable becomes the proxy.

What about exit criteria?

Outcomes are the exit criteria. When the named outcomes are reached, the engagement closes or moves to a new phase with new outcomes. The engagement does not close on the production of the last deliverable in the original scope. It closes on the business change that the work was hired to produce.

How does this align with client measurement systems?

By using the client's measurement systems wherever possible, and adding the minimum new instrumentation needed where the client systems do not cover the metric. The firm does not build a parallel measurement system. It plugs into the one the business already operates against.

Further reading

Where this lands

How we'd take this further with you.

B One

Our identity

Founder-led. Expert on every file. Four offices, two engines, one craft.

Consulting pillar

Performance & Value

Measurement systems, KPI design and value tracking that actually move the business.

Engine

Consulting

Our strategy and transformation practice across four pillars and four offices.

Brief us
We'll take it from there.

Tell us the decision you're trying to make. Strategy, transformation, performance or AI. We answer within one working day.

Let's talk.

Have a challenge to solve?
Let's turn it into something real.

Start a conversation