Case Study · IT Strategy - Engave S.A.
Digitalization strategy, IT environment audit, and transformation plan for one of the largest public-sector organizations in Poland
Project at a glance
Client
One of the largest public-sector institutions in Poland - thousands of employees, an extensive IT environment, processes critical to millions of citizens
Scope
IT Development Strategy 2018-2020, High-availability and risk audit of the environment, Digitalization Strategy
Nature
An advisory and analytical project - from diagnosis, through decision architecture, to a concrete action plan with priorities and business justification
Problem
This isn't a rare scenario. Most large public organizations in Poland built their IT environment reactively: a new project meant a new system, a new tender meant a new vendor, a new regulation meant another layer. Years later, the outcome is always the same: an archipelago of systems, dependencies no one fully maps, and purchasing decisions made without a view of the whole picture.
For an institution holding the status of Poland's first e-government office, with ambitions of setting the standard for the entire public administration, this was a strategic problem - not an operational one. It wasn't that something wasn't working. It was that no one knew exactly what to modernize, or in what order, to make things run better, cheaper, and more securely over the coming years - without risking that any single step would take down systems serving millions of people.
The question was: how do you carry out digital transformation at this scale without stopping the institution for even a single day?
Challenge
An environment built on the institution's own hardware infrastructure meant a long, costly procurement cycle for every new project need. By the time hardware reached the server room, the window for the project had often already closed. Full resource utilization was impossible to plan ahead of time.
An organization of this scale should be building internal expertise - but it lacked a knowledge management system that would make that possible. Every specialist who left meant a risk of losing operational knowledge. Every tender meant a risk of becoming locked into a new vendor.
IT projects were evaluated and prioritized without a consistent methodology. The lack of tools for tracking business justification, timelines, and risks made it hard to answer a basic question: which initiatives were actually worth continuing, and why.
Poland's public-sector digitalization was funded by a PLN 4.5 billion EU budget for 2014-2020. The window for transformation was open - but it required decisions grounded in solid diagnosis, not intuition.
Solution
Rather than arriving with a ready-made architecture, we carried out an in-depth audit: analytical data, a high-availability risk assessment of the PUE environment, and interviews with employees at every level of the organization. There was one starting point: understand how the institution actually operates - not how it's supposed to operate according to its documentation.
Complementary to the organization's overall strategy, defining IT principles, goals, and initiatives for the years ahead. A document that answered the question: what to modernize, in what order, and why that order specifically.
A broader transformation document covering not just technology but how the organization works: a service-based model instead of a hardware-based one, a knowledge management system to support retaining expertise, and project management tools and methodology with staged business-value accounting.
Separating the hardware layer from the application layer and moving to a service-based model. It's a single change that addresses flexibility, cost, and independence from the hardware procurement cycle all at once.
A proposed repository of expertise and operational documentation, designed so that knowledge about IT systems would no longer live solely in the heads of a few key employees.
Digital transformation at a public institution isn't an IT project. It's an organizational change project in which technology is a tool - not the goal. The biggest resistance doesn't come from the infrastructure. It comes from culture, habits, and the question "why do we even need to change this?"
Scope and results
3
strategic documents - IT development, PUE audit, digitalization strategy
2018-2020
planning horizon - the first multi-year IT plan grounded in diagnosis, not intuition
3 areas
priorities: infrastructure flexibility, internal expertise, project management
Before this project, the organization had plans. After it, it had a strategy: a documented diagnosis of the current state, priorities backed by risk and benefit analysis, concrete initiatives with business justification, and a delivery methodology.
It's a seemingly subtle difference. In practice, it means every subsequent investment decision - a new system, a new tender, a new project - could be evaluated in the context of the whole. Not in isolation, not reactively, but as part of a coherent picture.
Digitalizing selected areas, a path the strategy opened up, delivered smoother teamwork, higher efficiency, and optimized infrastructure maintenance costs. But the key outcome was something you won't find in any table: the institution gained a language for talking about IT at the management level - in terms of business value, not technicalities.
Context
"The organization is carrying out a new strategy and a process of transformation, aimed at increasing customer satisfaction through innovative solutions and greater transparency and efficiency in managing public funds. The modern reforms implemented have delivered measurable financial benefits and positive qualitative change."
From the client's strategic documents, which provided the context for Engave's project
Why it matters
Most conversations about digital transformation in the public sector get stuck at: "let's buy new systems." Less often does anyone ask: "do we actually know what we need, and in what order to do it?"
This project shows that the value of strategic IT consulting isn't measured by the number of tools deployed, but by the quality of decisions that become possible once someone from outside asks the right questions and carries out a rigorous diagnosis.
For Engave, this was proof of something we've stood by for 15 years: before you design anything, you have to understand it. And understanding the IT environment of a large public organization - with all its dependencies, constraints, and hidden risks - takes experience, not just tools.
What this means for your organization
If IT in your organization is growing reactively - project by project, vendor by vendor - let's talk. An IT audit is the starting point that shifts the conversation from 'how much does this cost' to 'how much is this worth'.
engave.pl/kontakt
Engave S.A. · engave.pl · All rights reserved
Cybersecurity, IT care, digitalisation - whatever the topic, we're happy to talk. Describe your need and the right specialist will get back to you within 24 business hours.
CONTACT:
biuro@engave.pl
+22 863 13 90
Technical support: +48 604 470 151
16 Czarodzieja St., 03-116 Warsaw, Poland