Grouping: The Architecture of Organisational Attention

Why structure is not an administrative decision, but a strategic one

Prologue: The Six Months That Changed Everything

Sarah had just completed a major reorganisation. Functions were consolidated. Market units were clarified. Innovation teams were launched. The consultants called it a success. The board approved it unanimously.

Six months later, nothing worked. Engineering had become a fortress—brilliant at protecting standards, but blind to shifting customer preferences. Sales chased every opportunity, spreading resources so thin that no market was truly won. The innovation team produced three prototypes and zero products anyone would buy. Partnerships that once felt like genuine collaboration now felt transactional.

Sarah stared at the organisation chart and for the first time saw it not as a map of power, but as a map of attention. Every structure is a choice about what gets noticed. And every choice about what gets noticed is a choice about what gets ignored. Engineering was built to protect standards, which meant it was not built to respond quickly. Sales was built to chase opportunity, which meant it was not built to focus. Innovation was built to experiment, which meant it was not built to deliver.

The question was no longer “How should we reorganise?” but “Which logic dominates and which logic has been abandoned?”

Defender: Protecting What Makes You Strong

The Defender is a strategic archetype oriented toward protecting the organisation’s core strength. It prioritises depth of expertise, operational reliability, and proven standards. A pharmaceutical company had 200 regulatory specialists who understood safety requirements across 40 countries. That knowledge had accumulated over 30 years. A young manager proposed placing specialists within each product team. “To be more responsive.” The proposal made surface sense. But specialists who once learned from 200 colleagues now learned from five. Knowledge of 40 countries fragmented into eight teams, each understanding only a fraction. When a Japanese regulator asked a question no one had ever answered, there was no one left to answer it. The company lost a $400 million contract because of a single question that a specialist—who had retired three months earlier—could have answered in an afternoon.

Function Grouping is how the Defender protects strength like that. But protection has a shadow. Ten years later, the regulatory function had become a fortress. Every product change required 47 forms. Every new idea was rejected because “we’ve never done it that way.” More dangerously: the function measured success by its own metrics—how many forms completed, how many risks avoided. No one asked whether compliance still served patients. And when a product manager questioned why a drug already proven safe in Europe took 18 months to approve in America, he was not promoted. He was “not a team player.”

Which capabilities would seriously weaken if fragmented? Which functional boundaries now protect comfort rather than excellence?

Reactor: Responding to What Must Be Won

The Reactor is oriented toward market response. It prioritises speed, competitive focus, and proximity to customers. A consumer goods company sold soap in 12 countries. For 20 years, they organised by function. Efficient. Standardised. Then a local competitor in Indonesia sold soap at half price with a tropical formula. In six months, market share dropped from 40% to 22%. The global team in New York didn’t see it coming—their data was six months late. The company restructured. Each country got its own market unit. Within a year, market share in Indonesia returned to 35%. Market Grouping moves attention closer to where value is contested. But responsiveness has a shadow.

Unit Indonesia launched a new product in three months—and succeeded. Unit Vietnam copied. Unit Philippines copied. Within a year, 12 different product variants, each with its own production costs and campaigns. No scale. Only duplication. Worse: units began competing. Indonesia cut prices to steal customers from Malaysia. Malaysia retaliated with bigger discounts. Margins collapsed in both markets. And when the CFO tried to stop the price war, both unit heads threatened to quit—because they were measured by market share, not profitability. No one changed the measurement system. The price war continued for eight months before the CEO intervened. Too late: two local competitors had already captured share in both countries.

Do our market units know where they must win—or are they chasing everything that looks attractive? When resources are contested, do we fund strategic importance or political influence?

Connector: Creating Value Across Boundaries

The Connector is oriented toward relationships and ecosystems. It prioritises collaboration, stakeholder integration, and shared value creation. A technology platform connected 50,000 developers with 2 million users. The platform itself had only 300 employees. But its value—billions of dollars—was created by developers building apps, partners integrating services, communities sharing knowledge. If the company had tried to create all that value itself, it would have needed 50,000 employees and still failed. Ecosystem Grouping is how the Connector creates value that cannot be created alone. But relationships have a shadow.

Five years later, the company had signed 200 partnerships. Every quarter brought a new announcement. But developers began complaining. APIs changed without notice. Commissions were cut unilaterally. The platform that once felt like an ecosystem now felt like a transaction. The company measured success by its own metrics—how many partnerships signed, how many transactions processed. No one measured whether developers became more capable, whether the ecosystem became healthier. And when a legendary developer who had built 40 apps for the platform published an open letter calling for change, the company responded with an automated email: “Thank you for your feedback. We will take it under consideration.” Within two years, 30% of the best developers left. Not because a competitor’s features were better, but because they no longer felt valued.

