I just published a new strategy simulator that explores a question I keep hearing across European companies:
What is an OSPO actually for?
Instead of answering it directly, the simulator puts you in the role of an Open Source Program Office lead at a European software company.
Over three simulated years, you have to make a small number of strategic decisions. How you position the OSPO. How you respond to AI pressure. How you handle cloud dependency once regulation arrives.
There is no scoring and no winning path. Each choice solves one problem while quietly creating another.
The goal is not to test knowledge, but to surface trade-offs that are easy to miss when we talk about digital sovereignty in the abstract. Control versus speed. Trust versus authority. Compliance versus long-term optionality.
If you work with or around an OSPO, I would love your perspective after playing it.
-
Which decision felt most uncomfortable?
-
Where did you feel you lost control without noticing?
-
Did the outcome match how your organization operates today?
You can try the simulator here:
I also wrote a longer blog post that explains why I think this question will matter even more for European companies by 2026:
David Peter Hirsch | Community Ecosystem Senior Manager
Looking forward to the discussion.