![]() |
|
||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||
|
Overview |
Iphen places a particular emphasis on the "as is" / "to be" analysis, requirements definition and rollout planning phases of its implementations. Here is why: Midsize businesses tend to vastly underestimate the complexity of data clean-ups and of migrations from legacy systems. By the time they have purchased and installed a system and migrated their data, their resources are depleted and momentum is lost. The executives who initiated the project abandon it to employees who can afford to spend time on details but who lack the authority to bring the project to completion. The implementation stalls. Technology has gobbled up all the allocated resources and time. Nothing is left for the two other pillars of software implementation success: Processes and People. Users are not properly trained, processes are not solidly defined and approved (or imposed), people opt-out (explicitly or implicitly). The "implementer" is gone and success does not materializes. None of this with Iphen. [back]
|
|
|||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||