How to See What’s Really Happening

If the last chapter described what operational dysfunction costs, this chapter is about finding where it lives. Not in the abstract—in your day-to-day operation, in specific areas, with specific questions that surface specific problems.

Most PMC owners know when something is off. They’ve felt it. The “but” at the end of “things are running fine, but…” is always there: but we keep losing good people, but onboarding takes forever, but execution is inconsistent across properties, but resident issues continue to surface, but we’re spending a lot of time on legal or compliance issues that have escalated, but I’m still the bottleneck for too many decisions. The problem is that the “but” is vague. It points in a general direction without telling you where to dig.

An operational assessment replaces the vague sense that something is wrong with a specific understanding of what’s wrong, where, and why. It’s the difference between “we have a turnover problem” and “we have a knowledge documentation problem that shows up as a turnover problem because new hires can’t get the information they need, experienced staff spend their days searching for answers that should be instantly retrievable, and everyone across the portfolio is constantly reinventing the wheel—solving problems that have already been solved because nobody captured the solution.”

The first one feels overwhelming. The second is fixable.

Why most PMCs have never assessed their own operations

It’s not that operators don’t care. It’s that property management runs on momentum. There’s always a lease to sign, a maintenance request to handle, a resident issue to resolve, a vacancy to fill. The urgent consistently crowds out the important. Nobody has time to stop and assess the machine while the machine is running—and in property management, the machine never stops.

There’s also a structural challenge: most of the waste in a PMC’s operation isn’t visible in any single report or dashboard. It lives in the time your team spends searching for answers, the inconsistencies between how different managers handle the same situation, the workarounds people have built to compensate for tools that don’t work well together, and the institutional knowledge that exists only in the heads of your most experienced people.

There’s a version of this that’s particularly unsettling: the moment when you ask someone on your team a question you already know the answer to—and they give you a completely different answer, delivered with total confidence. It’s not that they’re being careless. They genuinely believe they’re right, because the information they were given, or the process they were taught, or the answer they found the last time they looked, was wrong or outdated or different from what the person at the next property was told. If you’ve used AI tools that occasionally produce “hallucinations”—confident, articulate answers that happen to be completely and provably wrong—you’ll recognize the feeling.

The difference is that when your team hallucinates a policy or a process, the consequences land on a real resident, a real lease, or a real compliance file. As Chapter 1 demonstrated, these costs don’t show up on a P&L. They show up in turnover rates, onboarding timelines, resident complaints, and the owner’s persistent feeling that the operation should be running better than it is.

The feeling is right. The diagnosis has just been missing.

The gap you can’t see from the top

Before we get to the framework, there’s something important to understand about why self-assessment—even thoughtful, honest self-assessment—has limits.

The owner’s view of the operation and the frontline’s experience are often strikingly different—not because anyone is lying, but because the people closest to the problems have learned to work around them instead of reporting them. Your property manager who spends twenty minutes finding a document that should take thirty seconds doesn’t report it as a problem because she doesn’t know it could be different. Your leasing agent who re-explains the same process to every new hire doesn’t flag it as a training gap because he’s always done it that way. Your maintenance coordinator who tracks vendor insurance expirations in a personal spreadsheet doesn’t mention it because the spreadsheet works fine—for her.

The dysfunction has been absorbed into the culture as normal. Your team has adapted so completely that the workarounds feel like the job. And because the workarounds keep things functional enough to get through the day, the structural problems underneath them stay invisible to leadership.

I’ve found that the most valuable conversations during an assessment aren’t with the owner. They’re with the property manager who’s been quietly holding things together with systems nobody else knows about, or the leasing agent who built a personal checklist because the official onboarding was “good luck, you’ll do great,” or the maintenance coordinator who knows that the after-hours emergency procedure in the handbook hasn’t matched reality for two years but never said anything because nobody asked.

These aren’t complaints. They’re operational intelligence that’s been sitting untapped because nobody created the conditions for it to surface.

Seven areas, one connected system

What follows is the framework I use for assessing property management operations. It examines seven interconnected areas—listed separately here, but in practice they overlap constantly. A knowledge problem is also a workflow problem is also a staffing problem. The value of looking at all seven is that you start to see the root causes underneath the symptoms, and you can identify which one to fix first for the biggest impact.

