From Awareness to Action: How Highberg partnered with Philips to enable behavioral change through gamified learning
This whitepaper describes how we co-designed a gamified, behavior-driven intervention that led to measurable results.
Within the government, it is common (or even mandatory) to outsource a part or the entire IT through a (European) tender or RfP process. The contracting organization often starts by drafting a descriptive document, which is prepared independently or with the assistance of a consulting firm. After the actual tendering process, the transition to the new supplier begins.
The tender process leads to various changes in methodologies, processes, and procedures. The old IT organization is no longer in technical control; that responsibility has been transferred to the new supplier. You are now steering the supplier based on results.
This requires adaptability from the IT organization, such as the specialist who used to be hands-on and now needs to guide the supplier on a specific topic.
It may also involve saying goodbye to colleagues because fewer people are needed to do the work.
Colleagues who secure positions in the new organization will continue with the activities they were involved in before the tender and/or contribute to the project’s transition. This often leads to a busy period within the department, perhaps even too busy due to the combination of transition and maintaining ongoing operations.
Due to this busyness, there is often insufficient attention given to the new activities that the change has brought about, causing the department to fall behind. This includes activities such as setting up supplier management, portfolio management, and contract management.
Let’s go back to the beginning. Before even drafting the tender, it is wise to consider at least the following questions:
The answers to these questions, along with a set of other questions, form the sourcing strategy.
By creating this strategy, you gain insight into what you need to accurately request in the tender (suitable for the organization), as well as what you will need after the tender to successfully implement the change within your organization.
The change does not begin after the tender; it starts when you begin considering outsourcing the IT.
The next step after the sourcing strategy is defining the renewed organization, the governance organization. Properly establishing a governance organization is an important aspect that is often addressed too late (after the tender). By establishing the governance organization beforehand, everyone can find their position, and you can align the new tasks and responsibilities.
Perhaps you can configure the governance organization with a (significant) part of the existing organization. In any case, engage in conversations with colleagues; there’s a good chance that some colleagues have ambitions beyond their current roles.
This approach can help you retain colleagues and keep their expertise within the organization. Additionally, they can contribute to the tender process.
Involvement/contribution to a process like this ultimately generates more support.
Setting up a governance organization requires time, clarity, and patience. After all, it’s a change that impacts the entire organization.
Therefore, when setting up a governance organization, consider the following points:
By following these steps, your IT organization will have a clearer understanding of what is needed to establish a governance organization. This way, the team knows what is expected of them and doesn’t need to fill in the gaps. This creates an organization that is more agile, has control, and can provide integrated services to the customer.
Senior Consultant
This whitepaper describes how we co-designed a gamified, behavior-driven intervention that led to measurable results.
Government IT projects often fail not because of technology, but due to structural flaws in planning, organization, and execution. Issues such as deliberate deception, excessive optimism, and rigid governance lead to delays and cost overruns. The solution lies in Adaptive Flow: a flexible, iterative approach that sets realistic goals, monitors progress, and addresses organizational bottlenecks. Without attention to the organization, digital innovation remains ineffective.
In the Netherlands, several government security organizations share the same mission but serve different target groups. This overlap often causes confusion among the organizations' audiences. To address this, a decision was made to merge three organizations—each with distinct cultures, sizes, and ministerial oversight—into one integrated entity. This merger presented unique challenges. A large, bureaucratic organization with subcultures and high employee turnover had to integrate with smaller organizations that prioritized autonomy and maintained a flat structure. The absence of a shared culture posed a significant risk to effective collaboration. How do you create a unified organizational culture that harnesses the strengths of all three entities? Highberg was brought in to tackle this challenge by mapping the cultural landscape with the Culture Scan and guiding the subsequent culture change.