Operational Core — The Records Behind the Work
Manage the people, work, events, communication, knowledge, and relationships that support HEPO's three offerings alongside existing business systems.
Projects & Collaboration: organise a shared effort
Connect work, participants, events, knowledge, and reusable project templates in one shared operating context.
Connect work, participants, events, knowledge, and reusable project templates in one shared operating context.
Projects & Collaboration provides HEPO's records for organising a shared effort. A project brings together work, people, events, communication, content, and media. Templates provide a reusable starting structure for recurring efforts such as onboarding, reviews, or a product launch.
The project is the context in which activity takes place. Its connected records support the three offerings, while each offering retains its own decisions, evaluation, or learning purpose.
Carry an onboarding effort together
An onboarding project starts from an agreed template. The owner identifies participants and adapts the relevant work, reviews, and reference content to this situation. The team can then follow the effort through its connected tasks and events, rather than reconstructing it from a kickoff document alone.
A template is a starting point. Its usefulness depends on whether its assumptions still fit the people, responsibilities, and work involved. Reusing a template does not establish that the earlier effort succeeded or that the next one will.
The project and its working records
| Element | Contribution |
|---|---|
| Project record | Identifies the shared effort and the organisational context |
| Work items | Describe the tasks, deliverables, and lifecycle the team is carrying |
| Participants and relationships | Connect people and units to their role in the effort |
| Events and communication | Provide the reviews, discussions, and follow-ups |
| Content and media | Keep briefs, instructions, and supporting material connected |
| Templates | Preserve a reusable shape that can be examined and adapted |
Works owns the work-item account. Calendar owns occurrences, and Communication owns exchanges. The project connects their contribution to the shared effort.
Development journeys use this foundation
Achievement Campaigns & Programmes use shared project and work capabilities to support development. Their open participation, assigned journeys, progress, and recognition remain responsibilities of the development offering.
In that application, a template supplies the campaign's reusable structure, setup prepares the instance, and the project instance carries an employee's programme. Template definitions include completion criteria, difficulty, enrolment, template type, and trophy tier. The employee's journey connects those definitions to actual participation and work. Development programmes are a central use of this foundation, alongside the organisation's existing project-management arrangements.
Simulation & Gamification can supply an exploration or learning activity within a wider journey. An activity is not the whole programme, and a shared project is not automatically a multiplayer experience.
Learn from the effort that was recorded
A retrospective can follow work, events, and communication in the project context. Process analysis can examine the available flow evidence. Participants can contribute their account of what worked and what did not. A later template revision can carry the practical learning forward.
Project owners choose the responsibilities and review rhythm. Consultants help identify patterns worth reusing; implementers configure templates and connected surfaces. Walk one project from preparation through review, including the access available to an external collaborator if the engagement needs one.
