Execution
From the objective the board approved to the task someone finishes on Friday
Initiatives are how a strategy gets delivered. Below them sits a delivery spine you configure — programs, projects, work packages, tasks, activities — and health rolls up from the bottom, computed from the work rather than declared in a status meeting.
- Every level below the initiative is optional; a small team runs initiative → project → task
- Initiative types, priorities, planned budget and an external reference for your PMO tool
- Weighted completion, overdue and late counts, schedule and scope health
- Health reads unknown until something earns a colour; overrides need a recorded reason
In the application · Govern
- Initiatives
- Programs
- Projects
- Milestones & deliverables
- Work packages
- Tasks & activities
- Traceability
- InitiativeCyber defence modernisation58%
- ProgramIdentity, PAM & SOC automation64%
- ProjectPAM completion & secrets migration71%
- TaskMigrate service accounts100%
- TaskVault break-glass procedure40%
- ProjectSOC runbook automation—
Computed from tasks and milestones. Unknown until something earns a colour; manual override only with a recorded reason.
Delivery spine
A structure you configure, not one you inherit
Each initiative names the strategy it serves and the entity that owns it. A portfolio office adds programs and work packages; a two-person team does not have to. Milestones carry planned, forecast and actual dates.
- Initiatives with type, priority, planned budget and owning entity
- Programs and projects with milestones and deliverables
- Work packages, tasks and activities with assignees and due dates
- Projects linked to the risks they reduce and the controls they put in place
- StrategyTechnology & cyber resiliencev3 · published
- ObjectiveResidual cyber risk within appetiteweight 10% · 2 risks
- InitiativeCyber defence modernisationfunded · on track
- ProjectPAM completionmilestone 31 Oct
- TaskMigrate service accountsdue Friday
- PersonSarah Whitfieldassignee
Roll-up and health
Computed from the work, never from the slide
Completion, schedule, budget and scope health roll up from tasks and milestones to the initiative. Where the data is not there, health reads unknown, never a green that nothing has earned.
- Weighted completion by task and milestone
- Overdue and late counts at every level
- Budget health fed from Finance on the same spine
- Manual override only with a recorded reason and author
- InitiativeCyber defence modernisation58%
- ProgramIdentity, PAM & SOC automation64%
- ProjectPAM completion & secrets migration71%
- TaskMigrate service accounts100%
- TaskVault break-glass procedure40%
- ProjectSOC runbook automation—
Computed from tasks and milestones. Unknown until something earns a colour; manual override only with a recorded reason.
Traceability
One answer for the executive and the employee
Walk the chain in either direction: from a strategy down to the person assigned to a task, or from an activity up to the objective it serves. Risk, control and asset records join the same chain.
- Strategy → objective → initiative → project → task → person
- Traceability view from any node
- Lifecycle per record type, run by the workflow engine
- Every transition and edit in the record history
- PaymentsDomain
- Card acquiringCapability3 risks2 policies
- Merchant settlementService4 controls2 assets
- Daily reconciliationProcess1 risk2 controls1 finding
Every level links out to risks, controls, policies, findings, assessments, and assets
Framework alignment
Works with your control frameworks
This module shares the platform control library. International standards, sector regulations and your own internal standard are loaded the same way and mapped to one another, wherever you operate.
Solutions by role
Built for your team
See execution and delivery in your environment
A walkthrough scoped to your entities, your frameworks, and the way your programme is actually run.