Microlearning Examples: 9 Worked Lessons and a Free Template

Create bite-sized, high-retention training modules in minutes

Start Free

Microlearning is short, focused learning for a specific objective. In this guide I use a five-part workplace lesson plan: a moment, a target behaviour, a short explanation or demonstration, a check, and planned follow-up. That is the template used here, not a universal definition or a fixed duration rule. For example, a payroll officer compares two sample emails, checks a third and explains the clues behind the decision. Later practice uses different clues. Sender-domain inspection is one useful check, not proof that an email or link is safe.

The format came last: the side-by-side emails follow from the job, which is spotting a fake. I'm Carolina, an instructional designer at Coursebox, where we make a microlearning platform for building short workplace lessons, so I'll say where our product helps and where it stops. In this guide I write out nine microlearning examples in full, show how to pick a format from the job the person has to do, and work one manager's request into five lessons with a follow-up schedule. There is a free template to copy, three real workplace cases and a test of our own tool.

What counts as a microlearning example

Microlearning is short, focused learning for a specific objective. The five-part workplace template below is one way to plan it, rather than a universal definition.

A 2026 hospital review defined its interventions as focused and under 15 minutes. Other reviews use different boundaries; there is no agreed universal ceiling or ideal length. The worked lessons here generally take seconds or a few minutes. If a task needs more explanation, keep the needed context or choose a longer lesson rather than cut it to meet a number.

The moment is the place to start. It means where the person is, and what is happening, when they need the lesson: at the till with a queue, at the machine at the start of a shift, in the minute after a call ends. Our guide to the five moments of need covers the formal model; here I use the word in its plain sense.

Every example in this guide has the same five parts. They are the microlearning template, and the download further down sets them out as a page per lesson:

• The moment. Where they are and what is happening when they need it.
• The behaviour. The one thing they do differently afterwards, written as an action.
• The lesson. The shortest thing that shows that behaviour, usually one to three minutes.
• The check. One question they answer from the situation, not from a list.
• The follow-up. When it comes back, where it arrives and what changes.

The behaviour is the line people get wrong. Write it as something they do, not something they know.

The clearest published example of the follow-up at work comes from rural Kenya, where the repeated message was the whole intervention.

Case study: Twice-daily text messages for health workers in rural Kenya

Government health workers at rural dispensaries and health centres in coastal and western Kenya often did not follow the national guidelines for treating children with malaria, even after formal training.

• What they did: For six months, health workers at 54 facilities got two text messages a day on their own phones, at 9 am and 2 pm, Monday to Friday. Each message was up to 120 characters and asked for one action, such as "Check ALL sick children <5yrs for any severe signs!" or "Advise mother to give SECOND DOSE of AL after 8hrs" (AL is the antimalarial drug artemether-lumefantrine). Each came with a short quote unrelated to malaria. Health workers at 53 control facilities got no messages.
• Evidence and result: In Zurovac and colleagues' 2011 cluster randomised trial, 119 health workers received the messages, and care was assessed for 2,269 children through interviews with carers as they left. Correct management improved by 23.7 percentage points compared with the control group straight after the six months, and by 24.5 points six months later.
• Limitation: The trial was not masked, and the authors say part of the effect could have come from the motivational quotes rather than the malaria content. Even after the messages, only about half of the children were managed fully correctly. A similar trial in Malawi found no significant improvements.
• Lesson: One action per message, sent during the working day and repeated for months, backed up training the workers already had. It did not replace that training.

Which format fits which job

Start with what the person has to do. Almost every request I get is one of five jobs, and each job rules some formats out.

The selection rule I would retire is matching the format to the learner, where the visual learner gets the infographic and the auditory learner gets the podcast. A 2008 review of the learning-styles research by Pashler and colleagues found virtually no evidence that people learn better when lessons are matched to their preferred style. Formats differ by what they can show, not by who is watching. A video suits a procedure because a procedure has an order you can see. A scenario suits a judgement call because a judgement needs consequences.

The strongest workplace evidence I know of for short lessons on judgement calls comes from clinics in South Africa, where each lesson was a case to decide.

