Beyond the Moment: From The HUBER Strategy™ to Operational Intelligence
 | |
|
There is a particular kind of satisfaction that comes from solving a difficult problem.
The customer is taken care of. The system is working again. The deadline is no longer in danger. The team can finally exhale. Someone closes the ticket, updates the project plan, or sends the much-anticipated email confirming that everything has been resolved.
We did it.
Then everyone moves on.
That is often the moment when an organization becomes vulnerable all over again.
Resolving the immediate problem does not necessarily mean we understood what caused it. It does not mean the process is stronger. It does not mean the next person will recognize the warning signs, have access to the same knowledge, or receive the same level of support. It may only mean that a capable person worked very hard to prevent the organization from experiencing the full consequences of its own weaknesses.
That is an accomplishment. It is also a warning.
A problem can be handled beautifully and still teach the organization absolutely nothing.
The Moment After the Moment
The HUBER Strategy™ was created for the moments when work becomes messy.
Hear.
Understand.
Build Trust.
Execute.
Reinforce.
It is a practical way to respond when the facts are incomplete, the emotions are real, the systems are complicated, and somebody still needs an answer.
We begin by hearing more than the words being said. We work to understand the system beneath the symptom. We build trust by telling the truth while people can still do something with it. We execute with clarity and ownership. Then we reinforce what worked so the solution does not disappear the moment the meeting ends.
That approach helps us navigate the immediate situation responsibly.
But even Reinforce is not the end of the story.
Once the customer is safe, the work is stabilized, and the immediate pressure has passed, another set of questions becomes possible.
What did this problem reveal?
Why was it difficult to resolve?
Which part of the process worked only because someone knew a workaround?
Where did the official procedure differ from what people actually do?¹
What information was missing?
Which measurements told us everything was fine while the people closest to the work knew it was not?
Who had the knowledge we needed, and why was that knowledge so difficult to find?
Most importantly, what would have to change for better performance to become normal rather than heroic?
This is where The HUBER Strategy™ leads naturally into Operational Intelligence.
The HUBER Strategy™ is how we respond when the work gets messy.
Operational Intelligence is how we make better work repeatable.
The HUBER Strategy helps us navigate the mess. Operational Intelligence helps us learn from it.
Intelligence Is Not the Same as Information
Organizations have no shortage of information.
They have dashboards, reports, case histories, project plans, customer surveys, performance metrics, process documents, meeting notes, chat transcripts, knowledge bases, utilization figures, quality scores, forecasts, and enough spreadsheets to make a small forest file a restraining order.
What they do not always have is understanding.
Information tells us that something happened. Intelligence helps us understand why it happened, what it means, who it affects, and what should be done differently because of it.
That distinction matters because organizations can become highly efficient at collecting evidence without becoming any better at interpreting it.
A dashboard can tell leadership that response time improved. It may not reveal that employees are closing work before the customer’s actual problem is resolved.
A report can show that productivity increased. It may not show that the work was divided into smaller units, shifted elsewhere, or stripped of the difficult activities that made the original metric meaningful.
A process document can confirm that everyone received the instructions. It cannot confirm that the instructions were realistic, understood, consistently followed, or compatible with the systems people use every day.
A customer survey can provide a score. It may not explain whether the score reflects the product, the service, the relationship, the implementation, the billing process, the latest frustrating interaction, or the customer’s growing belief that nobody understands how their business works.
The numbers may be accurate and the conclusion may still be wrong.
Operational Intelligence requires more than access to information. It requires the discipline to connect information to reality.
Understanding the Work From Every Direction
Work does not exist from only one perspective.
A process that looks efficient to leadership may feel impossible to the employee performing it.
A policy that makes sense to Finance may create unnecessary friction for a customer.
A system configuration that appears logical to the technical team may conflict with the physical sequence of work on a warehouse floor.
A service model that works beautifully in a presentation may fall apart when a real person has an urgent problem that does not fit neatly into the approved categories.
None of these perspectives is automatically the whole truth. Each contains part of it.
Operational Intelligence requires organizations to understand the work from the perspectives of the people, customers, systems, and physical processes involved.
The people doing the work know where the process bends, breaks, and depends on memory. Customers know where the organization’s internal structure becomes their external burden. Systems contain records of what happened, although not always why. Physical processes reveal the constraints that cannot be solved by changing a field on a screen or adding another approval step.
Intelligence begins when these perspectives are brought together.
That does not mean every disagreement can be solved by putting twelve people in a conference room and asking them to “align.” We have all attended enough meetings to know that physical proximity does not automatically produce shared understanding.
It means recognizing that contradictions are useful.
When the documented process says one thing, the system records another, the employee describes a third, and the customer experiences a fourth, the contradiction is not an inconvenience to be smoothed over. It is the clue.
Something important is happening in the space between those accounts.
Operationally intelligent organizations investigate that space.
Measurement Integrity
This also requires measurement integrity.
Measurement integrity means processes are defined, communicated, followed, and evaluated in ways that reflect what is actually happening.
That sounds obvious. It is not.
Every measurement creates a temptation. Once people know what is being counted, they begin making decisions in relation to the count. Sometimes that improves performance. Sometimes it simply improves the appearance of performance.²
People are not necessarily dishonest when this happens. They are adaptive.
Give someone a quota without accounting for the rest of their responsibilities, and they will find a way to meet the quota.
Reward speed without protecting quality, and the work will become faster.
Measure closure without examining resolution, and things will be closed.
Ask for activity, and you will receive activity.
Then everyone will gather around the dashboard and admire the progress.
The danger is not that metrics exist. We need measurement. The danger is believing that a measurement remains meaningful regardless of how the work changes around it.
Measurement integrity requires us to ask whether the metric still represents the outcome we think it represents.
Do employees understand what is being measured?
Can they influence the result in ways that do not improve the underlying work?
Does the process make compliance possible?
Are exceptions visible, or are people forced to hide them so the report remains clean?
Does the measurement capture customer outcomes, or only internal activity?
What behavior does the metric encourage when nobody is watching?
A number without operational context can be precise, defensible, and completely misleading.
That problem becomes even more serious when we introduce artificial intelligence.
AI Can Connect the Work, or Compound the Misunderstanding
AI creates extraordinary opportunities for Operational Intelligence.
It can help organizations capture, organize, and retrieve knowledge that might otherwise remain scattered across documents, conversations, systems, and the memories of experienced employees, provided that knowledge is deliberately elicited and validated. It can compare customer feedback across thousands of interactions. It can identify recurring patterns that appear unrelated when viewed one at a time. It can help reveal contradictions between documented procedures and actual behavior when the organization has made both visible enough to compare. It can coach employees through complex decisions, reduce repetitive administrative work, and make expertise available closer to the moment when it is needed.⁴
Used responsibly, AI can help us see connections that are too large, too dispersed, or too subtle for any one person to recognize.
That is exciting.
It is also where we need to be careful.
AI does not float above the organization collecting objective wisdom from the universe. It works with the information we provide, the systems we connect, the assumptions we encode, the processes we document, and the outcomes we reward.
If those inputs are distorted, the output may be distorted too.
We have had a phrase for this since long before generative AI: garbage in, garbage out.⁵
It is so widely understood because it captures the problem cleanly. AI has not repealed the principle. It has simply made the garbage faster, more fluent, and easier to mistake for intelligence.
The difference is that AI can present the distortion with remarkable speed, consistency, and confidence.
Operational Intelligence requires organizations to understand the work from the perspectives of the people, customers, systems, and physical processes involved. It also requires measurement integrity: processes that are defined, communicated, followed, and evaluated in ways that reflect what is actually happening.
AI can help connect perspectives, preserve industry knowledge, identify contradictions, and reveal patterns leadership cannot see.
But when AI is built on incomplete data, manipulated metrics, inconsistent processes, and information detached from the work, it does not create intelligence.
It creates a more convincing version of the misunderstanding.
That may be the central operational risk of this next era.
Not that AI will know nothing.
That it will know exactly what we taught it, including the parts we never bothered to question.
Better Work Requires More Than Better Technology
This is why the next chapter of my work cannot be only about AI.
AI will be part of it because AI is already changing how organizations capture knowledge, design services, evaluate performance, and distribute decision-making authority.
But technology is only one participant in the system.
Operational Intelligence is also about people and perspective. It is about whether expertise is respected before a crisis makes it necessary. It is about whether employees are empowered to use judgment or merely instructed to follow processes that everyone knows do not work.
It is about knowledge. Not only how we document it, but how we recognize it, preserve it, challenge it, and pass it forward.
It is about manners, because operational friction is often made worse by the way people treat one another when something goes wrong. Courtesy is not decorative. Respect affects what people are willing to share, which risks they raise, and how quickly the truth reaches someone who can act on it.³
It is about practice and habits, because organizations do not become intelligent by announcing a new value in a town hall. They become intelligent by repeatedly doing the difficult, often unglamorous work of examining decisions, testing assumptions, improving processes, and learning without immediately looking for someone to blame.
It is about accountability, including the uncomfortable difference between holding people accountable for their responsibilities and making them responsible for failures created by the system.
It is about customer service and the growing temptation to use automation as a wall between companies and the people they serve.
It is about expertise, including what happens when organizations undervalue experienced employees because their knowledge is difficult to quantify, then discover that the knowledge was holding entire processes together.
And ultimately, it is about humanity.
Organizations are not intelligent because their technology is advanced. They are intelligent when they can perceive reality, learn from experience, exercise sound judgment, and improve how people work together.
AI may strengthen that capability.
It cannot replace the responsibility to build it.
Beyond the Rescue
Many organizations survive because someone notices what the process missed.
Someone remembers the history.
Someone calls the customer.
Someone translates between departments.
Someone questions the metric.
Someone stays late, follows up, finds the right person, reconstructs the missing context, and keeps pushing until the problem is truly resolved.
Those people are often described as heroes.
They deserve appreciation.
But heroism should be treated as evidence.
When the same people must repeatedly rescue the same kinds of situations, the organization is not witnessing a series of exceptional performances. It is receiving information about how the work has been designed.
The goal is not to eliminate human judgment, care, creativity, or initiative. Those are among the most valuable things people bring to work.
The goal is to stop requiring preventable heroics as a standard operating procedure.
That means going beyond the moment.
It means hearing what the problem revealed.
Understanding the system that produced it.
Building enough trust for people to tell the truth about how the work is actually performed.
Executing changes that address the real conditions rather than the most convenient explanation.
Reinforcing the learning until better work becomes repeatable.
The HUBER Strategy™ remains the way we respond when the work gets messy.
Operational Intelligence is what we build from what the mess taught us.
The problem may be resolved, but our responsibility is not finished until the organization is wiser because it happened.
I Am Here for YOU.
Supporting Research
The ideas and framework in this article come from lived operational experience. The sources below are included for readers who want to explore independent research and guidance that reinforce several of the operational patterns discussed.
1. The difference between the prescribed process and the work people actually perform
Tresfon, J., Weggelaar-Jansen, A. M. J. W. M., van der Sijs, H., and colleagues. “Aligning Work-as-Imagined and Work-as-Done Using FRAM on a Hospital Ward: A Roadmap.” BMJ Open Quality, vol. 11, no. 4, 2022, e001992.
The study applied the human-factors concepts of “work-as-imagined” and “work-as-done” to identify discrepancies between a written procedure and frontline practice, then incorporated frontline knowledge into a redesigned process.
2. The effect of incomplete performance measures on behavior
Holmström, Bengt, and Paul Milgrom. “Multitask Principal-Agent Analyses: Incentive Contracts, Asset Ownership, and Job Design.” The Journal of Law, Economics, and Organization, vol. 7, special issue, 1991, pp. 24–52.
Holmström and Milgrom examine the difficulties created when organizations reward selected measurable activities while people remain responsible for other work that is harder to observe or quantify. The research supports the broader operational concern that emphasizing one measure can redirect effort away from other valuable responsibilities.
3. The relationship between psychological safety and learning behavior
Edmondson, Amy C. “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly, vol. 44, no. 2, 1999, pp. 350–383.
Edmondson’s field study of 51 manufacturing teams found that team psychological safety was associated with learning behavior and that learning behavior helped connect psychological safety with team performance.
4. AI’s ability to assist with analysis and repetitive work
Organisation for Economic Co-operation and Development. OECD Employment Outlook 2023: Artificial Intelligence, Job Quality and Inclusiveness. OECD Publishing, 2023.
Organisation for Economic Co-operation and Development. Governing with Artificial Intelligence: The State of Play and Way Forward in Core Government Functions. OECD Publishing, 2025.
OECD research describes AI’s capacity to process large amounts of data, assist analysis and decision-making, identify patterns, and automate or reshape some repetitive work. The same research emphasizes that results depend on complementary human skills, governance, data, infrastructure, and institutional conditions.
5. The importance of data quality, context, and validation in AI
U.S. Government Accountability Office. Fraud and Improper Payments: Data Quality and a Skilled Workforce Are Essential for Unlocking the Benefits of Artificial Intelligence. GAO-25-108412, 2025.
National Institute of Standards and Technology. Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile. NIST AI 600-1, 2024.
The Government Accountability Office uses the familiar phrase “garbage in, garbage out” when explaining that poor-quality data lead to poor AI results. NIST identifies risks including confidently presented false information and recommends attention to data provenance, quality, testing, source verification, and the context in which an AI system will be used.