Two departments can share customers, processes and objectives without truly understanding how the other works. When the relationship is limited to urgent requests, forwarded emails and meetings to solve incidents, stereotypes, incomplete information and decisions that optimise one part of the work at the expense of the whole begin to appear.
Building bridges across silos
Collaboration does not appear simply because several departments share an activity. It appears when they must combine information, understand one another’s constraints and make a decision that none could solve alone.
Why collaboration between departments is difficult
A lack of collaboration is rarely caused by attitude alone. Each department works with different goals, timelines, language, data and incentives. Marketing may prioritise speed and reach; operations, stability; sales, immediate response; technology, security and maintainability.
Each team improves its own indicator without seeing the full impact.
The same words can mean different things in each area.
Each department holds only one part of the context.
The relationship begins only when something is already urgent.
A gamified activity can create a safe space to explore these differences, provided it does not become a superficial competition. The challenge should reproduce a real dependency: distributed information, limited resources, conflicting criteria or a decision that requires several perspectives.
Eight design decisions for genuine collaboration
1. Begin with a specific dependency
Avoid vague aims such as “improve communication”. Identify a moment when the departments genuinely need one another: a product launch, customer onboarding, incident resolution, campaign planning or project prioritisation.
2. Define what each department needs to understand
The activity can reveal what information another department needs, which constraints shape its decisions and what consequences arise from an apparently simple request.
3. Mix teams deliberately
Create groups with people from several areas and a size that allows everyone to contribute. Four to six participants usually works well. Avoid strong hierarchy turning the activity into an ordinary meeting.
4. Distribute information and responsibility
Each role should hold data, constraints or resources that others need. Interdependence encourages questioning, listening and explaining instead of allowing one person to solve the whole challenge.
5. Introduce decisions with consequences
A choice may shorten the timeline while increasing risk, reduce cost while harming customer experience or accelerate a campaign while creating operational pressure. Visible consequences make trade-offs between departments easier to discuss.
6. Facilitate a conversation about criteria
The goal is not to find someone to blame. The facilitator should ask which criterion the group prioritised, what information was missing and what it would have needed from other departments to decide better.
7. Turn insights into agreements
The closing should produce a concrete improvement: a question to ask earlier, a data point to share, an owner, a channel or a common prioritisation criterion.
8. Design follow-up
Return to the agreements after a few weeks. A microchallenge, survey or review of real cases can show whether collaboration has transferred into everyday work.
Six activities that can connect departments
Teams identify what they receive, what they deliver and where information is lost between departments.
Each department knows part of the case and must explain it to build the solution.
The group balances dates, resources, commercial promises, quality and post-launch support.
Participants trace the customer experience to identify contradictions, delays and unclear ownership.
People make decisions under another department’s constraints and compare the experience afterwards.
Each department solves one part and must integrate its result with the others to complete the mission.
Example: a cross-department launch
Marketing, sales, product, technology and customer service must launch a new feature. Each role receives different objectives and constraints. The team has a limited budget, a committed date and several decisions to make about scope, communication and support.
What to measure
- Distribution of contributions across departments.
- Information requested and shared during the challenge.
- Ability to identify dependencies and consequences.
- Quality of the agreements created at the end.
- Later application in real projects or processes.
From a one-off experience to a way of working
One activity cannot remove organisational silos by itself. It can reveal dependencies, create shared language and provide a first space to practise different behaviours. Its value increases when agreements are connected to real meetings, processes, tools and decisions.
Collaboration with Evenely
Evenely supports cross-department missions, decision scenarios, roles, distributed information, collective goals and analytics, turning a meeting between departments into a participatory experience with concrete outcomes.