Explain why training is a core BA responsibility and how it drives adoption and project success
Analyze a training audience using personas and a stakeholder matrix, and choose between train-the-trainer and direct end-user training
Develop user-focused training content: chunked, consistent, jargon-free, and visually supported
Select training modalities, set up and troubleshoot a training environment, and run engaging sessions
Handle difficult questions and resistance gracefully, and provide structured post-training support
Communicate new features and changes through the right content types and channels
Section 1
Training Is a BA Job
Here is a truth that surprises new BAs: you can gather perfect requirements, design a beautiful process, and pass every test, and the project will still fail if nobody learns to use the thing. Training is where the solution meets its users, and on most Salesforce projects, the BA is the trainer.
Why training matters in the project lifecycle:
It ensures end users and stakeholders can effectively use the solution
It reduces project risk by minimizing knowledge gaps
It fosters user adoption and maximizes return on investment
It ensures stakeholders can independently manage the solution after the project ends
It mitigates fears and builds confidence in the new solution
That last point deserves emphasis. A new system is frightening to many people: it threatens their competence at a job they were good at yesterday. Training is not just information transfer; it is confidence transfer. (Module 15 explores the deeper change-management side of this.)
And why the BA specifically? Because BAs are critical in translating technical details into user-friendly content, and their understanding of both business needs and system functionality makes them the natural bridge for knowledge transfer: creating detailed training documents and leading the sessions that walk users through them. You have spent the whole project learning what users need and why the solution answers it. Nobody else in the room can teach it with your context.
Section 2
Training Preparation
Preparation is most of training. The deck's own facilitator materials devote more time to preparation than to delivery, and that ratio is correct.
Understand Your Audience
Four questions shape everything downstream:
Who are you training? Knowing who will be in the session determines which training style and delivery method the group will learn from best.
What are their roles? End users, admins, stakeholders: define roles and expectations, and use them in examples and role-playing activities.
What are their skill levels? Use persona mapping to understand what each participant brings: beginners, advanced users, technical staff, non-technical staff.
How should content be delivered? Choose the delivery approach (modalities below) based on the audience, and frame all communication within the context of participants' roles.
Train-the-Trainer vs. Direct End-User Training
A strategic choice you will make on nearly every project:
Direct user training teaches end users yourself. Pros: the most effective knowledge transfer, with immediate clarification and feedback. Cons: resource-intensive, requires scheduling alignment, and scales poorly for large user groups.
Train-the-Trainer (TTT) teaches a select group who become trainers themselves. Pros: builds deep understanding in a subset of users, spreads knowledge across the organization, and cultivates solution advocates who remain after the project ends. Cons: potential for knowledge dilution, dependence on the trainers' capability and commitment, and an extra step in the chain.
Many consulting teams favor TTT for its strategic, scalable nature: it leaves the client self-sufficient, which is the real goal of enablement. Choose direct training when the group is small, the change is high-risk, or no credible internal trainers exist. Choose TTT when scale, sustainability, and internal ownership matter most: which is often.
The Training Stakeholder Matrix
Before building any content, map who needs what. Build a simple matrix: each audience group, their role in the new solution, what they must be able to do on day one, their current skill level, and the depth of training they need. This is your Module 7 security matrix's friendlier sibling, and it prevents both over-training (wasting a room full of executives on field-level detail) and under-training (handing complex admin duties to someone who got a one-hour overview).
Practice Exercise: Build a Training Persona
The source curriculum includes a full persona worksheet for exactly this purpose. Work through it for a typical user on any project you can imagine (real or practice):
Persona overview: a representative name; role (end user, system administrator, project manager); department or function; experience level (beginner, intermediate, advanced); technical proficiency (low, medium, high).
Background: their primary job responsibilities; typical daily tasks and workflows; pain points (common challenges and frustrations in their role); motivations (what drives them, and what they hope to achieve).
Training needs: skill gaps the training must address; tools and systems they must become proficient in; processes they need to understand or improve.
Learning preferences: preferred learning style (visual, hands-on, lecture-based); engagement methods that will work for them (interactive activities, real-world examples, quizzes); and barriers to learning (limited time, resistance to change).
Training objectives: clear, measurable goals for what this persona should be able to do after training, and the tangible outcomes the training should achieve for them.
Notice the shape of that last section: measurable objectives and outcomes. Training is a deliverable like any other, and "attendees felt good" is not an acceptance criterion. "A volunteer coordinator can create an event, add shifts, and confirm signups without assistance" is.
Section 3
Developing Training Content
Five best practices govern user-focused training materials:
1. Understand user personas. Tailor content to specific roles, grounded in their pain points, daily tasks, and technical proficiency (the worksheet above).
2. Chunk the content. Break complex information into smaller, digestible parts, in modular sections that can be learned independently. Nobody absorbs a ninety-minute wall of features; everybody can absorb "creating a record," then "updating a record," then "running your report."
3. Build in interactivity. Incorporate quizzes, exercises, and scenario-based learning to reinforce concepts and maintain engagement. Interactive, role-based scenarios make content relatable: train the intake team on their intake process, not a generic one.
4. Keep design consistent. All materials share a consistent format, structure, and tone; use templates for guides, slides, and handouts. Consistency lowers cognitive load: learners spend attention on content, not on decoding a new layout per page.
5. Use user-centric language. Avoid jargon unless necessary, and focus on how the information benefits the user directly.
The Rewrite Exercise
The source curriculum teaches user-centric language with a wonderful exercise: take a technical passage and rewrite it for humans. Its worked example, verbatim in spirit:
Technical passage: "To achieve optimal polymerization during the synthesis…
Technical passage: "To achieve optimal polymerization during the synthesis of polyethylene, it is crucial to maintain the reactor temperature at precisely 180°C. Deviations from this temperature can result in suboptimal chain growth and molecular weight distribution, leading to material with inconsistent properties. Additionally, the introduction of a Ziegler-Natta catalyst at a controlled rate is essential for ensuring the desired polymer architecture."
User-friendly rewrite: "Imagine you're baking cookies, but instead of…
User-friendly rewrite: "Imagine you're baking cookies, but instead of cookies, you're making plastic! You need the oven at exactly the right temperature, 180 degrees Celsius, so your plastic 'dough' comes out just right. If the oven's too hot or too cold, your plastic won't be as strong or stretchy as it should be. And just like adding the right amount of baking soda to cookies, you need to add a special ingredient (called a catalyst) very carefully. Too much or too little, and your plastic won't be as smooth and shiny as you want."
The techniques on display: an analogy anchored in universal…
The techniques on display: an analogy anchored in universal experience (baking), consequences expressed in felt terms (strong, stretchy, smooth), and zero unexplained jargon (the one technical term, catalyst, arrives with a plain-language escort). Now practice it yourself: take any paragraph of Salesforce setup documentation and rewrite it for a brand-new user. Do this regularly; it is the single most transferable training skill.
Simplification, Visuals, and Guides
Simplification techniques: use analogies and metaphors to relate new concepts to familiar ideas; prioritize by relevance, introducing essential concepts before complexities.
Visual aids: infographics summarizing data and processes; flowcharts mapping steps and decision trees clarifying choices (your Module 5 skills, reused); screenshots with annotations for step-by-step instructions; short video clips demonstrating tasks more effectively than prose.
Step-by-step guides: numbered lists for procedures, bulleted lists for related tips; "Did you know?" and "Pro Tip" boxes highlighting shortcuts; and, critically, test the guide with a small group to find confusing steps before wide release. A guide nobody test-drove always has a step 7 that makes no sense.
Section 4
Training Modalities
Match the delivery format to the audience and content:
Modality
Pro
Con
In-person, synchronous
High engagement; a more captive audience
Costly and time-consuming
Hybrid/virtual, synchronous
Highly engaging and easy to record
Participants more easily distracted
Asynchronous recording
Self-paced; reference material forever
Can be boring; requires self-motivation
Training documentation
Self-paced, searchable, durable
Can be dry and unengaging
Hands-on demo
Learn directly in the system, live or recorded
Time-consuming for trainees
Help line / chat
On-demand assistance exactly when needed
Requires staffed resources
Real enablement plans mix modalities: a live kickoff session, recorded for the absent; a step-by-step guide for reference; office hours for the first weeks (see post-training support below). Self-paced formats accommodate different learning styles and can enhance retention, but they demand learner motivation; live formats deliver immediate clarification but cost coordination. Choose deliberately per audience, using your personas.
Section 5
Setting Up the Training Environment
An hour of setup prevents a session of chaos. The facilitator practice, recovered here in full:
Technical Setup
Identify and test every tool: the meeting platform (practice its breakout rooms and features in advance), the presentation deck (always use presentation mode), and the Salesforce environment itself.
Prepare demo logins: identify the user or users you will log in as for demos, and confirm the login and every training step works with those users' actual permissions. (Remember Module 7: what you can see as an admin is not what the trainee persona sees. Demo as the persona.)
Conduct a dry run before the session and fix issues beforehand.
Create a setup checklist so no step gets forgotten: audio and video tested, screen sharing verified, participant access confirmed.
Troubleshooting Common Issues
Problems will happen live. The prepared trainer has answers ready:
User access issues. Preempt: confirm all users have necessary permissions and credentials before the session, and check for firewall or network restrictions. Common culprits: missing permissions, incorrect login details, expired passwords. Quick fixes: reset passwords, confirm permissions, clear the browser cache, or switch browsers. Know your escalation path, and have IT contacts on standby during the training.
Connectivity problems. Preempt by testing the platform with a few users beforehand. Live: ask participants to turn off video or close high-bandwidth applications; provide dial-in numbers as a backup for persistent trouble.
Audio and video issues. Have participants test microphones and speakers before the session; guide them to device settings, headphones (to reduce echo), or phone audio; ask everyone to stay muted unless speaking.
Section 6
Conducting the Training
Delivery craft, recovered from the facilitator script and worth practicing deliberately.
Create an Agenda and Keep It Visible
Sessions with visible agendas feel purposeful; sessions without them feel endless. State the plan, follow it, and mark progress.
Ask Questions That Drive Engagement
Purposeful questioning: open-ended questions that prompt discussion and critical thinking ("How would you approach this scenario?"), not yes/no roll calls.
The Socratic method: guide participants to discover answers through a series of targeted questions. Discovery sticks; dictation slides off.
Wait time: after asking, give people a few moments to think before expecting an answer. The silence feels long to you and generous to them, and it draws in quieter participants.
Cold calling: rather than always waiting for volunteers, occasionally select participants to answer. It keeps everyone attentive, knowing they might be called on. (Use warmly, never punitively.)
Use Interactive Polls
Real-time feedback on understanding, letting you adjust pace on the spot
Opinion polls on thought-provoking topics to spark discussion
Knowledge checks on key concepts, followed by brief discussion of the results to clear misunderstandings
Gamification: award points for correct answers or participation; light competition keeps energy up
Run Breakout Rooms That Work
Clear instructions before the split: exactly what to accomplish (discuss a case, solve a problem, prepare a share-back)
Assigned roles within each room (facilitator, note-taker, presenter) so everyone contributes
Focused, time-bound tasks with a specific outcome to bring back
Facilitator drop-ins: visit rooms periodically to monitor progress, answer questions, and keep groups supported and on track
Use Role Play
Simulate real-world scenarios during training: a service agent handling a difficult customer inquiry in the new system, a coordinator processing a rush request. Role play converts abstract features into muscle memory, and it is the closest thing to on-the-job practice a session can offer.
Section 7
Communicating Clearly and Effectively
Language is the trainer's instrument. Adapt it deliberately:
Do pre-session research: gather participants' roles, experience levels, and backgrounds beforehand, and pitch your language to their knowledge base. Training entry-level staff? Skip the industry jargon.
Map personas and stay contextually relevant: create personas for your audience segments (beginners, advanced, technical, non-technical) and frame examples inside their actual roles: train project managers with project scenarios, salespeople with deal scenarios.
Adapt technical versus non-technical: precise, industry-specific language and system intricacies for technical roles; simplified explanations focused on broader impact and outcomes for everyone else.
Adapt formal versus casual: concise formality for senior executives; an approachable tone for peers and junior staff.
Use active voice and direct address: "You will need to..." makes training personal and immediate; passive voice makes it a lecture.
Practice with role-play and feedback: deliver a complex topic in simple language to a peer, then swap feedback on both content and delivery. Trainers improve by training, observed.
Section 8
Handling Questions and Challenges
Encourage Open Dialogue
Create a safe space where participants ask questions without judgment. Open by acknowledging that all questions are valid, and use open-ended prompts to invite exploration. A session where people are afraid to ask "wait, what's a record?" is a session that fails silently.
Stay on Track
When conversation wanders, politely steer back to the topic, and use a parking lot: a visible list of off-topic questions to be addressed later. The parking lot is a small tool with a big effect: participants feel heard, and the session keeps its shape. Always actually follow up on parked items afterward, or the tool loses its credibility permanently.
Handle Questions You Cannot Answer
Stay honest. If you do not know, say so and commit to finding out: "That's a great question. Let me look into it, and I'll get back to you." Then do. You can also invite the room: ask whether anyone has insight or experience with the question, promoting peer learning and collaborative problem-solving. Faking an answer, by contrast, costs you the room's trust the moment it unravels: and it always unravels.
Address Resistance
Some pushback in training is really grief about change (Module 15 gives this full treatment). The in-session playbook:
Acknowledge concerns. Recognize the participant's perspective before responding. "You're right that this adds a step to your intake process" beats any amount of deflection.
Redirect to benefits. Connect the change to what the participant gains: time saved, errors prevented, visibility earned.
Provide context. Explain the rationale behind the process or change: people accept what they understand far more readily than what is decreed.
Offer a follow-up. When resistance is significant, suggest a conversation outside the group setting to address specific concerns in depth: it respects the person and protects the session.
Section 9
Post-Training Support
Training does not end when the session does. The support strategies that turn a session into sustained adoption:
Set up Q&A sessions for follow-up questions once people have tried the system in earnest
Hold drop-in office hours during the early weeks, when questions are small, frequent, and urgent
Collect immediate feedback via a survey or a mini-retrospective while impressions are fresh
Hand off the training materials formally: guides, recordings, and cheat sheets in a known, findable home
Measure training effectiveness with 30/60/90-day follow-up surveys: adoption is a trailing indicator, and the ninety-day answer matters more than the exit-survey smile
These structures flow directly into the post-launch support world of Module 14 (hypercare will feel very familiar), and the measurement habit is your Module 1 benchmarking discipline applied to your own teaching.
Section 10
Change Communication: Announcing Features People Actually Use
Enablement extends beyond formal training into ongoing communication, and the same skills apply every time new functionality rolls out (recall Module 8's release rhythm: this is perpetual work). The guiding insight from the source material: many features are only valuable if users actually use them, and teams sometimes discover new features only by stumbling across them months after deployment. Your job is to make sure that never happens.
Be concise and lead with "What's in it for me?" Users want to do their day jobs: salespeople want to sell, service teams want to solve problems. Communicate how a feature makes the day job easier, as succinctly as possible: if users can grasp the what and why of a feature in two minutes, take no more than two minutes.
Content types that work:
Feature pitch: one or two punchy sentences: what it is, and what is in it for the user
Storytelling demo: a brief demo that sets a scene and solves a specific pain point ("As a salesperson, I use list views to stay on top of deals. Now I can pin my favorite view so it opens first: a whole bunch of clicks saved.")
Cheat sheet: an at-a-glance summary tailored by role ("Top 10 features for customer service")
Power-user content: invite your user committees to make a short "my favorite new features" video or one-pager: a peer explaining real usage is the most credible communication that exists
Channels to reach users where they work:
In-app prompts: what's new, in context, at the right time
Email: ride along in widely read internal newsletters; consider having executives send key communications to signal leadership commitment
Chat and collaboration groups: a dedicated feedback channel, amplified by power users who highlight posts in team meetings (channels go quiet without deliberate tending: recruit your champions to keep them alive)
Lunch and learns: user committees demo live to their peers; free lunch remains undefeated
Internal release webinars: good for large or dispersed teams and calendar-blockers; always include Q&A
On the job: nothing beats a peer showing you the ropes exactly when a feature helps: this is where trained trainers and champions pay off
And maintain a roadmap. A simple, visible view of what is coming to your org next quarter builds buy-in, lets teams plan, and turns users from surprise-recipients into participants. It is the change-communication equivalent of the project roadmaps you have managed all course long.
Recap
Key Takeaways
Training is a core BA responsibility because adoption is the project's real finish line: BAs uniquely combine business context and system knowledge, and training transfers confidence, not just information.
Prepare before you build: know your audience (roles, skill levels, personas), choose train-the-trainer versus direct training deliberately, and define measurable training objectives per persona.
Content that works is chunked, interactive, consistently designed, visually supported, and written in user-centric language: practice the rewrite exercise until jargon-translation is reflexive.
Mix modalities to fit the audience; test everything with a dry run, demo as the trainee persona, and keep a troubleshooting playbook (access, connectivity, audio) ready.
Engage deliberately: open questions, Socratic guidance, wait time, warm cold-calls, polls, structured breakout rooms, and role play.
Handle the hard moments with honesty and structure: parking lots for tangents, "I'll find out" for unknowns, and acknowledge-redirect-context-follow-up for resistance.
Support after the session: Q&A, office hours, immediate feedback, formal material handoff, and 30/60/90-day effectiveness surveys.
For ongoing change communication: two-minute "what's in it for me" pitches, storytelling demos, cheat sheets, peer content, the right channels, and a visible roadmap.
📝
Knowledge Check
8 questions. Answer at your own pace, then check the explanation for each.
Question 1 of 8
Why is the BA often the natural trainer on a Salesforce project?
Correct answer: B. The BA's dual fluency (business and system) is exactly what knowledge transfer requires.
Question 2 of 8
Which situation most favors train-the-trainer over direct end-user training?
Correct answer: B. TTT scales, sustains, and cultivates internal advocates: its strategic advantages fit large organizations and long-term ownership.
Question 3 of 8
"Chunking" training content means:
Correct answer: B. Modular, digestible parts that can be learned independently: the antidote to the ninety-minute feature wall.
Question 4 of 8
Before a live demo, why should you log in as the trainee persona rather than as an admin?
Correct answer: B. Permissions shape the experience (Module 7); train the view the audience will actually inhabit.
Question 5 of 8
A participant asks a question you cannot answer. The best response is:
Correct answer: C. Honesty plus follow-through preserves trust; guessing spends it.
Question 6 of 8
What is the purpose of a "parking lot" during training?
Correct answer: B. It respects the question without derailing the agenda, provided you genuinely follow up.
Question 7 of 8
Which sequence matches this module's playbook for addressing resistance during training?
Correct answer: B. Acknowledge, redirect to benefits, contextualize, and take significant resistance offline.
Question 8 of 8
True or False: Measuring training effectiveness should end with the feedback survey collected at the close of the session.
Correct answer: False. Exit surveys capture mood; 30/60/90-day follow-ups capture adoption, which is the outcome that matters.
🎉
Module 13 complete
Nice work. Review any question again using the menu (top right), or move on.