TL;DR
Naming something is not the same as establishing it. Plenty of management ideas have a name, a book and a conference, and remain opinions with vocabulary attached. Six things separate a discipline from a label: a definition precise enough to be wrong, a unit of work, measures that can move against themselves, an explicit boundary, a standing owner, and a way of being corrected. Business Evolution has some of these and not all of them. Saying which is which is part of the discipline.
Somebody asked me a fair question after the third of these articles. What makes this different from the last framework somebody tried to sell me?
The honest answer is that at this point nothing does, and the difference is not something an article can establish. It is something a practice either accumulates or does not.
Management ideas have a low barrier to naming and a high barrier to earning the name. Between those two points sits a large population of things with a book, a diagram, a certification path and a conference, which are opinions with vocabulary attached. Some of them are good opinions. None of that makes them a discipline.
So it is worth setting out what the difference actually consists of, partly because the test is useful for anything arriving on your desk with a name and a model.
A definition precise enough to be wrong
The first test is whether the definition can fail.
A great deal of management language is constructed so that disagreement is impossible. Agility. Readiness. A culture of innovation. Nobody argues against these, which means nobody can act on them either, and the words survive indefinitely because nothing can falsify them.
A definition that can be wrong will say something specific enough that a reasonable person could look at a business and say no, that is not happening here. It will exclude things. It will have edges.
The test is simple. Ask what the definition rules out. If the answer is nothing, you have a label.
A unit of work
A discipline has something you actually do, at a size you can do it.
Project management has a project. Quality management has a defect. Accounting has a transaction. Each is small enough to handle and specific enough to be recognised by two different people as the same thing.
Without a unit, you get advice. Improve your culture. Align around outcomes. Build organisational resilience. All true, none of it actionable, because there is nothing to pick up.
The unit is also what makes a practice teachable. You can show somebody a transaction. You cannot show them alignment.
Measures that move against themselves
The third test is whether the thing can be observed changing.
Notice what this does not require. It does not require an industry benchmark, a maturity scale or a certified assessor. Those arrive later, and in many cases they arrive as a commercial product before the underlying measurement has been established, which is one reason to be suspicious of them.
What it requires is a number the business can take twice. The same measure, the same method, the same workflow, eight weeks apart. If the practice cannot produce that, then improvement can only ever be asserted, and asserted improvement is indistinguishable from good weather.
An explicit boundary
A discipline says where it does not apply.
This is the test most management ideas fail, and they fail it in a specific way: the idea expands until it covers everything, at which point it explains everything and predicts nothing. Culture becomes the answer to every organisational question. Agile becomes the answer to every delivery question. Digital becomes the answer to every strategic one.
A stated boundary does two useful things. It tells a reader when to stop reading, which builds more trust than a claim ever does. And it forces the practice to be specific about its own mechanism, because you cannot say where something stops working without saying how it works.
A standing owner
Nothing survives without somebody responsible for it after the enthusiasm passes.
This is the difference between a discipline and a campaign, and it is almost entirely unglamorous. Someone has to still be asking about it in eighteen months, when the person who introduced it has moved on and the business is busy with something else.
Where this usually fails is that the owner is appointed for the initiative instead of the practice, so when the initiative concludes the ownership concludes with it. A discipline needs the responsibility attached to a permanent role, which means somebody’s actual job, with the time to do it.
A way of being corrected
The last test is whether the thing can learn.
A discipline that cannot be revised by evidence is a belief system. That means somebody has to be watching where it does not work, recording it, and changing the practice as a result. It also means the changes have to be visible, because a practice quietly revised is indistinguishable from a practice that was always right.
This is where certification schemes tend to do damage. Once a body of knowledge has been fixed for examination, revising it becomes expensive, and the practice ossifies at whatever it understood in the year the syllabus was written.
Where Business Evolution actually stands
It would be poor form to apply six tests and then not apply them.
Business Evolution is the deliberate, continuous building of organisational capability at the rate a business’s ambition requires. Deliberate means designed instead of assumed. Continuous means it has a rate instead of a completion date.
On the definition, it does rule things out. It excludes change with an end state, which means most programme work. It excludes capability defined as skills. A reasonable person could look at a business and say this is not happening here, which is the test.
On the unit, it has one: a single workflow, one decision clarified, one handover strengthened, one measure added, one review date. That is roughly thirty days and it is specific enough to recognise.
On measures, six exist, none needs a platform, and each compares against itself over time. What does not yet exist is evidence across enough businesses to know how they behave in different conditions, and that takes years to accumulate.
On the boundary, it is stated: system migrations, merger integrations, regulatory deadlines and anything else with a genuine end state. It can also be misused as a reason to defer, which is worth saying out loud.
On the owner, the Edge151 Institute holds the model, which separates the standard from anything commercial. Whether that separation holds is a question about conduct over time, and no article settles it.
On correction, nothing yet. There is no published record of where the model has been wrong, because there is not enough use to draw from. That is the honest position, and it is the gap I would watch if I were reading this sceptically.
Why say any of that
Because a practice that only reports where it works is marketing, and the difference between the two is visible to anyone paying attention.
The more useful reason is that a reader can now check. Six tests, applied to this or to the next thing that arrives with a diagram and a certification path. If something fails three of them, that is worth knowing before the budget conversation, not after it.
Where to start
Take whatever framework is currently circulating in your business, and ask what its definition rules out.
If you cannot answer in a sentence, you are looking at a label. That does not make it useless, and it does mean nobody should be asked to change how they work on the strength of it.
Take the framework currently circulating in your business and ask one question of it. What does its definition rule out? If the answer takes longer than a sentence, or does not exist, that is worth knowing before anyone is asked to change how they work.
Series navigation
This is the last of five articles setting out the case for Business Evolution.
Previously: Three altitudes of change: organisation, workflow, task. The same weakness looks different depending on how closely you look at it, and choosing the wrong altitude is why improvement work misses. Read it at .
The full definition sits on the pillar page: What Business Evolution is.
The five
- Your AI business case assumes a capability you may not have.
- Capability is the connective tissue between AI spend and business value.
- Why transformation programmes keep failing the businesses that buy them.
- Three altitudes of change: organisation, workflow, task.
- What a management discipline needs before it earns the name. You are here.
Six things. A definition precise enough that it could be wrong, a unit of work small enough to actually do, measures that can be compared against themselves over time, an explicit statement of where the practice does not apply, an owner whose responsibility survives the initiative, and a mechanism for being corrected by evidence.
Ask what its definition rules out. Frameworks that explain everything predict nothing, and the ones that survive tend to be specific about their own limits. A stated boundary is a stronger signal of seriousness than any amount of case study material.
Because without one you get advice instead of practice. Project management has a project, quality management has a defect, accounting has a transaction. Each is small enough to handle and recognisable as the same thing by two different people, which is what makes a practice teachable.
No, and waiting for one usually delays the work. What is needed is a measure the business can take twice, with the same method, weeks apart. Industry benchmarks and maturity scales often arrive as commercial products before the underlying measurement has been established.
They fix a body of knowledge for examination, which makes revising it expensive. The practice then ossifies at whatever it understood in the year the syllabus was written, and the incentive shifts towards defending the syllabus instead of correcting it.
Alastair Jupp writes on organisational capability and the practical adoption of AI. The argument here is developed at length in Workflows, Decisions, Discipline: The Operating System Behind Every High-Performing Business, published by Edge151 later this year. Details and publication updates.
Discover more from Edge151
Subscribe to get the latest posts sent to your email.