Over recent years, I’ve had the opportunity to engage with block delivery from a range of different perspectives. As a senior leader, I shaped a studio-based engineering curriculum built around block delivery from its inception at NMITE, a new UK institution. I’ve worked with colleagues across the sector through workshops, consultancy, and advisory work focused on curriculum transformation and educational innovation. More recently, a Visiting Professorship in STEAM Education and Curriculum Innovation at Birmingham City University has provided another opportunity to explore how institutions navigate large-scale educational change through the Reimagining Engineering project.

Across these environments, I observe that academic teams often get caught up in immediate operational logistics: Can students cover enough material in seven weeks? How do we teach technical subjects like mathematics in an intensive block? What happens when a student misses classes?

These are understandable anxieties, but they focus on operational questions rather than curriculum design. The key reflection I find myself returning to is this: these are not really block delivery questions at all. They are questions of good curriculum design.

Within traditional, semester-based structures, it is remarkably easy to gloss over fundamental issues of assessment, student engagement, feedback, and programme coherence. One real power of block delivery is that it acts as a catalyst. It strips away the buffer of a traditional 12-week semester and forces us to confront the very curriculum design questions that may have been easier to skirt around in the past.

When you shift the conversation from logistics to learning design, scheduling friction gives way to deeper strategic choices. Drawing on several years of leading, studying, and supporting curriculum transformation, here are six reflections to consider in a transition to block delivery that moves past operational friction to achieve genuine educational transformation.

1. We’re often asking the wrong questions about block delivery

When institutions begin exploring block delivery, the default impulse is to ask how existing modules can be fitted into a seven-week unit; how our existing programme should be adapted into a block structure. It’s an understandable starting point, but it reveals an underlying assumption: that block delivery is primarily a scheduling challenge.

The institutions that gain the most from block delivery approach it differently. They use the transition as an opportunity to reconsider the purpose of the learning experience itself, and design a programme for block delivery. Rather than asking what content must be retained, they focus on what students should know, understand, and be capable of doing by the end of the block. Once the conversation starts there, the emphasis shifts from compression to design.

Institutions that approach block delivery as a curriculum redesign challenge discover possibilities that are simply not visible when the focus remains on timetabling. For programme teams, three fundamental questions guide success:

2. Students experience programmes, not modules

One of the most common design challenges I encounter in block-delivered curricula is establishing and maintaining programme coherence, especially over time. Without intentional design, students can easily experience learning as a sequence of disconnected units: complete the block, submit the assessment, and move on.

Yet many of the capabilities we value most – from critical thinking and communication, to professional judgement and systems thinking – develop over time through repeated application in different contexts. Students often struggle to make those connections for themselves. As a result, programme teams need to work much harder than they initially expect to make the bigger picture visible. Ultimately, success depends on whether students experience a coherent developmental journey across the programme as a whole. Programme coherence is therefore not a by-product of block delivery. It is something that must be deliberately designed, often requiring levels of programme-level thinking, team-working and collaboration between academic staff that are unnecessary in more modular approaches.

3. Capability development is often more important than content coverage

Higher education has a longstanding habit of asking what should be taught. Increasingly, I think the more important question is what students should become capable of doing.

Curricula have a natural tendency to accumulate content. Artificial intelligence, sustainability, entrepreneurship, and digital skills all make compelling cases for inclusion, but removing content is often much harder than adding it. Over time, curricula become crowded and the space available for application, experimentation, and reflection begins to shrink.

Yet when employers talk about graduate preparedness, they rarely focus on whether students have covered one additional topic. More often, they talk about problem-solving, communication, teamwork, judgement, and adaptability. Those capabilities develop through use rather than exposure. This is why teaching skills “just in time” – at the point of need within an authentic problem – is considerably more effective than teaching them “just in case” months before they are applied.

Engineering provides a useful example. Traditional curricula often separate mathematics into standalone modules, requiring students to learn concepts in one context and apply them much later in another. In block-delivered programmes, mathematics must instead be integrated throughout the curriculum and taught at the point of need, allowing students to apply concepts immediately to engineering problems. The result is not simply a different timetable, but a different philosophy of curriculum design.

4. The most important question is: what are students doing?

Many curriculum discussions focus on what academics are teaching. Perhaps they should focus more on what students are doing.

When reviewing curriculum designs, I often ask a deceptively simple question: what will students actually be doing during the learning experience? Will they be investigating, discussing, creating, testing, analysing, and reflecting? Or will they primarily be listening?

This is not an argument against lectures; expert explanation remains valuable. But explanation itself is not learning. Learning emerges through what students do with knowledge. One of the most useful features of block delivery is that it makes this dynamic explicit. In intensive learning environments, it quickly becomes apparent whether students are actively engaging with ideas or simply receiving information. One of the hidden benefits of block delivery is that it forces programme teams to confront that distinction directly.

5. Feedback is only feedback if students recognise it

Few topics generate as much discussion in higher education as feedback. In traditional semester models, feedback is too often post-hoc: written comments delivered weeks after an assessment is submitted, when the opportunity to apply that learning has already passed.

Block delivery structurally disrupts this pattern. By concentrating contact hours and shifting time away from passive lectures toward active studio, lab, or project-based work, block environments create far more frequent points of engagement between students and teaching teams. In these active settings, feedback becomes continuous and immediate – occurring naturally through design critiques, coaching conversations, project reviews, and informal discussions. This immediacy allows students to correct course while learning is still in-flight, which is precisely when feedback is most impactful.

The challenge, however, is one of recognition. Because these feedback loops happen dynamically within active sessions rather than as formal written comments on a rubric, students do not always recognise them as feedback. A member of staff may feel they have spent hours giving rich, developmental guidance; a student may think they simply had a casual conversation. Unlocking the true potential of feedback in block delivery therefore requires us to make it explicit. Simply signposting these active interactions as feedback can make a remarkable difference in how students perceive, value, and act upon it.

6. Design for reality, not for the ideal student

Almost every discussion of block delivery eventually reaches the same operational concerns. What happens if students miss classes? What happens when industry partners change plans? What happens when activities take longer than expected?

These are important questions, but they are not really questions about block delivery. They are questions about reality.

Educational innovation can sometimes be designed around ideal conditions: perfect attendance, flawless planning, and unlimited capacity. Real programmes rarely operate that way. Students fall behind, technology fails, staff become unavailable, and external partners change plans. The more institutions I work with, the more convinced I become that resilience is a design principle rather than an operational afterthought. Successful programmes intentionally create recovery routes, think about late entrants, and build flexibility into their design from the outset.

Final thoughts: from block structure to educational transformation

The more conversations I have about block delivery, the less convinced I become that they are really conversations about blocks. Very quickly, the discussion moves to assessment, feedback, student engagement, programme coherence, graduate capability, and curriculum design. In other words, the conversation becomes one about broader educational transformation.

This helps explain why block delivery can feel both exciting and unsettling. It surfaces questions that may have existed for years but which were easier to avoid within traditional structures: What assumptions about teaching and learning is block delivery exposing? How do students build capability rather than simply accumulate knowledge? Are we redesigning a timetable, or rethinking the educational experience itself?

Block delivery does not automatically answer those questions. What it does do is create the conditions in which they become much harder to ignore.

Ultimately, the most interesting conversations in higher education are rarely about whether a teaching period lasts seven weeks, ten weeks, or a semester. The real challenge for institutions is not whether they can implement a block timetable. It is whether they are willing to rethink the educational assumptions that timetable exposes.