Student-centred course design starts with the outcome, not the lecture

Education is often described as student-centred while still being organised around the lecturer: their timetable, their preferred sequence, their slides, and everything their expertise makes it possible to say.

This is understandable. Expertise is essential. But expertise and learning are not the same product.

A course becomes student-centred when the production question changes from “What does the expert want to convey?” to “What should this learner be able to understand, decide, or do—and what will help them get there?”

TL;DR

• Start with learner outcomes and evidence, then decide what content earns a place.
• Use production to refine an expert’s explanation across several iterations.
• Give learners control over pace, repetition, format, and optional depth.
• Design questions for synthesis and application, not only content checks.
• Keep expert live sessions for interpretation, feedback, and questions created by understanding.

Expertise is the source, not the structure

An experienced specialist sees connections that a beginner cannot yet see. That is precisely why “simply explaining the topic” can fail: the expert may skip hidden steps, use familiar language too quickly, or organise material according to the discipline rather than the learner’s task.

In a live lecture, the explanation is produced under time pressure. A strong presenter can adapt, but the room still receives one path at one speed. Some questions expose gaps; many remain unasked because learners do not yet know what they have misunderstood.

Asynchronous production creates a different opportunity. Before release, a team can:

1. define the learner and the real-world outcome,
2. map the decisions and prerequisite knowledge behind that outcome,
3. record or script the expert’s clearest explanation,
4. test it with representative learners,
5. identify missing steps and avoidable jargon,
6. revise the explanation, examples, visuals, and practice, and
7. measure where released learners hesitate or answer incorrectly.

The expert remains central. Production makes their knowledge more reachable.

Work backwards from what the learner must do

Suppose a finance expert is creating a course for founders. A lecturer-centred outline might follow the expert’s field: accounting principles, statements, ratios, forecasting, and controls.

A learner-centred design starts with situations:

• Can the founder distinguish profit from available cash?
• Can they identify the assumptions driving a forecast?
• Can they recognise when growth creates a funding problem?
• Can they ask a useful question when a number looks wrong?

From there, the team can decide what evidence would demonstrate competence, what practice would create that evidence, and only then which explanations are necessary.

This is not “making the content easier” or reducing standards. It is removing content that serves the speaker’s completeness more than the learner’s performance, while making the essential reasoning clearer and more demanding.

Pace and repetition reduce avoidable differences

Learners arrive with different vocabulary, experience, language fluency, confidence, schedules, and access needs. A fixed live pace turns those differences into a race.

Async cannot remove every inequity, but it can stop treating speed as a proxy for ability. A learner can:

• pause an explanation,
• replay a difficult step,
• read a transcript or use captions,
• inspect an example for longer,
• use an optional prerequisite lesson,
• skip material they can already demonstrate, and
• return when their attention and circumstances allow.

These choices should be designed, not left to a video player’s controls. Clear navigation, short conceptual units, searchable transcripts, downloadable references, and visible prerequisites make control practical.

Questions should help learners produce meaning

“Did you understand?” is rarely useful. It asks learners to judge their own learning at the moment the content feels most familiar.

Better prompts require an observable response:

• “Explain the difference to a colleague without using the two technical terms.”
• “Which fact in this case matters most, and what would you do next?”
• “Give an example from your organisation where this principle would fail.”
• “What assumption are you making?”
• “What would change your answer?”

These are not questions added after production to create the appearance of interactivity. They are part of the explanation. They give learners room to organise knowledge, connect it to experience, and notice what they cannot yet articulate.

Where possible, follow a prompt with a model, rubric, or expert commentary. Open-ended work without a response can preserve misconceptions just as easily as it can encourage reflection.

Prepare asynchronously; explore together

High-level business learning often uses pre-session material so that shared time can begin with a problem rather than a first exposure. The learner studies a case or framework, makes an initial judgement, and arrives ready to compare reasoning.

This is a useful model beyond business schools:

Stage	Learner’s role	Expert’s role
Async preparation	Learn the foundation, inspect the case, commit to a view	Provide a concise explanation and a purposeful prompt
Live exploration	Explain, question, challenge, and revise	Facilitate, probe assumptions, and add context
Async consolidation	Produce a final synthesis and apply it again	Provide feedback, examples, and a route back to weak areas

The async component does not need to imitate a lecture hall. Its job is to make the live component better: participants share a foundation, quieter learners have time to formulate a position, and expensive expert time can be spent on judgement rather than repetition.

Design live questions that come after understanding

In an unprepared session, Q&A is often spent repairing the basic explanation: “What does that term mean?” or “Where do I find the template?” Those are valuable signals, but the course should absorb the answers when they recur.

As the async foundation improves, live questions can move upward:

• “I understand the model; how would it change in a regulated market?”
• “I applied it and found a conflict between these two priorities. How would you decide?”
• “This evidence changed my initial view. What am I still overlooking?”

This is where an expert can shine. The objective is not zero questions. It is fewer questions caused by preventable confusion and more questions created by genuine thought.

Production is a learning-quality process

A camera, platform, and automation stack do not make a course student-centred. The production process does.

Useful review rounds include:

Outcome review

Does every lesson support a stated learner outcome? Is the outcome about performance rather than exposure?

Novice review

Where does a representative learner need an unstated step, definition, example, or pause?

Practice review

Does the activity require the kind of thinking the learner will need later? Can a learner receive meaningful feedback?

Access review

Are captions, transcripts, contrast, keyboard access, readable downloads, and plain navigation treated as requirements rather than extras?

Evidence review

After release, where do learners replay, leave, answer incorrectly, or ask the same question? Analytics are clues, not verdicts: combine them with learner work and conversation.

Every round moves attention away from how polished the expert appears and towards whether the learner can follow and use the expertise.

What student-centred does not mean

It does not mean that every learner gets an entirely personalised course. It does not mean removing difficulty, replacing expertise with popularity, or letting preference determine the curriculum.

It means being deliberate about difficulty. Productive challenge belongs in the decision, explanation, or practice—not in unclear instructions, inaccessible media, irrelevant detours, or a pace the learner cannot control.

Nor can async answer every individual need in advance. Some misunderstandings only become visible in dialogue. Some skills require observation, collaboration, or immediate correction. That is a reason to design a route to people—office hours, coached practice, peer discussion, or expert sessions—not a reason to make every explanation live.

A practical course brief

Before scripting, ask:

1. Who is the learner at the moment they enter? Describe prior knowledge, context, constraints, and motivation.
2. What should they be able to do afterwards? Use a decision or performance that can be observed.
3. What evidence would convince us? Define the scenario, artefact, explanation, or behaviour.
4. What practice produces that evidence? Include feedback and a route to try again.
5. What must the expert explain? Keep what enables the practice; label optional depth.
6. Where does the learner need control? Plan pacing, repetition, accessibility, and prerequisites.
7. Where is another person indispensable? Reserve live time for responsive feedback, ambiguity, and social practice.
8. How will the course improve? Decide what learner evidence the team will review and who owns updates.

Conclusion

Student-centred education is not a tone of voice. It is a sequence of production decisions.

Async gives a course team more time before delivery to examine those decisions, more consistency during delivery, and more evidence afterwards to improve them. It allows the expert’s knowledge to be edited around the learner’s journey rather than asking every learner to adapt to a single performance.

The best result is not a course with no lecturer. It is a course in which expertise is present exactly where the learner needs it—and live human attention is protected for the moments only a human can serve.