Henry Mintzberg · Understanding Organizations...Finally!

No single best way to organize.

A practical map of seven recurring organizational forms, the forces that pull them into shape, and the balance that keeps any one force from taking over.

The field atlas

Four fundamentals, three conditions.

The diamond places the four fundamental forms by their most revealing tensions. Select any form to read its coordination engine, power pattern, likely strengths, and signature risk.

Configuration map · ideal types Select to inspect

Seven forces in the field

Open the studio to balance them →

The design premise

Pure forms are caricatures. Real organizations hold a dominant force in check with another force, or combine different forms in different parts of the enterprise.

Seven forms

One grammar.
Many structures.

Each form resolves coordination differently. The useful question is not “Which is best?” but “Which force does this work require, and what will keep that force from becoming pathological?”

Form 01 / Autocracy Chapter 7

Personal Enterprise

A loose, founder-centered system coordinated directly by a chief with a wide span of control.

Structural signature

Force relationship

↑

Consolidation The force this form gives license to.

↔

Efficiency The counterweight that can keep the form from running away.

A strong chief can unify action quickly; disciplined resource choices keep the enterprise from becoming purely personal.

Coordination engine

Direct supervision. Most people look to one chief, while formal rules and planning systems stay thin.

Power pattern

Centralized around the chief; hierarchy is shallow and spans of control can be very wide.

Works when

New, small, founder-led, in crisis, or facing a simple environment where rapid focused action matters.

Signature risk

The organization becomes dependent on one person; succession, overreach, and lost nuance are persistent dangers.

Read it through

Start-up founder, corner diner, a new NGO, or a turnaround chief taking temporary command.

Remember this

The Personal Enterprise does not merely lack structure. It resists structure because structure competes with the chief’s authority.

Business-model mirror

How this form usually creates, delivers, and captures value — and where that model begins to strain.

Customer logic

Founder-led customers and personal trust

Value logic

Speed, conviction, and a distinct point of view

Activity logic

Direct decisions, deals, and hands-on coordination

Economic logic

Often transactional; can be founder-funded

Boundary logic

Mostly owned and tightly controlled

Likely model tension

Growth or recurring services expose the organization's dependence on one person.

Business model · Organization

Connect the value logic
to the way work works.

A business model describes how value is created, delivered, and captured. An organization form describes how people coordinate and decide. Choose four model moves to see where those logics align, collide, or need a hybrid.

Start from a model pattern

Try a recognizable pattern, then change its logic. The result is an interpretation, not a prescription.

Live result Programmed Machine with Divisional Form

Customer architecture

Who creates the demand for this organization’s value?

Value and activity signature

What must the organization actually be excellent at?

Economic bargain

How does value turn into resources, and who carries the risk?

Boundary logic

What must remain inside, and what should connect through a wider network?

Business model → organization

Programmed Machine

Hybrid opportunity

The model needs a stable platform core while several interdependent sides follow different economic needs.

Adjacent form Divisional Form

Dominant force Efficiency

Suggested anchor Collaboration

Model-to-organization links

Customers: Multi-sidedCoordinate interdependent groups and manage cross-side subsidies explicitly.
Value / work: Access and networkFavor platform coordination, partner governance, and network effects.
Economics: Cross-subsidy / FREEMake subsidy flows visible so one side does not quietly exhaust another.
Boundary: Open ecosystemProtect governance, identity, and contribution rules while keeping the boundary porous.

What strains

One useful experiment

Separate platform stewardship from the commercial interests of any single side.

What if…

What if the subsidized side began paying?

Business Model Canvas

Nine blocks.
One living system.

A business model describes how value is created, delivered, and captured. The Canvas is useful only when its blocks are read together: change one assumption and the others respond.

Customer

Offer

Infrastructure

Financial viability

Read the system

The Canvas is not nine independent checklists. A change in customer segment, value proposition, revenue logic, or key activity can make a different organization form more coherent.

Business-model patterns

Patterns are systems,
not templates.

The book’s patterns show recurring ways to solve a business-model challenge. Each changes the economics, the boundary of the firm, and the organization required to make it work.