Case study: Lunch-break WhatsApp lessons for clinic staff in South Africa's Eastern Cape

Nurses and community health workers at 50 mostly nurse-led clinics in four rural districts of the Eastern Cape have to keep up with national HIV guidelines that change often, such as which medicines interact with the HIV drug dolutegravir. Centralised or long online training is hard for rural staff to reach.

• What they did: Staff got "case-based microlearning lessons" of 10 to 15 minutes each in WhatsApp groups, timed for the routine lunch break: six lessons for nurses and four for community health workers, between 23 January and 8 February 2023. Mobile data was provided. Clinics in the control arm got the lessons after the trial.
• Evidence and result: In Chisholm and colleagues' 2025 cluster randomised trial, 232 nurses and 207 community health workers took part, and 96% of the nurses and 88% of the community health workers read the lessons within two weeks. Knowledge scores three months later were slightly higher than in the control arm: 0.5 points for nurses and 0.7 points for community health workers. In a review of 1,083 patient folders over the following year, the authors reported a 21% improvement in correct patient care after adjustment for baseline differences between the trial arms. That figure should not be read as a 21-percentage-point change.
• Limitation: The trial lead reviewed the folders and was not blinded, knowledge was already high at the start, and the same questions were used before and after. An educational grant from Aspen, a pharmaceutical company, covered the research costs; the authors state it had no role in the content.
• Lesson: Short case-based lessons, in an app staff already open, in a slot set aside for them, reached nearly everyone. Writing each lesson around a decision that leaves a record, here the patient folder, is what let the team measure behaviour rather than quiz scores.

The other constraint is the device. More than a quarter of course starts on Coursebox happen on a phone, and the moment of need is often away from a desk.

So build each lesson to work on a phone: readable text, controls that work on a small screen and a connection requirement that fits the workplace. That is why most of the examples below are a short video, a photo, a card or a single question.

Quizzes and knowledge checks as microlearning

A short quiz can provide retrieval practice. Ask learners to produce a fact from a relevant situation, then show the answer and an explanation. A weekly question can reinforce prior teaching; it does not necessarily supply the explanation a beginner needs.

It fits judgement calls badly when one answer is obviously right. A knowledge check for a judgement needs options a reasonable person might choose, and feedback on what each would lead to. Every check in this guide asks about a situation for that reason.

Where gamification fits

Points, badges and streaks are often sold with microlearning. In my view they can prompt someone to open the next lesson, but the behaviour they reward depends on how the rules are designed, so I would use them on the follow-up schedule at most and never in place of the check. I found no workplace study in this guide's sources that isolates their effect.

Nine microlearning examples, written out

Each example uses the same five parts. The details are illustrations for you to replace with your own; keep the shape.

1. Retail: the returns rule (recall)

For this fictional shop, the lesson covers change-of-mind returns under its own policy. Faults, consumer guarantees and acceptable proof of purchase are handled through the applicable approved process, not refused because someone lacks a receipt. Staff can keep the policy available while learning the common cases.

• The moment: A customer wants to refund a jacket bought 40 days ago, and there is a queue.
• The behaviour: Say the returns rule from memory, without checking.
• The lesson: One card per change-of-mind rule, in the words staff would use: "Within 30 days with the required proof for a refund." "Up to 90 days with the required proof for store credit." "If the proof or condition is unclear, check the approved returns process."
• The check: "Bought 40 days ago, has the receipt. What do you say?"
• The follow-up: One question a week in the team chat, taken from a real return.

2. Aged care: the escalation thresholds (recall)

Care staff record observations within their role and follow the resident's care plan and the service's approved deterioration and escalation procedure. The lesson can rehearse recognising a specified trigger and contacting the appropriate clinician. A concerning change can require escalation even when a single reading falls inside a stated range.

• The moment: A support worker takes a resident's observations and one reading looks wrong.
• The behaviour: Call the nurse when a reading crosses your service's threshold.
• The lesson: One card per vital sign, with the threshold and the phone number together.
• The check: Four readings, one out of range. "What do you do now?"
• The follow-up: Monthly, with a different reading out of range each time.

