When you bring people from different departments together and the project stalls

Updating a loyalty policy requires sales, marketing, purchasing, and production. Launching a new product again puts several functions at the same table. Any decision that touches multiple departments requires people with different goals, KPIs, and views of what matters to work together.

This is exactly where things slow down. Not because people are bad, but because no one has taught them how to work in this kind of team. There is no shared language, no decision-making methodology, and no understanding of how to run a meeting so it ends with a result rather than an agreement to “discuss it again.”

The Cross-Functional Teams course is a practical Adizes-based methodology for companies that want project teams from different departments to work and make decisions, instead of slowing processes down.


Deprecated: mb_convert_encoding(): Handling HTML entities via mbstring is deprecated; use htmlspecialchars, htmlentities, or mb_encode_numericentity/mb_decode_numericentity instead in /home/u682254541/domains/amazes.pro/public_html/wp-content/themes/amazes/content-factory/services/text.php on line 19

Why cross-functional projects are so hard

When people from different departments are brought into a project team, each person arrives with their own logic. Sales has one view of the world, marketing has another, and production has a third. Everyone is right from their own position. That is exactly why agreement is so difficult: participants do not have a shared language for discussion or a shared method for making decisions.

As a result, meetings drag on or end with nothing. Accountability is blurred: everyone thought someone else would do it. Decisions are made but not implemented, because participants do not feel like the authors of those decisions. The project leader spends more time aligning positions than moving toward the result.

This is not about discipline or goodwill. It is about a methodology that simply is not there.

Does this sound familiar?

The project requires several functions to be involved, and from the first meeting it is clear that agreement will not be easy: everyone has their own truth and priorities.

Cross-functional meetings drag on or end with nothing: people discuss the issue, leave, and discuss it again a week later.

Decisions are made but not implemented: each participant understood something different, and no one feels accountable for the result.

Accountability for the project result is blurred. When something goes wrong, it is not clear who should fix it.

The project leader spends most of their time managing “politics” inside the team instead of managing the project itself.

Good ideas that require several departments never reach implementation because alignment is too difficult.

Who should be trained?

HR directors and organizational development specialists

who need tools for building collaboration between teams at a system level

Project leaders

who regularly work with cross-functional teams and want to manage the process rather than put out fires

Middle managers and line managers

who coordinate work at the intersection of departments every day and understand exactly where and why it breaks down

Top managers

who initiate cross-functional projects and want to understand how to make teams from different departments actually work, rather than imitate work

Program content

Cross-functional collaboration: benefits and challenges

  • The value of collaboration between departments.
  • Barriers to collaboration: silo culture and the impact of management style.
  • Cross-functional collaboration formats and the conditions they require.
  • Practical review: Management style and attitudes toward cross-functional work. Strategies for reducing silo culture.

The CAPI principle and building effective teams

  • Authority, power, and influence as sources of energy for implementing decisions.
  • How to build a cross-functional team based on each participant’s contribution.

Synergistic teams: Synerteam

  • The Synerteam format as a meeting and working group format.
  • The eight-step decision-making technology and Adizes stages of teamwork.
  • Tuckman’s group dynamics for maximum productivity.
  • Stages of teamwork according to Adizes.
  • Practical review: Rules for a synergistic team.
  • Rules for Synerteams.
  • Practical review: How to formulate rules correctly.

Integration and conflict management

  • Sources of disintegration and conflict, both constructive and destructive.
  • The role of the integrator and methods of operational consensus.
  • Integration techniques: emotional and rational alignment.
  • Types of cross-functional meetings according to Adizes and how to integrate them.
  • Practical review: Formulating problems, tasks, and criteria.
  • Practical review: Building the stages of a synergistic team’s work.
  • Checklist: Good decisions.

Organizing the meeting system

  • The traditional approach: types of meetings and goals.
  • Lencioni’s four types of meetings.
  • The coordination value of regular meetings.
  • The Adizes system of cross-functional meetings.
  • POC: Participative Organizational Council.
  • Decision implementation plan. The meeting cycle: how to start the flywheel.

Facilitation for cross-functional teams

  • Types and levels of tasks solved through facilitation.
  • Main facilitation directions for successful cross-functional collaboration.
  • Pinpoint facilitation.
  • Digital facilitation.
  • LEGO SERIOUS PLAY facilitation.
  • LSP as an iterative process.

What changes after the program

Cross-functional projects stop getting stuck. The team gains a shared mechanism for making decisions and distributing accountability, so meetings end with results rather than an agreement to meet again.

Conflicts between people from different departments decrease, not because everyone has simply become more polite, but because the system-level causes of those conflicts are removed. Leaders start speaking the same language and working with the same method, regardless of which function they come from.

Over time, a stable meeting system is built that keeps coordination between departments working without having to push the process manually every time.

Program Facilitator

Iryna Sotnikava

Iryna Sotnikava

Co-Founder of A.maze.S

image

Tell us about the situation, and we will discuss how relevant the program is for your company

Получить бесплатную консультацию

+357 97 455 608   &   hello@amazes.pro

Free consultation
image

You May Also Be Interested In

Case Study: How BelAvtoMazService Turned Change Implementation from a Project into Part of Its Management Culture

Case Study: How BelAvtoMazService Turned Change Implementation from a Project into Part of Its Management Culture

The main result was the company's ability to independently develop its own management system and adapt it to changing external conditions.

Read more All cases
Review of the management competency development program from Resolut

Review of the management competency development program from Resolut

What is especially valuable is that the work didn't end on the last day of the module. Alexander continues to give participants challenging management tasks to this day, and periodically we all discuss the solutions together with Alexander.

Read more All testimonials
A durable integration skill helps a business handle any problem

«A durable integration skill helps a business handle any problem»

Every business problem is systemic in nature. They come from how companies respond to change — and that response leads to disintegration. We mean disintegration of everything and everyone: the interests of people, including owners and leaders, as well as business processes, organisational structure, the reward system, employee authority, and individual departments.

Read more All articles