Insights / Oracle EPM Planning

Common mistakes in system implementation

A successful planning system implementation depends on more than configuring the software. Early decisions about the model, project approach, implementation team and requirements shape the result. These are six common pitfalls to consider before the work begins.

01

Treating the system like an upgraded spreadsheet

A planning system and a spreadsheet are different tools, built for different ways of working. Reproducing every existing spreadsheet rule in the new system can create a model that is cumbersome, slow and difficult to maintain. Use the move to rethink the process, not just relocate it.

Read more about the differences between Excel and a planning system.

02

Adding detail just because you can

A planning system can store far more detail than Excel. That does not mean every possible detail belongs in the model. Excessive granularity adds operational complexity, slows the process and makes the system harder for people to use. Model the level of detail the business needs, not the maximum the software allows.

03

Choosing the wrong project approach

When the project allows it, an agile, iterative approach helps refine the solution as the team learns. This can improve accuracy, shorten delivery time and reduce costs. A long waterfall project may postpone feedback until late in the process, when changes are more expensive.

04

Choosing a provider based on past reputation

A company's past experience does not guarantee that the team assigned to your project today has the same expertise. Professionals move between roles and companies, so ask who will work on the project and what hands-on EPM experience they have in the relevant role. ERP implementation expertise does not necessarily mean EPM expertise, and EPM itself includes distinct specialties, such as financial consolidation and budgeting.

Learn about my experience and approach to planning projects.

05

Outsourcing requirements analysis unnecessarily

In most cases, a separate firm is not needed to define and analyze requirements. It can significantly increase project costs and add complexity. If the specification is written without deep knowledge of the chosen system, it may not reflect what can actually be implemented and may need to be rewritten. Have the analysis and design led by someone who knows both the specific system and the organization's business requirements.

06

Choosing a system that does not fit your needs

Choosing a planning system involves many considerations. Without a deep understanding of the market and how it changes, it can be hard to tell systems apart and identify the right fit for your organization. Recommendations from other customers and online research can help, but they cannot replace an assessment of your own needs and how well the system meets them.

Why Oracle?

Implementing a planning system is a strategic initiative.

When done well, it changes how the organization makes decisions.