See the variance. Find the assets. Understand why.
That simple principle captures something we’ve spent a lot of time working to perfect: helping real estate finance leaders trace portfolio performance back to the buildings that drove it – and the people who know why.
When you own 10 or 20 buildings, understanding what is happening across your portfolio can be relatively straightforward. Senior executives may know every property personally. They know the building with the difficult tenant, the one undergoing renovations, the property manager struggling with expenses, and the market where concessions are increasing. When the numbers arrive, much of the context is already in their heads.
But something changes as the portfolio grows.
More buildings mean more markets, more funds, more property managers, more asset managers, more operating partners and more people making decisions every day. The organization gains expertise, but its executives inevitably lose proximity to the individual buildings.
And that creates an interesting information problem.
The people closest to each property still know what is happening. Leasing knows why occupancy slipped. Operations knows why repairs increased. Asset management knows why concessions changed. Finance sees the resulting variance.
The knowledge exists. It is simply distributed across more people, systems and organizations. And that’s when the numbers and the narrative can begin to separate.
A financial system might tell leadership that NOI for a fund is 4% below plan. But that isn’t really an explanation, because a portfolio variance doesn’t happen at the portfolio level. It happens in buildings.
Perhaps six properties out of 150 are responsible for most of the miss. Perhaps occupancy fell unexpectedly at two assets, concessions increased at another, a renovation took longer than expected, bad debt increased in one market, or repairs at a single property were materially above budget.
Suddenly, the important question isn’t simply, “Why did the portfolio miss plan?”
It’s “Which assets caused it?” And then, “What happened at those assets?”
That’s where the questions become more difficult. Was the problem operational or market driven? Was it expected? Is it temporary or structural? Who is responsible for addressing it? What are they doing? When should performance recover?
The answers often exist. But as portfolios grow, finding them becomes harder. They may be sitting in Yardi or MRI, spreadsheets, variance reports, emails, meeting notes, or inside the heads of property managers, asset managers, leasing teams and operating partners. Someone has to connect them.
This problem becomes particularly visible in executive, board and investor meetings.
An investor doesn’t experience any of the organizational complexity behind the number. They simply see that NOI missed plan and ask, “Why?”
And then they keep asking questions. Which properties drove it? How much did each contribute? What’s happening at those properties? What does management think caused it? What are we doing about it? What should we expect next quarter?
At that moment, an executive either has a defensible explanation or starts saying, “We’ll have to come back to you on that.”
This is why I think growing AUM creates a challenge that isn’t simply about managing more data. It’s not fully answered by throwing numbers at Claude. It’s about maintaining institutional understanding.
A CEO or CFO managing 300 buildings cannot personally know every property the way they might have when they managed 20. Nor should they have to. But they still need access to that understanding when it matters.
That means every important portfolio result should have a path back to its explanation:
Portfolio → Fund → Region or Asset Class → Asset → Financial Driver → Management Commentary → Action
Follow the number until you reach the buildings that created it. Then connect those buildings to the observations of the people who understand what happened there. And finally connect those explanations to what management is doing next.
This is what we increasingly believe good executive reporting should accomplish. Not simply presenting more information, or another dashboard showing that performance changed, but giving executives the ability to explain why it changed.
Because the real test of reporting isn’t whether an executive can see the number. It’s whether they can defend it when someone across the table starts asking difficult questions.
Growth shouldn’t mean losing touch with your buildings. The challenge is finding a way to preserve the asset-level understanding you had when the business was smaller, even when hundreds of buildings and thousands of people now stand between the executive and the front door.
See the variance. Find the assets. Understand why.
With 20 buildings, an executive might be able to do that personally.
With 300, your ERP has the numbers. Your people have the insight. We bring them together.
What do you see as the real challenge?
