Skip to main content

Insight · Change

Scope the constraint, not the system

By Padding
10 November 2026 · 2 minute read

Illustration generated with AI

The failure is decided at the scoping table, not in delivery. A programme that cannot name the constraint it exists to remove has already lost.

The constraint is rarely the technology

A transformation programme is often scoped as a technology replacement: a platform is old, so a platform is bought. The constraint the business actually feels is left untouched: the decision that waits on one person, the reconciliation nobody owns, the handover that loses the customer. The new platform inherits it.

Scope the constraint, not the system

Before agreeing a roadmap, we establish what the business cannot do today, and what it would be worth to be able to do it. That answer, agreed at the start, is what the work is measured against at the end.

Accountability has to survive the handover

A strategy handed to a separate delivery partner loses the reasoning behind it. We keep the people who designed the change accountable for building it, until the change holds.

What to do first

Write down the one thing the business cannot do today and needs to. Name who feels it, and what it costs them. That page is the brief for whatever comes next.

Written by

The Padding team

Get insights by email

Insights from real work.

Unsubscribe at any time.