Strategy to Outcomes supports your build of the ERP high-level design from strategic intent to design readiness.
You have the strategy. You have the OKRs. You have the requirements. You may already have the RFP. But have you designed how the business must behave to produce the intended outcome?
Strategy to Outcomes translates strategic intent into a High-Level Operating Design defining the required system operating behaviour, decisions, controls, feedback and deep measurement. Your organisation and implementation partners can then evaluate which existing applications, combination of applications or custom development can fulfil that design.
We don't start with the software. We establish how the business system needs to behave.
Why book a 45-minute context?
Use this time to discuss one strategic initiative and a value chain. Before asking what the technology can do, ask what the business needs it to accomplish.
Bring us one strategic initiative and related value chain.
Where S2O fits
STRATEGIC INTENT -Organisation
↓
HIGH-LEVEL OPERATING DESIGN - S2O
↓
SOLUTION EVALUATION - Partner/Organisation
↓
DETAILED DESIGN & IMPLEMENTATION - Partner/Organisation
Your strategy establishes what the organisation is trying to achieve.
S2O establishes how the business system needs to operate for that outcome to become plausible.
The client and its implementation partners determine which technology should fulfil the design and how it should be implemented.
What the design makes Visible
A S2O High-Level Operating Design establishes, at the appropriate level:-
How processes behave.
What decisions must occur.
Who needs authority to act.
What must remain under control.
What feedback must return.
What needs to be measured.
How the proposed system behaviour relates to the expected business outcome.
The missing design question
Requirements can be complete.
User stories can be complete.
An RFP can be complete.
And the organisation can still be left to infer how all of those elements must work together to produce the intended business outcome.
The question S2O asks is different:
Can you show how the proposed operating behaviour will actually produce the intended outcome?
S2O develops that missing operating design.
The commercial boundary
We design what the technology must fulfil.
S2O is independent of the application decision.
The design may ultimately be fulfilled by:
an existing application,
several applications working together,
AI or automation,
a specialist solution,
custom development,
or a combination of these.
S2O does not sell that answer.
We provide the operating design against which the answer can be evaluated.
Direct or Partner Led
Strategy to Outcomes can be engaged directly by the client or through an ERP vendor, implementation partner or consulting organisation.
The approach and workflow is identical.
Only the commercial relationship changes.
Two Service Streams
Strategy to Outcomes Advisory
Co-develop the operating high-level design.
Strategy to Outcomes Enablement
Build your organisational capability to continuously develop, govern and improve operating designs.