3. Software: updating the CRM after a call (procedure)

A sales team may require deal records to be updated after a call so the forecast reflects the latest information. This example concerns a rep who knows the required fields but needs a prompt to complete them in the workflow. Check whether the cause is knowledge, access, workload or a habit before choosing the intervention.

• The moment: The 90 seconds after a sales call ends.
• The behaviour: Update the record now, not later.
• The lesson: A 70-second screen recording of one real deal, showing three fields change: stage, next step and close date.
• The check: A record where the stage moved but the close date did not. "What is missing?"
• The follow-up: The same three fields, pinned as a three-line checklist in the CRM.

If close dates are missing in your records, check why before scripting the lesson. A rep may need a clear date rule, a usable CRM field or permission to record uncertainty. The recording and checklist should demonstrate that approved process.

4. Warehouse: the forklift pre-start check (procedure)

A pre-start check must follow the actual forklift's instructions and the workplace's approved procedure. This lesson is an aid for an authorised operator, using safe images of what a defect looks like. It is not a complete check, operating instruction or substitute for required training.

• The moment: The start of a shift, standing at the machine.
• The behaviour: Finish the pre-start check before starting the engine.
• The lesson: A phone video shot on your own forklift by whoever does the check best.
• The check: Five photos from one walkaround, one showing a weeping hydraulic hose. "Which one means this forklift stays parked?"
• The follow-up: The approved daily check supplies repeated use. A supervisor still checks whether operators recognise and report defects correctly, and adds practice if they do not.

Build the check itself from your duties under Safe Work Australia's model code of practice for managing risks of plant, and use the lesson to show a new operator why each item is on the list. Our guide to warehouse safety training covers the wider programme around it.

5. Managers: the leave request you have to decline (judgement)

Sometimes a team member asks for something the company cannot give, and no policy covers it cleanly. The manager has to say no, in their own words, on the spot, and whatever they say becomes the version the rest of the team hears.

• The moment: A team member asks for leave they have not accrued, three days before Christmas. In this fictional example, the manager has checked that advance leave cannot be approved under the applicable arrangements and has authority to offer a different roster option.
• The behaviour: Decline clearly and offer what you can, without inventing a rule.
• The lesson: One situation and three replies written out in full: (a) "Company policy says no, sorry." (b) "I can't approve leave you haven't accrued, but I can give you the 27th off if someone covers your shift. Let's look at the roster now." (c) "Leave it with me and I'll see what I can do."
• The check: "Which reply would you give, and what goes wrong with the other two?" The feedback gives the reasoning: (a) hides behind a rule nobody can see, and (c) delays a no the person will hear anyway.
• The follow-up: The same decision six weeks later, with the facts changed.

Ask three of your own managers what they would say, then use their words. The wrong replies have to be the ones people actually give, or the check is too easy. Our guide to scenario-based learning goes further into writing these.

6. Sales: the discount request (judgement)

Late in a good sales call, the buyer asks for money off. The rep can agree, or offer the discount in exchange for something: a longer contract, more seats or a reference call. Agreeing takes a second. Asking for something back takes nerve.

• The moment: A good call is ending and the prospect asks for 20 per cent off.
• The behaviour: Ask for something in return before conceding.
• The lesson: Two 40-second recordings. One rep agrees on the spot. The other trades the discount for a two-year term.
• The check: "Which rep asked for a commitment in return for a concession, and was that trade within the approved discount authority?" A discount still reduces the quoted price; the proposed term may offer value in return.
• The follow-up: The weekly pipeline review, against a live deal.

Use recordings of your own team. A scripted actor does not sound like your market.

7. All staff: spot the phishing email (noticing)

A phishing message can imitate a trusted sender. Practise checking the sender, the request, links and the reporting route using the organisation's current security guidance. A familiar-looking or apparently internal domain is only one clue; it does not establish that a message is safe.

