> For the complete documentation index, see [llms.txt](https://productcommittee.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://productcommittee.docs.intersectmbo.org/committee-outcomes/2030-long-term-cardano-vision/insights-collected/insights-collection-workshops/workshop-9th-march-2025-japan.md).

# Workshop - 9th March 2025 - Japan

## Data Points

* [Notes](https://product.cardano.intersectmbo.org/docs/workshops/japan-mar-2025/)

## Key Learnings

* Language Matters: Reliance on Google Translate highlighted the need for professional translation or bilingual facilitators.
* Hybrid Ineffectiveness: The Tokyo hybrid workshop showed the value of separate in-person and virtual events.
* Planning is Paramount: Rushed planning impacted participation, stressing early and thorough preparation.
* Direct Feedback is Invaluable: The A-F rating provided actionable insights into community priorities.
* Community Engagement Drives Success: Direct engagement strengthens community bonds and fosters ownership.
* Cultural Nuances: Awareness of cultural differences is essential for effective communication.
* Vision Alignment: Strong support for Cardano's original vision, especially banking the unbanked and interest in Africa/LATAM.
* Governance Desire: A strong desire for participation in Cardano's future governance.
* Decentralization Priority: Maintaining and improving decentralization is a key concern.
* Global Strategic Advantage: Cardano's global presence, including the Japanese community, is a strategic asset.
* Regional Diversity: The Japanese Cardano community varies significantly by region.
* Demographic Considerations: The older demographic presents a challenge in attracting younger members.
* Founding Entity Trust: High trust exists in Cardano's founding entities.
* Daedalus Priority: Ongoing maintenance of Daedalus is crucial for the community.


---

# 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://productcommittee.docs.intersectmbo.org/committee-outcomes/2030-long-term-cardano-vision/insights-collected/insights-collection-workshops/workshop-9th-march-2025-japan.md?ask=<question>&goal=<user_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.