There is a moment that happens in a lot of growing property management companies. The owner is overwhelmed. So they hire. Then they’re still overwhelmed.
So they hire again. Eventually there are more people, more software, more communication, and somehow even more chaos.
It sounds backwards. But it makes sense when you look at the infrastructure.
Ten people and no rules
Imagine bringing ten people into an operation where nobody has clearly defined how information moves.
A work order comes in. Who sees it? Who decides if it’s urgent? Who contacts the tenant? Who contacts the vendor? Who approves the spend? Where is the documentation? Who follows up? When is the owner notified? What happens if the vendor doesn’t respond?
If those rules don’t exist, the new employee doesn’t solve the problem. They become another person asking someone else what to do.
That creates more communication. More handoffs. More questions. More places for information to get lost.
Hiring didn’t fail. The company hired people before designing the system those people were supposed to operate.
People are not the infrastructure
This is one of the biggest distinctions in how I think about property management operations.
People are not the infrastructure. Software is not the infrastructure.
The infrastructure is the system that connects people, processes, information, technology, automation, controls, and rules.
The people execute inside it. The software supports it. The automation moves it. The rules guide it. The controls protect it. And the information connects the decisions.
Why I don’t start with a hire
That’s why I don’t start an engagement by recommending another hire. I start by understanding the operation.
I want to know what each person actually does. Not their job description. What they actually do.
I want them to show me how they handle a renewal from beginning to end. How they handle a lead. How a move-in happens. How a move-out becomes a unit turn. How maintenance enters the company. How accounting receives information. How compliance gets tracked.
Where the spreadsheets are. Where the emails are. Where the information gets handed off. Where the owner has to step in.
Then we map it.
Only after we understand the operation can we decide what should be automated, what should be centralized, what should stay in existing software, what needs a rule, and what needs a human decision.
The goal isn’t fewer people
That is how you stop adding people to a problem that needs design.
The goal isn’t fewer people. The goal is people who can actually operate.
Because the best-run property management company isn’t the one with the biggest team. It’s the one where every person knows what happens next.