2. Everything is complete but the customer is still waiting
One of the easiest traps in operational improvement is to confuse local completion with business success.
Take an insurance claim where the claim form has been received, the response email has been written, and a claims assessor is actively working.
Every local area may be able to place a tick beside its own contribution. From the viewpoint of each team, activity is taking place and work is being completed.
Yet the customer can still be waiting with no visibility of progress.
That matters because the Business-System exists to create an Outcome, not simply to generate completed activities.
Business-Systems Engineering therefore pays particular attention to operational State. Instead of asking only What task has just been completed?, it also asks What is now true about the work?
Is the claim genuinely ready for the next step? Is information still missing? Can a decision now be made? Is it waiting because of a legitimate dependency, or because something in the Business-System has failed to connect?
This also changes the way we think about evidence. Activity counts and departmental measures remain useful, but they do not tell the whole story. Business-Systems Engineering also looks at customer outcomes, operational flow, State distribution, Capability performance and the effectiveness of governance. Evidence allows us to distinguish apparent progress from meaningful progress.
The visible gap in “Outcome pending” represents that distinction. Everything before the gap can be “complete”, while the operation as a whole for the customer remains unfinished.
The engineering question is therefore not simply “Did every participant do their part?”
It is “Did those contributions connect well enough for the Business-System to create our intended Outcome?”