‍
Every facility leader has seen some version of this. The rollout goes well. Training is completed, the dashboard looks good in the first review meeting, everyone nods along. A few months in, someone on the team is quietly back to keeping a spreadsheet on the side, just in case.
‍

Facilities teams don't need numbers to recognise the pattern. A new system gets implemented with real investment, real training, and real intent. Within months, people have quietly drifted back to the habits it was supposed to replace.
‍

So why do people go back to their old ways, even after the new system is in place?
‍

Most organisations know how to roll out technology. Knowing how to make the new behaviour stick once the initial push settles down is a different, harder problem. One useful way to look at this is as three layers stacked on top of each other: technology, behaviour, and the operating model underneath both. Most transformation efforts only really move the first layer, and the tool changes overnight. The other two move at a different pace entirely, because they depend on people actually changing how they work day to day, and on the organisation rewarding that change once it happens.
‍

The behaviour layer: people don't resist technology, they resist friction

Behavioural scientist BJ Fogg's model argues that people are far more likely to adopt behaviours that are easy to perform, and that even motivated people struggle to sustain behaviours that take unnecessary effort.
‍

Facilities management makes this easy to see. An engineer may already be moving between a CMMS, a BMS, emails, spreadsheets, and IoT dashboards just to understand what's happening with a single asset. Add another platform without simplifying that process, and you've added a screen rather than removed one. Add to that the pace of the job itself. Facilities decisions are often made under real time pressure, and when that pressure hits, people don't reach for something that takes more effort and feels unfamiliar, they reach for the workflow they already trust. That's exactly the condition under which Fogg's model predicts adoption breaks down, effort goes up right when someone has the least capacity to absorb it.
‍

Habits also don't change because of one training session. They change through repeated reinforcement, feedback, visibility, and recognition, over weeks and months. That's where supervisors and managers matter almost as much as the tool itself, because they're the ones who notice whether the new way of working is actually being used, and whether it's worth someone's while to keep using it. But that noticing only goes so far if nothing further up the chain is set up to reward it, which is where the second layer comes in.
‍

The operating model layer: people optimise for what gets measured

Even where the behaviour layer works, and supervisors are reinforcing the right habits on the ground, the layer underneath it, the operating model, usually stays untouched. Most legacy FM contracts still define success through planned maintenance completion, response times, and compliance rates, regardless of how well the day-to-day behaviour has actually shifted.
‍

Here's where it gets interesting. Say an asset shows early signs of trouble and modern, AI-native technology recommends acting on it ahead of the scheduled PPM. If the contract only pays out against three completed PPMs, not against failures avoided, the scheduled task usually wins, because it's the thing that shows up on a report and is easy to point to when bidding for the next contract. Flip it around, and the same problem shows up from the other side. If a team acts on the early warning instead of the routine PPM, and the asset holds up fine, there's nothing in the contract that credits them for it either. The PPM wasn't done, so the paperwork looks incomplete, even though the actual goal, the asset staying operational, was met. Either way, the thing that gets measured and paid is completion, not the outcome. That's exactly why smarter technology alone doesn't shift behaviour on its own, it needs the operating model to start recognising outcomes too, not just checklists.
‍

The cycle that keeps organisations stuck

The layers reinforce each other. If new technology adds effort, people fall back on old habits. If contracts keep paying for the same historical measures, there's little reason to change those habits either. When the expected benefits don't show up, organisations often conclude the technology failed. More often, only the first layer moved. Behaviour and the operating model stayed exactly where they were.
‍

Designing for the behaviour layer

Closing the distance between a new tool and a habit that actually holds means reducing the effort it takes to make a good decision, not adding to it. This is the direction platforms like Xempla have been leaning into, not as another system competing for attention, but as a layer that pulls fragmented inputs from BMS, CMMS, and IoT into one view, surfaces a recommendation where the pattern is clear, and lays out the full context where it isn't. For an engineer or supervisor, that can mean a single view showing exactly what matters to their role, prioritised, with a clear sense of where compliance stands, instead of five systems to check before making one call. Design the tool around the moment someone is actually in, under time pressure, and the newer workflow stops competing with the familiar one.
‍

