Ownership in IT projects, the key to successful change

In the previous blog in this series, we looked at predictability. With a clear roadmap, we make sure a project or program has direction and that stakeholders can see where the change is heading.

But a good roadmap alone is not enough.

Many projects have a plan, reports, and governance structures, yet still get stuck. Not because the approach is missing, but because nobody truly feels ownership of the result.

That is why ownership is the second foundation of the Quilyx VERDER method.

Responsibility is not the same as ownership

In many organizations, responsibilities are clearly defined. Roles are described, tasks are allocated, and reporting lines are set up.

Still, responsibility does not automatically mean ownership.

Responsibility is about carrying out a task. Ownership is about commitment to the result.

When someone takes ownership, they do not only look at their own task, but at the whole. Problems are not passed on. They are addressed because they affect the success of the project.

That difference often determines whether a project truly succeeds.

Why ownership is often missing

Projects take place in complex organizations with different departments, suppliers, and interests.

Each party has its own role and responsibility. Teams focus on their part of the work. Managers steer on reports. Suppliers deliver what was contractually agreed.

The result is that everyone does their part, but nobody feels ownership of the overall outcome.

The project then slowly turns into a collection of activities instead of a shared effort to realize an objective.

That creates the risk that problems are identified too late or that no one feels called upon to actually solve a bottleneck.

Ownership does not mean doing everything yourself

A common misunderstanding is that ownership means one person has to solve everything.

That is not the case.

A project manager is more like the conductor of an orchestra. Everyone plays their own instrument, but someone has to make sure the whole comes together.

Ownership therefore does not mean that one person performs every task. It means someone takes responsibility for the whole and ensures the right people act at the right moment.

That requires overview, involvement, and the willingness to step in when needed.

Ownership must be deliberately organized

Ownership does not arise by itself. It has to be deliberately organized.

It starts with clear roles and mandates. Teams need to know what they are responsible for and must have room to make decisions.

Specific topics within a project also need an owner. Think of risks, dependencies, or important decision points.

That is an important insight. If you want to organize ownership, you need to prevent responsibility from disappearing into a team, a meeting, or a report. A group is rarely the real owner. Ownership ultimately belongs to a person or to a clearly defined role.

By assigning ownership explicitly, you prevent topics from getting stuck between different parties.

Ownership also requires transparency. When progress is visible and results are shared regularly, confidence in the project approach grows.

Ownership requires reliability and consistency

Ownership is not only an organizational issue. It is also a personal quality.

Ownership starts with predictable behavior. Saying what you do. Doing what you say. Not avoiding decisions, but carrying them.

That requires reliability, clarity, and consistency. People need to be able to trust that agreements will not drift, that decisions will not be endlessly postponed, and that problems will not simply be pushed aside.

That is exactly how trust is built. And without trust, ownership is difficult to sustain in practice.

Ownership is also leadership

Ownership is not just about controlling or holding people accountable. It also requires someone to provide direction, maintain relationships, connect interests, and visibly take responsibility when things become difficult.

In that sense, ownership is leadership in practice.

Someone who takes ownership does not wait for others to move first. That person creates clarity, makes bottlenecks discussable, and keeps the project moving.

Modern ownership is often shared ownership

In modern project environments, ownership increasingly shifts toward teams.

That does not mean ownership disappears. On the contrary. It means ownership is allocated more intelligently.

The project manager remains responsible for the whole. The team takes ownership of the work. Stakeholders take ownership of decisions, priorities, and conditions.

That combination makes a project stronger.

Ownership is therefore not something to centralize. It is something to organize, support, and make visible.

Ownership within the Quilyx VERDER method

Within the VERDER method, ownership forms the link between predictability and calm.

A clear roadmap creates direction. Ownership ensures that direction is actually followed.

At Quilyx, ownership means that we commit ourselves to the success of the assignment. Not only to performing a role or guarding processes, but to achieving the objective of the project or program.

That requires involvement in the whole. In progress, in collaboration between teams, and in the impact of the change on the organization.

For us, ownership therefore means three things.

First, someone visibly takes responsibility for the whole.

Second, ownership is explicitly assigned where it belongs and does not remain implicitly suspended between different parties.

Third, ownership is only credible when it is accompanied by reliability, clarity, and consistent action.

The basis for calm in projects

When a project is predictable and when ownership is clearly assigned, something emerges that is rare in many organizations during major change.

Calm.

Calm means stakeholders trust the approach, problems are solved in time, and teams know where they are heading.

Calm does not arise by itself. It is the result of predictability and ownership together.

In the next blog in this series, we will therefore look more closely at the third element of the VERDER method: calm.