Blended learning is the correct answer to a real question: how do we produce behaviour change when a classroom alone cannot, and digital alone will not?
But badly designed blended programs have become the single biggest tax on manager time in most organisations. A program that demands five hours per month per manager for six months may move some learners, but usually at a cost the rest of the business cannot defend.
Good blended design is not about adding more elements. It is about choosing fewer, making each one higher leverage, and respecting the manager's calendar as the binding constraint it actually is.
The manager time problem
The average "blended" program now includes: a kickoff, an online module, peer discussion, a manager check-in, an application project, a coaching call, a showcase, and a follow-up. Per learner.
Multiply that by 50 learners per cohort per function. The manager layer is underwater before the program starts.
Three specific manager-time traps:
The "manager as co-facilitator" assumption. Programs that design in 60 to 90 minutes of manager time per learner per month are assuming a labour capacity most middle managers do not have. Adoption silently drops.
The duplication trap. The manager is asked to run a development conversation that the program already runs, creating redundant work with diminishing signal.
The accountability theatre. Programs ask managers to "hold learners accountable" in performative ways, filling out forms, sending reports, that take time but do not change behaviour.
Four design principles
The programs that land in 2026 share a few design principles.
Principle 1: Manager time is additive, not duplicative. If the program runs a check-in, the manager does not also run one on the same topic. Pick one place where the manager's presence is irreplaceable (usually the application conversation) and go hard on that. Eliminate the rest.
Principle 2: One manager conversation per month, max. Over a 6 month program, the manager should have no more than six dedicated program conversations with the learner, each no longer than 30 minutes. If the design requires more, either consolidate or cut modules.
Principle 3: The manager conversation has a single output. Not a form. Not a report. An observable commitment by the learner: "this week I will practise X in Y context." The manager's job is to notice and feed back on the commitment.
Principle 4: Skip the kickoff and the showcase. Both consume significant time for limited behaviour change. Most learners forget the kickoff within a week. Most showcases are performative. If either is retained, it should earn its place on the basis of a specific outcome, not habit.
What to keep, what to cut
Keep:
- Pre-work that is required before the live event (a short reading, a reflection question, a brief assessment)
- One live session per month with peers, maximum 2 hours
- A single application-focused manager conversation per month (30 minutes)
- Digital practice that is contextual to the learner's live work
- One cohort-level synthesis at the midpoint
Cut:
- Kickoffs that exist only to explain the program
- Showcases that exist only to perform completion
- Manager reports / forms that duplicate what is already captured digitally
- Weekly "check-in" touches that are too frequent to be meaningful
- Synchronous content that could be asynchronous
The measurement that justifies the design
The test of good blended design is not learner satisfaction. It is whether behaviour changed at work.
See measuring learning: 5 metrics that matter for the specific metrics, but the short version: pick three behaviours you expect the program to move, measure them before, measure them 60 days after, and be honest about the result.
A blended program that moves three out of three behaviours by 25%, costing 3 hours of manager time per learner, is worth repeating. A program that moves one of three by 10%, costing 12 hours of manager time per learner, is not worth repeating, regardless of how much the learners liked it.
A sample re-design
To make this concrete: a common 6-month leadership development program we have redesigned for clients.
Before (per learner):
- Kickoff (2 hours)
- 6 × monthly modules (2 hours each)
- 6 × peer group discussions (90 minutes each)
- 6 × manager check-ins (30 minutes each, with pre-read and post-form)
- Application project (variable)
- Showcase (2 hours)
- Total manager time: ~6 hours per learner, excluding the pre-reads and post-forms.
After (per learner):
- Pre-work and digital practice (async, ongoing)
- 6 × monthly peer sessions (2 hours each), no separate "module" delivery
- 3 × manager application conversations (30 minutes each, no forms, focused on a single commitment per conversation)
- Midpoint synthesis (async, 30-minute video debrief from the facilitator)
- Total manager time: ~1.5 hours per learner.
Same commercial outcome. 75% less manager time. Higher adoption. Better manager sentiment toward the program.
Where to start
Look at your largest active blended program. Count the manager time it demands. If it is above two hours per learner per month, run the redesign exercise, identify the duplicate touches, the performative moments, and the output-free meetings.
Publish the redesigned version as a pilot. Measure the same three behaviours. Compare.