Post-implementation enablement
The consultants have gone, the configuration moved after training was delivered, and the people running the process were not all in the room.
Training
Training Built Around the Way Your Finance Team Actually Works.
Not a course catalogue. A programme designed around your configuration, your process and the specific things your team needs to be able to do without help afterwards.
Why this exists
Standard training answers a question your team is not asking.
Product training teaches what the software can do. That is useful once. What a finance team actually needs, six months after go-live, is why their consolidation behaves the way it does, why their allocation produces that number, and what to do when the thing that always works does not.
Those questions can only be answered on your configuration. That is the whole proposition here — and it is why this sits separately from the two standard curricula.
When it is used
Seven situations, in rough order of how often we are asked.
New joiners and team refresh
A restructured group function, or one person who held the knowledge and has left. This is the cheapest possible insurance against that.
Close-cycle readiness
Walking the team through a full cycle on your own configuration before the cycle that counts.
Super-user and administrator capability
Building the internal capability that means most questions never leave the building.
Process changes after optimisation
When a remediation or optimisation has changed how something works, and the runbook no longer matches.
Training material and runbook refresh
Documentation that reflects the system as it is now, not as it was specified two years ago.
Targeted workshops on specific pain points
One half-day on the thing that goes wrong every period, rather than a week on everything.
How it works
Four things that make it different.
Built on your configuration, not a demo
We ask for access to your system, or a sanitised copy, and build the material around what you actually have. Generic product training is available from plenty of places and is not what this is.
Product-agnostic by design
This is not a course catalogue. It is centred on your configured process, your operating model and what your team needs to be able to do afterwards — whichever platforms that spans.
Delivered by practitioners
Sessions are run by people who design and deliver these solutions rather than by trainers working from a deck, which means questions about your specific design get answered in the room.
Scoped to outcomes
We start from what the team should be able to do unaided afterwards, and work backwards to the agenda. That is a different starting point from a topic list, and it produces a different day.
What you get
Material that stays useful after the session.
- Training-needs assessment before anything is designed
- A client-specific agenda, agreed in advance
- Configuration-aware training material built on your system
- Live workshops, on-site or remote
- Process walkthroughs and hands-on exercises
- Reference guides and job aids where scoped
- Recorded sessions where appropriate and permitted
- Typical duration
- Half-day workshops through multi-day programmes
- Scoped on audience, process breadth and how much tailoring the material needs. We agree this after the training-needs assessment rather than before it.
Related
Where this sits.
- Training overview — the standard Group Reporting and SAC curricula
- Group Reporting Health Check — where the real problem turns out to be the solution rather than the enablement
- SAC Health Check — the same, for a planning model
Next step
Tell us what the team should be able to do afterwards.
Start with the capability gap rather than a course outline. We will tell you honestly whether a workshop is the right answer, or whether the problem is in the solution design.