A customer negotiating a data-centre commitment needs to know who can say yes. The internal conversation may involve financing, engineering and the timing of a site. Whatever the organisational chart looks like, the answer eventually has to reach the customer as a commitment someone can keep.
That is the management question raised by Bridge Data Centres’ latest appointment. The Singapore-headquartered company announced on 3 November that Drew Chen had become co-chief executive, effective 1 November, working alongside Eric Fan. Chen previously served as a senior partner at Bain Capital. BDC describes the appointment as supporting its expansion across Asia Pacific.
The announcement establishes the leadership arrangement and its stated purpose. It does not describe a detailed division of decision rights between the two executives. There is no basis here to conclude that shared leadership is either causing confusion or producing better results.
Put the decision before the title
WCRC’s analysis uses Stakeholder Trust and Impact Index, leadership parameters referenced in the Guru Management Codex. Applied to this appointment, they prompt a concrete test: can the business connect a decision with an accountable owner and a result that can be examined?
A co-CEO structure could allocate responsibility by function, geography or stage of investment. The useful arrangement is the one employees can apply when a matter crosses those boundaries. If one executive owns a customer relationship and the other owns capital allocation, who resolves a commitment that requires additional spending?
The answer needs to work before there is a disagreement. A customer should not have to discover the limits of one executive’s authority after a proposal has been accepted. Employees should know which commitments they may make and which need a joint decision.
That does not require both executives to sign every routine matter. Excessive joint approval can consume time without improving scrutiny. The design should identify the decisions that genuinely require two perspectives and those that have one clear owner.
Make escalation usable
Consider a hypothetical delivery date that depends on a change in project scope. The responsible team needs a route for explaining the trade-off, a decision deadline and a record of the answer. An unresolved disagreement between senior executives should not become an unacknowledged delay lower in the business.
A useful review would examine exceptions: decisions that crossed the agreed boundary, commitments that had to be reopened and matters that waited for clarification. Those records could reveal whether the structure helps people act or makes them seek approval twice. No such review has been conducted for this article.
The same discipline applies to the board’s oversight. Directors need to understand how the shared leadership arrangement works in practice, including where the executives disagree and how those disagreements are resolved. A unified public message is useful; a reliable internal route to a decision is more consequential.
BDC’s expansion plans will eventually be judged through its delivery and operating record. For now, the appointment offers a narrower test of leadership design. Two people can share a title. Each consequential commitment still needs a decision the organisation understands and someone who remains answerable for it.