eBooks

Your PMIS platform should work the way you work, not require you to work the way it was designed. When software works the way end-users expect it to work, they tend to embrace the change. You can avoid being overwhelmed by software implementation if you implement it in a way that provides value early in the process. If your PMIS is flexible, you will be able to accomplish a long-term plan in as many phases as you need. Some organizations choose to go from zero to 100 without stopping. All gas, no brakes. But most will need to show incremental improvement and demonstrate value in stages. Kahua | www.kahua.com 02 Flexible - Capable of Bending Easily Without Breaking Being a flexible PMIS means your team does not have to learn new terminology to accomplish your company's standard business processes. You can continue to speak the same language. And you don't have to change those processes to accommodate the way your vendor created its software. No executive wants to continually hear that the software the company is paying for is "too hard to use" or "takes longer to complete." Having this kind of "flexibility" is a must! Staying consistent with your internal nomenclature is a major milestone in software acceptance, and having a PMIS that is configurable by the user organization should be a requirement. This means you can call it a Change Order Request, Request for Change, a Required Budget Adjustment or whatever you choose. In addition, the following should conform to your business out of the box without lengthy and costly customization: Multiple languages Multiple currencies Multiple cost code structures For a PMIS solution to avoid these pitfalls and stand the test of time, it must be flexible and agile. Your organization must adapt to external conditions that force change. Therefore, your PMIS must be able to do the same. Before considering examples, let's define the terms of flexible and agile. The vendor-built software does not fit the way the user organization works. The deployment is too complex and requires more work than the organization expected. The project fails to get buy-in at multiple levels. The "soft" side of technology – such as software or platform cloud data warehousing – will continue to evolve. The single overriding success factor to long-term viability of soft technology is adoption, especially when it comes to enterprise software technology, such as Kahua's PMIS platform. The cost or schedule of implementing a new technology is inconsequential if the technology isn't used. Software implementations fail for a few reasons:

• Cover