• The moment: An email arrives that looks like it came from inside the company.
• The behaviour: Check the sender's domain before clicking anything.
• The lesson: Two emails side by side, one real and one fake, both on your branding.
• The check: A third pair, no answer given until they choose.
• The follow-up: Every three months, with a different clue giving the fake away.

Withholding the answer feels unkind, and it is the point: noticing only counts when the person is unsure. If the clue never changes, staff learn your fake instead of the habit. Our guide to cyber security training for employees covers the rest of a programme.

8. Site safety: three hazards in one photo (noticing)

The first thing anyone should do on a work site is look around and register what is unsafe. That is a skill of noticing, and a list of hazards to memorise does not build it.

• The moment: Walking onto a work area at the start of a job.
• The behaviour: Spot what is wrong before starting.
• The lesson: One photo of a real area on your own site with three things wrong in it: a lead trailing across a walkway, a missing guard rail on a platform edge, and a pallet stacked above the marked line.
• The check: A different photo of the same area. "What would you fix before you start?"
• The follow-up: A new photo every month, with a different number of hazards, sometimes none.

Use a safe photograph or edited training scene; do not create a real exposed edge or other hazard for the lesson. Compare answers with the site's approved controls, and let an ambiguous feature prompt a question rather than an invented pass/fail answer.

9. Handover: the shift note (habit)

At the end of a shift in a hospital ward, staff write a note telling the incoming shift what happened and what to watch. When that note is vague, the next shift spends an hour piecing it together from other people, and sometimes misses something important.

• The moment: 6.55 am, writing the note at the end of a night shift.
• The behaviour: Write the same three things in the same order: what changed, what to watch, and what is outstanding.
• The lesson: A 40-second clip showing a real note beside the same note rewritten in the three parts.
• The check: "Rewrite this note into the three parts."
• The follow-up: A prompt at handover time, in the tool where the note is written.

If staff can already write an adequate handover but omit it under pressure, a workflow prompt may help. If they cannot, teach and practise the approved handover format first. Use fictional or properly authorised material and preserve clinical information the local process requires.

Microlearning video examples among the nine

Four of the nine are video lessons: the CRM screen recording (3), the forklift phone video (4), the two discount calls (6) and the handover clip (9). Each shows one behaviour, shot where the work happens. If you are making the video version of any example, film it on a phone at the real place, keep to the one behaviour, and turn captions on so it works with the sound off.

Most published trials of microlearning at work come from health services. This one is from retail, and it shows both what short units can do for shift workers and where they stop.

Case study: A phone course in short units for convenience store workers in Tokyo

Convenience stores in Tokyo serve customers living with dementia, who can struggle to pay or to find what they came for. The standard training in Japan is a 90-minute face-to-face group course, which part-time shift workers find hard to attend.

• What they did: Researchers built a course for phone or computer with 40 short units in seven lessons, 50 minutes in total. It mixed branching simulation games, such as a customer who is slow to pay at the counter, with brief lectures, three quiz questions per lesson and short documentary videos. Workers from seven franchise chains had one month to finish.
• Evidence and result: In Matsumoto and colleagues' 2023 randomised trial, 150 of the 166 workers randomised were analysed. Of the 83 sent the course, 67 (80.7%) finished within a month, in a median of 6 days. Compared with a wait-list group, attitude and knowledge improved after one month (effect sizes of 0.70 and 0.59) and stayed improved at four months. Self-reported helping behaviour rose, but not significantly more than in the wait-list group.
• Limitation: Outcomes were collected through questionnaires, including a knowledge measure; helping behaviour was self-reported rather than observed at the counter. The trial was open label, only 71 of 2,655 invited stores registered, and participants received small payments for surveys and completion.
• Lesson: Split into 40 units, the 50 minutes was finished by most workers within a month, in a median of 6 days. It changed what they knew and how they felt faster than what they reported doing at the counter, so practise the moment itself and do not oversell what a short course changes.

A worked request: turning "forecourt training" into five lessons

The nine examples each show one lesson. Most real requests arrive as a topic with several moments inside it, so here is one worked from the request to the follow-up schedule. The example is hypothetical; the business, the people and the numbers are illustrative.

