Sovereign workplace
In shortA sovereign workplace is not a product but five stages in the right order.
At a glance
- Components
- Video meetings, file storage, chat, email and calendar, document editing, identity management
- Best-known bundle
- openDesk from ZenDiS, built from Nextcloud, OpenTalk, Open-Xchange, Collabora and other parts
- Realistic timeframe
- Twelve to eighteen months for one hundred to three hundred workplaces; stages one and two in eight weeks
- Most common mistake
- Starting with email or document editing instead of video meetings
- What gets worse
- Integration between tools, search across all content, mobile applications, telephony integration
- Partial success counts
- Three of five stages in your own hands beats a debate of principle that ends at zero
A sovereign workplace is not a product you buy but an assembly. That is exactly where most projects fail: they look for a replacement for one bundle and find five separate tools that have to be introduced at different speeds.
The order matters more than the selection.
Why this order
Video meetings first, because no data moves. A new link in the calendar, an afternoon of work, and if it does not work you switch back. What you gain is proof that a European tool is not automatically worse — and you need that for everything that follows.
Then the cold half of file storage: archives, closed projects, contract folders. Nobody co-edits there, so it moves without friction.
Chat is politically harder than both, because history and habit hang on it. Expect that old history will not come across in full, and say so in advance.
Email and calendar only after that. The migration itself is solved; the risks are the deliverability of the new sending domain and the historical archive.
Document editing last, because that is where macros, templates and external correspondence sit.
What gets worse
The seamless integration is gone. Search across all content is weaker. Mobile applications are rougher. And no combination reaches the same level of telephony integration.
Say so in advance and you get patience. Leave it out and you lose it at the first incident.
What partial success is worth
For one hundred to three hundred workplaces, twelve to eighteen months is realistic alongside daily operations. Stages one and two are achievable in eight weeks.
And if it ends after stage three because the rest does not pay off, that is not half a result. Three of five layers in your own hands is more than any debate of principle achieves that ends at zero. That the public sector leads here has a reason of its own — see Public money, public code.
Common questions
- Why start with video meetings?
- Because there is no data migration. The effort is one afternoon, the risk is nil, and you get visible proof that a European tool works. You need that proof for every stage that follows.
- Is openDesk the only bundle?
- It is the best known, because it was built for public administration. Companies often assemble their own — Nextcloud or hosted storage, OpenTalk or Nextcloud Talk, Element for chat, a European mail provider, LibreOffice or Collabora.
- What is the hardest part?
- Document editing, because of macros, templates and external correspondence. That is why it comes last. Second hardest is the calendar, with external invitations, resources and delegation.
- What if we stop halfway?
- Then you keep the stages you moved. Stopping after stage three is not failure but a result — provided it is taken as a decision rather than as exhaustion.
Sources
See also
Related terms
- Public money, public codeSoftware the public paid for should be software the public may use.
- Digital sovereigntySovereignty is not a state but the answer to four questions: law, operations, data, capability.
- Vendor lock-inLock-in is not a property of a product. It is a number: what leaving would cost you.