The antagonist
The opposite of confidence is not fear. It is assumption.
Fear makes a programme look. Assumption keeps it calm until Realize.
Nothing in a programme is ever labelled assumption. It is labelled requirement, or process, or plan. Most businesses start with little documented, most of it in people’s heads, processes propped up by systems nobody owns, and a model only as good as the memory of the person who remembers.
Confidence in the baseline
You know what you actually know.
Every process, requirement and interface in the model carries who said it, on what evidence, and whether the client has confirmed it. A baseline built from one person’s recollection is recorded as exactly that.
A thin baseline is not the failure. Not knowing it is thin is. Navigator does not repair a thin baseline in Explore. It makes it visible in Explore, while a conversation can still fix it, instead of a change request in Realize.
Nobody is handed a blank page. The metamodel carries the standard, so what the client is asked for is a finite, named list of questions a real document is waiting on.
As the deliverable prints it
Sales orders arriving by EDI are validated and enriched before the order is created. Availability is checked= by advanced ATP, with short stock reallocated by a nightly backorder run. Blocked orders route to the credit release workflow. The margin monitor replaces the pricing spreadsheet. There are no interfaces on this process beyond EDI.
As the model holds it
How to read the thread.
The mechanism
One chain, from the objective a board signed to the number measured after go-live.
Capture the business once, richly enough that a document becomes a query, not a writing task. Business objective, capability, value driver, scenario, process, step, touchpoint, requirement, decision, build item, test case, deliverable, KPI actual. One chain of stored relationships, held inside the model rather than reported beside it.
Three consequences follow. A deliverable is a query against the model. A missing link is a named gap with an owner, not a red cell in a matrix nobody maintains. A release walks the chain to every process, extension and test it touches.
The chain is walked end to end on one process, with every identifier, in the deliverable this page describes.
Confidence in the build
Nothing is built because somebody remembers agreeing to it.
Open any build object and the requirement above it, the decision that authorised it and the test that proves it are all there.
When they are not, the document does not generate. Navigator names the records it is waiting on, why the document needs each one, and who is likely to own it. Absence is never readiness. A delivery lead can work a list. Nobody has ever worked a percentage.
Generate · Detailed design document · O2C-220 Create and process standard sales order
Declined. Three items outstanding.
R.503 Order-line margin and override monitor is being checked, not signed off.Step O2C-220-70 has no description of what happens at it.Nothing recorded under connections to other systems. Add what belongs there, or confirm there is none.Generate · Detailed design document · O2C-510 Manage credit limits and blocked orders
Ready.
Nine steps described and every contributing record signed off.
Two confirmed-none claims recorded by M. Chen: no interfaces on this process, and no reports.
Generate .docx
A refusal is not a failure state. It is the only honest answer to a document nobody can stand behind yet.
Confidence in the schedule
Where the plan and the model disagree, the plan is wrong.
Migration realism becomes a question with an answer instead of a number everybody nodded at. Navigator reads the plan against the model and says where the two do not hold.
Correct an assumption in Explore and it costs a conversation. Find it in Realize and it costs a rebuild.
Confidence in the platform, and in the processes
A clean core, and a release you can absorb.
SAP ships quarterly. When a release lands, the thread leads to every process, extension and test it touches, so impact analysis is a query rather than a fortnight.
The same chain closes the other loop. The processes signed off in Explore are the processes measured in Run, and conformance shows where what is run has drifted from what was designed. The design stops being a document about the business and becomes a description of it.
Whose name is on it
AI proposes. A consultant authors. The client signs.
A consultant draws the diagram in your own Signavio tenant. Navigator populates attributes through the API with source, evidence and confidence on every value, and never writes diagram topology. Sign-off is binary, and it gates generation.
Your tenant. Your licence. Your model. You buy Signavio from SAP and you own it. Libertas configures inside it and hosts nothing. If Libertas is fired, the model is still yours, in a tool you bought from SAP.
Confidence in the outcome
Go-live is the halfway point.
A folder of signed deliverables is shelfware within a quarter. The model that generated them is the model that runs the business, and the value drivers set in Discover stay linked to the processes that deliver them and the KPIs that prove them.
Bring one of your own processes. Walk it end to end and see what the model says it does not know.
Generation from the model runs today. The Run half, conformance and release impact, is designed and named as such.
The thread does not stop here.