For each area, I’ve included the questions that matter most. Be honest with your answers. If you don’t know the answer, that’s itself an answer. And if you find yourself thinking “we sort of have that” or “we used to”—that’s a no. “Sort of” and “used to” don’t help the leasing agent who needs the answer at 4:30 on a Friday.

1. Knowledge and documentation

This is where the biggest hidden costs almost always live. It covers your written policies, standard operating procedures, training materials, and any system your team uses to find answers to recurring questions.

If your best property manager quit tomorrow, how much of what they know is written down and accessible to their replacement? Can a new hire find the answer to a common question—how to process an ESA request, how to handle an after-hours emergency, what the lease renewal timeline looks like—without asking a colleague? When was the last time anyone reviewed your SOPs to confirm they still match how the team actually does the work?

If the honest answer is “most of it is in people’s heads,” you’re carrying the institutional risk described in Chapter 1—and you’re paying for it in slow onboarding, inconsistent execution, and the repeated interruptions that burn out your experienced staff.

There’s a subtler version of this problem that’s worth mentioning: many PMCs do have documentation, but it’s written for a binder—not for the person who needs an answer right now. A 200-page operations manual organized by legal category isn’t a knowledge system. It’s a shelf decoration. The question isn’t whether documentation exists. It’s whether your team actually uses it when they need an answer. If they’d rather text a colleague than open the document, the document has failed—not because the content is wrong, but because the format doesn’t match how people actually look things up.

2. Software and tools

Most PMCs have accumulated their technology stack over years, one tool at a time, each solving the problem of the moment. The result is a collection of systems that weren’t chosen to work together and often don’t.

How many times per day does your team re-enter the same information into different systems? Are there features in your property management platform that you’re paying for but not using because nobody configured them or trained the team? Is your team using workarounds—personal spreadsheets, sticky notes, text messages—to compensate for gaps in your software? Could your current tools do more if someone actually set them up properly?

The issue is rarely that you need different software. It’s that the software you already have isn’t configured, integrated, or adopted in a way that serves the team. Most PMCs are operating at 40 to 60% utilization of their existing platforms.

3. Communication infrastructure

This covers two things: the physical systems your team uses to communicate (phone, internet, mobile devices) and the channels they use to exchange information (email, messaging apps, meetings, shared inboxes).

Do you know your total telecom spend across all properties—every phone line, every internet circuit, every mobile plan, every legacy copper line connected to an elevator or alarm panel? Can your team identify the right channel for each type of communication—where to report a maintenance emergency versus a routine update versus a policy question? When critical information needs to reach the full team, does it reliably get to everyone?

This area has a dual cost: the efficiency cost of scattered, unreliable communication, and the direct financial cost of telecom services that nobody has audited. As noted in Chapter 1, most PMCs find 25 to 40% waste when they finally inventory their communication infrastructure. It’s one of the most concrete findings an assessment produces.

4. Staffing and roles

This isn’t about whether you have enough people. It’s about whether the people you have are deployed in the right structure, with clear responsibilities, and without bottlenecks that force decisions to flow through one person who shouldn’t need to be involved.

How many decisions require the owner’s or senior leadership’s input that shouldn’t? Do job descriptions match what people actually spend their time doing? Do you have single points of failure—one person whose absence would meaningfully disrupt the operation? Are your property managers spending their time on management, or are they buried in tasks that should be handled by someone else?

A well-structured PMC should be able to operate smoothly for a week without the owner in the building. If it can’t, that’s a structural issue, not a work ethic issue.

5. Workflows and processes

Workflows are how work actually moves through your operation—from the moment a maintenance request comes in to the moment it’s resolved and closed, from the moment a resident gives notice to the moment the unit is turned and re-leased. Every PMC has these workflows. Very few have mapped them, measured them, or asked whether they’re actually efficient.

How many handoffs does a typical maintenance request go through before it’s resolved? Does your lease renewal process start early enough, or are you scrambling with 30-day notices? If you asked three different property managers how they handle a move-out inspection, would you get three different answers? Where does work get stuck—what are the recurring bottlenecks that everyone on the team knows about but nobody has fixed?

There’s a specific workflow gap that consumes leadership time more than almost anything else: the missing escalation framework. When a situation falls outside the routine, your team has three options—freeze and let it sit, guess and hope they’re right, or escalate it to a manager or the owner. Without a documented framework that defines what gets handled at the property level, what gets elevated to a regional, and what requires senior leadership’s direct involvement, everything floats upward by default. Escalating feels safer than deciding.

