D365 F&O Training, Adoption and Change Management: the part that decides whether go-live is a success
Introduction: I’ve seen “perfect” D365 F&O projects fail anyway
I’ve watched technically excellent delivery teams miss a D365 Finance and Operations go-live.
Not because of X++.
Not because of performance.
Not because the chart of accounts was “too complex” (it usually is, but still).
It failed because the business wasn’t ready. Users didn’t understand what was changing, didn’t trust the new process, and didn’t have the right training at the right time. The project team had a training approach in their heads, but not a documented plan anyone could execute consistently. And a handful of key people were so overloaded they became the project’s single point of failure.
Microsoft’s own FastTrack guidance opens with the uncomfortable truth: “If you build it, they will use it” is a myth. Change is hard, and resistance is normal.
This article is a detailed, practical playbook for training, adoption and change management in D365 F&O programmes, based on the Microsoft FastTrack best practices, plus our project experience.
Why training fails in D365 F&O (even when “we’ve got a plan”)
The failure mode is painfully predictable:
- The team can describe the training strategy, but can’t produce a complete training and adoption plan that covers:
• who will be trained
• how training will be delivered (approach and format)
• what training content will be developed
• who owns content and delivery
• which environments will be used (and the logistics)
• how the plan fits the project timeline - Critical roles exist on paper, but in reality are overloaded or combined in a way that creates bottlenecks (typically PM, Solution Architect, Functional Leads and the one brave person who “knows security”). When things get busy, adoption work is the first thing to slip. It always does.
FastTrack’s “Journey” framing is useful here: manage the change, involve the user, build the foundation, create a communication plan, develop training materials, market internally. Training is not one activity at the end - it’s a thread through the whole programme.
The non-negotiables: roles and ownership (stop overloading the same humans)
Before you build a training plan, you need clarity on who owns what.
At minimum, D365 F&O projects should explicitly identify and document responsibilities for roles like:
- Executive Sponsor
- Customer Project Manager
- Technical Architect
- Solution Architect
- Functional Leads by business process area
- Data Migration Lead
- Testing Strategy Lead
- Integration Lead
- Security Lead
- Adoption / Change Management Lead
- Training Lead (sometimes combined with adoption, but be careful)
The point isn’t bureaucracy. The point is capacity and decision speed.
A simple rule of thumb that saves projects: If your Solution Architect is also acting as Adoption Lead, Training Content Author, UAT Triage, and Security Administrator… your “adoption plan” is basically hope with a logo on it.
What to do instead:
- Make adoption and training visible workstreams, with their own plan, deliverables, dates, and owners.
- Use a lightweight RACI for training and adoption deliverables (who is Responsible, Accountable, Consulted, Informed).
- Protect “maker time” for trainers and SMEs. Content doesn’t appear by magic the week before training.
FastTrack explicitly calls out that training planning is iterative and should start early, not after UAT.
Change management in D365 F&O projects: treat resistance as data, not drama
Users resist change for rational reasons: stability, status, power, habits, fear of the unknown.
FastTrack also highlights something most teams miss: resistance can be a good sign. It indicates engagement, forces validation of assumptions, and can be an early indicator of feasibility issues.
Common “resistance patterns” you will see in ERP programmes:
- Only game in town: “I’m the only one who knows spreadsheet X and I’m not giving it up”
- We are the world: “Our department is unique, ERP won’t work for us”
- The rules: “We can’t change because policy/union/audit”
- Analysis paralysis: “We need more analysis” (forever)
- The rumour mill: gaps in comms become fear and misinformation
Practical actions that actually work:
- Listen and understand objections (don’t “win” the meeting, learn from it)
- Focus on the why, not the how
- Remove barriers (access, time, clear decisions)
- Provide choice where possible (training formats, champion network)
- Demonstrate benefits with real scenarios
- Create hope and momentum with early wins
In D365 F&O terms, “demonstrate benefits” means showing:
- how a new posting process reduces rework
- how approvals become visible and auditable
- how inventory status becomes trustworthy
- how month-end closes faster because reconciliations aren’t spreadsheet archaeology
Make it real and specific, or it won’t land.
The training plan: what “good” looks like in D365 F&O
FastTrack’s training plan guidance can be summarised as: define who, what, when, where, how, and who will conduct it - then iterate.
Here’s how to build it in a way that survives real projects.
- Who will be trained (and how to group them)Don’t plan training by organisation chart. Plan it by role and task frequency.
Do:
• Group like users together
• Group like devices together (desktop users vs warehouse mobile scanning users)
Output:
• Role/persona list with headcount, location, device, and critical tasks
• Named participants (not “Finance team”) - What will they be trained on (tie it to processes, not menus)In D365 F&O, navigation training is cheap and short-lived. Process training is what sticks. FastTrack recommends gathering user requirements alongside business requirements and using business process flows with swim lanes.
Output:
• Process-based course catalogue (e.g., “Vendor invoice lifecycle”, “Sales order to cash”, “Warehouse outbound picking”, “Month-end close”)
• For each course: objectives, prerequisites, hands-on exercises, and success criteria - When will they be trained (work backwards from go-live)This is where most projects get caught out.
FastTrack explicitly says:
• allow sufficient time for training plan and content development in the project plan
• start training planning after design is completed
• update the plan continuously (it’s iterative)
• complete the content development plan before the first day of training delivery
• consider having content completed prior to UAT so documentation can be considered as part of UAT
A practical scheduling approach:
• Early: awareness + “what’s changing and why”
• Mid: role-based previews + champions training
• Late: end user training + hands-on labs (with production-like security)
• Post go-live: floor-walking, refreshers, new hire onboarding - Where will training be performed (and why the environment matters)Training environment selection is not an afterthought. It’s a performance and adoption decision.
FastTrack gives clear tier guidance based on concurrent users:
• Tier-2: 30-40 users
• Tier-3: 40-70 users
• Tier-4: 70-150 users
• Tier-5: 150+ users
Anti-pattern to avoid: "Let’s just use the Tier-2 UAT environment” even when you’re training 120 people.
If training is slow, unstable, or constantly reset, users learn one thing: the new system is unreliable. That perception is hard to undo. - Logistics: rooms, equipment, tools, capacity
A training plan must include logistics, not just dates.
FastTrack calls out:
• facility/tool used for training
• capacity of each training room/tool
• instructor equipment requirements
• participant equipment requirements
Output:
• A logistics plan (locations, VC links, sign-in, device readiness, test accounts, printers/scanners if relevant)
• A simple “day of training” runbook - Who will conduct training (and how to choose trainers)
Train-the-trainer can work brilliantly, but only if you pick the right trainers.
FastTrack’s selection criteria is refreshingly human:
• presentation skills
• empathy and patience
• attention to detail
• knowledge of the business process
Anti-pattern:
Selecting supervisors and managers purely because of seniority.
In practice, your best trainer is often:
• a respected SME who can explain “why we do it this way”
• a super user who’s calm under pressure
• a functional consultant who can translate system behaviour into business language - Security: train with production-like roles, or you’ll teach the wrong system
This one is so common it deserves its own heading.
FastTrack is clear:
• assign users the security role they will have in production during end user training
• don’t assign everyone System Administration for training
• don’t capture screenshots and videos with System Administration rights
Why it matters:
• Screens and available actions differ by role
• Excess security confuses users
• The “real” process is hidden behind duty/privilege boundaries
If you want adoption, your training must reflect reality. - Data for hands-on labs: seed it, duplicate it, protect it
Hands-on training fails when ten people try to post the same invoice number or pick the same sales order.
FastTrack recommends defining a strategy for training data and considering “seeding” or duplicating data, including use of the Data Task Automation tool.
Practical tips:
• Create training companies or legal entities if needed
• Provide pre-staged transactions per student or per group
• Reset data between sessions if exercises are destructive
• Keep a “golden dataset” that’s never touched during live delivery - Don’t exclude “small” roles (they’re often the highest risk)
Another common mistake: “Only one person does that, we’ll train them later.”
FastTrack’s pattern is the opposite:
• ensure sufficient training for all users
• for tiny groups, consider external training, on-the-job shadowing, or making specialty users business process owners so they’re close to design and configuration
In D365, the “tiny group” roles are often:
• credit control exceptions
• cash and bank specialist tasks
• intercompany settlement
• fixed asset specialists
• warehouse replenishment tuning
When these users struggle, the whole business feels it quickly. - Ongoing training: plan for new hires and continuous updates
Go-live training is not the end. It’s the start of a new operating model.
FastTrack recommends defining an ongoing strategy:
• choose training and content formats that can be repeated
• assign champions/content owners to maintain updates
• work with HR on training required per position
It also links ongoing training to continuous updates:
• release notes cadence
• Feature Management decisions
• rollout strategy that includes comms, training plans, and content development plans for each change
This is how you avoid “version shock” every time Microsoft ships an update.
Adoption: how to keep the business engaged (without spamming them)
Adoption doesn’t mean more emails. It means the right messages, repeated enough, from the right people.
FastTrack’s practical adoption ideas include:
- keep the initiative on employees’ radar with reminders, posters, launch events, how-to content
- gather feedback via polls, email, open-door sessions
- do informal lunch-and-learns with tips and adoption stories
- share success stories in-person and via short videos/newsletters
- provide ongoing training opportunities
- add recognition and even friendly competition to encourage engagement
A simple adoption cadence that works:
- Monthly sponsor update (why this matters, what’s next)
- Fortnightly “what’s changing” update per function (Finance, Procurement, Warehouse)
- Weekly champion sync (issues, rumours, feedback)
- Short “how-to” clips or cheat-sheets for top 10 tasks (especially just before go-live)
And yes - turning go-live into an event sounds cheesy… until you see how much momentum it creates. FastTrack literally recommends it.
A realistic timeline you can lift into your project plan
Here’s a practical backwards plan you can adapt (assumes a traditional big-bang go-live; adjust for phased rollouts).
T minus 16-12 weeks: build the foundation
- Confirm adoption lead + training lead ownership (and capacity)
- Identify personas/roles and training volumes
- Start comms: why change, what’s in it for each group
T minus 12-10 weeks: create the training plan (first iteration)
- Course catalogue, objectives, formats, prerequisites
- Trainer approach (internal, external, train-the-trainer)
- Environment choice (tier sizing)
T minus 10-6 weeks: develop content and labs
- Task recordings, job aids, slides, exercises
- Seed training data strategy
- Validate security roles for training users
T minus 6-4 weeks: pilot + refine
- Pilot with champions/super users
- Fix content gaps and confusing steps
- Validate logistics (devices, rooms, access)
T minus 4-1 weeks: deliver end user training
- Train with production-like security
- Reinforce “why” and new ways of working
- Capture feedback daily and adjust delivery
Go-live to +4 weeks: hypercare adoption
- Floor-walking and role-based office hours
- Micro refreshers on top pain points
- Publish “day 1” and “week 1” how-to packs
- Capture FAQs and update content owners for ongoing training
Patterns and anti-patterns (print this and stick it on a wall)
The difference between a smooth go-live and chaos is usually this list. // DrDynamics.co.uk
Recommended resources
- Training Plans and Content for your Fin Ops Project Part 1 Planning and Change Mgmt - TechTalk
- Training Plans and Content for your Fin Ops Project Part 2 The Training Plan - TechTalk
- Create Training Plans & Content for Finance & Operations Project Pt 3: Content Dev Plan - TechTalk
Closing: the blunt truth about D365 go-lives
D365 F&O programmes don’t usually fail because the system can’t do the job.
They fail because people can’t (yet).
If you want a calm go-live, treat training and adoption as first-class workstreams, not “nice-to-haves” you squeeze in after UAT. Build a documented plan, give it owners with real capacity, and design training around roles, processes, security, data, and environment realities - not good intentions.
If you want a quick self-assessment question for your steering group: If we had to run end user training next month, could we show the plan, the content owners, the training environment, the logistics, and the comms calendar… without making the solution architect cry?
If not, you’ve got time to fix it.