Nadler-Tushman Congruence Model: Diagnosing Organizational Fit

By Brian Tr · Updated Oct 10, 2026

The Nadler-Tushman congruence model is a diagnostic framework from David Nadler and Michael Tushman. It treats an organization as a system that turns inputs into outputs through four components: the work, the people, the formal organization and the informal organization. Its central claim is simple: performance depends on how well those four parts fit each other.

This guide covers the model's inputs, components and outputs, the six fit relationships, how it compares with 7S, Burke-Litwin, the Star Model and Weisbord's Six-Box, and a step-by-step method with a template you can copy.

Key Facts

• Originators: David Nadler and Michael Tushman, Columbia University. The core article is A model for diagnosing organizational behavior, Organizational Dynamics, 1980.
• Core idea: the tighter the fit between components, the higher the performance. Fit between parts matters more than the strength of any single part.
• Inputs: environment, resources and history, with strategy translating them into choices.
• Transformation process: four components: work, people, formal organization, informal organization.
• Outputs: performance at three levels: the total organization, groups or units, and individuals.
• Fit relationships: six pairs among the four components.
• Best used for: finding the root cause of a performance gap before choosing a fix, especially ahead of large-scale change.
• Closest relatives: the McKinsey 7S framework and strategic fit.

What is the congruence model?

The congruence model starts from a practical problem. When performance slips, leaders tend to grab a familiar fix. They see a pattern that looks like one they solved before and assume the same remedy applies. Nadler and Tushman's answer is to slow down and diagnose first.

According to Mercer Delta's paper on the congruence model, the approach grew out of systems theory. In the mid-1970s Nadler and Tushman built a simple, pragmatic way of looking at organizations on the foundations laid by earlier theorists such as Katz and Kahn, Lorsch and Sheldon, and Seiler. The paper describes an organization the way a biologist describes a living system: it takes input from its surroundings, runs it through an internal transformation process, and produces output. It can also use feedback, which means it can use its output to change its input and refine its own processes.

That's the first useful idea. Most organizational problems are treated as people problems or structure problems. The model asks you to look at the whole system and ask where the parts stop working together.

The second idea is fit, which the model calls congruence. You can have strong talent, good technology, clean processes and a healthy culture, and still get poor results if those things weren't designed to work as a set. The paper borrows an image from systems theorist Russell Ackoff: take the styling of a Jaguar, the engine of a Porsche, the suspension of a BMW and the interior of a Rolls Royce. Put them together and you don't get a great car, because none of them were designed to fit.

The model at a glance: inputs, process, outputs

Think of the model as three layers, with feedback running from outputs back to inputs.

Let's take each layer in turn.

Inputs: the givens

Inputs are the things an organization has to work with at any point in time. The Mercer Delta paper names three categories.

Environment. Everything outside the organization's boundary that can affect it: customers, suppliers, regulators, competitors, technology, economic and social conditions, unions, financial institutions and special-interest groups. The paper says the environment affects an organization in three ways. It makes demands, it imposes constraints and it creates opportunities.

Resources. The assets the organization can access, including people, technology, capital and information. Less tangible resources count too, such as reputation with customers or investors, or the internal climate.

History. The patterns of past behavior and effectiveness that still shape how the organization acts now. The paper points to strategic decisions, the acts of key leaders, past crises and core values and norms. Its examples show how two companies' histories pushed them in opposite directions: Xerox, which had to launch its first copier alone after larger firms turned it down, and Corning, which has long grown through collaborations.

