Imagine the public sector (government, cities, schools, and hospitals) is a massive, old-fashioned library. For decades, this library has relied on buying expensive, locked books from specific publishers (proprietary software). If the library wants to change a page in a book, they have to call the publisher, wait, and pay a fee. If the publisher goes out of business, the library is stuck.
Now, imagine a new way of working: Open Source. This is like a library where the books are written by a community. Anyone can read them, fix typos, add new chapters, or translate them. The "source code" is open for everyone to see.
But here's the problem: The library staff (government employees) are great at managing books, but they aren't always experts in how to write or edit these community books. They are scared of breaking things, worried about legal rules, and don't know who to trust.
This is where the OSPO (Open Source Program Office) comes in.
Think of an OSPO as the "Librarian's Guide to the Community Book Club." It's a special team inside the government whose only job is to help the library safely use, fix, and share these community books.
The Big Discovery: One Size Does Not Fit All
The researchers in this paper went around Europe (EU, Norway, Iceland, etc.) and interviewed 18 different "Librarian Guides" (OSPOs). They realized that just like libraries come in different shapes and sizes, these OSPOs come in six distinct archetypes (personality types).
Here are the six types, explained with simple analogies:
1. The National Architect (National Government OSPOs)
- Who they are: The big bosses at the national level (like the Ministry of Digital Affairs).
- What they do: They are the City Planners. They don't usually write the code themselves. Instead, they draw the blueprints for the whole country. They say, "All our cities must use this type of open book," and they build the central library where everyone can find the best books.
- Example: France, Germany, Italy. They create the rules and the big platforms that local towns can use.
2. The Internal Coach (Institution-Centric OSPOs)
- Who they are: A team inside a single large organization (like a specific Tax Agency or the European Commission).
- What they do: They are the Personal Trainers for that one gym. They teach the employees inside their building how to lift weights (write code) safely. They make sure the internal team isn't using dangerous equipment and that they are following the rules. They don't worry about the whole city; they worry about their own gym.
- Example: The European Commission's internal IT team, or the Dutch Tax Agency.
3. The Neighborhood Organizer (Local Government OSPOs)
- Who they are: Teams working for a specific city or town (like Paris or Bratislava).
- What they do: They are the Block Captains. They know exactly what their neighborhood needs. Maybe the town needs a new app for reporting potholes. They build it, share it with neighbors, and help other small towns use it too. They are hands-on and very practical.
- Example: The City of Paris or the City of Ventspils.
4. The Clubhouse Manager (Association-Based OSPOs)
- Who they are: Groups formed by many towns or cities joining together (like a union of mayors).
- What they do: They are the Community Center Directors. One small town can't afford to build a swimming pool, but if 50 towns chip in, they can. This OSPO manages the "pool" (the software) so everyone can swim. They handle the legal paperwork and the money so no single town has to do it alone.
- Example: OS2 in Denmark (a network of municipalities) or Open Cities in the Czech Republic.
5. The University Lab (Academic OSPOs)
- Who they are: Teams inside universities and research centers.
- What they do: They are the Science Fair Judges. Professors invent cool new software for their research. But they don't know how to sell it or license it. The OSPO helps them decide: "Should we give this away for free to the world, or sell it to a company?" They bridge the gap between a classroom idea and the real world.
- Example: Trinity College Dublin or Lero in Ireland.
6. The Civic Hero (Organisations with OSPO-like functions)
- Who they are: Non-profits or civil society groups (not part of the government at all).
- What they do: They are the Volunteer Firefighters. The government is too slow or too scared to act, so these volunteers step in. They build the tools the government needs, teach the government how to use them, and then hand them over. They are the "outside help" that makes the system work.
- Example: Code for Romania.
Why Does This Matter?
The paper argues that governments often try to copy-paste the "Corporate" way of doing things, which doesn't work for public services.
- The Problem: Governments are often risk-averse (scared of making mistakes), rely on outsourcing (hiding behind vendors), and have short-term budgets.
- The Solution: You need the right type of OSPO for your situation.
- If you are a small town, don't try to be the National Architect. Join a Clubhouse Manager (Association) to share costs.
- If you are a big university, you need a University Lab to handle research rights.
- If you are the whole country, you need a National Architect to set the rules.
The Takeaway
The paper concludes that OSPOs are not just IT departments; they are "Change Agents."
Think of them as the translators between two different languages:
- The Language of Politics: "We need to save money, be transparent, and be secure."
- The Language of Code: "We need to share this, fix this bug, and let the community help."
Without these translators (OSPOs), the government stays stuck in the old, expensive, closed way of doing things. With them, governments can build a digital future that is open, shared, and owned by the people.
In short: If you want your government to be modern and efficient, you don't just need better software; you need a dedicated team (an OSPO) that knows how to manage the "community book club" of technology. And that team looks different depending on whether you are a mayor, a minister, or a professor.