Case Study · Process transformation - Engave S.A.

Once a pile of folders.
Today, one, sometimes two.

How we led a process transformation at one of Poland's leading medical universities - changing not just the systems, but the way the entire organization thinks

Client: Medical University of Łódź · Scope: BPM, IBM BPM, integrations, organizational change · Duration: over 1.5 years

Project at a glance

Client

Medical University of Łódź - one of the leading universities in the country, a leader in scientific publications, several locations, several hundred administrative staff

Scope

Implementation of a BPM platform (IBM BPM), integration of domain systems, establishment of a Process Competence Center, organizational culture change

Engave's role

Consortium leader - analysis, tender advisory, process design, implementation and technical integration, program management

Funding

Operational Programme Human Capital - one of the first process management implementation projects in Polish higher education

Result

A fully operational Process Competence Center, decentralized management, processes running without IT department involvement, measurable decision-making criteria

Problem

A stack of folders with documents to sign would land on the chancellor's desk. Every day. Each folder meant someone's time, someone walking between buildings, someone's signature in a queue.

This wasn't a technology problem. It was a symptom of something deeper: an organization where decisions gravitate upward through the hierarchy because no one further down has clear criteria or authority to act. In an institution of this size and complexity - several locations, hundreds of administrative staff, dozens of domain systems - manual document flow also had, as one project manager put it, "a considerable social dimension." Walking around with papers was also a chance for a chat over coffee, informal information sharing, a way of staying in touch.

UMED knew it needed change. But it also understood something more important: that change of this scale couldn't be an IT project. It had to be an organizational project, with IT providing the tools. And that it couldn't be rolled out in one leap - because an overly ambitious undertaking is more likely to be resisted than completed.

For a year, an internal, grassroots process initiative was carried out - before anyone wrote a single line of code. Employees mapped their own processes using a modeling tool. The first descriptions, definitions, and tests took shape. That groundwork was what later made a meaningful technical dialogue with vendors possible.

The tender question was specific: who has the competence not to mess this up?

Challenge

It's easy to confuse a workflow tool with a process management tool. Getting this wrong at the outset undermines the whole project.

These words from UMED's chancellor capture precisely why this project was difficult from the specification stage onward. The market offered many tools for mapping processes as diagrams. None of them met the university's key requirements: easy, simultaneous access to process definitions for all stakeholders, and the ability to define and optimize them collaboratively. After technical dialogue with multiple vendors, only solutions built on IBM BPM remained in the running.

Integration with domain-specific systems - an unexpectedly deep problem.

During implementation, it turned out that process automation required modifying domain applications that no one had previously factored in. The HR area - HR applications, Active Directory, the organizational hierarchy - proved critical and completely unprepared for integration. It had to be sorted out first before processes could be built on top of it.

Virtual University with 100 custom modifications.

UMED's portal system was an older version with over a hundred custom extensions: a recruitment tool, workload settlement, a student interface, map integrations. Every modification made integration with the new process platform harder. Fortunately, the system's new owner - the American company Public Consulting Group - turned out to be an open and cooperative partner.

Changing organizational culture alongside changing systems.

Discussing processes is one thing; living with them every day through an actual system is another. People had to give up habits - including ones that carried not just an operational, but also a social dimension. No software does that automatically.

The temptation to pause the project and implement ERP first.

At the most difficult moment, voices called for pausing the project and starting over with an integrated ERP system instead. The university decided otherwise - rightly so. The iterative, participatory model proved to be the only approach that could succeed in an organization of this scale and complexity.

Solution

A year and a half spent building the specification before a tool was chosen. That wasn't a delay - it was a strategy.

Engave entered the project as the leader of the consortium selected in the tender - the only company that met both the mandatory and additional requirements set by UMED. But Engave's role effectively began earlier: with advisory support during the tender process, which helped the university precisely define its requirements and avoid the costly mistake of choosing the wrong tool.

Stage 1: process awareness before technology.

A process-awareness program for UMED employees - identifying process leaders, preparing the organization for change. Without this stage, any BPM system implementation would have been an IT project imposed from above, rather than a transformation the organization understands and co-creates.

