Back to Insights
    Design & PracticeGovernanceEquitySystems Collaboration

    Power Is Always in the Room

    Collaboration between unequal partners requires more than inviting everyone to the table.

    ROCeteer · 2 min read

    A meeting table seen obliquely, one seat with noticeably more space around it.

    A Seat Is Not the Same as Influence

    Multi-stakeholder collaboration often celebrates inclusion by counting who attended. Government, business, community, suppliers, academia and civil society are all represented, so the process appears balanced.

    But participation is not the same as influence. A major buyer and a small supplier may sit at the same round table while carrying completely different economic risks. A funder and a community organisation may technically have equal speaking time while only one controls the money. A senior executive and a junior employee may both be invited to challenge assumptions, but only one can safely ignore the consequences of doing so.

    Power changes what people can say, refuse and risk.

    Power Shapes Behaviour

    Power is not automatically malicious. Organisations need authority, expertise matters and resources create legitimate differences in responsibility. The problem is pretending those differences do not affect collaboration.

    A supplier may agree to an unrealistic demand because losing the customer would be catastrophic. A community representative may moderate criticism because access to future funding depends on the relationship. An employee may withhold bad news because the person requesting candour also controls promotion.

    In each case, apparently collaborative behaviour may be adaptation to dependency rather than genuine agreement.

    Make Power Visible

    Collaboration design should explicitly map power. Who controls money? Who controls access? Who has formal authority? Who owns critical information? Who can leave the collaboration with little consequence, and who cannot? Who carries risk if the decision fails? Whose legitimacy is needed even if they have little formal authority?

    These questions often reveal why a process that looks inclusive still produces predictable outcomes.

    Power mapping is not about assigning moral judgement. It is about understanding the forces shaping participation so the collaboration can be designed more honestly.

    Inclusion is not measured by who was invited. It is measured by whether relevant voices can influence what happens.

    ROCeteer

    Design Counterweights

    Once power is visible, the process can include counterweights. Independent facilitation can reduce direct pressure. Anonymous input can allow difficult information to surface. Structured rounds can distribute airtime. Community or supplier representatives can have explicit consent rights on decisions that disproportionately affect them. Data can be shared before meetings so expertise is not monopolised.

    Sometimes the right intervention is not procedural but material: pay community members for their time, fund supplier capability-building, or give smaller participants access to technical expertise.

    Equal treatment is not always enough when participants begin with unequal capacity to participate.

    Equity Improves Intelligence

    Power-aware design is often framed as fairness, and fairness matters. But there is also a performance argument. If people with relevant information cannot safely contribute it, the collaboration becomes less intelligent.

    A system that only hears from the most powerful actors will systematically miss risks and opportunities visible at the edges. It may also create commitments that weaker participants cannot implement, producing apparent agreement and practical failure.

    Designing for voice therefore improves both legitimacy and decision quality. Power is always in the room. Collaboration becomes stronger when we stop pretending otherwise.