The Architecture of Collaboration

Executive Summary Command-and-control remains the correct model for crises, unskilled teams, regulated environments and high-stress situations. However, applying it universally would be erroneous .

Collaborative models work better wherever consumer choice, ecosystem competition and/or experienced talent are operating realities.

Incentives must be structured to match the operating model: command systems reward input and resource use; collaborative systems must reward outcomes and behaviour in equal measure.

Organisational speed is a function of horizontal agility . The weakest link in the cross-functional chain sets the pace, not the fastest vertical.

Information asymmetries are the enemy of collaboration . Unless leaders actively dismantle them, siloes persist regardless of stated values.

The tolerance of poor behaviour in high performers is the most corrosive force in a collaborative organisation , because it signals to other team members that the model is not real.

Legacy is what a leader betters in their tenure. That standard, applied at every level of an organisation, is what sustains collaborative culture beyond any individual .

. The idea that leadership styles are moving from authority-centric to influence-based ones has been in vogue for decades. The conditions that once made command-and-control effective (stable markets, captive consumers, limited competitive options) have given way to ecosystem-based competition, multi-generational workforces and a pace of change where rigidity costs more than scale earns. Shiv Shivakumar, Operating Partner at Advent International and former chief executive of PepsiCo India, Nokia India and the Aditya Birla Group's branded businesses, examined what this shift demands of leaders in practice, and where most organisations are still perhaps missing the mark.

Command-and-Control: Origins and Enduring Relevance Managers may treat command-and-control as a relic, but it is a context-specific tool with a logical basis. Corporations borrowed their structures from the armed forces because, five hundred years ago, military organisation was the dominant model of coordinated human action. A hierarchical command chain, unity of authority and the absence of sanctioned dissent were key features of that model.

Even today, command-and-control remains the ‘correct’ approach in more environments, and more often, than leaders perhaps admit. A crisis unfolds, say, when a company faces a product recall or a regulatory emergency, and democratic deliberation becomes a liability. New or unskilled teams also require it, because distributed decision-making presupposes a shared base of competence. Highly regulated industries benefit from it, because compliance is non-negotiable. And in markets where consumer choice is limited, the predictability it offers is a competitive advantage.

The Conditions that Make Collaboration Necessary Collaboration is a response to market structures. In any environment where the consumer has genuine choice, where complexity rules out a single correct answer and where the organisation competes not company vs. company but ecosystem vs. ecosystem, command-and-control produces slower decisions, narrower information access and higher attrition, especially among the experienced people the organisation most needs. In regulated markets, the producer is king; in open markets, the consumer is. Whatever the market shifts towards, the operating model must change to match it.

The competition between Android and iOS is not between two products but between two sets of partners, developers, distributors and adjacent services. The same logic applies in financial servies: a durables company that, for instance, lacks linkages to Bajaj Finance in its retail channel concedes the entire customer access that ecosystem provides. Once locked out, there is no easy re-entry. The leader of an ecosystem has no authority over most of the people whose cooperation determines the outcome.

There is a generational dimension to this. Organisations where more than 3-% of the workforce is Gen Z cannot sustain a command structure, because the implicit contract of command-and-control — compliance in exchange for job security — will simply not hold for younger workers. Leaders who do not adapt deter the talent they most need to keep.

Incentives, Accountability and the Behaviour Trap In command systems, incentives are tied to inputs and resource deployment. These could include, for instance, whether the budget was spent as directed or whether the production line was expanded as approved. In collaborative systems, the only real anchor is the end result: profit sharing, equity participation, outcomes that everyone can see and verify. Nokia’s example illustrates how far this can go: 50% of the top hundred managers' incentives were tied not to their financial results but to their demonstrated behaviour on company values, assessed by colleagues across the organisation who had worked with them during the year.

High performers whose behaviour is inimical to collaboration are routinely tolerated because removing them feels riskier than managing the damage they cause. Such tolerance, though, signals to the rest of the organisation that collaboration matters less to the organisation than claimed. Every team member watching a boundary violation go unchallenged adjusts their own behaviour accordingly. Inconsistent accountability, in short, undermines whatever culture an organisation might claim to have.

Horizontal Agility: Where Speed Actually Lives Leaders routinely speak of desire agility, but they measure performance and manage vertically: by function, by hierarchy, by what each department delivers within its own boundary. Speed, however, abhors siloes. In any product or service delivery chain, the pace of the whole is determined by the slowest handover between functions, not by the fastest performer within any single one. Until organisations measure across the seams — from product development to R&D to marketing to sales, tracking the time taken in and quality of each transition — they are optimising the wrong variable.

Southwest Airlines best illustrates the principle. Southwest's competitive advantage is a 30-minute aircraft turnaround. Every process, policy and metric in the organisation exists to serve that single horizontal outcome. There are no job descriptions that would prevent a pilot from helping with ground operations if that is what the turnaround requires. The common goal is visible to everyone and measurable by everyone, which makes collaboration a practical necessity rather than an aspiration.

Information Asymmetry and the Contract Between Functions Most organisations suffer from information asymmetries. Procurement knows supplier timelines that manufacturing does not. Sales knows market conditions that product development does not. Finance knows cost constraints that commercial teams routinely ignore when bidding for contracts. These asymmetries require active intervention: shared databases, structured disclosure protocols and, perhaps most importantly, clear agreements between functions on what each party commits to deliver and what they commit to make visible.

In any organisation where functional lines report to both a global centre and local leadership, the organisation matrix is effectively a conflict-escalation mechanism. The solution for many firms may be to replace the implicit competition with an explicit contract: three shared priorities that both parties agree to, beyond which neither side can legitimately claim the other is non-cooperative. When Alex Lambert, Nokia's global mobile phone head, visited India to investigate reports of underperformance, the turning point came after he spent two intense days with retailers and consumers. Once he was speaking the same language as the local team, the conversation shifted from accountability to alignment.