Why Coupa?Watch Now
Coupa is a company of talkers, passionate about sharing tips, tricks and advice for improving finance and procurement and saving companies of all sizes time and money. But we’re not the only people with opinions and ideas. We’d love to hear from you so join the conversation!
- February 04, 2016
- Rob Bernshteyn
- Business Strategy
The cloud and Software-as-a-Service are making inroads with large enterprises because they promise better, faster, and a lower total cost of ownership for applying information technology to business problems that have never been adequately addressed. As these deployments grow in size, complexity and strategic importance, the risk of failure increases as well. People are wondering, will these new solutions fail as often and spectacularly as the on-premise solutions of past decades?
These concerns are well founded. Technology has changed, and we have a new chance to get it right. But what hasn’t changed are people, and we still need people to bring technology to life. The same issues that caused past technology failures could happen again. How can we ensure that these shiny new cloud deployments don't go the way of the old ones? Define, align and simplify.
1. Define success metrics
What we've learned from previous failed deployments is that no clear, measurable success criteria were set for the project. Completion of an implementation is not a measure of success in itself. Improved business processes and reduced deployment costs are nice but they’re too vague.
Instead, organizations should drive toward specific, measurable results such as reducing the cost to process an invoice by 50%, or speeding requisition to PO time to 3 days from 30, or saving $25 million on indirect spending in a year.
Specific business criteria such as these serve as the guiding principles for what you want to achieve. They help keep everyone on track during implementation and increase the likelihood that the new system will actually take.
2. Align and focus
Next, get all the constituents aligned around the success criteria. The company buying the software, the software vendor and the consultants who are doing the implementation each have their own priorities, but all three must have a shared vision of what success looks like. Find a way to align everyone’s interests with the agreed upon success criteria, and maybe even assign financial incentives to reaching them.
Then keep everyone’s eyes on the prize. Begin each project meeting with a reminder of what will be a successful outcome for everyone. On our projects, we've often gone as far as having the success criteria printed on the project collateral, and on the project teams’ mouse pads and desktop backgrounds.
Maintaining that kind of maniacal focus on the desired outcomes helps overcome showstoppers – the ringing of alarm bells that threaten to bring the project to a halt when challenges present themselves.
For example, I once worked on a global deployment of a procurement system targeted to save $50 million on indirect spend. Halfway through, someone sounded an alarm because Italian-language support wasn’t included in the contract, which it should have been. There were only a handful of users in Italy, and they all spoke English. The lack of support for Italian was an inconvenience, but wouldn’t have interfered with saving $50 million. The right answer was to continue the rollout to everyone else and circle back with support for Italian if needed.
3. Simplify your business processes
With past on-premise enterprise deployments, we customized everything so as to try and achieve a 100% feature-function line item match with the RFP. By doing that, we were coding existing business processes directly into the software, and adding a lot of complexity in the process. The difficulty and expense of changing those customizations made these systems rigid and unsuited for modern, dynamic ways of doing business. Don’t bring the old customization mindset into the new SaaS paradigm. Don’t be terminally unique.
SaaS is all about encoding crowdsourced best practices from all the companies using the platform, into the software. The code is not customizable for individual customers. However, the solution is highly configurable by end users and administrators, giving them flexibility, control and the ability to respond quickly to changing business conditions. You can do a lot with these approaches.
But how much should you do? The danger is that SaaS solutions are configurable to point where you can recreate the complexity of old and get yourself into a lot of trouble. Instead of looking to meet 100% of everyone’s feature requests, look at what really matters for the business. Stay focused on your success criteria, and why you subscribed to the solution in the first place—to make things easier.
A long–term commitment
Although SaaS solutions are faster and easier to integrate, an enterprise-wide deployment still represents a real investment in time, money and change management. It doesn’t require a capital expenditure, and it’s cloud so there’s the ability to cancel the subscription if it doesn’t work out, but with large scale deployments that’s not a comforting thought—or a realistic option.
Cloud solutions offer a once in a career opportunity to streamline business processes and generate huge business value, yet there remains a healthy trepidation that this new technology is unproven at scale and you might lose your job if the implementation fails. This time around, it’s often not the technology you need to worry about so much as the people. Establish clear and measureable success criteria. Get everyone aligned to them, and capitalize on the strengths of this new technology instead of trying to fit it into an outdated paradigm and you’ll be positioned for a big win.