Information Problem or Alignment Problem?

When organizations get stuck, one of the most common responses is to bring in a consultant.

And, hey, sometimes that’s exactly what’s needed. An outside expert can bring specialized knowledge, analyze a problem, benchmark against other organizations, identify options, and recommend a path forward.

But all too often, leaders bring in a consultant when they already know what needs to be done.

The real problem they’re trying to solve is that the people involved can’t agree about what to do.

Is this an information problem or alignment problem?

An information problem sounds like:

  • We don’t understand why this is happening.
  • We don’t know what our options are.
  • We don’t know what this will cost.
  • We don’t understand the likely consequences of each choice.
  • We need expertise we don’t currently have.

Those are all very good reasons to bring in outside expertise, gather data, conduct research, or analyze the problem more deeply.

An alignment problem sounds different:

  • We understand the issue, but disagree about what to do.
  • Different stakeholders have different priorities or incentives.
  • We disagree about which tradeoffs are acceptable.
  • Nobody is quite sure who actually gets to decide.
  • There’s history between the people or groups involved.
  • Trust has eroded.
  • We keep revisiting decisions we thought we’d already made.
  • We’ve been having some version of the same conversation for months (or years).

You can hire a very smart consultant in that environment. They may produce an excellent analysis and a thoughtful set of recommendations. But at the end of the engagement, the same people will still have to sit around the same table and work through the same disagreement.

Reasonable people can look at the same facts and disagree

One mistake organizations make is assuming that if people disagree, somebody must not understand the facts. But often, everyone understands them perfectly well.

Two reasonable stakeholders can look at exactly the same information and reach different conclusions because they have different responsibilities, risks, incentives, constituents, experiences, or definitions of success.

The finance leader sees an unsustainable cost, while the operational leader sees an essential capability.

Employees see disruption, but customers see declining service.

One stakeholder worries about what happens if the organization changes course. Another worries about what happens if it doesn’t.

More analysis doesn’t automatically reconcile those perspectives. At some point, the work shifts from figuring out the answer to figuring out how to make a choice together.

Consulting isn’t the only way organizations avoid conflict

There are many creative workarounds that organizations deploy to avoid hard conversations. They might:

  • Reorganize the team.
  • Change reporting relationships.
  • Create a new committee.
  • Commission a study or assessment.
  • Add another layer of governance.
  • Redesign a process.
  • Replace a leader.
  • Implement a new tool.
  • Schedule another round of stakeholder interviews.

Any of these might be exactly the right intervention. But they can also become ways of creating distance from a difficult conversation.

Moving boxes around an org chart won’t resolve an underlying disagreement about priorities, accountability, resources, or trust. Replacing a leader won’t solve a systemic conflict if the same conditions remain in place for the next person.

Creating a committee won’t help if nobody has defined what that committee can actually decide.

And asking a consultant to recommend the answer doesn’t usually change the difficult reality that leaders ultimately have to own that decision themselves.

Before prescribing the solution, it’s worth asking: What problem are we actually trying to solve?

Start with the decisions

When an organization is stuck, one of the most useful things it can do is surprisingly simple:

Define the decisions that actually need to be made.

Not the usual vague “we need to discuss our strategy” or “address concerns about the operating model” or “improve collaboration.”

What specifically needs a yes, no, choice, commitment, owner, or next step?

Once those decisions are explicit, you can separate three very different things:

  1. What do we know?
  2. What do we still need to know before we can responsibly decide?
  3. What do we know already but disagree about?

That distinction matters. If a genuine information gap is preventing a responsible decision, by all means, go get the information. Bring in the consultant. Find the technical expert. Run the financial analysis.

But if the necessary information already exists and the obstacle is competing interests, unresolved tradeoffs, unclear decision rights, damaged trust, or an inability to work through disagreement, more analysis may simply give everyone more material with which to defend the positions they already hold.

Sometimes neutral facilitation should come first

A well-designed facilitated discussion can be a useful (not to mention substantially less expensive) first step when you’re not yet sure what kind of problem you have.

Good facilitation isn’t about getting everyone to agree. It’s about helping people disagree productively enough to move.

That can mean surfacing the interests underneath stated positions. Clarifying decision rights. Separating facts from assumptions. Naming tradeoffs. Identifying areas of genuine agreement. Determining what additional information is actually necessary. And creating enough structure that difficult conversations result in decisions rather than another meeting.

Sometimes that process reveals a genuine information gap. Great! Now you can bring in the right expertise with a much clearer question to answer.

Other times, the group discovers that it already knows enough to move forward.

Don’t let the conversation disappear when the meeting ends

This is also why I’m a big believer in decision and commitment logs. For every significant issue, capture:

  • What did we decide?
  • What remains undecided?
  • What additional information is needed?
  • Who owns the next action?
  • By when?
  • When will we revisit it?

It sounds almost too simple. But complex organizational conversations often fail not because people aren’t capable of reaching agreement, but because conclusions remain fuzzy. Different people leave with different interpretations. Decisions quietly reopen. Commitments lose their owners.

A decision and commitment log turns conversation into organizational action.

Diagnose before you prescribe

Consultants, reorganizations, leadership changes, studies, new governance structures, new technology, and redesigned processes all have legitimate uses.

The question is whether the intervention matches the problem.

So before you bring in the next consultant, redraw the org chart, or create another committee, ask two questions:

#1) What don’t we know?

And then:

#2) What do we already know… but haven’t been able to agree about?

If the second question is the harder one, you may not have an information problem. You may have an alignment problem. And that requires a very different kind of work.


Hey there, Chiefs of Staff:

I’ve written a companion piece on how to recognize these patterns from your seat, too.

Scroll to Top