Education, Training and Learning Development

01Purpose and scope

• This manual supports the course Education, Training and Learning Development. It is written for people who design, run, buy or manage learning in organizations, classrooms, community groups and professional associations, and for newer practitioners who need a dependable sequence of steps rather than a list of theories.
• In this field, education usually means broader and longer lasting development of knowledge and reasoning, training usually means building specific skills tied to a task or role, and learning development means designing the wider system that supports both, including pathways, resources, policies and the way people get feedback. Most real projects mix all three. A onboarding program for hospital schedulers, for example, includes some education about privacy rules, a lot of training on the scheduling software, and a development plan that tells new staff what to learn at six and twelve months.
• This manual covers needs analysis, objective setting, design, development, delivery, evaluation and continuous improvement. It does not set certification requirements, which differ by sector, employer and jurisdiction. Where training covers safety critical tasks, licensed professions, medication handling, financial advice or other regulated work, this guidance does not replace qualified professional judgment, approved procedures or required authorization. Check the current requirements from the regulator or authority that governs your field.

02Core principles

• Start with the performance problem, not the content. A useful learning intervention begins with a gap between what people do now and what the work requires. If the gap is caused by unclear procedures, poor tools, weak supervision or incentives that push people the wrong way, a course will not fix it on its own. Ask what people need to do differently, and why they are not doing it already.
• Adults bring experience, habits and time pressure to learning. Build on what learners already know, give them realistic practice, and make the relevance of each activity clear. Short, applied tasks usually work better than long lectures for skill building, although lectures still have a place for introducing concepts that learners cannot discover through practice alone.
• Alignment is the backbone of good design. Learning objectives, practice activities and assessments should all point at the same performance. If the objective says a learner will calculate medication doses accurately under time pressure, the assessment should involve calculation under similar conditions, not a multiple choice quiz on dosage definitions.
• Transfer to the job matters more than completion. A learner who finishes every module but never changes behavior has not benefited from the program. Design with transfer in mind by including job aids, follow up tasks, manager conversations and opportunities to apply new skills within a week of training.
• Accessibility and inclusion are design requirements, not finishing touches. Decide early how learners with different abilities, languages, bandwidth and schedules will participate.

03Planning and preparation

• Begin by identifying the sponsor, the people who will be affected, and the subject matter experts who know the work. Sponsors decide budget and priority. Subject matter experts validate content. Learners and their managers tell you what the work looks like on a normal day. Compliance, legal, information security or union representatives may need to review content in some organizations. Map these people early so that you do not discover a review requirement after the materials are built.
• The main early deliverable is a needs analysis summary. It usually includes the performance gap, the population affected, the evidence behind the gap (such as error reports, customer complaints, audit findings or interview notes), possible non training solutions, and a recommendation. Methods include interviews with supervisors and high performers, observation of tasks, review of work samples, and task analysis, which breaks a job into steps and identifies where errors happen.
• Next, write learning objectives in observable terms. Verbs such as explain, classify, perform, diagnose and conduct are more useful than understand or appreciate, because they point to something you can assess. Keep the number of objectives small enough that a learner can reasonably achieve them in the time available.
• Decide on the delivery model. Instructor led sessions allow discussion and real time correction but are costly to repeat and hard to schedule across shifts. Self paced modules scale well and suit stable content, but they need strong design to hold attention and they offer weak feedback on complex skills. Cohort based programs create peer support and accountability but require coordination. On demand job aids work best for short, infrequent tasks. Blended designs combine these options and are common in practice, though each added component increases maintenance work.
• Prepare a schedule, budget and resource list that includes time for review, pilot testing and revision. Projects often underestimate the time needed for subject matter expert review and for getting approvals, so build that time in explicitly.

04Recommended workflow

1. 1
   : Confirm the performance problem with the sponsor and at least two people who do the work. Write a one page statement of the gap, who it affects, what has been tried before, and what success would look like. Stop here if the evidence points to a tool, policy or staffing problem rather than a skill or knowledge gap.
2. 2
   : Conduct the needs analysis. Interview a small group of workers, observe the task in its real setting, collect examples of good and poor work, and identify the critical steps where errors occur. Record the decisions you make about what to include and what to leave out.
3. 3
   : Define the target audience and the entry conditions. Note prior knowledge, required tools and access, language needs, and any prerequisites. This prevents building a course that assumes knowledge half the audience does not have.
4. 4
   : Write the objectives and the assessment plan together. For each objective, decide how you will know a learner has achieved it. Include at least one performance based assessment where the task allows it, and specify the conditions, standard and evidence required.
5. 5
   : Design the sequence and the practice. Organize content from simple to complex, with worked examples before independent tasks. Build scenarios drawn from real cases, with enough variation that learners cannot memorize one answer. Write a storyboard or design document that lists each screen, session or activity, its purpose, and its time estimate.
6. 6
   : Develop the materials and the facilitator or support guide. Create slides, job aids, activities, assessment items and any digital content. Keep a version history and note the source of every factual claim so that reviewers can check it. Test all links, media and tools on the devices learners will actually use.
7. 7
   : Pilot with a small group that resembles the real audience. Observe where learners struggle, time each activity, and ask a few targeted questions about clarity and relevance. Use the results to revise objectives, activities and assessments before a full rollout. A pilot that only collects satisfaction ratings will not reveal much.
8. 8
   : Deliver the program and support its use. Brief managers on what their staff are learning and what they can do to reinforce it. Track attendance and assessment results, answer questions quickly, and keep a log of issues so that the next revision has a clear basis.
9. 9
   : Evaluate and revise on a schedule. Review the results against the original performance gap, not only against course completion. Decide what to change, what to keep, and who approves each change, then update the version history.

