When Greg Christensen started in the CMMS space back in the late ’90s, software tools were clunky, slow, and often misunderstood. Since then, he’s seen it all—from bloated rollouts that missed the mark to lean implementations that quietly transformed how teams work.

In this episode of Reliability 4.0, Greg shares what he’s learned after decades in maintenance and software, including insights from his podcast, CMMSradio. From business case building to leadership gaps, he breaks down what actually works when it comes to CMMS success—and why root cause analysis is more important than ever.

Quick Overview (TL;DR)

• Greg Christensen is the host of CMMSradio and a former CMMS company founder.
• Most CMMS failures stem from leadership gaps, weak training, and poor communication—not bad software.
• Success requires buy-in from the floor, milestone tracking, and clear expectations.
• RCA helps reliability teams go beyond data storage and into real problem-solving.
  

Table of Contents

• Greg’s Background and the Launch of CMMSradio
• Why Most CMMS Deployments Fail (and How to Avoid It)
• Building a Strong CMMS Business Case
• Where RCA Fits in the CMMS Conversation
• How EasyRCA Supports Smarter CMMS Strategies
  

Greg’s Background and the Launch of CMMSradio

Greg didn’t start in tech—he started in facilities. His early career gave him firsthand experience of what it’s like to troubleshoot breakdowns and chase downtime issues. That background shaped his later work in co-founding a CMMS company in the early 2000s.

In 2021, Greg launched CMMSradio, a podcast focused on practical conversations with planners, reliability managers, and vendors. His goal? Help teams stop making the same mistakes over and over again, and highlight what works in the real world.

Why Most CMMS Deployments Fail (and How to Avoid It)

Greg doesn’t sugarcoat it when it comes to CMMS deployments. In his experience, most failures don’t come down to software; they come down to people.

Here’s where things often go wrong:

• Leadership disappears after the kickoff.
• Technicians aren’t trained or consulted.
• There’s no feedback loop or ongoing support.
• Shiny features often take priority over real problems.
  

“It’s not just about turning it on and walking away,” Greg says. “You need milestones, champions, and actual wins you can show.”

And most importantly, the entire team—from operations to IT—needs to understand why the change matters.

Building a Strong CMMS Business Case

For any team considering a software switch, Greg offers this advice:

• Start with pain. What’s not working? What’s it costing you?
• Involve the front line. Let techs help design the future process because they know the gaps.
• Don’t fall in love with the demo. Ask the vendor what implementation actually looks like, and what support they’ll provide post-launch.
• Measure real outcomes. Focus on time saved, not just data stored.
  

Whether you’re weighing new tools or managing a rollout, Greg makes one thing clear: success hinges on clarity, ownership, and follow-through.

Where RCA Fits in the CMMS Conversation

Greg often asks: What’s the point of storing all this data if no one uses it?

That’s where root cause analysis comes in. It’s how you turn reactive firefighting into strategic decision-making. The CMMS should support RCA, not replace it.

“The CMMS is just the drawer,” Greg says. “The real value comes when RCA helps you figure out what’s in it, and what to do next.”

How EasyRCA Supports Smarter CMMS Strategies

At EasyRCA, we believe reliability isn’t just about data collection; it’s about decision clarity. That’s why our tools help teams perform RCAs quickly, visually, and in a way that integrates with CMMS workflows.

If you’re looking to pair your CMMS with smarter root cause tools, explore EasyRCA.

Curious how AI can support your team, not replace it? Explore EasyRCA’s AI features to see how we help engineers go deeper, faster.

Want to hear Greg’s full perspective on the future of AI in maintenance? Watch the full podcast episode on YouTube, or listen on Spotify and Apple Podcasts.

Further Reading:

• Continuous Improvement: How Justin R. Smith Keeps Reliability Moving at Americold
• AI in Reliability: How Allen Garcia is Blending Mechanical Engineering and Machine Learning at Baker Hughes