Skip to content

A finance transformation roadmap names the preconditions, and the dates follow.

A roadmap of 6 phases with a quarter against each leaves out the preconditions, and those are what slip. Each phase starts once its precondition is met, with 1 person answerable for it.

A finance transformation roadmap lists what has to be true first, and the dates come from that list.

A finance transformation roadmap is the plan a multi-entity group writes when an IPO, an integration or an AI mandate changes how it closes. Constancia is an EPM consultancy. We write roadmaps around their preconditions, and the dates follow from them.

A roadmap of 6 phases with a quarter against each carries 6 dates and 0 preconditions. The board remembers those 6 dates, and the sponsor struggles to defend them when phase 2 starts late.

The phase 2 date might rely on 3 ERPs exporting at the same grain, and no one has checked. Written down as a precondition, that check becomes a task with an owner and a clear finish.

A multi-entity roadmap needs 5 preconditions in place before any date goes on it.

  1. 01

    1 set of entities, accounts and periods

    The group has agreed the entity list, the chart and the calendar that every process will read, and a named person owns each.

  2. 02

    1 owner for each definition

    Gross margin, headcount and revenue by customer each have a written definition and a person who would defend it to the auditor.

  3. 03

    The legacy consolidation's rules, read

    Someone on the team has sat through a close in HFM, BPC or the workbook and written down every rule it applies, including the 4 nobody remembers adding.

  4. 04

    Each ERP's export at a known grain

    Each of the 3 ERPs has been asked what it will release, at what level and in what format, and the answer is on file.

  5. 05

    A named person to sign each phase

    Each phase has a person in finance whose name goes on its completion, and that person has agreed to the precondition above it.

We write the dates last, in the order the 5 preconditions can be met, and the first date is the survey that tests them. A precondition with no name against it stays open on the roadmap until someone signs for it.

Dates slip on a roadmap because the precondition under them was never written down.

A phase 2 dated for the second quarter starts in the fourth because the third ERP exports at a different grain from the other 2. The roadmap never said the grains had to match. The problem arrives as a change order, and the sponsor has to explain it to the board.

The design document for the consolidation had 3 versions in the shared drive, and nobody on the programme could say which was current. The roadmap had a date for the design and no description of a finished design.

The build team built from the second version, and the auditor read the third.

A roadmap written at the budget round, before anyone has opened the consolidation, moves in month 4 when someone finally opens it. A roadmap written after the survey moves less, because the survey finds the third ERP in week 2.

In month 4, the board will ask why phase 2 slipped. A sponsor with written preconditions can name the one that failed and the person who owns it.

The data model sets the order of the phases, and the platform choice comes after it.

The first phase on a roadmap with preconditions is the survey that tests them. The survey covers the consolidation as it runs, each ERP's export and the owner of each definition.

The survey lists the preconditions that fail today, and that list becomes the roadmap.

The platform choice comes after the survey, because OneStream (EPM software) and Abacum (FP&A software) each reproduce the data model they are given. A platform chosen in phase 1, before the data model is read in phase 3, gets rebuilt in phase 5.

On a multi-entity roadmap, consolidation comes before planning because the plan reads the consolidated actuals. A plan built before the consolidation settles reads actuals that will change, and it needs a second planning phase once the consolidation lands.

The AI phase holds the board's mandate, and it comes last on the roadmap. The roadmap shows the board the 4 preconditions that sit before the AI phase.

A board funds the preconditions it can see. Shown only the AI date, the board asks in month 6 why no AI is live.

We write the roadmap and build it, so the roadmap has 1 author and 1 signature.

A roadmap passed from its writers to a separate build team has 2 authors and 1 signature. The build team learns the group's data model on the group's budget, and finds any assumed precondition during the build.

We write the roadmap after the survey, and the consultants who did the survey build what it describes. The people who tested the preconditions are the people held to them.

We fix the price of the build once the roadmap is written. A fixed price holds only when the preconditions were real.

Each phase on a roadmap should answer 1 question, what has to be true before it starts and who has confirmed it. Put to all 6 phases in 1 meeting, the question usually produces 2 answers and 4 actions.

See more on our

Subscribe on YouTube
  • Latest episode

    How an EPM implementation works, and why the software comes last

Every Sunday, 6am

The Sunday Close.

Our weekly newsletter on AI in finance.
Yours to enjoy with your Sunday morning coffee.

  • AI in finance observations from Alex (CEO) and Brad (COO)
  • Newest video from our YouTube channel
  • AI in finance trends we have spotted each week

Tell us the date you are working to.

The people who would do the work read every message and reply inside 2 working days.