05Quality checks, risk controls and compliance

• Quality checks happen at several points. During design, use peer review of objectives and assessments, asking whether each assessment truly measures the stated objective. During development, check factual accuracy with subject matter experts and confirm that procedures match current approved versions. Before launch, run an accessibility check against a recognized standard such as the Web Content Accessibility Guidelines for digital content, and test with assistive technology where feasible. Review captions, color contrast, alternative text and keyboard navigation.
• Risk control is important when learning content could lead to harm if wrong. Outdated procedures are a common source of error because training materials are often copied and kept alive long after the process has changed. Assign a named owner to each module, set a review date, and tie updates to changes in policy, equipment or regulation. Where a task requires a license or authorization, make clear in the program that completing the training does not confer that authorization unless the authorizing body says so.
• Privacy and data handling depend on jurisdiction and sector. If you collect learner records, assessment results or personal information, check the data protection rules that apply to your organization and the retention schedule required by your employer or institution. Limit access to records, avoid storing unnecessary personal details, and document who can see what.
• Some learning outcomes require formal sign off. Competency assessments for regulated or safety critical tasks often must be carried out by qualified or authorized assessors, and the record must meet the requirements of the governing body. Confirm who is permitted to assess, what evidence is required, and how long records must be kept before you design the assessment.
• Intellectual property and licensing also matter. Confirm that you have the right to use images, video, published frameworks and third party material, and record the license terms in the design file.

06Collaboration and documentation

• Learning projects involve many handoffs between subject matter experts, designers, developers, reviewers and managers. Clear documentation prevents rework and disputes. The design document should record the performance gap, audience, objectives, assessment method, content outline, decisions made and the reasons for them, and the approval history. A decisions log is especially useful because it explains why a topic was dropped or a scenario changed.
• Use version control with plain labels such as draft for review, approved for pilot and released. Keep one current master copy of each module and archive older versions rather than letting several copies circulate. Facilitator guides should include timing, materials, common questions and prompts for discussion, so that a new facilitator can deliver the session consistently.
• Agree on roles at the start. Decide who writes, who approves content, who owns the learning platform, and who answers learner questions after launch. Hold short review meetings with a clear agenda and send written comments in a shared place. When a subject matter expert disagrees with a design choice, write down the disagreement and the decision rather than letting it stay informal.
• Share results with the sponsor and with the managers whose teams took part. Keep the language specific, such as which tasks improved and which still show errors, rather than general statements of success.

07Measures and continuous improvement

• Evaluation models help you structure measurement. The Kirkpatrick model is widely used and describes four levels: reaction (how learners felt about the experience), learning (what they could demonstrate at the end), behavior (whether they apply the learning on the job), and results (the effect on the outcome the organization cares about). Most programs can measure reaction and learning easily. Behavior and results take more effort but are the measures that tell you whether the program was worth its cost.
• Useful indicators depend on the objective. For a call center skills program, you might track the rate of first contact resolution, the number of escalations, and supervisor observation scores in the eight weeks after training. For a safety program, you might track the frequency of near misses or the rate of procedures completed correctly on observation. Completion rates and satisfaction scores are easy to collect but tell you little about performance, so pair them with at least one behavior measure.
• Collect data before and after the program where possible so that you can compare change over time. Be cautious about attributing improvement to training alone, since staffing changes, new tools and seasonal workload can all affect results. Where you cannot isolate the effect, say so in your report.
• Continuous improvement works best when it is scheduled. Set a review cycle for each program, usually tied to the rate at which the work changes. Keep a backlog of suggested changes from learners, managers and facilitators, and decide regularly which items to address. Retire content that no longer serves the performance goal.

08Common mistakes and how to prevent them

• The most common mistake is starting with content rather than performance. Teams gather slide decks from experts and build a course around them, which produces a long program that does not match the work. Prevent this by writing the performance gap statement and objectives before any content is built, and by removing material that does not support an objective.
• A second mistake is writing objectives that cannot be assessed. Phrases such as know the policy or be aware of risks give designers nothing to test. Rewrite them with observable verbs and conditions, then check that each assessment matches.
• Third, many programs ignore the manager. When supervisors do not know what was taught or do not expect the new behavior, learners return to old habits within weeks. Brief managers before launch, give them a short list of observable behaviors to watch for, and ask them to hold a short follow up conversation.
• Fourth, teams often evaluate only satisfaction. High ratings can coexist with no change in performance. Include at least one measure of learning and one of behavior in the evaluation plan from the start.
• Fifth, materials go stale. Assign ownership, set review dates and check the content against current procedures each time the process changes. A short module that is accurate is worth more than a long one that is partly wrong.
• Finally, accessibility is often left until the end and then rushed or skipped. Build captions, readable layouts, alternative text and keyboard access into the design from the first draft, and test with real users where possible.

09Practical checklist

• Confirm the performance gap in writing with the sponsor and at least two people who do the work.
• Decide whether training is the right response, or whether a tool, policy or staffing change is needed first.
• Identify the audience, prior knowledge, language needs and access constraints.
• Write observable objectives and an assessment for each one before building content.
• Check every fact and procedure against the current approved source and name the owner who will review it.
• Pilot with a small group, revise based on what you observe, and record the changes.
• Brief managers on what is being taught and which behaviors to reinforce.
• Plan at least one behavior measure and one results measure, with a date for the first review.
• Confirm privacy, record retention, licensing and authorization rules with the responsible authority before launch.

★Learning sources

• Micro Degree: Education, Training and Learning Development
• Micro Degree: Leadership and Team Management
• Micro Degree: Business Intelligence Management
• Micro Degree: ESG Advisory Services