A family-owned chain runs 8 highway service stations on the Pacific Highway on the NSW Mid North Coast: Bulahdelah, Taree, Port Macquarie, Kempsey, Macksville, Nambucca Heads, Coffs Harbour and Woolgoolga. Four of them (Taree, Port Macquarie, Kempsey and Coffs Harbour) open 24 hours. The chain has 72 console operators, 9 at each site, and about two thirds of them are casual. They already run the console, take payments and stock the shop.

Sunil, the area operations manager, sends this request: "We need forecourt training for all console staff. Drive-offs are up, we had a spill at Macksville nobody knew how to handle, and people keep charging the wrong pump." That is a topic with three problems inside it, not a lesson. Tahnee, the site manager at Kempsey, has offered to shoot video and photos at her site.

The work happens at a console, between customers, on shifts, and most operators open lessons on their own phones in quiet periods. Nobody can sit through a 40-minute module mid-shift. The goal is that each operator handles five forecourt moments the company's way. Chasing a vehicle, deciding who pays for a spill and anything a manager or the police decide are outside it.

Sunil and Tahnee list every moment where an operator gets it wrong. Sunil's three problems are there, plus two more Tahnee sees at Kempsey: a card declined at the counter and a rule broken on the camera screen. Each one is a different job:

The five lessons below are written out with the same labels as the nine examples.

Lesson 1. The drive-off record (recall)

• The moment: A silver hatchback pulls away from pump 3. The nozzle is back, and nobody has come in to pay.
• The behaviour: Write down the five drive-off details straight away. Never follow the vehicle or step in front of it.
• The lesson: One card: "Drive-off? Write five things now: pump number, time, number plate, make and colour, which way it went. Then call your site manager. Do not follow."
• The check: "A white ute has just left pump 7 without paying. What do you write down, and what do you not do?"
• The follow-up: One question in the staff group chat after 1 week and again after 1 month, each with a different vehicle and pump.

Check the actual incident records for missing details before choosing what to practise. The drive-off example asks for a record and a manager call; it does not ask staff to follow a vehicle.

Lesson 2. A fuel spill at the pump (procedure)

For this example, a trained site lead supplies a response plan from the site's approved spill procedure. The teaching focuses on five responsibilities, not a universal clean-up sequence:

1. Stop fuel delivery using the site's approved emergency control, if safe to do so.
2. Warn people away from the spill and ignition sources; use the approved safe area.
3. Notify the responsible site lead and follow the emergency escalation plan.
4. Keep the affected area isolated. Only trained, authorised staff assess and contain a spill when the plan says it is safe.
5. Record the incident and reopen only after the authorised person permits it.

• The moment: A customer overfills a jerry can (a portable fuel can) at pump 4, and petrol runs across the forecourt.
• The behaviour: Recognise the spill, stop fuel delivery if safe, keep people clear and contact the authorised responder under the site plan. Do not send an untrained console operator out to clean petrol.
• The lesson: A short training recording in a closed, safe setting shows the console response, warning, isolation and escalation. Use a dry simulation and approved props; no fuel is released. It illustrates the site procedure that a responsible person has checked.
• The check: The five steps shuffled. "Put these in order."
• The follow-up: The steps printed inside the spill kit lid, plus the same ordering question after 3 months with the steps reworded.

The recording rehearses the approved console response and escalation. Confirm the actual error pattern with the site lead rather than assume operators always run outside first.

Lesson 3. The card that will not go through (judgement)

• The moment: A driver has filled up, their card is declined twice, two people are waiting, and they ask if they can pay tomorrow.
• The behaviour: Use the company's promise-to-pay form, or call the site manager if the customer will not complete it. Do not argue at the counter.
• The lesson: One situation and three replies written out in full: (a) "Sorry, you can't leave until it's paid." (b) "No problem. I just need you to fill in this promise-to-pay form with your details and rego, and we'll hold it here." (c) "Just come back tomorrow, it's fine."
• The check: "Which reply follows our process, and what is wrong with the other two?" The feedback gives the reasoning: (b) follows the process, (a) starts an argument at the counter, and (c) leaves no record.
• The follow-up: The same decision after 6 weeks, with the facts changed: the customer refuses to fill in the form.

