Why It Matters
Cross-organizational initiatives fail when tool adoption becomes a barrier. Dutch public sector organizations have digital sovereignty constraints. Communities use existing tools effectively. Forcing migration destroys adoption. Openness and integration remove the friction.
Core Principle
Design for interoperability and choice. A collaborator should be able to bring the tools that work best for them. Our role is to connect and coordinate, not to replace.
Problems Addressed
Opportunities Enabled
Examples in Practice
- APIs and integrations that link operational tools without forcing adoption
- Support for open standards (OAuth, SAML, webhooks)
- Bring-your-own-tool workflows for document storage and communication
- Respect for digital sovereignty and local IT governance
Guiding Questions for Decisions
- Does this feature force participants to adopt new tools or remove their choice?
- Can participants integrate their preferred systems here?
- Are we respecting local IT policies and constraints?