> For the complete documentation index, see [llms.txt](https://usecaseframework.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usecaseframework.openactive.io/understand-and-plan/activities.md).

# Activities

## One - Identify and prioritise use cases

Use case communities should work collaboratively to define use cases by:

1. Conducting [user research](https://www.gov.uk/service-manual/user-research/how-user-research-improves-service-design) to help understand the problem more deeply, identifying qualitative and quantitative insights which evidence the need for the use case. This may use existing insights and reports or explore needs through direct engagement between individuals and organisations representing the use case community, and the users they are designing for.
2. Completing [use case templates](https://docs.google.com/presentation/d/14_UsKGtBUKPGqiycFEhDF_UUqOTiEvg58o0-l68TLqk/) that identify the gap between the current (problem) state and desired (goal) state.
   * Who are the users that the use case impacts?
   * What is the nature of the problem?
   * Why is it important to address?
   * What impact will addressing the problem have?
3. Use case communities can prioritise use cases using the [decision-making matrix](/appendix-five-use-case-template/use-case-prioritisation-decision-making-matrix.md), if required, due to the number of use cases identified. The matrix provides a means to prioritise use cases against [OA’s strategic objectives](/introducing-the-framework/context.md).

## Two - Plan delivery of OA solutions to the defined use cases

Once the viability of a use case has been agreed, a plan can be created to outline the roadmap for its development and implementation through the following steps:

1. Define [MEL criteria](/appendix-three-mel-framework/overview.md)
   * Define SMART objectives
   * Define SMART KPIs
2. Define the [data requirements](/appendix-four-data-requirements-framework/data-requirements-framework.md) needed to deliver your SMART objectives
3. Identify what a [minimum viable product](https://en.wikipedia.org/wiki/Minimum_viable_product) (MVP) looks like
4. Identify the initial pilot publishers and/or users of the data
5. Outline the [funding model](/appendix-six-funding-model-guidance/funding-model-guidance.md) for the use case
6. Create a timeline for mobilising the use case

## Responsibilities

<figure><img src="/files/Bbt2qMmVykbZo3eeqER2" alt="Responsibility chart for the understand and plan stage of the framework. It outlines the activities in the stage, and which of three groups are responsible for them, OA governance, OA community or Use Case Communities. In this stage, all activities are the responsibility of use case communities, with OA governance and OA community supporting. The first activity is identifying and prioritising use cases. This activity has two parts. One - defining use cases, and two - prioritising use cases. The second activity is planning delivery of use cases. This activity has three parts. One - sourcing funding for use cases, two - defining MEL criteria and data requirements, three - creating a development road map."><figcaption><p>Understand and plan responsibility chart</p></figcaption></figure>


---

# 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://usecaseframework.openactive.io/understand-and-plan/activities.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.