> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/implementation-playbook/development/implementation/design-service/2-designing-the-future-service-to-be/2.1-define-the-vision-and-future-experience.md).
# 2.1 Define the Vision and Future Experience
Define the future vision
\\
This 15 minute warm up activity helps teams define a clear future vision for the service that will guide ideation and to-be mapping.
How to do it
In groups, describe what the future service should look and feel like.
**Ask groups to answer these questions:**\
What is the future service?\
How does it help users?\
What are the most important qualities or features?
They can write short statements, use post-it notes or sketch a simple illustration.
Outputs
* [ ] One future vision per group (written or sketched).
* [ ] A clear reference point for ideation and to-be mapping.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://specs.govstack.global/implementation-playbook/development/implementation/design-service/2-designing-the-future-service-to-be/2.1-define-the-vision-and-future-experience.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