Stage 2: technical integration - welding the infrastructure together.

Implementation of the IBM BPM platform, integration with domain systems, building missing components (a calculator, a clock - functions none of the existing systems offered), cleaning up the HR area in Active Directory, integration with the Virtual University portal. No shortcuts, no "it'll probably work." Every integration was designed and verified.

Stage 3: processes without the IT department.

A pivotal moment in the project: the process system - at the level of defining, modeling, and deploying processes - had to function without involving the IT department in development work. This was a fundamental shift in the model: the process department defines and optimizes independently, while IT provides infrastructure and integration. Not the other way around.

Process transformation isn't an IT project with a training component bolted on. It's an organizational change project to which IT contributes tools. Organizations that reverse this order - buying a system first and then asking "what do we do with it now" - always lose out. UMED didn't make that mistake. That's why the project succeeded.

Results

1 folder

on the chancellor's desk instead of a stack - real decentralization of decisions

0

IT department involvement in defining and optimizing processes - organizational self-sufficiency

Center

Process Competency as a lasting outcome - the university manages change on its own

The project's most measurable outcome is also its most symbolic: the stack of folders with documents to sign on the chancellor's desk has shrunk to one, sometimes two. That means dozens of decisions that used to gravitate up the hierarchy are now made at the right level - by people who know the details, based on clear process criteria.

A second effect, just as significant: initiatives and projects with high costs and unclear financial justification stopped being submitted for discussion. Not because someone rejects them - but because the processes now enforce transparency and evaluation against clear criteria. That's a cultural change, not just a technical one.

A third: UMED's process department independently defines, models, and implements process changes - without involving the IT department in development work. The university is no longer dependent on an external vendor for every modification. The Process Competence Center is a lasting organizational asset that will keep generating value for years.

Client's voice

"I'm very glad I no longer have to check whether buying mice or erasers is justified."

Dr. Jacek Grabowski, Chancellor of the Medical University of Łódź

"We managed to reach a point where projects or initiatives with significant costs but unclear revenue figures aren't even submitted for discussion anymore. That's exactly the effect of having processes in place."

Paweł Zawieja, Head of the UMED Process Competency Center

"If we had tried to create one big task and force everyone to move at the same pace in the same direction, we would have failed. An overly ambitious undertaking is more likely to be resisted than completed."

Dr. Jacek Grabowski, Chancellor of the Medical University of Łódź

Official endorsement

"Over the course of a year and a half of cooperation, Engave Sp. z o.o. proved to be a reliable, flexible, and results-oriented partner. We wholeheartedly recommend Engave as a trustworthy partner for delivering complex organizational and technological projects."

Dr. Jacek Grabowski, MD, Chancellor of the Medical University of Łódź

Why it matters

UMED was one of the first Polish universities to carry out a process management implementation of this scale. Not because it had the best budget or the most cutting-edge equipment. But because it adopted the right premise: change starts with people and processes, and technology provides the tools to scale them.

The Process Competence Center - established as a result of the project - is proof that transformation can last. It doesn't depend on an external vendor, and it doesn't end when the project closes. UMED has matured into an organization that can manage change formally and now carries it out on its own.

For Engave, this project confirmed a thesis we bring to every transformation engagement: an organization that understands its own processes can do anything with technology. An organization that doesn't understand them gets nothing out of technology - no matter how much it pays for it.

What this means for your organization

How many decisions a day land on the desk of someone who should be focused on something else? And do you actually know why that happens - or do you just know that it does?

Process transformation doesn't start with choosing a tool. It starts with a question: how do we really work, and where are we losing value? If you want to answer that - let's start with a conversation.

Let's talk

Engave S.A. · engave.pl · All rights reserved

Contact us
with Engave

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

The controller of your personal data is Engave S.A., headquartered in Warsaw. Information on data processing principles is available in the Privacy Policy. Consent may be withdrawn at any time, without affecting prior processing, by contacting: biuro@engave.pl