Students are reporting that their experience varies substantially between modules on the same programme.
In one module, the structure is clear and weekly expectations are easy to follow. In another, important information is distributed across several locations. Assessment guidance differs in format and level of detail. Activities that appear similar are described differently, while familiar terms are sometimes used to mean different things. Feedback may be timely and purposeful in one part of the programme but harder to interpret or act upon elsewhere.
None of the modules is necessarily poorly designed when considered on its own. Each may have appropriate learning outcomes, defensible assessments and committed educators making thoughtful decisions about their subject.
The inconsistency becomes visible when students move between them.
This creates a learning design problem that cannot be resolved simply by asking whether each individual module meets its requirements. Students experience the programme over time. They must repeatedly interpret different structures, expectations and ways of working, often while trying to understand unfamiliar content and manage competing demands.
There are several defensible ways to respond.
Option One: Standardise Templates and Minimum Expectations
The most direct response is to establish greater consistency across modules.
A programme might adopt a shared module structure, common terminology and agreed locations for essential information. Assessment briefs could follow a standard format. Expectations around navigation, communication, accessibility and feedback could be expressed through minimum requirements that apply across the programme.
Students would spend less time working out how each module operates. Familiar structures could reduce navigational effort and make it easier to locate activities, deadlines, assessment guidance and support. Consistency could also strengthen accessibility by reducing unnecessary variation and giving learners a more predictable experience.
Shared expectations may be particularly valuable when several teams contribute to the same programme. They provide a baseline against which modules can be reviewed and give staff a common starting point for discussing quality.
Standardisation can also make institutional support more effective. If modules use broadly similar structures, guidance and templates can be developed once and applied more consistently. Problems become easier to identify because expectations are explicit.
The risk is that consistency becomes confused with sameness. Disciplines do not all teach in the same way. Modules may require different forms of participation, practice, assessment and feedback. A structure that works well for one type of learning may become restrictive or artificial when applied elsewhere.
Templates can also acquire authority beyond their original purpose. A format introduced to make essential information easier to find may gradually become a rule about how all learning must be organised. Staff may concentrate on completing the template correctly rather than considering what the learning requires. Visible compliance can create reassurance even when the underlying experience remains fragmented.
The initial problem may be inconsistency, but excessive standardisation creates a different risk: local professional judgement is narrowed in pursuit of a surface-level uniformity.
Option Two: Support Module Teams to Improve Their Own Designs
A second response is to retain local ownership while giving module teams stronger support.
Rather than imposing a common structure, the programme could provide design guidance, examples, workshops, accessibility support and opportunities for peer review. Teams would examine student feedback and improve their own modules while retaining the freedom to make decisions appropriate to their subjects and learners.
This approach recognises that those closest to a module often understand its educational purpose best. They know where learners tend to struggle, which activities require flexibility and how assessment relates to disciplinary practice. Improvement can therefore remain grounded in the context of the learning rather than being imposed through a general model.
Supported local development can also build capability. Staff have opportunities to understand why particular approaches work, test alternatives and develop their own judgement. Changes are more likely to reflect genuine educational reasoning when teams are involved in deciding what should improve and how.
This avoids treating variation itself as a failure. Some differences between modules may be purposeful and valuable. Students may benefit from encountering different forms of learning when those differences are clearly explained and educationally justified.
The risk is that local improvement may leave the programme-level problem largely intact.
Each team can make sensible changes while continuing to interpret good design differently. One module may improve its navigation, another its assessment guidance and another its feedback. The individual experiences become stronger, but students may still encounter inconsistent expectations as they move through the programme.
The quality of change may also depend heavily on the time, confidence and resources available to each team. Staff who already have strong design capability may make substantial progress, while those facing greater workload pressures or needing more support may struggle to participate. Variation in staff circumstances can reproduce variation in the student experience.
This response preserves professional autonomy, but it may ask local teams to solve a problem created across organisational boundaries.
Option Three: Design at Programme Level
A third response is to treat the inconsistency as a programme design problem.
Instead of beginning with individual modules, the programme team could examine the learner journey across them. This might include mapping assessments, workload, terminology, expectations, feedback and opportunities to practise or revisit important capabilities. The aim would not necessarily be to make every module look the same, but to understand how they work together. This approach changes the unit of analysis.
A duplicated activity may appear entirely appropriate within each module while creating unnecessary repetition across the programme. Two assessments may be independently defensible but place unreasonable demands on students when scheduled together. A particular term may make sense within one disciplinary context but create confusion when used differently elsewhere. These problems are difficult to see through module-level review alone.
Programme-level design can distinguish between variation that supports learning and variation that creates avoidable friction. Teams can agree where consistency matters, where difference is purposeful and how transitions between modules should be supported. Decisions about shared expectations can then emerge from an understanding of the whole experience rather than from a desire to impose uniformity.
This also creates an opportunity to examine whether responsibility is distributed effectively. If recurring issues cross module boundaries, the programme may need mechanisms through which those issues can be discussed and addressed collectively.
The risk is that programme-level design requires coordination, authority and sustained participation.
Someone needs to see across the modules, bring together the people involved and ensure that agreed changes can be implemented. Module teams may need to reconsider decisions that make sense locally but create difficulties elsewhere. Questions about ownership can become politically sensitive, especially when programme-level coherence is interpreted as interference in academic or disciplinary judgement.
The process also demands time. Mapping the student journey, examining evidence and negotiating shared expectations cannot be reduced to a template or a single workshop. Without clear ownership and decision-making authority, programme-level work can generate discussion without producing meaningful change.
This option addresses inconsistency most directly, but it depends on institutional conditions that individual module teams may not be able to create for themselves.
What Kind of Consistency Do Students Need?
All three responses are defensible because each recognises something important. Standardisation acknowledges that unnecessary variation creates work for learners. Supporting module teams protects contextual expertise and professional judgement. Programme-level design reflects the reality that students experience relationships between modules as well as the modules themselves. The choice cannot be reduced to consistency or autonomy.
The more useful question is where consistency supports learning and where variation remains educationally meaningful.
Students should not need to relearn basic navigation, decode avoidably different instructions or search for information that could be presented predictably. Those tasks consume time and attention without necessarily contributing to the intended learning. Shared minimum expectations may therefore be justified where they reduce unnecessary effort or remove barriers.
At the same time, an institutionally consistent experience does not require every module to use identical activities, structures or teaching approaches. Meaningful differences should remain possible when they reflect the discipline, the learners, the stage of study or the capabilities being developed. The challenge is distinguishing purposeful variation from accidental inconsistency.
That distinction requires more than a template. It requires evidence from across the programme and conversations between the people who influence different parts of the learner experience.
My Judgement
I would begin at programme level, then use the other two responses selectively.
The student reports concern inconsistency across modules, so examining each module separately is unlikely to reveal the whole problem. Programme-level analysis is needed to understand where learners are repeatedly encountering friction, where workload and expectations conflict, and which differences are purposeful rather than accidental.
That does not mean redesigning the entire programme or centralising every decision.
The analysis may show that a small number of shared expectations would remove much of the avoidable inconsistency. It may identify modules that need more focused design support. It may also confirm that some variation is valuable and should be retained, but explained more clearly to students.
Standardisation can then be applied where predictability has a clear educational or accessibility benefit. Module teams can retain judgement where local context matters. Programme-level coordination provides the means to understand the relationship between the two.
This remains a nuanced response because the risks do not disappear. Shared expectations can still become compliance exercises. Local support can still be uneven. Programme-level work can still become bureaucratic or lose momentum. The difference is that the programme becomes visible as a designed experience rather than being treated as a collection of independently acceptable modules.
Students reporting inconsistency are not necessarily identifying a series of isolated module failures. They may be revealing the absence of a level of design that no individual module team can provide alone.
The responsibility therefore cannot sit entirely with templates, module teams or programme leadership. What matters is whether the institution creates the coordination, authority and space needed for decisions made at each level to work together. That is where inconsistency becomes more than a quality problem. It becomes a problem of institutional practice.
Leave a Reply