> For the complete documentation index, see [llms.txt](https://template.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://template.ishare.eu/business-and-organisational-building-blocks/business-building-blocks/use-case-development/guiding-questions.md).

# Guiding Questions

{% hint style="info" %}
**Purpose of this Building Block Component:** Use cases are the anchor points of any data space; they provide a concrete reason for stakeholders to participate and collaborate. Each use case should be mapped along: Stakeholders involved (who needs what data, and why), Data flows and value exchanges, Business and sustainability outcomes, and Scalability and replicability potential.
{% endhint %}

{% hint style="success" %}
**Purpose:** Create a recognisable name and ID for easy reference.
{% endhint %}

1. **Use Case Title and Identifier**

* *What is the name of the use case?*
* *Is there an identifier or code used internally or by the consortium?*

{% hint style="success" %}
**Purpose:** Define the environmental or operational challenge being addressed.
{% endhint %}

2. **Problem Definition & Context**

* *What environmental, regulatory, or market need does this use case aim to solve?*
* *What is the context in which this problem occurs (sector, region, system)?*
* *What makes the problem relevant for the Green Deal or EU sustainability goals?*
* *How can gaps in data availability or quality be addressed when choosing use cases?*

{% hint style="success" %}
**Purpose:** Clarify the goals and ambitions of the use case.
{% endhint %}

3. **Use Case Objectives**

* *What are the specific outcomes this use case aims to achieve?*
* *Which sustainability metrics or business goals will it support?*
* *How will success be measured?*
* *How can business, regulatory, and technical requirements be integrated efficiently?*

{% hint style="success" %}
**Purpose:** Identify key actors in the data value chain and their roles.
{% endhint %}

4. **Stakeholder Involvement**

* Who are the key stakeholders involved (e.g., data providers, processors, users, decision-makers)?
* *What role does each actor play (e.g., share data, analyse, visualise, take action)?*
* *Are any public authorities, SMEs, or NGOs participating?*
* *How can participants provide input to ensure use cases are relevant and practical?*

{% hint style="success" %}
**Purpose:** Describe what data is needed and where it comes from. What types of data are required (e.g., emissions data, material flows, building info)?
{% endhint %}

5. **Data Needs & Sources**

* *What types of data are required (e.g., emissions data, material flows, building info)?*
* *Who are the data providers?*
* *What is the format, frequency, and level of detail of the data?*
* *Are there interoperability or standardisation challenges?*

{% hint style="success" %}
**Purpose:** Describe how data will be shared and exchanged between parties.
{% endhint %}

6. **Data Sharing & Interactions**

* *What data sharing agreements or governance rules are needed?*
* *Which participants will consume or enrich the data?*
* *How will data sovereignty and access control be ensured?*
* *Is there a need for a specific Trust Framework or data space technical connector?*
* *How can alignment among participants be maintained during implementation*

{% hint style="success" %}
**Purpose:** Show how the use case integrates with the broader architecture.
{% endhint %}

7. **Architecture**

* *Which building blocks (Governance, Business, Technical) are used?*
* *Will the use case integrate a Data Space Connector, a Trust Anchor, or a data intermediary?*
* *Does it follow some standards, like DSSC, iSHARE, SIMPL, etc?*
* *What mechanisms ensure smooth scaling and integration with existing systems?*
* *How can coordination be improved across federated operators or multiple ecosystems?*
* *Which tools best support collaboration and scaling?*

{% hint style="success" %}
**Purpose:** Define the development status and roadmap of the use case.
{% endhint %}

8. **Timeline and Maturity**

* *Is this a concept, pilot, or operational use case?*
* *What are the key milestones (e.g., prototype, deployment, scaling)?*
* *What technical or organisational dependencies exist?*
* *How can insights from abandoned use cases guide future decisions?* 
* *How can feedback loops be structured to allow flexible adaptation?*

{% hint style="success" %}
**Purpose:** Summarise the added value for stakeholders and broader sustainability goals.
{% endhint %}

9. **Value Proposition & Expected Impact**

* *What concrete value does this use case deliver to stakeholders (economic, social, environmental)?*
* *How does it contribute to Green Deal objectives (e.g., circular economy, emissions reduction)?*
* *Is there potential for replication or scaling?*

{% hint style="success" %}
**Purpose:** Identify potential challenges and mitigation strategies.
{% endhint %}

10. **Risks and Barriers**

* *What are the technical, organisational, or legal barriers?*
* *Are there risks related to data quality, privacy, or stakeholder engagement?*
* *How can these be mitigated?*

{% hint style="success" %}
**Purpose:** Ensure strategic alignment with regulatory and policy frameworks.
{% endhint %}

11. **Alignment with EU Policies or Standards**

* *Does the use case align with EU Taxonomy, CSRD, EPBD, SFDR, or other legislation?*
* *Are any standardisation frameworks (e.g., ETSI, CEN/CENELEC) being applied?*

{% hint style="success" %}
**Purpose:** Provide diagrams, mock-ups, or links that support understanding.
{% endhint %}

12.**Supporting materials (Optional)**

* *Data flow diagrams*
* *Mockups or MVP screenshots*
* *Stakeholder maps*
* *Links to documentation or previous results*


---

# 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://template.ishare.eu/business-and-organisational-building-blocks/business-building-blocks/use-case-development/guiding-questions.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.