Performing the Self-Assessment

Scoring Individual Questions

Each question within a Key Process Area (KPA) includes a set of answer options mapped to a score (typically ranging from 0 to 100). Questions are usually presented with a six-option response scale, and scores from 0 to 100 are progressively assigned across options 0 to 5. The progression between response options is not uniform; instead, different values were assigned by the authors based on their assessment of the maturity level represented by each option.

How to Score

• Review the question and its context carefully

• Select the option that best reflects your current state

• Assign the corresponding numerical score

• Be evidence based: Avoid aspirational scoring

• Score current state only: Not planned or future capabilities

• Use consensus: Discuss differences and agree as a group

• Be consistent: Apply the same interpretation across all KPAs

If your organization sits between two options, select the lower score unless there is strong evidence to justify the higher level.

Calculating KPA Scores

Each KPA contains multiple questions.

Method

• Sum the scores for all questions within the KPA

• Divide by the number of questions

Formula:

KPA Score = (Sum of Question Scores) ÷ (Number of Questions)

Example

If a KPA has 4 questions scored:

• 50, 75, 50, 25

KPA Score = (50 + 75 + 50 + 25) ÷ 4 = 50

Determining Domain and Overall Maturity

Domain Scores

Each domain consists of one or more KPAs.

• Calculate the average of all KPA scores within the domain

Domain Score = (Sum of KPA Scores) ÷ (Number of KPAs)

Mapping Scores to Maturity Levels

Use the following ranges to determine maturity level:

Two approaches may be used:

1. Weakest Domain Approach (Recommended for decision-making)

• Overall maturity = lowest domain level

• Ensures balanced capability across all areas

2. Average Score Approach (Recommended for tracking progress)

• Overall score = average of all domain scores

• Provides a general view of maturity progression

Both perspectives should be considered together.

Interpreting Results

Identify Strengths and Gaps

• Highlight domains with higher maturity (strengths)

• Identify domains with lower scores (priority gaps)

Assess Balance Across Domains

Maturity should be relatively balanced. Significant variation between domains may indicate:

• Over-investment in technology without adoption

• Strong governance without implementation

• Adoption without interoperability

Focus on:

• Low-scoring domains

• KPAs with the greatest impact on interoperability and data quality

• Areas that enable progress across multiple domains

Set realistic goals:

• Short-term: Improve by one level in priority domains

• Medium-term: Achieve balanced Level 3 or Level 4 maturity

• Long-term: Progress toward Level 5 optimization