Do we understand what stakeholders genuinely value—or only what we want from them? Would they describe this ecosystem as shared strength, or as a network built for our benefit?

Prospector: Exploring What Does Not Yet Exist

The Prospector is oriented toward the future. It prioritises exploration, experimentation, and building options. A media company had printed newspapers for 80 years. In 2005, its young team saw readers shifting to mobile. Management refused. “Our readers read newspapers.” In 2010, they saw social media becoming a primary news source. Management refused. “Print advertising still makes money.” In 2015, print advertising revenue fell 60%. The company tried to build an app. Too late. The company didn’t fail because its people were stupid. It failed because every new idea had to prove itself against the existing business logic. And that logic always said: “This will never be as big as print.”

Opportunity Grouping gives the future a place to grow without being immediately judged by the logic of the present. But exploration has a shadow. The digital unit produced 15 experiments. Three succeeded. Twelve failed. No one knew why. No one documented the learning. When the unit was disbanded for “not showing results,” all knowledge of why twelve experiments failed—and why three succeeded—left with the people. Six months later, the company tried to build digital products again. They repeated the same mistakes. Twelve experiments failed again. Three succeeded again. But this time, no one remembered they had already done it before.

Where can employees explore possibilities that don’t yet have a proven business case? Are we building options—or waiting until disruption forces us to move?

Orchestrating the Tensions: Leadership in the Face of Paradox

The four archetypes cannot be held together harmoniously. They are fundamentally in conflict. The Defender wants stability. The Prospector wants change. The Reactor wants speed. The Connector wants depth. Picture a technology company with all four. When the market unit wants to ship a feature in two weeks, engineering wants to test for two months. When the venture unit wants to hire the best engineer, the market unit wants that same engineer for its project. When the ecosystem team wants to give developers a bigger commission, the CFO wants to protect margin. This is not a design problem. This is the permanent condition of a living organisation. And every wrong compromise—every time one logic suppresses another without clear reason—creates a small wound that goes unnoticed until the organisation bleeds out.

A mature leader does not seek a solution that satisfies everyone. They orchestrate—deciding when one logic dominates, when another is suppressed, when a trade-off is made, when the balance must shift. And they know that every decision has casualties. The market unit that doesn’t get budget. The engineer who must test faster. The developer whose commission is cut. Leadership is not about making everyone happy. Leadership is about making the right choices—and having the courage to bear the displeasure they produce.

Where is tension between logics creating conflict—and is that conflict productive or destructive? Are you orchestrating the tension—or is it orchestrating you?

Epilogue: Sarah’s Question

Sarah stared at the chart again. Now she saw something different. Engineering grouped by function—protecting expertise, losing responsiveness. Sales grouped by market—chasing opportunity, spreading too thin. Innovation given space without connection. Partnerships announced without embedding. The structure wasn’t wrong. It was incomplete. And Sarah realised something that kept her awake that night: the company she had led for eight years might not survive after she left. Not because she had failed. But because she had succeeded in building something that only worked because she was there—and she had never noticed the difference until now.

Sarah began asking different questions. Not “How should we reorganise?” but “Which logic dominates—and which logic has been abandoned? What is this structure making us win—and what is it making us lose?” That question changed how she led. Not because it gave her answers, but because it gave her a way of seeing.

Organisational Assets — What Will Remain After You Leave?

When Sarah began orchestrating the four logics, she touched something deeper than structure. She touched organisational assets—four interconnected forms of organisational value whose full strength can never be understood from the balance sheet alone.

Financial Assets are the result of the relationship with owners. Human Assets are the result of developing people. Relation Assets are the result of serving customers and society. Structural Assets are the organisational systems through which leaders orchestrate and institutionalise the synergy among Financial, Human, and Relation Assets. Together they form a circle that reinforces itself. When orchestration is embedded in Structural Assets, that circle keeps turning—even after the leader who started it is gone.

Leaders do not wait for the four assets to exist before orchestrating. They orchestrate from the beginning—and the four assets form as a result. The final question is not whether you will leave. The question is what you will leave behind. And if you cannot answer that question with confidence, the organisation may still depend more on your presence than on the system you have built. The danger is not always visible while the leader remains. It becomes visible when circumstances change and the organisation discovers that what appeared to be institutional strength was actually personal dependence.

Are we merely accumulating Financial, Human, and Relation Assets—or are we building the Structural Assets required to keep them strengthening one another after we are no longer personally driving the circle? The answer is determined not by what you accumulate, but by what you institutionalise.

Three Questions to Ask This Week

1. Which grouping logic is strongest in your organisation? Which is weakest?

2. Where is tension between logics creating conflict—and is that conflict productive or destructive?

3. If you left tomorrow, what would continue to work—and what would collapse?

Have a good day!

Greetings of Transformation