Pattern 01

Unbundled businesses

Relationship, innovation, and infrastructure work can conflict when they share one operating logic.

Before

One company combines customer relationships, product innovation, and infrastructure under one roof.

Challenge

Different economics and cultures create trade-offs, slower decisions, and diluted focus.

Pattern move

Separate or protect the three business logics while coordinating their shared dependencies.

Organization lens

Often a Divisional Form or assembled hybrid: relationship units, project units, and a shared infrastructure platform.

Book examples: Private banking and mobile telecommunications.

Model design

Make the model visible.
Then test the logic.

Business-model innovation can start from resources, an offer, customers, or economics. The Canvas becomes useful when teams use it to surface assumptions, compare alternatives, and prototype organizational consequences.

Start with the customer

Begin with an unmet job

Start with a customer need, accessibility problem, or point of friction rather than with the existing product or structure.

Design move

Change who is served, how access works, or what the customer is trying to get done.

Organization consequence

Niche complexity often favors professional or project logic; shared identity can point toward a Community Ship.

Which customer assumption are we treating as a fact, and how could a prototype challenge it?

Step 01

Assemble

Bring different functions, seniority levels, experiences, and customer perspectives into the same conversation.

Step 02

Immerse

Study customers, technologies, alternatives, and the external environment before narrowing possibilities.

Step 03

Expand

Generate many options by starting from different Canvas blocks and asking deliberately awkward “what if” questions.

Step 04

Select

Make criteria explicit: customer value, feasibility, risk, speed, and organizational consequences.

Step 05

Prototype

Sketch complete models and test the assumptions before committing the organization to a fixed structure.

Market forces

Customer needs, segments, switching costs, revenue attractiveness, and market issues.

Industry forces

Competitors, new entrants, substitutes, suppliers, stakeholders, and value-chain shifts.

Key trends

Technology, regulation, society, culture, and socioeconomic patterns.

Macro forces

Capital markets, commodities, economic infrastructure, and the wider economy.

Multiple models

An established organization can hold more than one business model. When the models conflict, the design question is whether to integrate, separate, or phase that separation—considering strategic similarity, conflict severity, risk, and the synergies that must still be protected.

Cases

From a model pattern
to a real company.

One well-known company is selected for each pattern. Read the short passage, follow the organizational bridge, then use the official link for deeper context or reopen the pattern in Bridge.

01 · Unbundling IBM → Kyndryl Infrastructure separated from cloud, consulting, and software.

Two different operating logics, allowed to separate

IBM and Kyndryl · 2021

IBM completed the spin-off of its managed infrastructure services business as Kyndryl. Kyndryl could focus on operating outsourced infrastructure at scale, while IBM positioned its remaining portfolio around hybrid cloud, software, and consulting. The separation made two different economic logics easier to manage independently.

Bridge logic: infrastructure resembles a Programmed core, while advisory and innovation work need Professional or Project freedom. The new company boundary becomes part of the organization design, and partnerships must recreate the coordination lost through separation.

Read IBM’s official case source ↗

02 · Long Tail Amazon A vast platform aggregates many small and niche offers.

One platform, an enormous catalog of niches

Amazon Marketplace · Global

Amazon Marketplace connects buyers with millions of independent sellers, whose products range from mainstream items to highly specific niches. Individual niche products may sell only occasionally, but together they create a vast assortment that can be discovered through Amazon’s search, reviews, payments, advertising, and logistics infrastructure.

Bridge logic: a Programmed platform core provides scale and repeatable rules, while independent sellers create Long Tail variety outside that core. The design tension is preserving niche diversity without letting standardized marketplace controls force every seller into the same model.

Read Amazon’s official case source ↗

03 · Multi-sided platform Apple App Store Users and developers create value through one governed platform.

A central platform orchestrates a vast developer network

Apple App Store · Global

The App Store connects people seeking software with developers who create it. Apple governs distribution, review, discovery, payments, and commercial terms, while developers supply much of the product variety and innovation. More useful applications can attract more users, which in turn makes the platform more valuable to developers.

