One of the expensive realities of hiring is that a person can interview well, understand the right language, and still struggle to turn that understanding into daily ownership.
The employee was a property manager responsible for a mix of single-family and multifamily properties. The role also included supervising two on-site employees, managing current problems, maintaining the company’s records, and using those records to understand how we had solved similar problems before.
They interviewed well. We have a list of questions we generally use, and the people we hire are usually good at answering them. They know the language. They appear to understand our style of management, discipline, and ownership. You believe they get it.
This employee definitely got it—in the interview.
Then comes an infatuation phase. You think the employee is going to be great. The employee thinks the company is going to be great. Neither side has been tested against the daily reality of the role.
The record is part of the work
Property management produces recurring problems. A supply needs to be purchased. A repair has to be coordinated. An owner or resident needs an answer. The properties are not identical, so no procedure can anticipate every circumstance. But many new problems resemble something the company has already solved.
That is why the system of record matters. Purchase history, maintenance notes, accounting codes, vendor information, and previous decisions allow the next person to research what happened before. A good record keeps the organization from paying to solve the same problem again.
The employee had been shown the systems. We had a long training packet and a long training process. Then came on-the-job training, because no packet can contain every problem a property manager will encounter.
At some point, however, training has to become ownership. You have to hand over the work—including problems neither the employee nor the manager knows how to solve today—and trust the person to investigate, decide, document, and move forward.
Escalation can look like progress
The employee kept asking for help. At first, that seemed reasonable. New employees should ask questions, and working through real problems creates useful repetitions.
But much of what felt like training was actually the managerial staff solving the employee’s problems. The problem moved upward, someone else supplied the answer, and the record still was not updated.
Then the questions slowly stopped. We took the quiet as evidence that the work was happening. It was not.
Small incidents began to accumulate. Supplies were over-purchased because earlier orders had not been researched. Decisions that had already been made had to be made again. The employee sometimes did the work of the two people they supervised instead of supervising them, leaving other responsibilities untouched. The company could end up paying more than twice for work that should have been completed once.
Escalating a problem is not the same as taking ownership of it.
Ownership means researching the history, asking a clarifying question when necessary, making the decision at the appropriate level, and leaving the record better for the next person. It also means supervising the work without quietly absorbing every task yourself.
Leaders still have to manage the details
Leadership does not eliminate management. The details matter. If the record is incomplete, supplies are duplicated, employees are not supervised, or important work simply goes quiet, the leader cannot assume that empowerment is working.
I still have to train. I still have to give feedback. I also have to inspect enough of the work to know whether responsibility has actually transferred.
I did not resolve where “figure it out” ends and “we didn’t train them” begins.
That tension is real. Asking for help can be rational. Training can always be improved. At the same time, no training program can anticipate every future problem, and a role that requires judgment cannot succeed if every difficult decision returns to the manager.
Better paperwork is not the whole answer
We made our training documentation more robust. AI has made it easier to capture procedures, organize instructions, and preserve more of what the company has learned. The company became a little smarter on paper.
But documentation only works when someone values it enough to use it. A longer training packet cannot manufacture attention, judgment, or ownership. More paperwork may reduce avoidable errors, but it cannot guarantee the outcomes we want.
About four to six months into the relationship, the pattern was clear. I did not fire the employee. When a new problem arrived and the standard became unmistakable, the employee recognized that the role exceeded their current competency and chose to leave.
Learn earlier. Keep going.
This is not an unusual story. Leaders and direct reports will recognize themselves somewhere in it: the strong interview, the hopeful beginning, the repeated questions, the false quiet, the late discovery, and the expensive realization that responsibility never fully transferred.
It is not necessarily a failed endeavor. It is one that did not meet the expectations we brought into it.
The answer is not to stop trusting people or to pretend that better hiring will remove every mismatch. Improve the documentation. Make the training useful. Inspect the details. Distinguish questions that build capability from escalation that transfers ownership. Learn to recognize the warning signs earlier, because allowing the pattern to continue is expensive.
Take the lesson. Reduce the waste. Keep striving.
This is work I actually do. If you’re in that stretch, that’s a conversation I’m willing to have.
Working through a people decision?Start a conversation →