Organization design & team topology

An organization chart describes reporting. It does not necessarily describe how value moves, where decisions wait, or how much context a team must hold. Organization design connects those realities deliberately.

The goal is not a frictionless structure. Some coordination is necessary. The aim is to place durable ownership around meaningful outcomes and make the remaining interactions explicit enough to manage.

Begin with a value stream

Choose one customer or business outcome and trace the work required to produce it. Mark teams, handoffs, queues, dependencies, decisions, and recurring failures. This reveals the operating structure more reliably than titles.

Ask where work changes hands without context, where two teams believe the other owns the decision, and where one specialist or platform becomes a queue for unrelated demand.

Design for manageable cognitive load

A team cannot own an outcome it cannot understand. Inventory the domains, technologies, stakeholders, operational duties, policies, and change demands that compete for its attention.

When the load is unreasonable, adding coordination meetings rarely solves the problem. Consider narrowing the boundary, improving a platform, simplifying a process, removing a service, or changing which expertise is embedded.

Do not use “cognitive load” as a euphemism for removing autonomy. A smaller boundary still needs meaningful end-to-end responsibility.

Name the interaction mode

Teams interact differently for different reasons. A temporary collaboration to discover an interface is not the same as an ongoing service relationship or a team consuming a platform with minimal coordination.

For every material dependency, state:

• the outcome and owner;
• the expected interaction mode;
• the information or service exchanged;
• the decision boundary;
• the time horizon; and
• the trigger for changing or ending the interaction.

Unbounded “collaboration” often means no one can plan independently.

Treat reorganization as an intervention

Changing boxes carries cost: relationships reset, local knowledge moves, identity is disrupted, and delivery slows while new boundaries form. Define the problem and expected evidence before announcing a structure.

Compare structural change with less disruptive options such as a clarified decision right, shared objective, platform improvement, temporary team, or removed dependency. If a reorganization is still warranted, state what should become easier and when you will inspect the result.

Practice with one live flow

Map one value stream from demand to realized outcome.

1. Identify teams, queues, handoffs, and decision owners.
2. Ask each team which context and operational load it must carry.
3. Classify every important interaction as collaboration, service, platform consumption, or another explicit mode.
4. Select one boundary or dependency that materially constrains flow.
5. Compare at least three interventions, including no structural change.
6. Run one bounded change and define delivery, quality, and human guardrails.
7. Review whether the expected friction moved, disappeared, or reappeared elsewhere.

Use process and system evidence. Do not turn individual sentiment or employee performance details into a public learning artifact.

Use resources selectively

The public Team Topologies concepts provide a compact vocabulary for team types, cognitive load, flow, and interaction modes. Scaling People connects structure to spans, layers, communication, and operating mechanisms.

Use the vocabulary to improve a diagnosis, not as a template that dictates four boxes for every organization.

Evidence of Practice

You may be ready to record Design when you can:

• trace a value stream across reporting boundaries;
• identify cognitive load and dependency costs with concrete evidence;
• give teams meaningful outcome ownership;
• name the purpose and duration of material interactions;
• compare structural and non-structural interventions;
• define guardrails and review evidence before reorganizing again; and
• show that a changed boundary improved flow without exporting hidden harm.

These prompts inform an explicit proficiency judgment; they do not create it automatically.

Continue through the tree

Leading leaders & management systems places accountable leadership inside the design. Decision rights & governance clarifies authority across its seams. Goals, planning & operating cadence and Systems thinking & leverage expose whether the new structure works as intended.