Define the desired outcome
Step 1 of 8: start with the decision the work must support
Every piece of work begins with the decision, relationship or area of uncertainty that prompted the question. It might be an approaching renewal, an investment you are being asked to approve, a partner whose results no longer match what people report, or a portfolio that has outgrown the way it is reviewed.
This step turns that starting point into a clear brief. I establish what the system needs to support, so that everything built afterwards serves a real decision.
What this step settles
Together we specify:
- The decision and the outcome the system must support.
- The partner relationship or portfolio in scope.
- The evidence required to inform the decision, and what already exists.
- The people on each side who need to contribute.
This also determines which application of the Oversight System fits, whether a single relationship, a portfolio, both sides of a partnership or a wider ecosystem.
Why it comes first
The outcome sets the design requirements for the knowledge framework, the maturity model, the assessment and the reporting. Without it, each of those can be built competently and still answer a different question from the one you are facing.
The question is recorded at the start, so every finding and recommendation that follows can be traced back to it.
Starting the conversation
If any of this reflects a relationship or decision you are working through, get in touch. A short outline of what you are trying to understand is enough to start, and I will help you work out the most proportiona