Walk into most senior living organizations and you’ll find a strange mix. There’s a modern CRM next to a clinical platform that should have been retired years ago, a business intelligence tool next to a binder, and a laminated spreadsheet by the desk phone that somebody has been quietly maintaining since 2011.
That mix isn’t a failure of investment. It’s what happens when technology gets bought one problem at a time, over two decades, by different people solving different emergencies. Every purchase was defensible. The result usually isn’t.
The gap isn’t between operators who have technology and operators who don’t. It’s between operators who have systems and operators who have an operating system.
A resident exists as a prospect in one system, a responsible biller in another, a clinical record in a third, a participant in a fourth, a fall-risk profile in a fifth, a budget line in a sixth and a caregiver schedule driver in a seventh. One of those is usually a spreadsheet. At least one is just in somebody’s head. If those are seven unrelated representations of the same person, we didn’t build an operating system. We digitized seven silos.
Which brings up the argument the industry keeps having: best in class or best in suite? The strongest product in each category, or one platform that does everything adequately? Both camps have whole conferences. It isn’t a philosophy question. It’s about what you require from a technology partner and how much of your team’s attention you’ll spend compensating for what the product doesn’t do.
Two requirements are non-negotiable. Systems must integrate with the rest of the technology stack so work moves across the operation without someone carrying it. They must also deliver complete, current data into our own environment, allowing us to understand our own operation without asking permission.
The gap isn’t between operators who have technology and operators who don’t. It’s between operators who have systems and operators who have an operating system.
Miss the first and somebody pays for it. In duplicate entry. In opening a second system to confirm what the first one said. In the shadow spreadsheet that exists because two products can’t agree on what a move-in is. That bill never arrives labeled as a technology failure. It arrives as labor, delay and a team member who spent part of a shift being the integration.
Miss the second and something quieter happens. When the enterprise can’t see its own data, the only way to learn anything new is to ask the frontline to document more. We’ve been doing that for years, one perfectly defensible data point at a time. A lot of what we want to know is already produced through work people are doing anyway. It’s just trapped inside somebody’s product.
There’s real work in maintaining integrations, but it belongs in the price the way security and uptime do.
Best in class only becomes dangerous when every connection is a negotiation. Meet both requirements and the architecture debate mostly goes away. Fail either one and you aren’t best in class, whatever the feature comparison says. You’re a very good product that makes the enterprise worse.
Software does not improve care outcomes. People and operating processes do. Technology can make risk visible, remove friction and standardize execution. But cameras don’t reduce falls simply because they exist, and a CRM doesn’t improve occupancy because leads became digital.
The chain runs from technology to changed information and workflow, to changed human behavior, to outcomes. Skip the middle and you get the ROI claims nobody believes anymore. If every technology improved length of stay by months, the average length of stay in assisted living would be 40 years.
So, here’s one of ours. We’ve seen a meaningful association in our own communities between strong engagement platform usage and longer median length of stay. It’s an association, not proof of causation. The communities with the strongest adoption are typically the ones with the strongest leadership. Pretending otherwise is how this field ended up with so many numbers that don’t survive a second question.
Not all of this is finished at New Perspective. Some of it is fully operational, some is in progress and some is still a stack of barely legible notepad pages with sticky notes saying, “Do this” or “What does this even mean?”
But the direction is clear:
• The systems should carry the work.
• The data should land somewhere we own.
• The definitions should agree.
• A signal should reach the person who can act on it, and we should eventually know whether the action worked.
That’s what we mean by an operational intelligence platform. Parts of it are purchasable. The definitions and the follow-through are not, and that’s usually where it breaks.
The immature organization celebrates implementing something. The mature one talks about conversion, response time, staffing, aging in place and margin. The technology is simply how the work happens.
Nobody ever talks about adopting electricity.
