Nobody disagreed. Everyone nodded. The notes were sent out, and the team felt aligned.
Three weeks later, engineering built one thing, design expected another, and marketing promised a third.
Agreement is cheap. It often means people have not understood each other well enough to disagree. In my experience, the teams that collaborate best argue earlier, and they argue about the problem rather than about each other.
Silos are expensive
McKinsey's Business Value of Design reported one of its strongest correlations between top financial performers and companies that could break down functional silos and integrate designers with other functions.
The report also tells a story that I find painfully funny. One company opened a flagship design studio. Soon the designers moved in and deactivated door access for marketing, engineering and quality teams. Cooperation fell, and so did the performance of the wider business.
Designers can build silos too. We just give them better lighting.
Why collaboration breaks
Different definitions of done. Design thinks done means validated. Engineering thinks it means deployed. Business thinks it means revenue.
Late involvement. Bring engineers in after the design is finished, and you are asking for approval, not collaboration.
Shared meetings, separate goals. If each function is rewarded for different results, each will quietly protect its own.
Nobody owns the decision. Everyone contributes and nobody is responsible.
A working model for cross-functional teams
| Practice | What it looks like | What it prevents |
|---|---|---|
| One shared metric | Everyone can name the outcome | Local optimisation |
| Early kick-off | Product, design, engineering, and business frame the problem together | Late surprises |
| Clear decision owners | Each decision has one named owner | Endless debate |
| Shared user exposure | Everyone watches at least one research session | Opinion wars |
| Regular walkthroughs | Review real work in progress | Big reveals |
| Written decisions | Short notes on what changed and why | Rewriting history |
The shared research session is my favourite. It takes only an hour. It is hard to argue for an internal opinion after watching a real customer struggle.
Disagree in the open
I try to make it safe for people to say, "I think this will not work." In a kick-off, I might ask each function a direct question: what will make this fail from where you sit?
The answers are often the most valuable part of the meeting. Engineers name technical risks. Support names what customers already complain about. Legal raises a problem while it is still cheap to solve.
The designer's role
Designers are well placed to bring a group together, because we make ideas visible. A rough prototype can end a debate that words cannot. A simple journey map can show three departments that they are all looking at one customer.
At Capgemini, I was the design authority for a 150+ member global insurance platform team spread across India, Egypt and North America. With that many time zones and functions, alignment could not depend on meetings. It had to live in shared standards and clear decisions. Much of what makes the work go well is simple: be curious about what other people are responsible for.
Questions people ask
What is cross-functional collaboration? It is when people from different functions work together towards a shared outcome, instead of passing work from one team to the next.
How do you improve collaboration between design and product? Share one goal, involve each other early, agree on who makes each decision, and look at user evidence together.
Is your team too polite?
That may be the most useful question in this post. If you recognise this pattern, I would be glad to hear how it shows up for you. Write to me at pranjal.productmind@gmail.com.