THE OPERATING CODE | 007 | EXPLORE FURTHER

WHAT SUCCESSFUL RESULTS CAN HIDE

A deeper discussion of invisible responsibility, capability, capacity, sacrifice, and organizational dependency.

Every position carries work nobody sees. That comes with responsibility.

There will be phone calls after hours, problems that have to be handled when the day was supposed to be over, weekends when something needs attention, and personal plans that occasionally have to change because responsibility does not always fit neatly inside a work schedule.

But there is a difference between sacrifice because circumstances require it and sacrifice because the operation depends on it.

Good people will step outside their normal responsibilities when the situation requires it. They will learn something they have not done before, make another phone call, find the missing material, make the trip, work the additional hours, and figure out how to protect the customer and produce the result. Most of that work may never be seen. That is okay. The result matters more than the recognition.

But when the same person repeatedly has to become the answer to whatever the organization is missing, leadership should pay attention. Being capable of solving a problem does not mean that person should become the permanent solution.

There is an important difference between capability and capacity. An organization may have someone capable of performing specialized work. That does not automatically mean the organization has built the capacity to repeatedly accept and perform that work.

Organizational capacity asks different questions. Do we have enough trained people? Do we understand the work before we commit to it? Do we have the material and equipment? Do we have the planning and support? Do we have coverage when specialized knowledge is unavailable? Can we perform the work repeatedly without depending on the same individual to rescue it?

A project can finish successfully because the organization was prepared and capable. It can also finish successfully because one or two people absorbed everything the organization was not prepared for. The customer may see the same successful result. The operating condition behind those results is completely different.

That is why the work nobody sees matters. It tells leadership what the result actually required.

If extraordinary effort was necessary because something truly unexpected happened, handle it, learn from it, and move on. But if extraordinary effort is required project after project, the organization should stop treating that effort as extraordinary. It has become part of the operating model.

That is when leadership needs to ask harder questions. Are we accepting work before we are ready? Are we depending too heavily on individual knowledge? Are responsibilities distributed correctly? Do field leaders have the support they need? Are we developing additional capability? Are successful results hiding weaknesses because strong people continue finding ways to overcome them?

Those questions are not about blame. They are about sustainability.

There is another cost to continually depending on the same people. Every time the organization uses someone to cover one gap, that person is not available somewhere else. The person capable of being a superintendent may be performing technician work. The person who should be managing several projects may be sourcing material. The person who should be developing other leaders may be continually pulled back into production.

The immediate problem gets solved, but the organization may be using its strongest people below the level where they could create the greatest value.

Sacrifice belongs in this conversation. There will be times when responsibility costs something personally. Sometimes the project needs another night. Sometimes the customer needs an answer. Sometimes something has to happen on a weekend. Sometimes you miss something you would rather not miss. That is part of carrying responsibility.

But sacrifice by itself is not leadership. The sacrifice has to accomplish something worthwhile: protect the customer, protect the result, help the team, solve the unexpected problem, build knowledge, create another capable person, improve the process, or prevent the next project from requiring the same sacrifice.

The goal should never be to build an organization where the most committed people continually prove their value by carrying more than everybody else. The goal is an organization where commitment is supported by preparation, people, systems, and shared responsibility.

The work nobody sees will always exist. Senior leadership should still understand what is happening underneath the successful result.

Was the organization prepared? Did the system work? Did the team have the capability and capacity required? Or did somebody simply refuse to let it fail?

Both can produce a successful project. Only one is consistently scalable.

The strongest person on the team should be an advantage. They should never become the operating plan.