Write the wrong replies from what your own operators say. Ask three site managers before you script them.

Lesson 4. Three things wrong on the forecourt screen (noticing)

The company's forecourt rules are on signs at every pump: no smoking or naked flames, engines off while fuelling, and no mobile phone calls while holding the nozzle.

• The moment: Between customers, the operator glances at the forecourt camera screen before authorising a pump.
• The behaviour: Spot a breach of the forecourt rules and act, by using the intercom or holding the pump, before authorising it.
• The lesson: A staged composite or safely edited camera still from Kempsey shows three breaches, such as smoking, an engine running during fuelling and a violation of the site's posted device rule. Nobody lights a cigarette or runs a vehicle at an active pump to make the image.
• The check: A new still. "How many breaches can you see, and where?" No answer is shown until they commit.
• The follow-up: A new still every month, with a different number of breaches, sometimes none.

If every still has exactly three breaches, people learn to stop looking at three. Vary the count.

Lesson 5. "Pump 6 and these drinks" (habit)

• The moment: A customer at the counter says "pump 6 and these drinks", with a queue behind them.
• The behaviour: Say the pump number back and check that pump's amount on the console before taking payment.
• The lesson: A 40-second clip with two takes at the same console. In one, the operator scans the drinks and charges pump 5 by mistake. In the other, the operator says "Pump 6, that's the blue Corolla?" and checks the screen first.
• The check: "Rewrite what the first operator should have said, in your own words."
• The follow-up: A one-line prompt on the console's payment screen, "Pump number said back?", if the console allows it; otherwise a sticker on the card reader.

Confirm whether operators know how to verify the pump and amount. If they do but omit it under pressure, a console prompt is one option to trial. If not, teach the check first and observe a later attempt.

The five lessons together take under 10 minutes. The template has lesson 1 filled in, the follow-up schedule below filled in for all five, and blank pages for your own.

Plan the follow-up as well as the lesson

A lesson seen once is easy to forget. Bringing it back a second and third time helps it stick, so plan the gaps between those contacts. A 2006 review of the spacing research by Cepeda and colleagues pooled 839 assessments of spaced practice from decades of memory experiments, mostly with students, to work out how long those gaps should be.

The review found that the gap associated with strongest retention tended to grow with the retention interval in verbal-recall experiments. Treat that as a planning clue, not a fixed workplace schedule. Reuse relevant questions where helpful and add new situations to check application; keep approved operational wording unchanged.

Here is the forecourt schedule. Every follow-up has a place it arrives, and someone or something that puts it there.

When customers write to our support team about microlearning, the question I keep seeing is not how to build a short lesson. It is how to release the next one on a schedule and bring the old ones back. So decide when each lesson comes back before you build it, and decide what will send it. A group chat message, a card inside the spill kit lid and a sticker on a card reader need no software at all.

Benefits of microlearning

A short format can offer practical benefits when it fits the objective, access needs and workplace. These are design opportunities, not benefits established by duration alone.

• It can arrive at the moment of need: at the till, at the machine, in the minute after a call.
• It can fit mobile use when designed and tested for a small screen. The Coursebox figure above, 28.1% of 178,799 course-start events from 20 July 2025 to 19 July 2026, describes all course starts, not microlearning specifically.
• It is easy to bring back. A short lesson can return after a week or a month, and the spacing review by Cepeda and colleagues found that the best gap for retention grew with how long people had to remember.
• A small, separate lesson can be easier to update. A rule change may affect one card or question, but check linked lessons, assessments and job aids too.

The hospital review does not isolate the effect of short duration: in a 2026 hospital review, 30% of 40 outcomes across 15 studies were statistically significant, although 90% pointed in the right direction.

When a short lesson is the wrong shape

Short lessons are a sensible default, and it helps to be straight about how strong the evidence is.

