A group is not yet a team

Many ERP and AI projects start with the wrong assumption. Ten capable people sit at the table: purchasing, sales, production, IT, controlling. Everyone knows their job. So it must be a team.

No. At first, it is a group. A group shares a schedule. A team shares a goal, common rules and the willingness to become visible to one another. The difference sounds soft. It is hard. It decides go-live, data quality and whether AI arrives in daily work or ends up in a drawer.

This is exactly where our long-standing friend and partner Dr Roland Förster of Förster Consulting – Change & Agility works. For years, he has helped organisations assess and build functioning work teams. Not with appeals. With criteria. With practice. With an instrument that makes team readiness measurable.

The blind spot before kick-off

In mid-market trading and manufacturing companies, the start often looks the same. Software selected. Budget approved. Key users named. Milestones defined. Then the work begins. And at some point the organisation notices: decisions take too long, conflicts stay under the table, errors are not reported and responsibility moves back and forth. The project plan stays green. The mood turns grey.

Then the answer is called change management. More communication. Another workshop. Too late. Asking at go-live whether the team can carry the project is the most expensive timing.

Roland Förster knows this point from many organisations. His work starts earlier, with a simple question: what turns a group of people into a team that can deliver under pressure?

What turns a group into a team

A team is not created by an organisational chart. It is created by shared clarification. At least five things must be in place:

• Shared goal: Not “we are implementing ERP”. Rather: which operational result should be better in six months? Less duplicate work? Faster order confirmation? Cleaner inventory?
• Clear roles: Who decides master data? Who stops a bad process? Who is allowed to say no to scope? Who carries go-live in front of leadership?
• Aligned processes: Not only the future ERP processes, but how the team itself works: prioritising, escalating, resolving conflicts and sharing knowledge.
• Mutual motivation: Teams withstand pressure when members experience that their contribution matters and that mistakes are not punished, but worked through.
• Visible development: A team that does not measure itself drifts. Goals and processes must be sharpened over time.

If one of these is missing, the group remains a collection of capable individuals. That may work in quiet weeks. It does not work in ERP and AI projects.

Team readiness can be measured

This is Roland’s particular contribution. Many companies talk about culture. Few make it tangible. On Change-Agility, Roland has built an instrument that measures one critical prerequisite directly: whether the team dares to raise mistakes, conflicts and open questions at all: psychological safety. Anonymously, within the team, creating a shared picture instead of relying on gut feel.

Not as a mood barometer for HR, but as a working basis for leadership and project steering. Measurement does not replace conversation, but it ends the excuse: “we can feel it anyway”.

For PRODVIS, this is extremely valuable. Digitalisation rarely fails because of the cloud. It fails because teams do not report errors, do not resolve conflicts and do not carry decisions.

Why this matters for ERP and AI

A cloud ERP such as Exact Online Premium needs key users who carry responsibility. It needs departments that take master data seriously. It needs leadership that holds priorities when daily business pushes back.

Agentic AI needs even more. It needs teams that can say: this task may be prepared by the machine. This decision stays with the human. This data error must be reported. This exception goes to leadership.

Without team readiness, shadow work appears. Excel next to ERP. Private chatbot next to process. Everyone builds their own workaround. Nobody keeps the overview.

With team readiness, something else emerges: shared goals, shared processes, shared responsibility. Then software becomes operations. Then AI becomes relief instead of risk.

The PRODVIS view

At PRODVIS, we connect two worlds: robust ERP and AI architecture on one side, robust collaboration on the other. Technology without a team remains an expensive slide. A team without technology remains good intent. Together, they change work.

That is why we do not value Roland Förster as a soft add-on. We value him as a partner for the hard part: the working ability of the people who must carry the system. Before kick-off. In the middle of the project. Before go-live. And afterwards, when daily operations test the new processes.

PRODVIS practical impulse

Before approving the next ERP or AI initiative, ask the intended project team five questions:

1. Goal: Which operational result will we measurably improve within six months?
2. Roles: Who decides what, and who is allowed to stop?
3. Processes: How do we prioritise, escalate and decide within the team itself?
4. Motivation: Where do participants experience that their contribution counts?
5. Measurement: Have we used Roland’s team instrument, and discussed the result as a team?

If one answer remains vague, do not start with the software. Start with the team.

PRODVIS is happy to check with Roland Förster and with you whether your project team is robust enough before budget, timelines and nerves are burned.

Instrument and further reading

• Team questionnaire: what does your team really experience? – Dr Roland Förster, Förster Consulting – Change & Agility.
• Start the team survey – direct entry at Change-Agility.
• Why concepts fail and what makes real change possible – Dr Roland Förster at PRODVIS.
• Responsibility cannot be ordered. Only enabled.
• Sponsor self-check for ERP and AI go-lives