A Capability Assessment records current and target maturity scores for a specific Capability within an Initiative. Together, all assessments for an Initiative form a heatmap that answers the central transformation question: where are we now, and where do we need to be?
Each assessment links one Capability to one Initiative and captures two scores on a 1–5 scale:
- current_score — A snapshot of capability maturity when the Initiative was scoped (“as-is”)
- target_score — Where the capability needs to be when the Initiative completes (“to-be”)
The gap (target_score - current_score) is derived at query time, not stored. A large gap means significant transformation work ahead; a zero or negative gap means the capability is already at or above target.
Scoring Scale
| Score | Color | Meaning |
|---|---|---|
| 1 | Red | Deficient — significant gaps or critical issues |
| 2 | Red | Deficient — issues present, needs substantial improvement |
| 3 | Yellow | Developing — adequate but improvement needed |
| 4 | Green | Strong — well-established, minor issues only |
| 5 | Green | Exemplary — best-in-class, minimal effort required |
Red (1–2) capabilities with high target scores (4–5) represent the highest-priority transformation areas. These are where the Initiative must deliver the most change.
One Assessment Per Capability Per Initiative
Each Capability can have at most one assessment per Initiative. This uniqueness constraint is enforced at the database level — attempting to create a second assessment for the same Capability/Initiative pair will fail. Use the upsert action to update existing scores without needing to look up the existing assessment ID first.
Key Fields
| Field | Purpose |
|---|---|
| current_score | Current capability maturity (1–5) — as-is state when Initiative was scoped |
| target_score | Target capability score (1–5) — to-be state when Initiative completes |
| rationale | Optional explanation for the scores — why is the capability at its current level? |
| initiative_id | The Initiative these scores belong to |
| capability_id | The Capability being assessed |
Using Assessments in an Initiative
Capability Assessments are typically created during the Planning stage when the Initiative is being scoped. The workflow:
- Identify the Capabilities relevant to the Initiative’s scope
- Score each Capability’s current maturity (be honest — optimistic scores produce unreliable roadmaps)
- Set the target score for each Capability (what does “done” look like for this engagement?)
- Review the resulting heatmap to validate scope and surface the highest-gap capabilities
During Build, assessments can be updated if the understanding of current maturity changes based on deeper discovery. Target scores typically remain stable unless scope changes.
Heatmap Visualization
All assessments for an Initiative render as a heatmap table:
| Capability | Current | Target | Gap |
|---|---|---|---|
| Invoice Processing | 2 | 4 | +2 |
| Reporting & Analytics | 3 | 4 | +1 |
| Data Quality Management | 1 | 5 | +4 |
| User Authentication | 4 | 4 | 0 |
High-gap, low-current capabilities surface as red heatmap cells with large gap numbers. These become the focus areas for Change Proposals and Initiative Tasks.
Relationships at a Glance
| Related Concept | Relationship |
|---|---|
| Initiative | Assessments belong to an Initiative |
| Capabilities | Each assessment scores one Capability |
| Change Proposals | High-gap capabilities drive what Changes need to be proposed |
Best Practices
Score current state honestly, not aspirationally.
The heatmap is only useful if current scores reflect reality. Scoring a 3 (“it’s okay”) when the capability is genuinely a 1 (“it’s broken”) produces a misleading picture and an under-resourced Initiative. Red cells are expected — that’s why the Initiative exists.
Involve subject matter experts in scoring.
Current maturity scores should come from the people who live with the system, not from project sponsors. SMEs will score more accurately; sponsors tend to score more optimistically.
Set target scores based on what the Initiative needs to deliver.
Target scores do not have to be 5. If the current capability is a 2 and the Initiative only needs it to reach 3 to satisfy the business outcome, a target of 3 is correct. Over-scoping to “achieve 5 on everything” creates unnecessary work.
Add rationale to support the scores.
A rationale field note like “Invoice matching fails 15% of the time due to legacy field mapping errors” is far more useful during stakeholder review than a bare score of 1. Rationale turns a number into a shared understanding.
Reassess after major discovery milestones.
An assessment created at Initiative kick-off may be outdated after two weeks of discovery. Update scores when significant new information arrives — the heatmap should evolve as understanding improves.
Next Steps
- Understand Capabilities — Learn how Capabilities are defined and organized
- Scope Initiatives — Understand how assessments fit into Initiative planning
- Review Change Proposals — See how high-gap capabilities drive requirement changes
Pro Tip: Before reviewing the heatmap with sponsors, add rationale notes to all red cells. A sponsor who sees a red score without context will ask “why?” — having the answer ready in the rationale field saves time and builds credibility.
Support
- Documentation: Continue reading about Capabilities and Initiatives
- In-App Help: The AI assistant can help interpret heatmap patterns
- Email: support@catalio.ai
- Community: Share scoring approaches with other Catalio users