# 8.4 Key Considerations for Use Case Design

<figure><img src="/files/bk7BcAWCj1p8HwDiH1o5" alt=""><figcaption></figcaption></figure>

When designing use cases, GET evaluates five core aspects:

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Point of view</td><td valign="top">Explanation</td></tr><tr><td valign="top"><p>① Can contributions be visualized?</p><p> </p></td><td valign="top">Is it easy to score voting, support, and communication with GET Miles?</td></tr><tr><td valign="top">② Is there a natural motivation to use tokens?</td><td valign="top">Does it match the behavior of "wanting to support" and "wanting rewards"?</td></tr><tr><td valign="top">③ Is it possible to form a community?</td><td valign="top">Will relationships between users be created through voting and support?</td></tr><tr><td valign="top">④ Is there secondary value?</td><td valign="top">Is there room for NFTs and tokens to be recirculated and reused?</td></tr><tr><td valign="top">⑤ Is there room for governance and co-creation?</td><td valign="top">Is the design allowing users to be involved in production, planning, and events?</td></tr></tbody></table>

Use cases should empower users to "realize value through action", not merely "introduce Web3" superficially.


---

# 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://docs.global-entertainment-token.org/8.-use-cases-and-deployment-scenarios/8.4-key-considerations-for-use-case-design.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.