> For the complete documentation index, see [llms.txt](https://open-dataspaces.gitbook.io/ods-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-dataspaces.gitbook.io/ods-docs/introductory-guide/open-data-spaces-introductory-guidebook-for-users/08-outro.md).

# Chapter 8: Conclusion

## 8.1 Summary

This document was written with the aim of organizing the perspectives needed for users to evaluate entry into dataspaces-related businesses — specifically, whether to enter, what roles their organization can play, and how to allocate initial investment.

* **Chapter 2** organized the changes in industrial structure and the background context that makes necessary of Open Dataspaces.
* **Chapter 3** presented the fundamental concepts of Open Dataspaces and the significance of its three pillars (DAD, OSI, and IUC), and organized four entry patterns available to users.
* **Chapter 4** organized the roles of participants in Open Dataspaces and the positioning of the organization itself, while **Chapter 5** presented a four-step process for making the entry decision.
* **Chapter 6** covered the implementation planning process, and **Chapter 7**!organized the three stages of Evaluation, Proof of Concept, and Rollout (GTM).

What this document has presented is neither a "universal architecture" nor "the one right answer." The focus has been on systematically organizing the points of uncertainty that users are likely to encounter, and providing a foundation for making informed decisions.

## 8.2 Deciding "How Far Not to Go" Determines the Success of Entry

A consistent theme throughout this document has been the importance of clarifying "how far not to go" — even more so than "how far to go." Distinguishing the areas the organization itself will handle, the areas a managed service will handle, the areas integration partners will handle, and the areas to be added in the future — and clearly defining the boundaries between each — is what makes it possible to avoid excessive initial investment and sustain participation over time.

## 8.3 Entry as a Users Begins with "Using"

Unlike servicers, the first step for users is often to begin by "using" ODP-implemented managed services and applications. Before any technical implementation, it is an important prerequisite to understand "what it means to provide data" and "what conditions and responsibilities that entails."

## 8.4 Start Small: Three First Steps

Open Dataspaces may appear complex, but at its core it is a collection of simple activities — connecting, coordinating, and complementing. The three things users need to take their first step are:

1. Define the minimum use case the organization will take on
2. Rather than attempting to implement everything in-house from the outset, leverage managed services to advance incrementally
3. Learn through connections with integration partners, and expand the scope of participation in a phased manner

It is our hope that this document serves as a resource to support your evaluation and preparation, and as an opportunity to discover new possibilities for data collaboration and data utilization through Open Dataspaces.