.png)
When LinkedIn Changed FM Partners, It Rewrote the Contract to Make Proactive Maintenance a Requirement
LinkedIn's fault-detection program had a straightforward problem with its FM vendors: the technology was identifying issues proactively, but the FM team was still operating reactively based on the agreed-upon contracts. When a building issue surfaced on the FDD platform, it generated a work order that landed on an already full queue of reactive requests. From the FM team's perspective, the program wasn't making their job easier; it was making it bigger.
Andrew Knueppel of Athena Blue Global, who supports LinkedIn's engineering program, describes the FM sell as the hardest part of scaling FDD across LinkedIn's global portfolio. The operations team was easier to convince: FDD gave them visibility into where FM vendors were spending time and KPIs to hold them accountable.
When LinkedIn changed FM partners in North America, it used the contract transition as an opportunity to improve FM reliance on the FDD platform. The new agreement embedded proactive maintenance expectations directly: KPIs for proactive work order completion, comfort score, and energy waste, all tied to the fee-at-risk. The FM vendor's compensation is now partially contingent on hitting proactive performance targets, not just responding to reactive requests.
Contract changes and transitions are rare windows when expectations can be reset. Once a vendor is operating under an existing agreement, changing the terms is slow and adversarial. Getting proactive maintenance language into the contract before a vendor starts is significantly easier than retrofitting it afterward.
There's also a FDD implementation reality that LinkedIn had to set expectations around upfront. When FDD is first deployed, maintenance costs go up because the system surfaces issues that were previously invisible. The expectation needs to be set clearly that this is temporary. With time, and with a vendor team that knows how to act on the tool's outputs, the proactive work order volume should displace reactive work rather than add to it. LinkedIn is still working toward that equilibrium globally.
Register for the next Nexus Labs event.
Sign up for the newsletter to get 5 stories like this per week:
LinkedIn's fault-detection program had a straightforward problem with its FM vendors: the technology was identifying issues proactively, but the FM team was still operating reactively based on the agreed-upon contracts. When a building issue surfaced on the FDD platform, it generated a work order that landed on an already full queue of reactive requests. From the FM team's perspective, the program wasn't making their job easier; it was making it bigger.
Andrew Knueppel of Athena Blue Global, who supports LinkedIn's engineering program, describes the FM sell as the hardest part of scaling FDD across LinkedIn's global portfolio. The operations team was easier to convince: FDD gave them visibility into where FM vendors were spending time and KPIs to hold them accountable.
When LinkedIn changed FM partners in North America, it used the contract transition as an opportunity to improve FM reliance on the FDD platform. The new agreement embedded proactive maintenance expectations directly: KPIs for proactive work order completion, comfort score, and energy waste, all tied to the fee-at-risk. The FM vendor's compensation is now partially contingent on hitting proactive performance targets, not just responding to reactive requests.
Contract changes and transitions are rare windows when expectations can be reset. Once a vendor is operating under an existing agreement, changing the terms is slow and adversarial. Getting proactive maintenance language into the contract before a vendor starts is significantly easier than retrofitting it afterward.
There's also a FDD implementation reality that LinkedIn had to set expectations around upfront. When FDD is first deployed, maintenance costs go up because the system surfaces issues that were previously invisible. The expectation needs to be set clearly that this is temporary. With time, and with a vendor team that knows how to act on the tool's outputs, the proactive work order volume should displace reactive work rather than add to it. LinkedIn is still working toward that equilibrium globally.
Register for the next Nexus Labs event.
Sign up for the newsletter to get 5 stories like this per week:
This is a great piece!
I agree.