In my role leading the Solutions team at Onspring, I have the distinct honor of being one of our company’s primary storytellers. When your primary responsibility is helping clients piece together the various, individual aspects of their GRC programs—risk assessment software, compliance and control, and other solutions—into a compelling narrative about the overall health of the organization, you quickly realize that this analogy is apt.
A lot of fear comes from not being prepared, not having the correct support needed to fulfill and complete a job. The more it happens, the more FOMO creeps in and takes over, and that can become a truly destructive force in an office setting.
If you were old enough to ride a 10-speed or file taxes in the 80s, you probably have fond memories of mixtapes—a collection of favorite songs on a well-worn cassette that you listened to over…and over…and over again. We’re a long way from mixtapes in 2017, but the concept holds true: sometimes the good stuff just keeps getting better. As the year draws to a close, the Onspring team would like to offer our own mixtape of sorts: a collection of our most popular blog posts from 2017. We invite you to sit back, “press play” and enjoy these stories again (…and again…and again).
Too many decision makers purchase a tool based on the fact that it “can” automate GRC/other business processes, not on “how” it does it for your organization. Just like buying a volume maximizing shampoo will indeed clean your hair…beware the unintended consequences.
We live in an era of choice and flexibility, but sometimes the places where we need flexibility the most are the ones that remain painfully rigid. I hear this a lot from internal auditors—particularly those who work on small or mid-sized teams. Their frustration with hard-coded, “do-it-this-way” solutions seems to have reached an all-time high.
If your software provider is committed to keeping the product up to date and delivering new and valuable features, then your software implementation really should stand the test of time. But here’s the kicker: You have to take advantage of what’s available to you. Those new features from your vendor won’t do much good if you don’t incorporate them into your work. And when your team and processes evolve (as they always will), your software may need some fresh configuration to adapt to your changing needs.
We frequently meet with people who are ready to solve problems with new technology, but they’re struggling to assemble the right team to move the project forward. Building a solid project team can be tough, especially when multiple business functions are involved. However, I can’t overemphasize the importance of finding that “magic mix” of stakeholders. It can make all the difference between success and disappointment.