Clarify the real capability problem before committing to the solution
Before you commit to a programme, platform, credential or change initiative, I help you clarify what capability is actually needed, what the evidence already shows and what decision is justified next.
“Graeme has a real strength for making sense of complexity. He has an ability to turn challenging capability questions into clear, meaningful and usable solutions.”
— Conny Huaki
When this is useful
This work is useful when:
- a course, platform, credential or change initiative is being discussed, but people do not yet agree on the real capability need;
- leaders hold different accounts of the problem or the evidence;
- a team or workflow must change, but no one has made explicit what people and systems will need to do differently;
- available data shows activity or output without showing whether meaningful capability is present;
- an independent view is needed before the organisation commits time, money or authority.
The purpose is not to manufacture complexity. It is to prevent an institution from solving the wrong problem expensively.
What the work can include
Depending on the question, a focused discovery may include:
- decision and problem framing;
- capability mapping across people, roles, workflows and systems;
- evidence inventory and gap analysis;
- dependency, friction and risk mapping;
- stakeholder inquiry and synthesis;
- options, trade-offs and decision criteria;
- a practical review and assurance approach for the next phase.
The scope is agreed before the work begins. Discovery does not become an endless research exercise.
What this work produces
The output is a defensible account of:
- the capability question that matters;
- the capability and conditions involved;
- the evidence already available;
- the material uncertainties, dependencies and risks;
- the options that remain open; and
- the smallest justified next decision or piece of design work.
The form may be an advisory brief, capability map, evidence picture, decision frame or clear design specification. It should be usable by the people who must decide or act next.
How a bounded discovery runs
Frame
Define the decision, scope, authority, constraints and evidence threshold.
Gather
Bring together existing documents, artefacts, perspectives and relevant field evidence without collecting more than the decision requires.
Map
Make the capability, evidence, dependencies, uncertainties and friction visible.
Test
Examine assumptions, competing interpretations, risks and the conditions under which an option would remain credible.
Advise
Return a bounded recommendation, the reasons for it and the next decision gate.
Current status
This is an emerging area of commissioned practice, supported by a governed manual method. It is not presented as a validated diagnostic instrument or mature institutional platform.
The method is designed to produce a transparent, inspectable basis for judgement. Any public claim about institutional application or validation will remain bounded by the evidence actually available.
Where this can lead
Discovery may show that the next move belongs in another area of work:
- a credential, assessment, recognition or progression pathway;
- an AI-enabled learning, evidence or professional-practice system; or
- a focused implementation or professional-learning intervention.
It may also establish that the proposed intervention should not proceed. A useful discovery earns the right to recommend less.
Explore credentials, assessment and recognition →
Explore AI-enabled learning and capability systems →
Start with the question that must be answered
Bring the decision, the capability it depends on and the evidence or uncertainty already in view. We can test whether a bounded discovery would create enough clarity to justify the work.