MSAMM
Back to course

Administering Cloud EPM: The Platform Beneath the Business Processes · Module 17 · The EPM Center of Excellence

What breaks

Lesson 194 of 201 · 2 min

Seven cases, and none of them is technical. One. "The project team left and took the capability with them." No standing function. The most common failure, and the one this module exists to prevent. Two. "Everything depends on one person." No deputies. A continuity risk equivalent to an untested backup. Three. "Governance is so heavy people work around it." Process heavier than risk. Four. "Nobody knows why this was configured this way." No decision log. Five. "The CoE was cut in a cost review." Could not demonstrate value. Module 14's data exists for this. Six. "The CoE and the functional teams are in conflict." The line was never drawn. Seven. "We have a steering committee that approves things and nobody does the work." A committee, not a CoE. EVERY FAILURE IN THIS MODULE IS ABOUT PEOPLE AND DECISIONS. Seventeen modules of configuration, and the last list has nothing in it

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 17 · The EPM Center of Excellence

  1. 1Why the last module and not the first
  2. 2What a Center of Excellence is
  3. 3The capability inventory
  4. 4Staffing and roles
  5. 5Standards and governance
  6. 6The operating model
  7. 7Making the case
  8. 8What breaks
  9. 9Lab: assess the capability and write the one-page proposal
What breaks — Administering Cloud EPM: The Platform Beneath the Business Processes — MSAMM