The result: senior leaders spend their days handling situations that should have been resolved two levels down, often after the issue has already compounded. A resident complaint about a delayed repair becomes a one-star review and a demand letter. A miscommunicated policy becomes a fair housing inquiry. A missed renewal window becomes a vacancy. None of these had to reach the owner’s desk. They got there because nobody had the framework to handle them correctly at the source.

That last question—about the bottlenecks everyone knows about—is one of the most revealing you can ask. Your team knows where the problems are. They’ve just stopped mentioning them.

6. Financial operations

Beyond telecom, there are areas where PMCs quietly lose money through operational inefficiency: late fees that aren’t charged consistently, vendor contracts that haven’t been renegotiated in years, maintenance spending that isn’t tracked against budget by property, or billing processes that create revenue leakage through timing gaps or manual errors.

Do you have a clear picture of maintenance spending per unit across your portfolio? Are your vendor contracts current, or are some auto-renewing without review? Is your team applying late fees, utility chargebacks, and other ancillary revenue consistently across all properties? How much time does your accounting team spend on manual reconciliation that could be automated or streamlined?

The telecom waste described in Chapter 1 is a financial operations finding. So is the discovery that vendor contracts across the portfolio haven’t been competitively bid in three years, or that ancillary revenue varies by 15% across properties because enforcement isn’t standardized.

7. Resident experience

The resident experience is where all the other areas converge. Slow maintenance response times, inconsistent communication, policies that vary between properties, staff who can’t answer basic questions—these aren’t resident experience problems. They’re operational problems that the resident feels.

What does your average maintenance response time look like, and do you actually measure it? When a resident calls with a question, does your team give a consistent answer regardless of who picks up the phone? Are your online reviews telling you something about operational quality that your internal metrics aren’t capturing? Do residents renew at the rate you’d expect, or are you losing people to frustrations that better operations would prevent?

And here’s a question that connects directly to the situation I described in the Introduction: does your team have a documented framework for handling resident complaints and escalations—including the ones that arrive as AI-generated legal demands? Because those are coming with increasing frequency, and the difference between a situation that resolves in a conversation and one that consumes weeks of staff time and legal fees is almost always whether a clear de-escalation process existed before the complaint arrived.

What the seven areas reveal together

The seven areas are listed separately but overlap constantly in practice. A knowledge documentation problem is also a workflow problem is also a staffing problem. The leasing agent who can’t find the pet policy (Area 1) is using a workaround spreadsheet (Area 2) and asking colleagues through a group text (Area 3) because nobody owns the process of keeping documentation current (Area 4) and the workflow for updating policies doesn’t exist (Area 5). The inconsistency that results shows up in the resident experience (Area 7) and the late fee revenue that varies by property (Area 6).

This interconnection is why assessing one area in isolation produces misleading results. The owner who sees a turnover problem and focuses only on compensation is looking at Area 4 (staffing) without seeing that the root cause lives in Area 1 (knowledge) and Area 5 (workflows). The owner who buys new software to solve efficiency problems is addressing Area 2 (tools) without realizing that the tools aren’t the bottleneck—the undocumented processes they’re supposed to support are.

The value of examining all seven areas together is seeing the root causes underneath the symptoms—and knowing which one to fix first for the biggest impact.

If you’re looking at all seven areas and wondering where to start: knowledge and documentation (Area 1) is the root cause of the most dysfunction in the most PMCs. It feeds directly into workflows (Area 5) and staffing (Area 4)—because undocumented knowledge means unstandardized workflows, which means roles that can’t function independently, which means everything escalates to the person who happens to know the answer. These three areas are where roughly 80% of operational dysfunction originates. Fix them and the downstream effects—resident experience, financial leakage, software underutilization—begin to improve on their own.

That said, if you need a quick, concrete win to build organizational momentum, communication infrastructure (Area 3) often produces the fastest financial result. A telecom audit is the kind of finding that pays for itself immediately and gives leadership confidence that the broader assessment is worth continuing.

And resident experience (Area 7) is the canary. If your online reviews, renewal rates, and complaint patterns are telling you something, they’re reflecting the operational reality underneath. You don’t fix the resident experience directly. You fix Areas 1 through 6, and the resident experience improves as a result.

Why your team won’t tell you what’s broken

If the seven-area framework gives you the questions to ask about your operation, the next question is: who do you ask?

