Learning in the Flow of Work
Learning in the Flow of Work
What is Learning in the Flow of Work?
- Learn while you work, not instead of working
- Short, instant help at the moment and on the screen where it’s needed
- Measure results with business metrics, not completion rates
What this approach really changes is not employees’ schedules but the HRD team’s deliverables and budget lines. A team that reported results by number of courses opened and completion rate now manages a 'list of points where work gets stuck' and 'the number of content pieces actually attached to those points.' The money shifts too, from instructor fees, venue rental, and group travel toward producing short content, integrating with work systems, and improving search quality. Naturally, training managers end up working with the business’s work screens open, not in the classroom.
It helps to separate this from similar terms. Microlearning is about 'how short to cut the content,' but this concept is about where to place that content. Even a two-minute video is not in the flow if employees have to log in to the LMS to find it. A common rule of thumb is findable in 2 minutes, within 3 clicks, 1 to 3 minutes long. Scope matters too. It works well where there is a right answer, such as system operation, policy lookup, and approval procedures. But skills built on judgment and experience, such as negotiation, coaching, and organizational leadership, cannot be replaced this way.
The most common misconception is "We cut our videos into short clips, so we've done it." If the content never reaches the work screen, it is just shorter e-learning. Neglect is even more dangerous. When a system is revamped but a tooltip still describes the old screen, employees follow the wrong procedure. After getting burned once or twice, nobody clicks the help again. Performance support that is no longer updated does more harm than none at all. Be careful with metrics too. If you count only fewer help desk tickets as success, you cannot tell whether employees learned and stopped asking, or gave up because asking was pointless.
Hwi KimCEO of HRDIST & Talent Development Systems Consultant
John KimJohn Kim, author of B2B Marketing Design and CEO of Nanum ConsultingThe concept was put forward and popularized around 2018 by HR analyst Josh Bersin. It starts from the view that learning should not be a separate 'event' apart from work but should be woven into the flow of work. Alongside the rise of microlearning, performance support, and searchable knowledge bases, it has become a central topic in corporate HRD.
Consider a hypothetical case. Company A, a home and living retailer with 1,200 employees, switched fully to a next-generation order management system (OMS) in December. The system that about 400 call center and branch sales staff use every day changed overnight, and in week 2 of the transition helpdesk inquiries soared to an average of 180 a day, so many that the IT operations team could not get its own work done.
- Kim, a manager on the HR development team, classified 1,400 helpdesk tickets from two weeks by hand and found that 62% of the questions came from just two screens: 'return intake' and 'partial cancellation'.
- The call center QA lead put it bluntly: "Nobody reads a 200-page manual. If they can't find it on screen in 3 seconds, they just call." So the team rebuilt it with 14 videos under 90 seconds and 27 tooltips.
- Working with the IT team, we added a question-mark button to the right side of the OMS returns screen. Click it and only the 3 cards relevant to that screen appear. We deliberately left out the full list.
- We moved exception policies and refund criteria to the internal wiki and tagged them with words agents actually use, such as 'return' and 'partial cancellation.' Every Friday, Kim, the team manager, removes any card with zero views.
- Eight weeks later, helpdesk inquiries fell to 47 a day, and the time for a new agent to handle a return alone dropped from an average of 6 weeks to 3.5 weeks.