Imagine a meeting called to discuss a company's late deliveries.
The sales manager speaks first:
— We are losing customers because production cannot meet the deadlines.
The head of production replies:
— Our capacity is not the problem. Orders arrive with changes after the schedule has already been finalized.
Planning offers another interpretation:
— If the information arrived complete and on time, we could organize the operation better.
In just a few minutes, three different explanations emerge for a problem everyone recognizes.
And what is most interesting is that none of them necessarily has to be false.
Each professional may be describing situations they genuinely experience.
But there is an important difference between recognizing a situation, offering an explanation, and demonstrating what actually produces it.
If everyone seems to know the problem, why do so many organizations continue to face the same difficulties?
Perhaps because recognizing a symptom is not the same as understanding its causes.
When experience becomes certainty
Professional experience is a valuable resource.
People who work with a particular activity every day develop knowledge of its routines, constraints, difficulties, and opportunities.
An operator may identify an anomaly before it appears in the indicators. A salesperson may notice changes in customer behavior before they become evident in commercial results.
Likewise, an experienced manager may recognize patterns that have not yet been formally investigated.
That knowledge deserves recognition.
The problem arises when what someone perceives starts being treated as a definitive conclusion.
Consider some common statements:
"The team is demotivated."
"The system is too slow."
"The problem is a shortage of staff."
"Sales promises what operations cannot deliver."
These statements may describe real situations.
But they may also combine observations, interpretations, previous experiences, and hypotheses that have yet to be verified.
When an organization accepts these explanations without examining them further, it risks turning convictions into decisions.
A convincing explanation is not necessarily a proven cause.
And the more confidence placed in an unverified explanation, the less willing people may be to investigate alternatives.
The same problem can have different perspectives
Let us return to the company experiencing delivery delays.
For sales, the problem appears in customer dissatisfaction and the difficulty of fulfilling commitments.
For planning, it appears in unstable schedules, order changes, and the challenges of coordinating resources.
For production, it may show up as missing materials, interruptions, rework, or an inability to carry out activities as planned.
Each department sees part of the reality.
And that is a natural characteristic of organizations.
People have different responsibilities, receive different information, and are evaluated through indicators that do not always represent the performance of the business as a whole.
This influences how they interpret events.
Sales may consider an order late because delivery did not take place on the date promised to the customer.
Production may believe it met the deadline established in the latest schedule it received.
Planning may demonstrate that the original date became unworkable after a specification change.
All three statements may be supported by accurate records.
Even so, the organization still lacks a complete explanation of what caused the delay.
That is precisely why bringing different perspectives together does not simply mean selecting the one that sounds most convincing.
It means understanding how those perspectives relate to one another.
Fact, perception, hypothesis, and evidence are not the same thing
A recurring difficulty in management is using these words as though they represent the same level of knowledge.
They do not.
Fact is something that can be identified and verified.
An order should have been delivered on Friday but was delivered the following Monday.
There is an objective difference between the planned and actual dates.
Perception is how someone interprets or experiences a given situation.
A customer may perceive a lack of commitment. A salesperson may perceive difficulties in production. An operator may perceive disorganization in planning.
These perceptions matter because they help reveal situations that need investigation.
Hypothesis is a possible explanation for what happened.
The delay may have been caused by a shortage of materials, a change in scope, inadequate scheduling, or a combination of these factors.
Evidence is verifiable information that supports or contradicts a particular claim.
Records of order changes, material availability, production logs, and scheduling history can help assess which explanations are consistent with the events.
But an additional precaution is needed.
Finding information consistent with a hypothesis does not automatically establish a cause-and-effect relationship.
A company may establish that materials were missing during a particular period and that some deliveries were late.
That alone does not prove that the material shortage explains all the delays.
It is necessary to check which orders were affected, when the constraints occurred, and whether other relevant factors were involved.
The goal is not to accumulate information.
It is to build an understanding sufficiently sound to guide decisions.
The cost of deciding based on an incomplete explanation
Imagine that, in response to complaints about delays, senior management decides to hire more people for production.
The decision seems reasonable.
If the company cannot deliver on time, expanding capacity may be a legitimate option.
But what happens if the main constraint lies in scheduling?
New employees may be idle at certain times and overloaded at others.
And what if recurring material shortages are the problem?
The team may grow even though, at certain moments, there is no work available for it to perform.
And what if order changes are disrupting the production sequence?
Hiring may increase the cost structure without eliminating interruptions.
This does not mean that hiring is a mistaken decision.
In some situations, it is exactly what the organization needs.
The question is different.
Which problem are we trying to solve, and what evidence supports the chosen solution?
The same reasoning applies to decisions about technology, automation, cost reduction, team reorganization, or supplier replacement.
An intervention may produce localized improvements while leaving intact the mechanism behind a recurring problem.
In some situations, it may even create new difficulties.
That is why, before assessing the quality of a solution, we need to understand the quality of the diagnosis supporting it.
Investigating does not mean looking for someone to blame
There is a fundamental difference between investigating a problem and looking for someone to hold responsible.
When a meeting begins with the question "who made the mistake?", people may concentrate their efforts on justifying decisions, protecting their teams, or demonstrating that they fulfilled their responsibilities.
The conversation becomes a contest between explanations.
Important information may never surface.
By contrast, when the goal is to understand how the organization operates, the dialogue changes.
Instead of asking why a particular department missed the deadline, we can investigate:
- What was originally planned?
- What actually happened?
- At what point did the first discrepancy appear?
- What information was available to each department?
- Which constraints influenced the decisions made?
These questions do not eliminate individual responsibilities.
They allow behaviors, decisions, and working conditions to be evaluated within the context in which events occurred.
This is particularly important because not every problem results from an inappropriate individual decision.
Some difficulties arise from the interaction of rules, systems, resources, priorities, and processes that may seem appropriate when examined separately.
One department can meet its targets perfectly and still contribute unintentionally to difficulties elsewhere.
The purpose of a sound investigation is not to find out who has the best justification. It is to understand what must change for the outcome to be different.
How can we build a more consistent understanding?
There is no single way to investigate every situation.
The depth required depends on the nature of the problem, the risks involved, the information available, and the consequences of a mistaken decision.
Nevertheless, a few practices help improve the quality of analysis.
Start with what happened, not with the most popular explanation.
There is a difference between saying "production is running late" and identifying which orders were late, under what conditions, how often, and in relation to which commitments.
Listen to the people involved in the actual work.
Indicators reveal important aspects of performance, but they do not always show how activities are carried out, what adaptations are necessary, and which difficulties must be overcome every day.
Compare information from different sources.
Operational records, decision histories, indicators, and team accounts can reveal relationships that remain hidden when each source is analyzed in isolation.
Consider alternative explanations.
A hypothesis should not be considered correct merely because we have found information that appears to confirm it.
We must also look for situations it cannot explain.
Assess the relevance of the factors identified.
Not every difficulty observed is a determining cause of the problem. Some are consequences, others are associated conditions, and some may have little influence on the outcome.
The challenge is to distinguish these relationships without turning every situation into an endless investigation.
Because investigating also consumes resources.
And an organization needs to balance analytical rigor with the need to act.
Understanding before deciding does not mean postponing every decision
There are situations in which an immediate response is essential.
An unsafe working condition, a critical equipment failure, or a serious customer service issue may require containment measures before the causes are fully understood.
In such cases, acting quickly may be the most appropriate decision.
But there is a difference between controlling the immediate effects of a situation and considering its causes definitively resolved.
An emergency measure may restore an operation without eliminating what caused the interruption.
Similarly, a temporary solution may preserve service while the organization develops a more consistent alternative.
The mistake is not necessarily acting before the investigation is complete.
It is confusing an emergency action with a permanent solution.
We cannot always wait to act. But we must recognize what we know, what we still do not know, and which risks we are accepting when we decide.
This distinction is essential to reconcile speed with decision quality.
A responsibility that does not depend on job title
Responsibility for decisions is often associated with professionals in formal leadership positions.
But the quality of the information and interpretations supporting those decisions depends on many people.
Someone performing an activity may identify differences between the planned process and what actually happens.
Someone serving customers may notice recurring difficulties that have not yet appeared in reports.
Someone analyzing data may find patterns that help challenge apparently settled explanations.
And leaders need to create conditions for that information to be shared, analyzed, and used constructively.
That requires a willingness to listen.
Including when what we hear contradicts our initial impressions.
An experienced professional does not need to abandon prior knowledge upon encountering a new reality.
But they need to recognize that previous experiences provide references, not automatic diagnoses.
The same solution that worked in one company may not produce similar results in another.
Because people, processes, resources, constraints, and the business environment may differ.
Professional knowledge helps us ask better questions.
It should not remove the need to answer them.
Before the answer, the quality of the question
Let us return to the meeting about late deliveries.
Sales remains concerned about customers.
Production continues to face difficulties.
Planning continues trying to coordinate resources and priorities.
Perhaps everyone has offered relevant information.
Perhaps some explanations are partially correct.
Or perhaps there is a relationship among factors that no single department can perceive in isolation.
In this context, the most useful decision may not be to choose one version immediately.
It may be to build a shared understanding of what happened, why it happened, and which conditions need to change.
This does not guarantee that every decision will be correct.
But it creates better conditions for acknowledging uncertainties, comparing alternatives, and learning from results.
Because organizations do not face difficulties only because they lack information.
They often face difficulties because they turn partial information into definitive conclusions.
And those conclusions guide decisions affecting people, processes, customers, and economic results.
The question is not only whether we know the problem. It is whether we can demonstrate that we understand what produces it.
And in your organization?
When a recurring problem arises, how does your team construct an explanation?
Are decisions based on verified facts or on the interpretations of those who present the most convincing arguments?
Is there room to question hypotheses that have already been accepted?
And, above all, when a decision does not produce the expected results, does the organization revisit the diagnosis or simply look for another solution?
Power 4P believes that developing management capability also means improving the way organizations understand their own reality.
Because a good decision does not necessarily begin with an answer.