The instinct is to assess from the top—the owner and senior leadership evaluating each area based on what they know. That’s a useful starting point, and it will surface the obvious gaps. But it will miss the most important ones, because the most important gaps are the ones leadership can’t see.

Your team knows where the problems are. They experience them every day. But they’re not telling you—and understanding why is essential to getting the real picture.

The trust deficit

Silence from your team is not agreement. It’s almost always a sign that people have learned their input doesn’t lead to change—so they’ve stopped offering it. Most PMCs have tried some form of employee feedback before: an annual survey, a town hall meeting, a suggestion box, a one-on-one check-in where someone asked, “how are things going?” And in most cases, the honest answer—even when it was offered—didn’t lead to visible change. Maybe the feedback went into a spreadsheet that nobody looked at. Maybe leadership acknowledged the concern and then got consumed by daily operations and never followed through.

The result is a trust deficit. Employees learn that giving feedback is a waste of their time. The next time you ask, you get polite non-answers, surface-level positivity, or silence. And leadership interprets that silence as contentment. The cycle reinforces itself: leadership thinks things are fine, so they don’t ask harder questions, so the real problems stay hidden, so nothing gets fixed, so employees become more disengaged, and the gap between perception and reality widens.

Fear of consequences

Even in companies with genuinely well-intentioned leadership, frontline staff often perceive risk in being honest. Will my hours get cut? Will I get assigned the difficult properties? Will this affect my review? Will the owner remember that I’m the one who complained about the new policy?

These fears don’t have to be grounded in reality to be effective. They just have to exist in the employee’s mind. And in an industry with high turnover and at-will employment, they almost always do. The power dynamic compounds the problem: your maintenance tech is not going to walk into the owner’s office and say, “the software you chose is making my job harder”—even if it’s true—because the owner chose the software, and criticizing that decision feels like criticizing the owner. The incentives for honest upward feedback are structurally broken in most organizations, and no amount of open-door policy changes that reality.

Normalization of dysfunction

This is perhaps the most insidious barrier. When a process has been broken for long enough, people stop seeing it as broken. They’ve built workarounds. They’ve adapted. The inefficiency becomes invisible because it’s just “how things work here.” The examples I described above—the twenty-minute document search, the re-explained process, the personal spreadsheet—aren’t reported as problems because the people living with them no longer recognize them as problems. They’re just the job.

The dysfunction has been absorbed into the culture as normal. And because the workarounds keep things functional enough to get through the day, the structural problems underneath them stay invisible to leadership.

How to actually hear what’s happening

When most companies think about employee feedback, they think about surveys—a set of questions with a 1-to-5 scale, distributed annually, with an aggregate score that goes into a report. Surveys have their place. They give you trends over time and benchmarkable numbers. But they don’t give you the thing you actually need, which is understanding.

A survey tells you that your team rates “communication” a 2.8 out of 5. A structured listening session tells you that your maintenance team doesn’t find out about lease renewals until the resident has already decided to leave, that your property managers use a group text thread because the official communication platform is too slow, and that nobody can find the updated pet policy because it was emailed six months ago and never added to the shared drive. One gives you a number. The other gives you three problems you can fix this month.

Structured listening sessions—small-group or one-on-one conversations with prepared questions, conducted in a way that feels safe for honest answers—are the highest-value feedback mechanism most PMCs aren’t using. They surface specific, actionable operational problems that no survey or town hall will ever reveal.

A few principles that make them work:

Small groups, no supervisors. Three to five people in the same role or department. The owner or direct supervisor should not be in the room. This is not optional. The presence of someone who controls your paycheck fundamentally changes what people are willing to say. If you’re the owner, delegate the sessions to someone the team trusts, or bring in an outside facilitator. People talk to outsiders in a way they simply won’t talk to their boss.

Ask about the work, not the feelings. Don’t ask, “how do you feel about working here?” That’s too broad and too personal. Instead, start by identifying the various parts of the jobs that the people in the room actually do—leasing, maintenance coordination, resident communications, accounting, administrative work, reporting, vendor management, whatever applies.

Then, for each of those areas, surface the real picture: where the friction is, what frustrates them, what workarounds they’ve built, what technical issues they deal with, where the disconnect is between the official process and how things actually get done, what they’d change if they could, what tasks they’d eliminate, what processes don’t work, what activities they don’t see the value or need for, what feels like unnecessary busywork, and what one or two or three things would make that part of their job easier.

