All Articles

Before You Solve the Problem, Make Sure You Understand It

By
Mike Horne
July 28, 2026
Share this post

Organizations begin solving problems before they understand what is producing them. A leader asks for better communication, stronger accountability, improved decision-making, or greater alignment, and the request quickly becomes an initiative. A training program is commissioned, a consultant is engaged, or a new process is introduced. The organization moves before anyone has established whether the proposed response fits the situation.

Solutions create momentum. They give leaders something visible to approve and teams something tangible to deliver. Diagnosis is less satisfying because it requires patience, uncertainty, and a willingness to discover that the original request may rest on a partial or mistaken explanation.

Moving too quickly wastes money and time, weakens confidence in future interventions, and can place capable people in the position of delivering work they already suspect will fail. Competent delivery cannot compensate for a problem that was never understood well enough.

I learned this earlier in my career while leading a development intervention for senior leaders just below the executive team. The work was successful, and senior leaders wanted to expand it across the organization.

The difficulty was that the intervention depended heavily on the person delivering it. We were working with the psychologist who had created the approach, someone with exceptional command of both the material and the room. He had a team, but his capability could not simply be multiplied. The original intervention succeeded because of its expertise, audience, timing, and context.

I advised against a broad rollout, but the organization proceeded. The expanded program relied on less experienced facilitators and assumed the design could be transferred intact through materials and process. The results were poor. Participants received a weaker version of the work, skepticism spread, and the credibility of the organizational development function declined.

The organization had reproduced the visible form of the intervention while losing the conditions that had made it effective. The initial question focused on how to bring a successful program to more leaders. A better inquiry would have examined what produced the success, which elements could be reproduced, and what would be lost at scale.

The Requested Solution Often Arrives First

Internal advisors and consultants are frequently approached with a solution already embedded in the request. A leader asks for a workshop on accountability, a communication plan, a leadership program, or a new decision process. The request sounds clear because it names an action, but it may say very little about the condition beneath it.

An accountability concern may involve unclear ownership, conflicting authority, or consequences applied inconsistently. A communication concern may reflect disagreement that leaders have avoided resolving. Resistance may be a reasonable response to an impractical change. A request for leadership development may arise from a structure that asks capable leaders to operate with uncertain decision rights.

Once the solution has been named, the organization begins organizing around it. Budgets are assigned, timelines are established, and sponsors become attached to the initiative. Questions about the diagnosis can then feel obstructive, even when they are necessary.

The advisor must respect the client’s concern without treating the first explanation as complete. That requires independence, political judgment, and a few simple questions: What has actually been observed? Where does the pattern occur? When does it disappear? What evidence supports the conclusion already reached?

Success Can Be Misunderstood

Organizations usually think of diagnosis as a response to failure, but success can also be misread. A program works in one part of the business, a leader produces unusual results, or a team develops an effective practice. The organization then tries to reproduce the outcome by copying what is most visible.

The visible elements may include a training design, meeting format, tools, or activities. Less visible conditions often matter more: the skill of the person leading the work, participant readiness, sponsor credibility, timing, and trust within the group.

When organizations scale the visible elements without understanding those conditions, they preserve the form and lose the substance. The materials remain, but the judgment that made the work effective does not.

This is especially common in leadership development. A powerful experience with a skilled practitioner creates understandable pressure to reach more people. The question is whether the experience can survive the delivery model required for scale. Some interventions can be redesigned successfully. Others depend too heavily on expertise that is scarce, tacit, or difficult to transfer.

Recognizing that limit is part of sound diagnosis. Repetition does not guarantee replication.

Training Is Often Asked to Carry Too Much

I have also seen organizations respond to broad concerns about decision-making by commissioning surveys, training programs, and new tools. These efforts can grow quickly because decision-making touches nearly every part of organizational life. The initiative gathers data and teaches techniques while the underlying condition remains unchanged.

The source may lie in authority rather than skill. Leaders may know how to make sound decisions but lack clarity about who owns them. Senior executives may reopen decisions, functions may operate with competing priorities, and people may avoid risk because earlier decisions were punished inconsistently.

Training can improve judgment and process. Its effect is limited when the deeper condition involves contradictory authority, unstable sponsorship, or leadership behavior that no one is prepared to address.

Broad labels such as decision-making, accountability, communication, and culture often conceal several problems. A useful diagnosis identifies where the pattern appears, who holds authority, and what consequences follow.

Some Problems Survive the Intervention

