# O2.7 Design systems to capture evolving user needs

{% tabs %}
{% tab title="Principle" %}
[O2 Evolve with evidence](/safeguards/universal-dpi-safeguards-framework/principles/operational-principles/o2-evolve-with-evidence.md)
{% endtab %}

{% tab title="Risk" %}
[R13 Exclusion ](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-inclusion.md)

[SV1 Digital distrust, ](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-structural-vulnerabilities.md)
{% endtab %}

{% tab title="Life Cycle Stage" %}
[L5- Operations and Maintenance ](/safeguards/universal-dpi-safeguards-framework/responsible-authorities/r3-donor/l5-operations-and-maintenance.md)
{% endtab %}
{% endtabs %}

## Practice

* Monitor DPI usage patterns and user outocmes to ensure the system adapts to shifting demands.
* Identify and close gaps between expected and actual usage.


---

# Agent Instructions: 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:

```
GET https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/o2.7-design-systems-to-capture-evolving-user-needs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.