> For the complete documentation index, see [llms.txt](https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/digital-pathway-framework/sub-themes-and-capabilities.md).

# Sub-Themes and Capabilities

## **Introduction to Sub-Themes and Capabilities**

The Digital and Cybersecurity Pillar framework is built around **sub-themes**, which focus on specific areas of capability within each architecture domain (e.g., Strategy under Business Architecture or Data Management under Data Architecture). These sub-themes provide the structure for evaluating digital maturity.

To assess these sub-themes, the framework incorporates **capabilities**, **Indicators of Good Practice (IGPs)**, and **Metrics/KPIs**. Together, these elements provide measurable criteria for benchmarking maturity, identifying gaps, and planning improvements.

{% embed url="<https://app.guideflow.com/player/vkm9ol2u3p>" %}

***

## **How Sub-Themes Drive Focus**

Sub-themes define **what needs to be assessed** in each architecture domain. They narrow the scope, ensuring critical aspects of digital maturity and cybersecurity are not overlooked.

**Example Sub-Theme: Data Management (Data Architecture)**

* **Definition**: Secure storage and access controls are in place, ensuring data is organised and protected.
* **Purpose**: To establish the foundational ability to manage and safeguard data, supporting operational goals and compliance.

***

## **Capabilities, IGPs, and KPIs: The Building Blocks**

Each sub-theme is supported by underlying capabilities, IGPs, and Metrics/KPIs to provide measurable insights into maturity.

**Example: Data Management**

* **Capabilities**:
  * **Processes**: Secure data storage and retrieval processes documented and followed.
  * **Tools**: Use of data storage tools with access controls and backup capabilities.
  * **People**: Defined roles for managing access and data integrity.
* **Indicators of Good Practice (IGPs)**:
  * Not applicable at this foundational level.
* **Metrics/KPIs**:
  * Percentage of data secured with proper access controls.
  * Number of unauthorised access incidents.

***

## **Progressing Through Maturity Levels**

Sub-themes and their capabilities form the foundation for evaluating and improving maturity. Each is mapped to the maturity model’s three levels: Bronze, Silver, and Gold.

**Bronze (Foundational)**

Focus: Establish essential capabilities for compliance and basic security.

* **Example Outcome**: Secure storage processes are documented and implemented with basic access controls.

**Silver (Managed)**

Focus: Formalise and manage practices to ensure consistency and resilience.

* **Example Outcome**: Automated tools for backup and periodic audits of data access are in place.

**Gold (Optimised)**

Focus: Optimise practices for continuous improvement and advanced resilience.

* **Example Outcome**: Fully encrypted storage, real-time monitoring, and predictive analytics for proactive data management.

***

## **Why Sub-Themes and Capabilities Matter**

* **Clarity**: Sub-themes break down each architecture domain into manageable focus areas.
* **Measurability**: Capabilities, IGPs, and KPIs ensure progress is evaluated quantitatively and qualitatively.
* **Improvement**: This structure provides a roadmap for advancing through the maturity model, targeting specific areas for development.

***

## **What’s Next?**

* Explore detailed assessments for each sub-theme in the [**Assessment Guide**](/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/assessment-guide/preparing-for-the-assessment.md).
* Find actionable steps for improvement in the [**Best Practice Resources**](/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/best-practice-resources/best-practice-guides.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/digital-pathway-framework/sub-themes-and-capabilities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.