Collaboration isn’t democracy

Collaboration isn’t democracy

I had a long-term client a few years ago who took our approach to cross-functional collaboration quite seriously. They reconfigured the make-up of their teams and worked hard to create a culture that welcomed opinions from everyone. It seemed to work well in getting ideas surfaced and debated. It failed at making decisions. Why? The team took the concept of collaboration to a point where inclusivity meant no one wanted to deny anyone else’s opinion. The teams, well-structured and intentioned, ended up stuck at the most critical moments unable to advance their best ideas. They learned the hard way that collaboration, although a wonderful way to bring forward diverse thinking, is not an exercise in democracy. Without clear decision making, the best collaborations in the world will fail.?

Someone has to make a decision

Collaborative teams need a decision maker – a designated individual whose job it is to decide how the team will move forward from its current position. More of than not that person is the product manager. They own the decision. They can participate in the collaboration too but when the time comes to make a decision they weigh the current options and data and choose a way to proceed. Would it be nice to bring the team to a consensus? Absolutely. If you can do that quickly by all means you should. However, if getting everyone to agree becomes arduous or seemingly impossible, the decision maker steps in. This is a crucial role and step in any team’s process.?

Choosing a direction doesn’t negate other ideas

Just because someone made a decision doesn’t mean the ideas they chose are bad. The team may have to disagree and commit to the chosen direction but it’s not without its guardrails. Each decision must come with dedicated success criteria and a learning loop that ensures the team is in fact proceeding in the right direction. If it turns out that the chosen idea is not going to work out as expected, the team goes back to the backlog of unused ideas from the original collaboration and begins the decision making process again.?

Diverge, converge, repeat

Collaboration is powerful. Often the most successful products come from the collaboration of diverse individuals. It can also slow teams down if they can’t definitely exit the collaboration effort with a clear decision. Diverging initially only provides value if the team can converge quickly. Someone has to make that decision. When it’s coupled with success metrics and short learning loops, those whose ideas were not chosen get onboard with the chosen direction more easily. This is a cycle. Getting through this cycle is crucial for the best ideas to emerge over time. It isn’t, however, an exercise in democracy. Inevitably, someone’s opinion is the one that is executed. As long as that decision is data-informed and reflective of inbound learning our collaborations will continue to bear fruit.?

Vivek Agarwal

Lead Product Manager | Bajaj Finserv 30under30 | IIT KGP | Zero to One Products

1 个月

Totally Agree. One of the hardest thing I had to learn as a PM was to say "No" and you have to say that a lot.

Timo Salzsieder

Experiment.Measure.Learn.Deliver

1 个月

There’s a fine balance between genuine collaboration and democracy. I often see teams treating the PM as the team lead, which I believe is the wrong approach—the PM is NOT the CEO of the team! A successful team relies on a strong triad of product, UX, and engineering to make well-rounded decisions. Discussions and alignment are crucial, but when conversations start going in circles, someone needs to step in and make a decision, and that can be anyone from this triad, depending on the issue. I’ve also noticed some strategic management consultants advocating for digital teams to be business-led—a misconception, particularly in corporate environments where business is often "just" a stakeholder, not necessarily representing the true user of the digital product (whether internal or external). While it’s important for business to have a voice and be involved, they don’t lead digital teams and don't take decisions for these teams.

David Armstrong Jr

Principle Product Owner with Data & Analytics at Bridgestone Americas

1 个月

Yes. The leader still needs to pull these ideas together and ensure the team moves forward with a decision.

Andrew Hilger

Writer | Advisor | Guest Lecturer | Former Allegis Group President | Searching for Wisdom in an Intelligence-Crazed World

1 个月

Well said, Jeff. I used to open meetings with the old adage: a camel is a horse designed by a committee. As you suggest, inclusion and diverse perspectives are critical, but you have to have a decision-maker in the room and everyone needs to know and respect that decision maker. People can disagree, but when the decision's made, they need to commit. Great stuff!

要查看或添加评论,请登录

社区洞察

其他会员也浏览了