A guide for executives who need to know what is actually broken before spending money fixing the wrong thing.
Most leaders do not wake up eager to buy an organizational diagnostic. It is expensive, and when most things are working, there is no reason to. They arrive here because the same problem keeps coming back. They have tried to fix it, sometimes more than once. A change effort fizzled, the symptom moved somewhere else, or the organization worked around the problem until the workaround became the real process. They know what they want. They know they are not getting it. What they do not yet know is why.
This guide is written to help you buy well, including if the right answer is another firm or no diagnostic at all. It covers what a diagnostic is, the patterns that generate organizational friction, whether outside help is warranted, which kind of firm fits, what credible work must include, what to ask, and what it should cost.
What is an organizational diagnostic?
An organizational diagnostic is a structured, qualitative investigation into why an organization is not performing the way its leaders intend. It examines the conditions shaping behavior: where decision authority actually sits, what the measures reward, where work loses momentum between functions, and which commitments quietly lose when priorities compete. The value of an outside researcher is straightforward: fresh eyes, no vested interest in a particular answer, and a way around the big edit button that exists between every lower-level employee and the C-suite.
Data can tell you what is happening and where to look. Confidential interviews help explain how and why. A credible diagnostic tests what people say against documents, metrics, workflows, and observed behavior. The goal is not to count complaints. It is to determine the organizational footprint of the pattern and whether it is consequential enough to require a decision.
It is diagnosis, not implementation. The work should identify the findings, the decisions leadership has to make, and the actions or initiatives those findings require. It does not automatically choose the final design or provide the implementation roadmap.
Diagnosis before prescription. Truth without blame.
What is organizational friction?
Organizational friction is the gap between what the same time and money could produce in an ideal, frictionless state and what current conditions actually allow. That gap is a conceptual model, not a score anyone can calculate with false precision. It becomes visible through broken workflows, workarounds, rework, delay, repeated escalation, frustration, and heroic effort.
Most organizations are not uniformly stuck. They contain smaller systems, cultures, and ecosystems. Some parts move well while other friction points make a stated goal harder to achieve than it should be. Leaders often call the visible result a communication problem, an accountability problem, a leadership problem, or a culture problem. Those labels may be right, but they are not complete enough to support a decision. The mechanism underneath is what tells you what to change.
What are the patterns that generate organizational friction?
In our work, nearly all systemically generated friction can be understood through five distinct mechanisms, often operating in combination. Organizations are living systems, not science artifacts, so the framework is a disciplined way to test evidence, not a container that forces every finding to fit.
What separates these mechanisms from a general model of organizational health is the third column. Each pattern states what it is not. A pattern that cannot be ruled out cannot be ruled in. Broad categories that can accommodate any evidence may sound comprehensive, but they do not help an executive make a better decision.
| Pattern | The question it asks | What it is not |
|---|---|---|
| Decision Gravity | Do the people responsible know what to do, but still refuse to move without a senior leader's approval? | Legitimate executive governance. Uncertainty caused by unclear strategic direction. A handoff failure. |
| Ownership at the Seams | Was the work clear enough to execute, but the baton pass became the place where efficiency and effectiveness went to die? | General teamwork concerns. A decision that was never made executable in the first place. |
| Priority Collision | When the organization cannot protect both commitments, which one consistently survives, and what are employees learning from that choice? | Too many initiatives. Explicit, deliberate prioritization. An isolated tradeoff. |
| Agreement Without Enactment | Did leaders agree to a concept, or did they create an executable decision? | People who understand what to do but lack permission. Ordinary implementation difficulty. |
| Incentive Crosscurrents | What behavior does the measure actually produce, and how does that differ from the behavior leadership intended? | General culture concerns. People waiting for authority. An unspoken value hierarchy with no formal reinforcement. |
Three of these are worth stating plainly
Culture is not created by the priorities leaders name. It is created by the priority that wins when priorities collide.
Metrics do not drive the behavior leaders imagine. They drive the easiest behavior that satisfies the metric.
Shared words are not necessarily shared meaning. Shared meaning is not yet a decision. A decision is not enacted until it changes ownership, resources, behavior, or work.
Why do the same problems keep coming back?
Because leaders often move from a broad label to an obvious-sounding action before they understand the mechanism. We have a communication problem becomes communicate more. We have an accountability problem becomes hold people more accountable. Our culture is broken becomes launch another culture initiative. The label may be right. The prescription may still be exactly wrong.
Telling managers to take more ownership does not help when the system has taught them that moving without approval is not actually safe. Communicating the strategy again does not help when leaders agreed to words rather than to what those words require. Revising the KPI does not help when the measure itself is making the unwanted behavior rational. Acting before diagnosing is a fast way to increase both organizational friction and executive frustration.
There is also a separate question worth asking, which is not a sixth pattern:
What part of the operating model still assumes an organization that no longer exists?
We call this the Scale Gap. It is a contextual lens rather than a sixth friction mechanism. Growth, leadership transition, a merger, integration, restructuring, or expansion can outpace the systems, governance, and coordination that used to work. The five patterns explain how friction is being generated. The Scale Gap helps explain why it may be surfacing now.
It matters because the two call for different responses. A pattern can be addressed. An outgrown operating model has to be redesigned. Adding people, meetings, policies, or new metrics to compensate may keep work moving for a while, but it often asks people to carry a system that no longer carries the work.
Do you actually need a diagnostic?
Sometimes the honest answer is no. An outside diagnostic is worth buying when several of these are true:
- The same problem keeps returning after you have addressed it more than once.
- Your leadership team agrees in the room and the agreement does not survive contact with the week.
- You have a theory about who or what the problem is, and enough doubt that acting on it feels risky.
- A decision is coming that depends on the answer: a restructure, a leadership change, an acquisition, a new strategic plan.
- The people who know what is wrong are unlikely to say it to you directly.
You probably do not need an outside diagnostic when the issue is contained, trust is high enough for people to speak candidly, and the internal team doing the assessment is not part of the problem. If nothing in the organization occasionally gives you stressful 3 a.m. thoughts, that is good. Keep us in mind when those thoughts start. And if leadership does not have the capacity or intestinal fortitude to act on the findings, wait. There is nothing worse than not doing a diagnostic except asking people for their candor, hearing what they have to say, and then doing nothing with it.
What is the difference between an organizational diagnostic and an employee engagement survey?
An engagement survey gives you the what and the where. An organizational diagnostic investigates the how and the why. They work hand in hand, but they do not answer the same question.
| Engagement survey | Organizational diagnostic | |
|---|---|---|
| Question it answers | How do people feel about working here, and how does that compare to benchmark? | Why is this organization not performing the way its leaders intend? |
| Method | Standardized instrument, large sample, quantitative scoring | Confidential interviews, decision and document review, workflow and incentive analysis, qualitative synthesis |
| Output | Scores, benchmarks, trend lines, heat maps | An account of the mechanism generating the problem, with evidence, and the decisions that follow |
| Best used for | Tracking over time, spotting where to look, measuring whether something changed | Understanding a specific problem well enough to act on it |
| Common failure | You learn engagement dropped in operations and still do not know why | Findings are accurate, uncomfortable, and nobody decides anything |
Engagement scores, heat maps, and comments are useful evidence. They can show where to look, shape the interview sample, and help a researcher ask better questions. If a survey tells you something is wrong but cannot explain how the organization is producing it, that is when a diagnostic becomes the next step rather than another survey.
How do you tell whether you have a people problem or a system problem?
Our philosophy is systems first, not systems only. A leader may genuinely be part of the problem. But if that leader has been able to survive, and sometimes thrive, while repeatedly creating friction, the system has also allowed, protected, or rewarded the behavior. Our view is direct: bad leaders do not survive and thrive in good systems. Removing a person without examining the conditions that sustained the behavior can leave the organization ready to repeat the pattern.
Four useful tests can improve the question before anyone is hired:
The replacement test
If you swapped this person for the best version of the role you can imagine, would the problem go away? If the answer is "not really," it is not the person.
The pattern test
Is it happening in one place, or in several places with different people? A pattern across capable people is a system signal.
The predecessor test
Did the person before them struggle? If not, did they design the role around their own strengths, relationships, and institutional knowledge? A role can look proven when it was actually custom-fit to one person. Before blaming the successor, ask whether someone else could reasonably be selected, trained, and supported to succeed in the role as designed, or whether the organization needs a different role.
The incentive test
What does the organization actually reward here, as distinct from what it says it values?
These tests help determine whether you are asking the right question. They do not answer it. A credible firm should be able to explain how it reaches a people-versus-system conclusion through a preponderance of evidence, not instinct, chemistry, or one dramatic interview.
Who does this work, and which kind of firm is right for you?
Five categories of provider, with honest guidance on when each is the right call. None is inherently superior. The right choice depends on the question, scale, evidence needs, and who you want doing the work.
| Type | Examples | Choose them when | Be aware |
|---|---|---|---|
| Global strategy firms | Bain (Org Navigator), McKinsey (OrgSolutions) | You are operating at enterprise scale, need operating model redesign across many business units, and want benchmark data behind the recommendation. | You are buying a team with leverage. The partner who pitches may not be the person conducting interviews or writing the synthesis. Ask who will actually do the work, how much senior oversight exists, and whether the institutional method is enough for the question you need answered. |
| Leadership advisory arms of search firms | Korn Ferry, Spencer Stuart, Russell Reynolds | The real question is whether you have the right executives, or the work connects to succession and assessment. | These firms also place executives. That is a structural incentive worth saying out loud (not an accusation). Ask how they guard against concluding you need different people. |
| Assessment platforms and instruments | Gallup, Culture Amp, Denison, Human Synergistics | You need measurement at scale, benchmarking, or the ability to track quantitative values over time. | An instrument tells you what and where. It does not tell you how the problem is being generated. |
| Boutique and independent advisors | Smaller firms and senior independents, including Evolve | You want the senior expert close to the interviews, synthesis, CEO or board advice, and final decisions. Typically a strong fit for organizations of roughly 100 to 1,000 people. | Capacity is finite because the senior people are doing the work. Ask how the firm scales, who joins the team, and whether implementation is available or intentionally outside its model. |
| Internal HR or OD | Your own team | The issue is contained, trust is high, and the leadership team is not itself part of the question. | People rarely tell an insider the whole truth about the executive team, and your HR leader has to keep working there afterward. |
A practical note on comparison. If you invite several firms to bid, give them all the same written brief. Ask them to determine whether your performance problems are generated primarily by decision authority, cross-functional handoffs, competing priorities, unexecuted agreements, incentives, or an outgrown operating model, and to recommend what should change. Do not ask them to assess the leadership team unless leadership assessment is actually the question. That framing invites a stack of individual reports and may miss the system entirely.
How many people should be interviewed?
More is not automatically better, and this is the easiest place for a diagnostic to become expensive without becoming more accurate.
For most mid-sized organizations, 15 to 20 confidential interviews is enough to begin seeing the pattern. That typically means the executive team, selected skip-level leaders, and people who sit at the seams where work crosses functions. The researcher should be looking for data saturation and organizational footprint, not simply counting how many people said the same thing. Frequency and magnitude are not the same.
Larger counts make sense when there are multiple business units that operate differently, two post-merger populations that need separate reading, or an organization large enough that 20 people cannot represent it. Those are real reasons. Being thorough is not. A one- or two-week diagnostic can also be credible for a tightly bounded team, function, workflow, or friction point. It should not be sold as an enterprise diagnostic when fewer than ten voices cannot represent the enterprise.
What to ask for: a stated number of interviews in the proposal and a stated method for choosing participants. A firm that will not commit to a number may be planning to under-sample or leave the door open to scope creep. Ask how participants are selected, because who is in the room determines what the diagnostic can see.
One practical warning from experience: be precise about the difference between the number of interviews on offer and the number of calendar slots being held. Those are not the same thing, and confusing them is how a bounded engagement quietly triples.
What should you actually receive?
A diagnostic that ends in one long report has a predictable failure mode. Executives read it, understand it, feel the weight of it, and decide nothing. A 150-page report can preserve rigor. It cannot serve as the organization's everyday action tool.
Ask for layered deliverables designed around use. Each layer should stand on its own, while the full evidence and nuance remain available without being mandatory for every reader.
| Layer | What it does | Why it matters |
|---|---|---|
| Something visual, one page | Shows the whole pattern at a glance | This is what gets put on a wall, forwarded to a board member, and referred to six months later |
| A short decision document | States the choices leadership must make, with tradeoffs, implications, ownership, and timing | This is the layer that converts findings into decisions. Without it you have a description, not a useful diagnosis |
| A private note to the CEO | Isolates sensitive feedback and leadership moves intended only for the chief executive | Some findings should inform the CEO without becoming a public correction in front of the leadership team |
| Section entry points | Gives each leader an entry point into the findings within their domain | Lower-level friction can be owned and resolved inside a function without turning every finding into an enterprise initiative |
| The full evidence base | Preserves the complete findings, method, evidence, and reasoning | The organization retains the context and does not have to depend on the researcher being available to explain it later |
If a firm offers only the full report, ask how leaders will use it to decide. If it offers only the executive summary, ask what evidence and reasoning sit underneath it. Rigor should be available without requiring every leader to absorb the entire evidence base before acting.
What must a credible diagnostic include?
Whoever you hire, require these. A proposal missing several of them is selling something less than a diagnosis.
- Confidential qualitative interviews, not only a survey. The most useful findings are often things people will say only when they understand how the information will be handled. The people interviewing should remain close to the synthesis; dozens of hours of listening cannot be fully handed off through transcripts and notes.
- Input from below the executive team. This is where the gap between what leaders believe and what actually happens becomes visible. Even the most empathetic executive receives edited information.
- A decision rights analysis. Who actually decides, who believes they decide, what escalates, and why.
- An incentive review. What behavior the organization pays for, formally and informally.
- Examination of specific stalled work. Take two or three initiatives that did not land and trace what actually happened. Generalities hide the mechanism.
- A named mechanism, not a theme. "Accountability needs improvement" is a restatement of the symptom. You should end with a specific account of how the friction is being generated, its organizational footprint, the evidence behind it, and what other explanations were ruled out.
- An explicit people-versus-system determination, stated plainly and supported by the preponderance of evidence. The answer may be both.
- A defined point where leaders decide. Put a session on the calendar where findings become choices, not a report delivered into a full inbox.
What should you ask before hiring anyone?
Ask whatever you need to feel comfortable moving forward. These five questions are especially useful because they test method, continuity, confidentiality, and courage. The quality of the answer matters more than the polish.
| Ask this | What a strong answer sounds like |
|---|---|
| "If our leadership team tells you the problem is our people, how will you determine whether the real problem is the operating model?" | A concrete qualitative method. The firm should explain how it triangulates interviews against structure, documents, decisions, results, and observed behavior, and how it weighs organizational footprint rather than simple frequency. Vagueness here is disqualifying. |
| "Who will actually conduct the interviews and write the synthesis?" | A named person or small team available to meet before you sign. Ask whether the people who listen to the interviews will also code the evidence and write the synthesis. Important context is lost when those responsibilities are separated. |
| "What happens to what people tell you?" | A crisp explanation of attribution, aggregation, anonymized quotes, raw notes and transcripts, storage, access, and destruction. The answer should also adapt to the organization's level of trust. If the firm cannot explain this clearly, employees will sense it and edit themselves. |
| "What does this look like if you find something we do not want to hear?" | A direct answer, ideally with an example. Be wary of anyone who cannot imagine the scenario. |
| "What will we need to be ready to decide when this is finished?" | Specific decisions, named in advance. It also tells you whether they have thought past the deliverable. |
What are the red flags?
- The primary deliverable is a score or dashboard, and the firm cannot explain the qualitative evidence underneath it.
- They promise a comprehensive enterprise diagnostic in one or two weeks without a very small or tightly bounded scope.
- They describe the solution before they have looked at anything.
- They cannot tell you who will conduct the interviews, who will write the synthesis, or how close those people will remain to one another.
- The recommended next step is always their own implementation practice.
- They will not put an end date on the diagnostic.
- They promise to eliminate organizational friction, identify every root cause, or produce a specific outcome. Nobody can honestly make those promises in a living system, especially before leadership has made the decisions that follow.
- They treat a qualitative organizational problem as a purely quantitative or automated exercise. AI can support the work. It cannot replace the senior researcher's judgment, context, and responsibility for the synthesis.
- They will not tell you what is out of scope.
- The findings could have been written before the interviews.
What does an organizational diagnostic cost and how long does it take?
There is no standard market rate and most firms do not publish pricing. These are budgeting ranges, not fixed prices or a verified market benchmark.
| Type of engagement | Timeline | Interviews | Typical range |
|---|---|---|---|
| Focused or rapid diagnostic | 1 to 2 weeks | Under 10 | $10,000 to $30,000 |
| Full organizational diagnostic | 4 to 6 weeks | 15 to 35 | $40,000 to $75,000 |
| Diagnostic plus operating model design | 8 to 10 weeks | 30 to 40, plus design | $75,000 to $150,000 |
| Global strategy firm engagement | 8 weeks and up | Varies widely | Not published. Generally well into six figures and often beyond. |
Four to six weeks is the practical range for most mid-sized organizations. Shorter can work for a genuinely bounded team or workflow. Shorter at enterprise scale usually means the work cannot test what executives say against how the organization actually behaves. Longer can allow diagnosis to drift into implementation before anyone has decided what to do.
What Evolve charges
We publish our range so you can tell early whether this is a serious conversation and whether the economics fit the problem you are trying to solve.
| Engagement | Timeline | Interviews | Fee |
|---|---|---|---|
| 30-Day Executive Alignment Sprint | 4 weeks | Up to 20 | $40,000 |
| Extended diagnostic | 6 weeks | Up to 35 | $55,000 to $65,000 |
| Diagnostic plus operating model design | 8 to 10 weeks | Up to 40, plus design | $80,000 |
| Enterprise diagnostic | Bespoke | Above 40 | From $100,000 |
Most engagements fall between $40,000 and $80,000. Two things move an engagement up the range: the number of interviews and whether the work extends past diagnosis into designing the operating model, meaning decision rights, structure, and the accountability system that has to hold afterward.
Interview counts are stated rather than open-ended on purpose. It keeps the scope honest in both directions and means you know what you are buying before the work starts.
Terms are 50 percent to begin and 50 percent on delivery.
What happens after the diagnostic?
Three honest things are worth knowing before you buy.
A diagnostic can reveal the truth. It cannot compel leaders to act on it.
A good diagnostic ends with a small number of decisions in front of the people who can make them. Whether those decisions get made is not something any outside firm controls. The organizations that get value treat the findings as the start of a decision process rather than the end of a project. They also recognize the obligation created when employees have invested time and candor in telling the truth.
To explicitly say the quiet part out loud: organizational friction is not like wine or whiskey. It does not get better with age. It also does not disappear forever. No organization eliminates chaos in perpetuity. That is a rule of living systems, not a failure of leadership.
Friction is generated continuously by growth, turnover, changing priorities, new systems, and the ordinary movement of an organization through time. Anyone selling you a permanent end state is selling something that does not exist, and you may have bought it before.
What good organizations have is not the absence of friction. It is the capacity to see it early, be honest about what is producing it, and act before the organization begins amplifying it. That capacity rests on a small number of conditions: alignment across the system, collaboration that actually works, systems that serve the stated goals, a systematic way to turn what one person notices into how the organization adapts, and the discipline to integrate all of that back into daily work.
Periodic re-examination can be a reasonable investment, not a consultant inventing reasons to stay. It also means you should be suspicious of any proposal that implies the problem will be finished forever.
Before you commission anything, ask yourself one question. If this work tells you something you do not want to hear about your own role in the pattern, what will you do? If the honest answer is nothing, spend the money elsewhere.
Where Evolve fits
Evolve Your Performance is a senior-only practice. Dr. Mary Barnes conducts the interviews, does the synthesis, and is in the room when findings are presented. Her superpower is patterns: taking the spaghetti bowl of an organization and turning it into strands executives can see, test, and use. Interviewing, real-time pattern mapping, formal coding, and report writing stay in the same senior hands. This is not automated transcript summary, and your engagement is never handed to a junior consultant.
When an engagement needs more than one person, Evolve assembles a team from a network of vetted boutique firms and senior independents selected for that specific work. The same applies to implementation after the diagnostic. You get additional capacity when the work requires it without a leverage model and without being handed to whoever happened to be on the bench.
This shape fits organizations of roughly 100 to 1,000 people with real operational complexity, where the executive team is part of the question and where the value is senior judgment, candor, qualitative rigor, and the ability to connect patterns while the evidence is still being gathered.
What you receive
| Artifact | What it is |
|---|---|
| Findings Placemat | One page, visual. It turns the spaghetti bowl of findings into a pattern leaders can see and use together. |
| Decision Brief | The choices leadership now has to make, with implications, ownership, and timing. |
| CEO Advisory Note | Private and forward-looking. Sensitive feedback and leadership moves intended only for the chief executive. |
| Section Cover Memos | One page per finding area so each executive can act on lower-level friction within their domain. |
| Performance Friction Report | The full evidence base, with each finding structured as what we observed, why it matters, the tensions and tradeoffs it creates, and what leadership should consider. |
| Enterprise Maturity Model | Where you are, where you intend to be, and which gaps sit in which part of the organization, so prioritization is possible. |
| Executive Themes Brief and Visual Appendix | Shareable summary for the wider executive group, and full-size versions of every visual. |
We aren't the right fit if you need simultaneous work across many business units globally, benchmark data drawn from a large normed database, or a recognizable brand name on the cover for board purposes. Those are legitimate reasons to hire elsewhere. We will say so in the first conversation rather than the fourth.
A useful place to start
The Organizational Signals Assessment is free, confidential, takes about five minutes, and does not require talking to anyone.
It asks 25 statements about how your organization operates, then returns a ranked Organizational Friction Signal Map across the five patterns, a separate Scale Gap reading, an interpretation of the strongest signals, and questions your leadership team can examine.
What it is not: a diagnostic, diagnostic light, or a root-cause determination. It works from one leadership perspective and cannot evaluate individual leaders or represent every part of the organization. It provides clarity about signals and a credible hypothesis worth investigating.
It can also be a useful shared-language exercise. C-suite members can complete it with their own silos in mind, then compare where they see the same signals and where their experiences diverge. If you take it before speaking with us, it can create a useful foundation for the conversation. If you would rather begin with a 15- or 30-minute call, do that. The assessment is a useful starting point, not a gate you have to pass through.