A HEPO engagement puts the software to work on an agreed organisational question. The partner helps establish scope, definitions, deployment and practice. The client supplies the people, authority and context needed to make the result useful.
The five stages below describe a P&C-led engagement, with Process Orchestration and Simulation & Gamification included where they serve the purpose. The stages are a working sequence, not a fixed week-by-week timetable.
1. Assess the question and readiness
Begin with the decision or development need: who is responsible, what they need to understand and what action could follow. Review the available records, existing systems, access constraints and participant involvement.
The output is an agreed scope and readiness account. A preliminary software reading is appropriate only when definitions, permitted evidence and a suitable environment already exist. Discovery should not be presented as a computed assessment of an organisation that has not yet been configured.
2. Establish the working definitions
The catalogue workshop examines supplied definitions and adapts or extends them in the client's language. The group agrees the relevant traits, observation scope, sources, interpretation and ownership.
For Process work, establish the steps, inputs, responsibilities, human gates and expected results. For a simulation or learning activity, declare the scenario, assumptions and participant purpose. The client approves what these definitions mean in its own work.
3. Configure and demonstrate the application
Implementers prepare the deployment and the supported configuration. They establish source ownership, mappings, access, inference and any separately authorised outbound delivery. The team verifies representative success and failure paths.
The output includes a working demonstration and an operating handover: who maintains definitions, connections, permissions, storage, updates and recovery. Architecture & Security provides the technical evaluation guide.
4. Run and interpret the first cycle
Run the agreed evaluation or process with appropriate records. Review the available result and its basis, including missing context and uncertainty. The partner facilitates interpretation; the client decides what merits action or further inquiry.
The output is a reading or process account with a clear next decision. A recommendation is a proposed response. The first cycle does not require that every reading produce a programme, nor that every stage happen automatically.
5. Undertake the chosen work and return to it
If a response is selected, scope the programme, process change or learning activity. Identify participants, owners, milestones and how progress will be reviewed. Achievement Campaigns & Programmes carries development journeys; Simulation & Gamification can contribute an activity within them.
Return to the relevant evidence and participant experience at an agreed time. Compare like with like and consider other changes in the organisation. A changed index alone does not establish the cause of an outcome.
Assemble the necessary capabilities
| Capability | Main contribution |
|---|---|
| Assessment practice | Question, scope, evidence readiness and interpretation |
| Catalogue facilitation | Definitions and client ownership |
| Implementation | Configuration, integration, verification and handover |
| Advisory practice | Response design and subsequent review |
One person may carry several responsibilities if equipped to do so; a title or certificate does not remove the need to demonstrate competence in the actual scope. The enablement framework describes the capability tracks.
Leave the client able to continue
The engagement should leave understandable definitions, usable records, clear operating responsibilities and a way to carry the next review. Recurring work is agreed because it serves a continuing need.