Galbraith Star Model

Theory & origin

Jay Galbraith built the Star Model across four decades of organization design work, starting from Chandler's observation that structure follows strategy and turning it into a usable design method. The claim is that five choices determine how an organization behaves. Strategy sets direction and the criteria every other choice must serve. Structure distributes power and groups people. Processes move decisions and information across the structure's boundaries. Rewards tell people what actually matters, whatever the strategy deck says. People covers the skills and mindsets the design assumes. The model's teeth come from its misalignment logic: performance leaks wherever two points contradict, and the most common contradiction is a new strategy running on an old bonus formula. The formula wins every time. The Star's discipline is to translate strategy into explicit design criteria first, then test and redesign each point against those criteria, in order, and to treat a reorganization that only moves structure as a fifth of a design.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

How a consultant runs it

1. 01 Turn the strategy into design criteria before touching anything: "win SME lending on speed" becomes testable demands on structure, process, rewards, and people.
2. 02 Test each point against the criteria and score the fit honestly. The misfits, not the org chart, are the redesign agenda.
3. 03 Design in sequence, structure before processes before rewards, but iterate: a rewards constraint can send you back to structure.
4. 04 Give rewards the attention it never gets. It is the point most often left contradicting the strategy, and it overrides the other four quietly.
5. 05 Close with the people plan: the skills, hiring profiles, and development the new design assumes, priced and scheduled, not assumed.

Worked example

A multifinance group stands up a digital lending unit with a speed strategy: approve small loans in hours, not weeks. The Star scan shows why it is failing. The structure is functional, so every application crosses three departments. Processes run sequential approvals. Rewards pay for volume and loss rates, so nobody is paid to be fast. People are deep specialists in a design that needs end-to-end generalists. Only the strategy scores well. The redesign moves in sequence: cross-functional pods own an application end to end, approvals run in parallel inside the pod, incentives get a speed component, and a retraining path turns specialists into pod generalists. Time-to-yes falls from nine days to 36 hours, and the point of the exercise lands with the leadership team: the earlier "reorg" had only ever moved the boxes.

Common pitfalls

1. 01 Structure-only reorganizations, the classic one-point redesign that changes nothing
2. 02 Rewards left for later, which means the old incentives quietly veto the new design
3. 03 Skipping the design-criteria step, so alignment gets debated on opinion instead of tested
4. 04 Copying another company's star. The points must fit your strategy, not their case study.
5. 05 Treating the people point as an afterthought instead of a priced, scheduled capability plan

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.