From Manual
to Mastery

The system was live.
The people were not ready.

A mid-size financial services organisation had completed a significant technology transformation — replacing three legacy finance systems with Oracle Financials Cloud, Oracle's integrated suite covering General Ledger, Accounts Payable, Accounts Receivable, and Fixed Assets. The implementation had taken eighteen months and significant investment. The go-live date was fixed and immovable.

When I came on board as Lead ID, there were 400 users across four locations and two countries who had never seen the system. There was no training programme in place — not a poor one, not an incomplete one. None at all. Oracle University's generic cloud training courses had been dismissed early in the project as too broad for the organisation's specific configured workflows — a correct assessment, but it had left a training vacuum with a four-month window to fill it.

The stakes were clear. Oracle Financials Cloud centralises all financial transaction processing — General Ledger journals, AP invoice processing, AR collections, and Fixed Asset depreciation. A user population that did not understand how to operate their specific role in the system on go-live day would produce incorrect financial data, stalled approval workflows, and a support desk overwhelmed with queries the organisation was not resourced to handle.

The system wasn't the problem.
The process was.

Before a single screen was storyboarded, I ran a two-week discovery phase. I reviewed 340 pages of Oracle Financials Cloud configuration documentation, functional design documents, and the organisation's chart of accounts and approval hierarchy. Only approximately 12% was instructionally usable — the rest was technical configuration detail relevant to the implementation team, not the end user.

More critically, I conducted structured interviews with 18 SMEs across all six user groups — Finance Business Partners, AP clerks, AR managers, procurement officers, General Ledger accountants, and Fixed Asset controllers. The question I was asking was not "what Oracle functionality do you need to train?" It was "what decisions do users in this role make every day, and what do they need to understand — about the business process, not just the system — to make those decisions correctly?"

What those conversations revealed changed the entire design strategy: the errors users were most likely to make were not about navigating Oracle's interface — they were about not understanding the underlying financial process the system was built to support. An AP clerk who did not understand the three-way match between a purchase order, goods receipt, and supplier invoice would misprocess invoices regardless of how well they could navigate the Payables dashboard. A GL accountant who did not understand the organisation's period-end close process would create journal entries that violated the approval hierarchy — not from ignorance of the system, but from ignorance of the business rule.

Six role-based pathways.
One integrated process view.

I restructured the entire programme around a process-first, system-second principle. Every pathway began with the business process — what the role does, the decisions it makes, and how its transactions connect to other roles within Oracle's integrated workflow — before introducing any Oracle Financials Cloud navigation.

The six role-based pathways mapped to Oracle Financials Cloud's core user groups:

Each pathway was built in four layers — a process explainer video establishing the business context before any system navigation; Show Me guided demonstrations of the Oracle Financials Cloud interface for each key transaction; Try Me simulations at three levels of support, where learners completed the same transaction independently in a sandboxed Oracle environment; and scenario-based assessments drawing directly from the error patterns the SME interviews had surfaced.

Process understanding first.
System navigation second.

Each role-based pathway followed the same four-stage sequence, designed to build process understanding before system confidence:

Four challenges.
Four resolutions.

100% certified.
Go-live approved. Support desk quiet.

The go-live itself was clean. The support desk query volume in the first 30 days — the standard measure of training effectiveness on an ERP implementation — was 62% lower than the equivalent period following the organisation's previous system rollout. This was the first Oracle Financials Cloud implementation in the organisation's history to achieve 100% pre-go-live user certification.

The readiness dashboard data told a more detailed story. The highest proficiency scores came from the AP and AR pathways — where the process-first design had most directly addressed the gaps the discovery phase had identified. The GL accountant pathway produced the lowest first-attempt scores — not because the training was weaker, but because the period-end close process in Oracle General Ledger Cloud was genuinely more complex than the equivalent legacy process, and the assessment scenarios reflected that complexity accurately.

The differentiated entry point — routing users based on a diagnostic assessment rather than treating all 400 as a uniform group — proved its value in the post-go-live data. The India-based processing team, who had received the extended process context module, performed within 4 percentage points of the UK-based team on the final assessments — a gap that would likely have been far wider without the differentiated approach.