Redefining what success looks like on paper

The operating model is slower to shift, because a contract can't be rewritten overnight, and no single team decides that on its own. Buildings are becoming more connected, while clients increasingly expect providers to demonstrate measurable outcomes rather than simply completed activity. In practice, that shift starts small: a supervisor flagging in a handover or review, the two or three calls that fell outside the schedule but paid off, and a client beginning to ask for that story alongside the checklist. Once outcomes like that are visible somewhere, even informally, they become easier to build into how a contract gets renewed or renegotiated down the line.
‍

Moving toward outcomes within the existing system

So how does that shift happen without waiting for contracts to change? A contract is really just the floor. There's still room to build on top of it, in which asset gets attention first, which early warning gets acted on, and that judgement, applied consistently, is exactly the kind of thing a standard compliance report never captures, even though it's often what a client remembers at renewal time.
‍

One approach we're exploring at Xempla starts from a simple observation: most monthly reports in soft services prove that activity happened, checklists filed, staff deployed, tickets closed, but rarely show whether that activity changed anything, or what happens differently the following month as a result. The reporting format we've been building sits alongside the usual activity reporting, it keeps the operational metrics a contract already asks for, but also begins to show where a decision changed an outcome, and what that decision means for the following month's plan.
‍

Where the evidence starts to matter

The contract itself doesn't move because of this. Procurement decides what gets scored and what gets rewarded, and that decision sits with the client, not with anything sitting underneath the work. What that evidence does is give someone something new to bring to that decision, whether that's a client asking harder questions mid-contract or a rebid on the table. Showing up with a working history of better calls made, and what they were worth, is a different starting point than showing up with a checklist, and it gives clients a stronger basis for conversations about rewarding outcomes, rather than activity alone.
‍

This is the same shift, just visible from the organisation's side instead of the individual's. An engineer only keeps making the better call if it's easy enough to make under pressure and someone notices when it pays off. An organisation only earns a contract that rewards outcomes if it can first show, consistently, that better outcomes are already happening.
‍

Buildings don't decide whether change succeeds. People do. And people rarely change because they're told to. They change when the new way of working becomes easier than the old one, and when there's finally something worth showing for making that choice. Technology can start the shift, but it only holds once behaviour and the operating model move with it.
‍

FAQs

Why do facilities management technology rollouts often fail to deliver expected results?

Most technology rollouts change the tool but not the behaviours or operating model around it. If day-to-day habits and organisational incentives remain the same, adoption often fades after the initial rollout, limiting the value the technology was expected to deliver.
‍

What is BJ Fogg's Behaviour Model, and how does it apply to facilities management?

BJ Fogg's Behaviour Model suggests that behaviour occurs when three elements come together: motivation, ability, and a prompt. In facilities management, new ways of working are more likely to stick when they're easy to perform, fit naturally into day-to-day workflows, and are consistently reinforced over time.
‍

Why do traditional FM contracts make it difficult to reward better operational decisions?

Many legacy FM contracts reward completed activity, such as planned preventive maintenance (PPM) completed on schedule, rather than outcomes like failures avoided or asset performance improved. As a result, teams can make better operational decisions without receiving formal recognition for the value those decisions create.
‍

Can technology alone solve change management challenges in facilities management?

No. Technology can make better decisions easier, but it cannot change procurement models, contract structures, or the incentives organisations operate under. Lasting change happens when technology, behaviour, and the operating model evolve together.
‍

How can FM providers move toward better outcomes without changing existing contracts?

FM providers can begin documenting the operational decisions that improved outcomes alongside standard compliance reporting. Over time, that evidence helps demonstrate the value of an outcome-focused approach, strengthening client conversations, contract reviews, and future rebids without requiring existing contracts to be rewritten.