Bridge logic: Apple’s platform stewardship is centrally coordinated, but the ecosystem is distributed. This is a hybrid of a controlled machine-like platform and a project-like developer network. The central tension is how much rule-setting and value capture can coexist with ecosystem autonomy.

Read Apple’s official platform source ↗

04 · FREE Google Search Free consumer access is funded by another side of the model.

Users search for free; advertisers fund the system

Google · Global

Google Search is available to users without a direct charge. Advertising creates the main cross-subsidy: businesses pay to reach search users through paid results and other advertising formats. The enormous user base, detailed intent signals, and machine-scale infrastructure make the advertising side valuable enough to sustain the free service.

Bridge logic: the free side grows through scale and automated service, while the paying side requires measurement, sales, and optimization. The organizational risk is letting advertising metrics dominate decisions in ways that weaken user trust or product quality.

Read Google’s official company source ↗

05 · Open model P&G Connect + Develop Internal capability meets a global network of external innovators.

Open innovation turns the company boundary into a resource

Procter & Gamble · Global

P&G’s Connect + Develop program invites outside innovators, suppliers, universities, and individuals to help solve product and technology challenges. P&G brings customer insight, brands, testing, manufacturing, and distribution to the collaboration, while external partners contribute ideas and specialist knowledge that may not exist inside the company.

Bridge logic: open value creation behaves more like a Project network and community than a closed hierarchy. The organization still needs strong gateways, intellectual-property rules, internal champions, and governance so that external ideas can move into commercialization without losing quality or control.

Read P&G’s official program page ↗

These are concise interpretive cases, not affiliated endorsements. Official links open in a new tab for further reading.

Force studio

Design is a balancing act.

Raise the forces you feel at work. The studio names the form they currently favor, then suggests the counterweight the book uses to keep that force productive.

Start from a design moment

Current posture Personal Enterprise Anchor with efficiency

Consolidation 88

Pull many efforts into one direction.

Efficiency 32

Get more output from fewer resources.

Proficiency 22

Protect expert skill and quality of judgment.

Collaboration 44

Coordinate experts through mutual adjustment.

Separation 18

Give units autonomy while holding them to results.

Culture 62

Bind people through shared norms and identity.

Conflict 18

Contest power, priorities, and direction.

This is a thinking aid, not a validated diagnostic. The book treats forms and forces as simplifications. Use the result to ask better questions, especially about age, size, technical system, environment, power, and history.

Transitions

Organizations do not stand still.

A form is a tendency, not a destiny. Age, success, crisis, external control, and political pressure can move an organization toward another form or hybrid.

Stage 01 / Birth

The personal beginning

New organizations usually turn toward a founding chief because resources, people, facilities, and culture all have to be assembled from scratch.

Personal Enterprise Direct supervision

What is happening

Direct supervision is the most natural first coordinating mechanism. Mutual adjustment is limited until people know one another, and standards take time to establish.

The design question: how does the founder create enough structure for others to act without turning the enterprise into a cult of personality?

Common pathways

Transitions are conditional.

The life cycle is a set of leading tendencies, not a sequence every organization must follow. Select a pathway to see the condition that makes it plausible and the tradeoff it introduces.

Seek simplicity and distrust it.

Start with a useful form. Then look for the counterforce, the cross-cutting team, the protected pocket of difference, and the pathway people actually walk. That is where a living organization appears.

About this atlas

Two lenses.
One design conversation.

This interactive atlas connects business-model thinking with organization design. It helps you make assumptions visible, compare alternative logics, and ask better questions about how value creation should be coordinated.

01

Choose a lens

Start in Bridge for the central connection, or use Canvas and Patterns to learn the ideas behind each model move.

02

Change an assumption

Select a pattern, Canvas block, organization form, or force. The interpretation updates immediately in your browser.

03

Read the tension

Useful results identify a likely form, an adjacent form, and the friction that still needs a design response.

Choose by task

All selections and calculations happen locally in your browser. Your language preference is saved locally; no account, server, or external model is used.