Case Study: Positioning of CIO and IT Director
Background
With the introduction of the CIO system within the government, many governmental organizations have started appointing a CIO (Chief Information Officer). The background of this decision was that many governmental organizations make use of a Shared Service Centre which they wanted to have more control over.
Challenge
There are many different interpretations regarding the role of the CIO and how this person should relate to the IT directorate responsible for execution. Some governmental organizations, therefore, have a CIO who is also responsible for execution, while others opt for a more policy-oriented CIO.
Approach
To make a considered decision, it is necessary to gain insight into the nature, scope, and impact of digitalization. Is it a modernization effort or a digital transformation, is it about many small projects or a set of large programs worth millions, and does it affect a part or all employees, and are they located in one or multiple locations? Depending on the answers to these questions, a merger of policy and execution is needed or a clear separation.
Result
For the client in question, we concluded that integral management of policy and execution was necessary. The underlying reason was that a significant regulatory change was imminent, impacting both the organization of digitalization and its execution. To avoid duplicate command lines, a CIO was chosen who was responsible for both policy and execution.
What Did We Learn?
The complexity of managing digitalization in a largely digital world requires short lines of communication and clear priorities. Separating policy and execution would lead to dual priority settings.
Legacy Systems
Virtually all governmental organizations have legacy systems and struggle to implement strategically desired changes. This is not only a technological issue but also a matter of people, processes, and not least, money. About ten years ago, we often encountered CIOs who believed that the more money was invested in digitalization, the lower the operational IT costs would be. After all, that was why one invested. In practice, with the increase in digitalization, more and more processes are also being digitized.
The CIO system within the government is thus a crucial part of the strategy to modernize the Dutch government and prepare it for the challenges of the digital future. However, the practice of digitalization is stubborn. Outsiders often only see the overly expensive IT projects and hear about what went wrong behind the scenes. Knowledge and understanding of why things go wrong are limited among both executors and recipients and supervisors.
As QA Consulting, we have been observing programs and projects within the government and semi-government for ten years. So, if you ask us why large IT projects often go wrong there, our answer is: there is a confluence of causes and circumstances:
1. Special Requirements and Wishes
While the private sector easily stores and manages information worldwide, the government rightly requires that data remains in Europe and often even in special government data centres. These are centres that thirty years ago were already concluded to be less well managed and operated than the market. In the future, managing their own data centres for the government is estimated to be five to ten times more expensive than leaving information storage to the market. It is therefore expected that governments will also transfer their information to ‘the market’, particularly to the domains of Amazon, Microsoft, and Google.
2. No Standardized Processes
While the private sector operates from globally standardized processes, most government processes are completely different from those of the surrounding countries. Look at departments like the tax office or UWV. No country around us has similar legislation and has digitized its services as much as the Netherlands. The number of European tenders is also nowhere as high as here. Because we want to be an attractive business climate, the Netherlands has many specific, customized procedures and rules for companies. For example, the Tax Office has so-called ‘rulings’, statements from inspectors on how to handle specific cases. Think of IKEA, Starbucks, Procter & Gamble, Nike, and UBS, all companies that made fiscally favourable agreements with the Dutch tax office about their tax obligations. All these agreements lead to deviations in the rules, which are all put into a digitized system.
3. Change Fatigue
Knowledge of many of the points mentioned under 1 and 2 is scarce and slowly disappearing. Due to aging and staff turnover, much depends on individuals with specific knowledge and skills. Individuals under a lot of pressure who often need to be in ten places at once. Combined with the complex consultation structures and many organizational changes over the years, people have become ‘change tired’. They no longer see the usefulness of yet another new way of working.
4. Too Large Projects
Many projects and programs within the government are large. For years, the ICT Advisory Board (AC/ICT), formerly BIT, has been stating that projects should be smaller. But how do you do that when you have to replace an entire system, such as that of value-added tax? Unfortunately, you can’t do that piece by piece. At the same time, the whole is too large to replace at once. A devil’s dilemma that applies to many government systems.
5. Lack of Knowledge among Administrators
Many administrators still have inadequate knowledge of digitalization. In the majority of vacancies at the General Administrative Service (ABD), the word digitalization, IT, or ICT does not appear. The ABD does offer training in digitalization, but managing programs and projects is not something you learn in a course. Experience provides the most insight into what is possible, what risks there are, and what the best approach is. Furthermore, many people who do have that digital experience and sensitivity do not have enough voice at the administrative top. They are simply not heard or understood.
The above list could be discouraging. However, there are indeed solutions available. As we described above, banks and insurance companies made the necessary digital transformation twenty years ago, integrating digitalization into the user side of the organization instead of having an IT department performing tasks for the organization. These companies have strict requirements regarding team size (4 to 6 in most banks), ways of working (agile), and they evaluate a lot. Not to analyse what went wrong, but to emphasize what went right and how it can be even better. Administrators are substantively involved and have their own experience with digitalization.
Many governmental implementation organizations nowadays resemble banks more than classical government; they are essentially primarily benefit and payout agencies. Yet, they are often still managed as if they were a classical governmental organization. In the board of directors, there is no director responsible for digitalization. An exception to this is the UWV. Since 2023, a member of the Board of Directors there has had responsibility for digitalization.