Eleven of the 15 studies in the hospital review used before-and-after implementations, and none compared microlearning head to head with a traditional course. The review cannot establish that short duration itself caused a benefit, or that microlearning is better than another well-designed format. The pros and cons of microlearning discusses the wider choice.

Being short is also not the same as arriving at the right moment. In a stepped-wedge trial across 44 nursing units in Minnesota, a one-minute sepsis video linked from the electronic health record's sepsis alert was viewed 30 times while the alert fired over 30,000 times, and the time to antibiotics did not change. In that trial, a lesson attached to an interruption, at the busiest point in a shift, was barely opened.

Three kinds of training need a different shape:

• Skills that need supervised practice. Lifting a patient or reversing a truck has to be done with someone watching.
• Material where the connections are the point. A process that only makes sense end to end breaks when you slice it.
• Anything that must be right first time, unsupervised. That needs an assessment and a sign-off, not a card.

If you cannot yet name the moments at all, the problem may be upstream of the format, and a training needs analysis questionnaire is a better first step.

Building the forecourt series with an AI course tool

You do not need software for any of the examples in this guide. Each one can be built with a phone, a shared drive and a calendar entry, and for a small team that is often the right call. A platform starts to help when you are assigning lessons to hundreds of people across several sites and need a record of who finished what. Our comparison of microlearning platforms covers the main options.

On 26 October 2026 I gave the forecourt series to the Coursebox AI course creator as a written brief. Coursebox is our product, so weigh my account with that in mind. The brief set out the five moments, each with its behaviour, lesson, check and follow-up, the original spill steps and the three replies. The spill design was revised after this test, as explained below. It asked for exactly five lessons of under two minutes each, with no learning objectives and no introduction to forecourt safety.

The outline contained the five core lessons, but also an introduction and a wrap-up despite the request to avoid an introduction. The setup summary showed 5 sections, 7 pages and about 7 minutes: a "How this series works" page, one page per lesson in the briefed order at about a minute each, and a wrap-up page last. Lessons 1 and 2 each showed the five labelled parts, lesson 1 starting with "The moment: A silver hatchback pulls away from pump 3; the nozzle is back and nobody came in to pay." The drive-off check stayed the situation question, answered in open text rather than turned into a multiple-choice question: "A white ute has just left pump 7 without paying. What do you write down, and what do you not do?", followed by "Submit your answer to reveal the model answer." Lesson 2 kept the five spill steps in the briefed words and order in a video script that opens "The operator begins at the console."

The problem was the spill check. It was an ordering activity that shuffled the five steps but kept each step's original number on it: "(3) Take the spill kit from beside the shop door ...", "(1) Stop the pump from the console.", and so on. A learner could put the steps in order by reading the numbers, without knowing the procedure.

In the page editor I opened the check block's code view and removed the number from the front of each of the five items. After I reloaded the learner view, the items read without numbers, starting "Take the spill kit from beside the shop door and cover the spill with absorbent." and "Stop the pump from the console." I submitted the steps in that shuffled order, and the check returned "Not correct yet."

I inspected the outline and lessons 1 and 2 after reloading, and submitted one wrong order. I did not test the correct-order path or inspect the checks in lessons 3 to 5. The original lesson 1 model answer omitted the instruction to call the site manager, and the numbered spill procedure remained visible above the ordering activity. Those were not fixed in the run. The test therefore shows removal of one answer cue, not a complete recall or safety assessment. The blog's spill example has since been revised to require the approved site plan and authorised responders; that revised design was not retested in Coursebox. Follow-up delivery remained the team's responsibility. No learners were enrolled or workplace outcomes measured.

Putting microlearning examples to work

A useful short lesson connects a focused objective with an explanation or demonstration, a suitable attempt and feedback. The nine examples use the five-part template to make those choices visible. Choose the format for the task and access needs, plan later practice or a work check, and include supervised training where the skill requires it. A short lesson can support that programme without replacing it.

Your next step: pick one moment your team got wrong this month, fill in the five lines of the template for it, and write down the date and the sender of the first follow-up before you build anything.