Earlier in my career, I worked with companies under severe financial pressure where the response centered on reducing headcount. In some cases, layoffs were unavoidable. In others, they lowered costs while leaving deeper problems in strategy, market position, pricing, or operating discipline largely intact. Fewer employees improved the expense line, but the business remained weak.

Organizations often choose responses that can be implemented through existing authority. Leaders can approve training, reorganize a function, buy technology, or reduce staffing more readily than they can address senior leadership behavior, strategic choices, or established power arrangements. Diagnosis therefore includes a practical assessment of whether the sponsor has the authority, appetite, and support to act on what the inquiry may reveal.

Evidence Before Interpretation

Good diagnosis begins by separating observation from conclusion. “Employees are resisting” is an interpretation. The evidence may be delayed adoption, low participation, repeated questions, or continued use of an older process. Each observation could support several explanations.

The same discipline applies to claims about accountability, culture, communication, and leadership. These terms often describe frustration without explaining what is producing it.

An advisor needs to ask what people are doing, when the pattern occurs, where it does not occur, and what happens before and after it. Contrasts often reveal more than averages. If one part of the organization is making decisions effectively while another is struggling, the difference may point to leadership practice, decision rights, or operating conditions.

The history of earlier interventions also matters. What has already been tried, which assumptions guided those efforts, and under what conditions did any part work? Repeated training may point to a transfer problem that training alone cannot solve.

Early explanations are appealing because they reduce uncertainty. They can also cause later evidence to be interpreted in ways that confirm the first view. Staying with the situation longer protects the organization from an intervention built around a convenient story.

The Advisor’s Credibility Is Part of the Decision

Advisors sometimes agree to poorly diagnosed work because saying yes preserves the relationship. The sponsor wants action, the budget is available, and resistance may be interpreted as a lack of responsiveness. Delivering the requested intervention can feel safer than questioning it.

The risk appears later. When the work fails, participants rarely distinguish between a weak diagnosis and competent delivery. They conclude that the training was ineffective or that the organizational development function cannot address real business problems.

That was one of the most damaging consequences of the failed rollout I described earlier. The original intervention had strengthened confidence in the function. The effort to scale it weakened that confidence because the organization could not reproduce the conditions required for success.

Advisors have a responsibility to say when an intervention is unlikely to work. They can propose a smaller test, a different design, or further investigation before a large commitment is made. The client may still proceed, but the quality of the advisory work depends on whether the risks were identified honestly and early enough to matter.

Credibility is built partly through responsiveness, but it also depends on judgment. An advisor who delivers every requested solution without examining the premise may appear cooperative in the moment and become less trusted over time.

Understanding Before Commitment

Leaders often feel pressure to act quickly, especially when a problem is visible and others expect a response. Speed becomes valuable after the situation is understood. Before that point, it can lock the organization into an expensive interpretation.

A disciplined diagnosis asks what evidence supports the proposed problem, where the pattern appears, what conditions seem to produce it, and what has already been attempted. It also examines whether the solution depends on unusual expertise, whether it can operate at the required scale, and whether the sponsor has the authority to address what may be discovered.

These questions help leaders see when an intervention is too broad, too dependent on one person, or disconnected from the source of the problem.

Organizations are often rewarded for visible responsiveness. A program is launched, a task force is formed, or a new process is announced. Movement can relieve pressure even when the work has little connection to the condition that produced the concern.

Before committing resources, leaders and advisors should be able to explain what they believe is happening, what evidence supports that belief, and why the proposed response fits the circumstances. A successful intervention may depend on conditions that cannot be reproduced at scale. Training may have little effect when authority is unclear. Cost reduction may leave the underlying business problem untouched. Sound action begins with a credible understanding of the situation.

Featured Articles

Subscribe to newsletter
By subscribing you agree to with our Privacy Policy and provide consent to receive updates from us.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Related Articles

How HR Leadership Builds Rich Cultures of Mutual Regard With These Powerful Hacks

Unlock the "People Dividend" in your organization. Discover practical HR tools to build a workplace culture based on respect, empathy, and mutual regard to drive ROI.

Designing Change: How Leaders Build Teams and Solve Big Problems

Learn the essential leadership skills for designing effective change. Discover how to build strong teams, co-create a shared purpose, and solve big problems systemically.

The Hidden Cost of Organizational Distance

As organizations grow, additional layers of leadership, new processes, and more formal decision-making structures often emerge. In many cases, these changes are necessary. Growth creates complexity, and complexity requires coordination. The challenge is not the existence of structure itself but what can happen when structure begins to create distance between decisions and the people responsible for carrying them out.