The Problem That Appears to Be Solved
Have you ever noticed how many problems inside a service company get resolved without anything actually changing?
A technician makes a mistake. A customer becomes frustrated. The service manager steps in, works through the situation, and finds a solution.
The customer is satisfied. The technician returns to work. The schedule continues.
From the outside, the problem has been handled.
And in many respects, it has.
But what happens when a similar situation occurs the following week?
Does the next technician know what to do?
Does the next manager make the same decision?
Is there an established standard to follow, or does the outcome depend on who happens to be involved?
These questions reveal a distinction that is easy to overlook.
A resolved customer problem is not necessarily a corrected operating problem.
A company can become exceptionally good at handling individual situations while continuing to reproduce the conditions that create them.
And sometimes the people most responsible for keeping the company running are also the people preventing its weaknesses from becoming visible.
Not because they intend to hide anything.
Because they are doing their jobs as they understand them.
Leadership Teaches Through Response
Consider a manager who recognizes a recurring problem.
Perhaps technicians handle warranty concerns differently. Maybe there is confusion about callbacks, customer communication, pricing exceptions, or who has authority to make a particular decision.
The manager approaches the owner for direction.
The response may sound familiar.
“Use your common sense.”
“That’s what I hired you for.”
“You should know how to handle that.”
To the owner, these words may communicate confidence in the manager’s ability.
To the manager, they may communicate something else.
I shouldn’t have brought this up.
I’m expected to already know.
Asking for direction makes me look incapable.
Neither interpretation automatically establishes the owner’s intention.
But the manager’s interpretation can influence what happens next.
The next time a similar issue arises, the manager may choose to handle it independently.
Then again.
Eventually, bringing problems forward may feel less productive than absorbing them.
This is how an organization can develop unwritten expectations that contradict its stated intentions.
An owner may genuinely believe in an open-door policy while repeated interactions teach managers that certain concerns are better kept to themselves.
A manager may believe they are demonstrating independence while gradually assuming responsibility for decisions that should have defined organizational boundaries.
Leadership does not only train through instruction. It trains through response.
What gets acknowledged, dismissed, supported, corrected, or ignored becomes part of the working experience of the people responsible for carrying out the company’s expectations.
Over time, those experiences influence conduct.
And conduct, repeated often enough, becomes the way the company operates.
Responsibility Without Consistent Authority
I once accepted a management position with a company that reminded me of an earlier stage of my own business.
I recognized the opportunity. I understood many of the challenges that came with growth, and I believed I could help the organization move beyond them.
Early in the engagement, I began noticing recurring problems that appeared different on the surface but shared the same underlying cause.
I approached the owner about establishing a consistent operating standard.
His response was that handling those problems was what he paid me to do.
So I began establishing the standard.
Within days, employees raised objections to expectations they had not previously been required to meet.
The owner then instructed me to make exceptions for particular people.
That experience revealed something important.
I had been given responsibility for improving performance, but the authority necessary to establish consistent expectations could be withdrawn when those expectations created discomfort.
The difficulty was not simply that employees resisted change.
Resistance is a normal possibility when expectations change.
The difficulty was that the organization had not established how those expectations would be introduced, supported, enforced, and maintained.
A manager cannot reliably build consistency when the standard changes according to who complains, who receives the complaint, or how the situation is interpreted.
And when leadership overrides a standard without establishing a clear reason or communicating the exception, it teaches something.
Employees may learn that expectations are negotiable.
Managers may learn that enforcing standards carries personal risk.
And owners may become frustrated when the same problems continue appearing.
Responsibility without dependable decision authority does not create accountability. It creates a contradiction that someone must continually manage.
When the Manager Becomes the Operating System
A capable manager does not simply stop working when the structure becomes difficult.
They adapt.
They resolve customer concerns.
They coach technicians.
They negotiate exceptions.
They protect developing employees from consequences they believe may be disproportionate.
They prepare new employees for expectations that are still changing.
They try to maintain relationships between people who may interpret the same situation differently.
Much of this work can be valuable.
An experienced manager should exercise judgment. They should recognize when an employee needs development rather than punishment. They should be capable of resolving routine problems without asking the owner for permission.
But there is a difference between managing within a dependable operating structure and compensating for the absence of one.
In the company I described, maintaining progress increasingly required managing the exceptions as carefully as managing the work itself.
The operation continued producing results.
But the consistency depended heavily on personal judgment, relationships, and the ability to absorb situations that the organization had not clearly addressed.
From the owner’s perspective, many problems appeared to be handled.
From the manager’s perspective, those same problems were recurring.
The owner might encounter one escalated incident.
The manager might have already handled several similar incidents before it reached that point.
Both could be looking at the same business and seeing different operating realities.
The better a manager becomes at absorbing operational friction, the less visible that friction may become to leadership.
That is the danger of confusing an effective manager with an effective operating system.
One is a person applying capability.
The other is a structure that allows capability to be developed, repeated, and sustained across people.
A company needs both.
The Hidden Cost: When Capability Walks Out the Door
The cost of this arrangement does not always appear immediately.
Customers may remain satisfied.
Revenue may grow.
Employees may continue producing.
Leadership may reasonably believe the organization is progressing.
And it may be.
But growth alone does not establish that the underlying operation is becoming more sustainable.
During my time in that management position, we achieved substantial growth.
At the same time, maintaining performance required continually navigating inconsistencies that should have been addressed through shared standards and decision authority.
That work consumed attention.
It required repeated conversations, individual accommodations, employee development, customer recovery, and constant judgment about which problems could safely be resolved without involving ownership.
Eventually, the cost became greater than I was willing to continue absorbing.
I left.
The important lesson is not that the company could no longer succeed without me.
A business is larger than any individual, and capable people can continue building after someone leaves.
The lesson is that much of the operating knowledge, informal coordination, and practical consistency had remained dependent on the person performing the work.
Some time later, a manager who succeeded me described encountering similar difficulties and asked how I had managed them.
That conversation reinforced the distinction.
The problem had not necessarily been eliminated by replacing the person responsible for managing it.
The next manager was encountering the same structural demands.
When a company depends on one person’s ability to interpret expectations, negotiate exceptions, develop employees, and protect performance, replacing that person does not automatically replace the capability.
If the operating standard exists primarily inside the manager, the company is borrowing that manager’s capability rather than building its own.
And when the manager leaves, much of that capability may leave with them.
This is one reason a business can continue growing while remaining operationally vulnerable.
The numbers may demonstrate progress.
They do not, by themselves, demonstrate that the progress can be sustained without the same individuals continually holding the structure together.
Common Sense Is Not a Shared Operating Standard
There is nothing wrong with expecting people to exercise judgment.
Experienced technicians and managers should be able to think independently, recognize unusual circumstances, and make appropriate decisions.
But independent judgment requires boundaries.
Consider a customer who calls shortly after a completed repair because the system is not cooling again.
Is the return visit a callback?
Does the company charge a diagnostic fee?
Does the answer depend on whether the new failure is related to the original repair?
Who determines that relationship?
What happens if the customer disagrees?
These are familiar situations in HVAC service operations.
They should not require the owner to personally decide every outcome.
But they do require established expectations.
Without them, one manager may waive a charge, another may collect it, and a third may leave the decision to the technician.
Each may believe they are acting in the company’s best interest.
Yet the customer experience, employee expectations, and financial results may differ.
That is where the phrase “common sense” becomes insufficient.
An owner with decades of experience may consider the appropriate decision obvious.
A technician with two years of experience may not recognize the same factors.
Even experienced managers may reasonably disagree when no shared decision criteria exist.
A useful standard does not eliminate professional judgment.
It establishes the conditions under which judgment should be exercised.
It identifies what is expected, who has authority, when an exception is appropriate, and when additional direction is required.
Standards should develop independent decision-makers, not eliminate independent thinking.
Higher Expectations Require More Than Higher Demands
There is another consequence of inconsistent leadership that deserves attention.
When a company introduces higher performance expectations, employees are being asked to change established behavior.
That change may be necessary.
But demanding a higher standard is not the same as developing the capability to meet it.
Consider a technician who has worked for years without consistent documentation requirements.
A new manager begins requiring complete service notes, clear customer explanations, photographs, and defined closeout procedures.
Those expectations may be entirely appropriate.
But if the company introduces them without explanation, training, reinforcement, or consistent leadership support, the technician may experience the change as additional demands rather than professional development.
Now consider what happens if certain employees are exempted from the requirements after complaining.
The company has taught two conflicting lessons.
The manager communicates that the standard matters.
Leadership demonstrates that it may not apply equally.
Employees notice.
And the next time a standard is introduced, the organization must overcome not only the difficulty of change but the credibility of its previous decisions.
Building higher performance requires more than announcing higher expectations.
Employees need to understand what is changing, why it matters, how success will be demonstrated, and what support is available.
Compensation, development opportunities, leadership conduct, and working conditions can also influence whether employees view those expectations as part of a worthwhile professional environment.
Not every new responsibility requires additional compensation.
But sustained performance requires a reasonable relationship between expectations, support, accountability, and the value employees receive from remaining with the organization.
You cannot build a higher-performing company simply by demanding higher performance. You must establish the conditions that make it possible and sustainable.
Correction Is Not the Same as Organizational Learning
Suppose a technician fails to explain a repair recommendation clearly.
The manager addresses the issue.
The technician is reminded to communicate better.
The immediate problem has been corrected.
But what does “communicate better” mean?
What information should the customer receive?
How should the technician explain the findings?
What options should be presented?
How does the manager determine whether the explanation met the company’s expectations?
And what happens when the same behavior continues?
Without those answers, correction remains dependent on interpretation.
One manager may expect a detailed explanation.
Another may consider a brief summary sufficient.
A technician may believe the conversation went well simply because the customer did not complain.
A meaningful operating standard makes the expected conduct understandable, teachable, observable, and correctable.
That does not mean every customer conversation should follow a rigid script.
It means the company has defined the elements of a complete professional interaction while allowing the technician to communicate naturally.
The same principle applies to management and ownership.
When a manager identifies a recurring problem, there should be an established way to determine whether the issue requires coaching, individual accountability, a policy clarification, or a structural correction.
Otherwise, the organization may continue correcting individual incidents without learning from the pattern.
Solving a problem restores the immediate operation. Learning from the problem improves the operation that follows.
Both responsibilities matter.
Turning Leadership Response Into an Operating Standard
Correcting this pattern does not require every decision to reach the owner.
It requires a dependable way for the organization to recognize recurring issues, establish direction, and reinforce expectations.
A practical approach can begin with five actions.
1. Notice
Identify recurring problems rather than treating every incident as unrelated.
A callback, incomplete service record, pricing exception, or customer communication problem may be isolated.
When similar issues continue appearing, examine whether they share an underlying cause.
The purpose is not to document every minor mistake.
It is to recognize patterns before they become emergencies.
2. Receive
Establish a reliable way for employees and managers to bring forward concerns.
A request for direction should not automatically be interpreted as incompetence.
Useful questions include:
- What happened?
- What have you already done?
- Has this occurred before?
- What decision or authority is missing?
- What would allow you to handle this consistently next time?
Being receptive does not mean accepting every recommendation.
It means giving legitimate concerns a dependable path toward evaluation and resolution.
3. Resolve
Address the immediate customer, employee, or operational need.
Managers need sufficient authority to make appropriate decisions within established boundaries.
Not every problem should become an owner-level decision.
But exceptions should have clear limits, and situations exceeding those limits need a defined escalation path.
4. Review
Determine what the incident reveals.
Was the standard missing?
Was the expectation unclear?
Was training inadequate?
Did the employee understand the standard but choose not to follow it?
Did the manager lack authority?
Or did the existing process fail to account for the situation?
Different causes require different responses.
Not every mistake is a training problem.
Not every inconsistency is a leadership failure.
And not every recurring problem requires another written procedure.
The objective is to identify what actually needs correction.
5. Reinforce
When a problem reveals the need for a change, the organization must carry that change into everyday conduct.
Communicate the expectation.
Provide the necessary training.
Establish decision authority.
Observe whether the expected behavior occurs.
Correct deviations consistently.
And when an employee repeatedly disregards a clear, reasonable, and properly supported standard, apply appropriate individual accountability.
The standard must survive beyond the meeting, the complaint, and the person who introduced it.
Otherwise, the company has created another temporary correction rather than a sustainable operating practice.
Leadership Must Be Accessible Without Becoming the Bottleneck
An owner does not need to personally resolve every concern.
Constant interruption is not the same as effective leadership.
But someone with sufficient authority must be available to address recurring operating problems, unresolved decisions, and concerns that exceed a manager’s established authority.
In a smaller HVAC company, that person may be the owner.
In a larger operation, it may be a general manager, operations director, or another designated leader.
The title is less important than the responsibility.
People need to know where unresolved concerns belong.
They need to know how decisions will be made.
And they need to know that raising a legitimate issue will not automatically damage their credibility.
An organization cannot expect managers to develop independent judgment while discouraging them from seeking the direction necessary to exercise it.
Nor should managers continually escalate routine decisions that fall within their established responsibility.
The objective is a balance: clear authority, dependable communication, appropriate accountability, and visibility into recurring patterns.
The goal is not to bring more problems to the owner. It is to make recurring problems visible without requiring them to become emergencies.
What Is Your Organization Teaching?
Consider the next time a manager approaches you with a recurring concern.
Or the next time a technician questions an expectation.
Or the next time a customer complaint reaches your desk after several people have already attempted to resolve it.
Before deciding who should have handled the situation differently, examine what the organization has actually established.
Was there a clear standard?
Was it understood?
Did the person have the authority to act?
Was the expectation applied consistently?
Had the problem occurred before?
And what did the response teach everyone involved about what they should do next time?
These questions do not remove individual responsibility.
They help establish where responsibility belongs.
A company does not operate only according to what leadership says it expects.
It also operates according to what leadership repeatedly demonstrates, reinforces, permits, and corrects.
Those responses become part of the organization’s working standards, whether anyone intended them to or not.
Every response from leadership teaches something. The question is whether it teaches the behavior the organization actually needs.
Performance Architecture Systems (PAS) examines how leadership conduct, communication standards, technician development, and field execution work together to create repeatable HVAC company performance.
Related PAS reading: “Why HVAC Training Doesn’t Become Behavior” and “Your Technicians Aren’t Inconsistent. Your Standards Are.”