The structure matters. By grounding the conversation in specific job functions rather than general satisfaction, you get answers that map directly to the seven assessment areas. And you often discover that the same friction point shows up across multiple functions—which tells you it’s a systemic issue, not a role-specific one.

The answers to “what would make this part of your job easier” are almost never extravagant. They’re things like “I wish I could find the pet policy without asking three people” or “I wish the move-out checklist was the same at every property” or “I wish someone would fix the printer.” Small, specific, fixable problems that nobody has addressed because nobody asked.

Listen for patterns. In any feedback session, you’ll hear a mix of legitimate operational concerns, personal frustrations, and occasional gripes. The skill is distinguishing between them. If one person says the software is slow, that might be their computer. If four people independently describe workarounds they’ve built because the software doesn’t support their actual workflow, that’s an operational problem. Patterns are the signal.

Hear past the frustration. There’s a difference between a valid concern and a complaint, and getting this distinction wrong in either direction is costly. If you dismiss valid concerns as complaints, you lose credibility with your team and miss real problems. If you treat every gripe as an action item, you’ll exhaust yourself chasing things that don’t matter.

A valid concern points to a systemic issue that affects the team’s ability to do their work. It usually comes with specifics—a process that’s broken, a tool that doesn’t work, a gap in communication or documentation. A complaint is typically personal, situational, or about preferences rather than function.

The discipline is to hear past the frustration—which is often real and legitimate—and find the operational signal underneath. When someone says, “this place is so disorganized,” that’s frustration. But if you ask, “can you give me a specific example?” and they describe spending thirty minutes trying to find the current lease template because there are four versions in different folders—now you have something actionable. The frustration was valid. The root cause is a knowledge management problem in Area 1. Strong leaders learn to extract the signal without being derailed by the emotion, and without dismissing the emotion either.

Closing the loop—the part that makes it work

This is where the vast majority of feedback initiatives die. You run the sessions. You hear real things. You have a list of problems. And then the daily demands of the operation take over, the list sits in a document somewhere, and nothing changes. Your team notices. And the next time you ask for feedback, you get nothing—because you just confirmed their belief that giving it is a waste of time.

Closing the loop is the entire game. Without it, listening sessions are worse than useless—they’re actively damaging, because they raise expectations you don’t meet.

Prioritize ruthlessly. You will hear more problems than you can fix at once. Rank them by impact and effort. Start with quick wins—a configuration change in your software, a document that needs to be updated and reshared, a communication channel that needs to be set up. They build momentum and prove the feedback loop is real.

Communicate back. Within a week of the sessions, tell your team what you heard. A summary of the themes. Then tell them what you’re going to act on first, what you’re planning to address later, and what you’ve decided not to change and why. The “and why” is critical. People can accept “no” if they understand the reasoning. What they can’t accept is silence.

Make the first change visible. Speed matters more than scope on the first fix. If your team told you the shared drive is a mess and nobody can find anything, reorganize it within two weeks and announce it. The first visible change is the deposit that earns you trust for the next round. It doesn’t have to be the biggest problem. It has to be the fastest proof that listening led to action.

Follow up and repeat. Check back in 60 to 90 days. Did the changes stick? Did they help? What’s next? This isn’t a one-time event. It’s a cadence. Over time, your team learns that honest feedback produces real change, and the quality of what they share improves dramatically. This is how you build a culture of continuous improvement rather than resigned acceptance.

Where to start

If you’ve read through the seven areas and found yourself answering “I don’t know” to more than a few questions, that’s not a failure. It’s a signal. Most PMC owners are too deep in daily operations to have visibility into how the full machine runs. Recognizing the gaps is the first step toward closing them.

If you want to start on your own, pick the area where you felt the most discomfort reading the questions. That’s your biggest gap. Spend a week paying attention to it—not trying to fix anything yet, just observing. Watch how information flows, where people get stuck, what questions keep getting asked. Write down what you see. The patterns will emerge fast.

Then talk to your team. Not in a town hall. Not in a survey. In small, structured conversations where the questions are specific and the supervisor isn’t in the room. What you hear will be more valuable than anything you can observe from the top—because your team has been living with these problems every day, and they’ve been waiting for someone to ask the right questions.

The assessment tells you what to fix and in what order. The next chapter shows you how to build the systems your operation needs—starting with the highest-leverage work and building momentum from there.