Strategy. Sitting between the inputs and the transformation process, strategy is the set of decisions about where and how to compete. The paper splits it into corporate strategy (which businesses to be in) and business strategy (how to configure resources in response to the environment, given the organization's history). Many summaries fold strategy into the input layer, so you'll see it drawn both ways. What matters is that the organization's design has to serve it.

The four components of the transformation process

The heart of the model is what happens inside the organization. Per the same paper, there are four key components.

1. The work. The basic activity the organization does to carry out its strategy. A design analysis starts here, with the nature of the tasks, expected workflow, and the knowledge, skills, rewards and stress the work involves. Two retailers with very different strategies, one low-cost and one luxury, still do the same basic work of store-based retail. The difference is in how that work is configured.

2. The people. Who does the work. What knowledge and skills do they bring? What do they need and expect from the organization, financially and personally? How do they see their relationship with the company?

3. The formal organization. The structures, systems and processes that group people and coordinate their work: reporting lines, job design, planning and budgeting, performance management, rewards.

4. The informal organization. The unwritten rules that shape behavior: values, beliefs, accepted norms, political relationships and the way things actually get done. The paper notes this is sometimes called culture or operating environment, and that it can end up replacing formal structures that have lost their relevance.

If you know the McKinsey 7S framework, you'll recognize the territory. Both models say that structure, people and culture-like elements have to line up with strategy. The difference is in how they organize the question, which we'll compare below.

Outputs: performance at three levels

Outputs are what the system produces. The Mercer Delta paper defines them as the pattern of activities, behavior and performance at three levels.

• The total system: goods and services produced, revenue, profit, shareholder return, job creation, policy or service outcomes.
• Units within the system: how divisions, departments and teams perform and behave.
• Individuals: the behavior, activity and performance of people in the organization.

This three-level view is easy to skip and shouldn't be. A company can hit its revenue target (organization level) while one department burns out (group level) and its best performers quietly leave (individual level). A diagnosis that only looks at the top line misses both.

Fit: the six relationships

Fit is what the model is really about. The paper states it plainly: the tighter the fit, the higher the performance. It also makes a strong claim, that the interaction between each set of components matters more than the components themselves.

With four components there are six pairs. For each one, the paper's fit chart supplies the questions to ask.

A quick example shows how fit breaks. Suppose the work needs autonomy and fast decisions, and you've hired capable people for it. The formal structure even gives them authority. But if people have learned over the years to stay anonymous and avoid risk, the informal organization is working against the other three. Moving boxes on the org chart won't fix it. As the paper puts it, the culture will keep getting in the way.

Fit isn't static, either. In normal times managers keep adjusting to maintain it. When the environment shifts sharply, say through a technology breakthrough or a new kind of competitor, maintaining the current fit isn't enough and can lead to disaster. Those moments call for more radical change across most of the components.

How it compares with other diagnostic frameworks

Several models try to answer "why isn't this organization performing?" They differ in how much they include and where they draw lines.

The Burke-Litwin model, published in 1992, splits its factors into transformational ones (mission and strategy, leadership, culture) and transactional ones (structure, work unit climate and others). The Galbraith Star Model stresses that strategy, structure, processes, rewards and people all have to point the same way. Weisbord's Six-Box model comes from a 1976 article on six places to look for trouble in an organization.

Two differences stand out. First, the congruence model is explicitly input-to-output: it asks you to define the performance gap before you look for causes, which keeps a diagnosis from drifting into a general audit. Second, 7S gives you a list of seven things to align, while the congruence model gives you four components and six specific relationships to test between them.

How to run a congruence diagnosis

The Mercer Delta paper lays out an eight-step method. Here it is, adapted into a working sequence.

1. Identify the symptoms. Start with what you can see: missed targets, turnover, slow decisions, customer complaints. Symptoms aren't causes, but they tell you where to look.
2. Specify the inputs. Gather data on the environment, resources and history, and write down the strategy. The paper flags that some of the most serious problems come from external change. Check strategy before blaming internal causes, or you risk doing the wrong thing more efficiently.
3. Define the output. Decide what output the strategy needs at each of the three levels, then measure what you're actually getting.
4. Determine the problems. Find the specific gaps between planned and actual output. Where you can, attach a cost: extra expense or missed revenue.
5. Describe the four components. Collect data on the work, the people, the formal organization and the informal organization. Interviews, surveys, workflow maps and observation all help.
6. Assess the congruence. Rate the fit for each of the six pairs.
7. Generate hypotheses. Look for links between poor fit and the output gaps from step 4. Test whether a given misfit really explains a given problem.
8. Identify action steps. Choose changes, from targeted fixes to further data collection, and predict their consequences, since a change to one component will ripple through the others.

This pairs naturally with a gap analysis, which is essentially steps 3 and 4 done formally. And once the diagnosis points to a change, you'll need a plan to carry it out. For that, see strategy execution and Kotter's 8-step change model.

Congruence diagnosis template

Copy this table into a spreadsheet or doc. Score each fit pair from 1 (poor) to 5 (strong) and write the evidence next to it.

Then fill in the output side:

A good diagnosis usually finds one or two low-scoring pairs that line up with the biggest gaps. Start there instead of trying to fix everything at once.

Examples by business function

The model is built for whole organizations, but the same logic works at team level. These are generic, illustrative scenarios.

Take the sales case. The outputs show missed enterprise targets (organization level) and uneven team results (group level). Looking at the components, the work is long and collaborative, the people are capable, but the pay plan rewards individual speed. The misfit sits in work to formal organization. The fix is a design change to incentives and deal credit, not a round of sales training.

Do's and don'ts

Do:

• Define the output gap before you describe any components.
• Score fit between pairs, not just the health of each component alone.
• Include the informal organization. It's usually where the surprises are.
• Look at all three output levels.
• Check the environment and strategy first. Sometimes the problem is the plan, not the organization.
• Repeat the diagnosis after a major change. Fixing one component can create a new misfit.

Don't:

• Treat it as a one-time audit. The environment moves, and so does fit.
• Redesign structure alone and expect results. One changed component with three unchanged ones just moves the misfit.
• Diagnose from the executive suite only. People and informal norms show up in interviews with the people doing the work.
• Confuse a symptom with a cause. High turnover is a symptom; poor individual-to-work fit may be the cause.
• Use the model to justify a decision you've already made.

Common mistakes

Starting with the solution. The model exists to stop that reflex. If a reorganization is already decided, the diagnosis becomes a rubber stamp.

Treating culture as soft. The informal organization carries real weight. A formal change that contradicts it will usually lose.

Ignoring history. Past decisions and crises still shape what the organization can do now. A company that was burned by a failed merger will approach partnerships differently from one that grew through them.

Scoring components instead of pairs. "Our people are strong" tells you little. "Our people's skills don't match the new work" is a finding.

Skipping the output step. Without a defined gap, every misfit looks like a problem and nothing gets prioritized.