Outcome & learning
Executed is not successful.
After execution the real question begins: did it arrive, has something moved, and does the business gain anything? Vlera OS answers in separate statements, each with its own evidence.
- ExecutionThe action is done and recorded.Executed is not verified.
- Technical verificationRead back at the target: it arrived.Verified is not successful.
- Business outcomeThe goal has moved in measured values.Successful is not the same as learned.
- LearningMemory and Business Brain take in the result.
- Divergence between expected and actual result: Expected / Actual. Learning signal: Business Memory, Business Brain.Reprioritise
Statements and evidence
Every statement has its own evidence.
A successful run is first a statement about the run. What the business gains from it is another.
- ExecutedWas it done?Holds whenThe execution is recorded: who, what, when.
- Technically verifiedDid it arrive?Holds whenThe state was read back where the change is meant to take effect.
- MeasuredDid the metric move?Holds whenTwo equally long periods before and after the change exist from one source.
- InterpretedHow is the relationship to be read?Holds whenThe measurement is labelled and names other possible influences.
- Business outcomeDoes the company gain from it?Holds whenThe goal itself has changed in measured values.
Each statement stands on its own. If its evidence is missing it stays open, and the next one is not claimed.
Verification
Verified is what was read back at the target.
The message “done” is not a verification. Vlera OS reads the state where the change is meant to take effect and compares it with what was prepared and approved.
- Reading back at the targetThe live page is fetched again, or the object is read back in the connected system.
- Comparison with the approvalWhat is found is compared with the approved wording, not with a general expectation.
- Time and sourceEvery verification records when and from where the state was read.
- Tasks for peopleA person's reply counts as a statement. Where reading back is possible, it is verified in addition.
Four possible results
- ArrivedWhat is found matches what was approved.
- DeviatingSomething is there, but not what was approved.
- Not arrivedNothing can be found at the target.
- Not verifiableThe state could not be read.
Only “Arrived” leads to measurement. Everything else stays visible as an open state and is reported to the Command Center as a matter for attention.
Measure and interpret
First compare periods of equal length, then interpret.
Measuring starts after verification, on a figure that belongs to a goal. How far a measurement reaches is stated with it.
Example for illustration, not a customer statement
- Before periodSame length as the after period
- Change verifiedThe window starts here, not at execution
- After periodSame length as the before period
- Other influencesAnother change in the window: noted with the measurement
- One metric, one goalWhat is measured belongs to the goal, not whatever is easiest to count.
- Equally long periodsBefore and after are equally long and built alike, for example with the same weekdays.
- Source and data qualityEvery measured value names its source, period and knowledge state. Measured is not estimated.
- Other influences visibleIf a second change, a campaign or a season falls in the same window, the measurement says so.
Correlated is not caused.
A before-and-after comparison shows that something changed. It does not show why. Vlera OS therefore labels every measurement so it does not promise too much.
- Relationship visibleThe metric moved after the change. That does not prove the cause.
- No relationship visibleThe metric did not visibly move. That too is a result and feeds in.
- Not conclusiveOther influences in the same period do not allow a clear statement.
- Cannot be judgedData is missing or insufficient. The measurement stays open.
The business outcome is a statement of its own.
- Executed
- Technically verified
- Measured
- Interpreted
- Business outcome
It holds only once the company goal itself has changed in measured values, such as revenue, margin or utilisation. More visits or more enquiries are intermediate steps on the way.
Learning & reprioritisation
A result is finished when it changes the next decision.
Verified, measured and interpreted results do not stay in a report. They go into the Business Brain and with it into the next assessment.
- OutcomeVerified, measured and interpreted, with source and period.
- Business BrainThe result is stored as knowledge, with its knowledge state. Company state and gap to the goal are updated.
- LearningWhat worked in this company and what did not is recorded: as this company's experience, not as a general law.
- ReprioritiseWith the new state, what counts now is assessed again. A few priorities remain, each with a rationale.
Reprioritise
Learning changes order and rationale. It does not change your goals, limits or approvals: they stay with you.
The Command CenterGoals & StrategyHow execution is steeredThe whole loop
The first step
Impact can only be measured against a starting picture.
The free first analysis draws a first picture of your business. The results that follow are measured against it.
Start your free first analysisNo account required · Non-binding