Compliance Monster Hunting: Finale
We’re almost at the end of our Compliance Monster hunt, and I have to admit: I wasn’t totally ready for everything that’s happened along the way. We had some close calls with Mr. Snap, Tedium, and the Spreadsheet Eater, but after the events of last week—when Malaise actually wormed her way into our blog—I’ve been wondering if this endeavor is worth the danger.

Sure, we’ve given them cute names, but we’re talking about monsters here: cruel, powerful, inhuman forces that can take down entire workforce compliance programs. An encounter with a Compliance Monster could precipitate a regulatory enforcement action, lawsuit, or damaged reputation—and it could sap you of your will to do your job. These creatures are big, scary, and complicated. Is it possible that messing with them only causes more problems?

That’s exactly what this week’s Compliance Monster wants you to think.
Good thing we’re a few steps ahead of him.
The Compliance Monsters are back, and they’re more fearsome than ever. If you’ve felt a chill walking by that abandoned office full of paperwork, or if you’ve been editing a spreadsheet and the lights have suddenly started to flicker, you’d better beware. Mr. Snap, the Obfusticator, Malaise, the Spreadsheet Eater, Tedium, and That Which Shall Not Be Named have returned to their old haunts, and our intel suggests they’re more fearsome this year than ever before.
But so are we. And this time, we’re fighting back. Join Compli’s monster-hunting squad as we track the Compliance Monsters down and drive them away for good. Throughout October, we’ll show you how to eradicate these creatures one by one.

The Obfusticator is That Which Shall Not Be Named, hiding in plain sight.
That’s nothing to fear. It’s something to embrace.
Don’t let your CMS turn into a monster. Bring it out into the open and give it some love, and it will love your organization right back.