An exciting new online programme has taken shape. Market research that predicted strong demand has proved correct and thousands of students have enroled before launch. The proposition promises to be both groundbreaking and commercially significant.
Then the build begins to slip.
Content arrives late. Approvals become bottlenecks. Teams wait on one another. Quality checks are compressed, and the fixed launch date draws ever closer. What looked like a strategic success is suddenly at risk.
At this point, institutions often feel forced to choose between moving quickly and accepting compromises or protecting quality and risk missing the moment.
The Agile Execution chapter of Leading with SCALE: A framework for resilient digital higher education challenges that assumption. Speed and quality are not natural opposites. More often, it is rigid processes that make them appear that way.
The full SCALE guide sets out five interconnected pillars for building sustainable digital capability: Strategy First, Collaborative Design, Agile Execution, Learner-Centric Quality and Evergreen Innovation. Strategy establishes the direction and Collaboration creates shared ownership. Agile Execution turns that alignment into progress without allowing urgency to erode standards.
The problem is not always the deadline
Higher education projects rarely unfold in a straight line because subject matter experts (SME) are balancing competing responsibilities and approval cycles can be complex. Requirements change, feedback arrives late and dependencies appear only once the work is under way.
Yet many digital learning projects are still managed through linear processes in which one stage must be fully completed before the next can begin. When a delay occurs early in the chain, every team downstream feels the impact.
That is when pressure builds, and quality assurance starts to feel like a final obstacle rather than an integral part of development.
Agility offers a different way of working.
“Agile execution isn’t so much about asking people to work faster as about creating a process that can absorb change,” says Arlene Stewart, Director of Academics and Operations at OES UK. ” Applied well, agility exposes risks earlier and keep progress moving without losing sight of academic quality.”
Agility is structure, not haste
First coined in 2001 as an innovative and effective software development methodology, the term “agile” is sometimes misunderstood as shorthand for speed, informality or constant change.
Within SCALE, it means something more disciplined: breaking complex work into manageable stages, creating regular opportunities for review and allowing different areas of the project to progress in a coordinated way.
The need for this is particularly acute in UK higher education. Nine in ten vice-chancellors report unprecedented uncertainty combined with a desire for rapid growth, yet many institutions continue to rely on linear planning and sequential delivery models. The SCALE guide’s central insight is that agility is less about accelerating every task than about building the resilience to respond when plans inevitably shift.
The difference becomes visible when something goes wrong.
In a rigid process, one missing approval can stall an entire build. In an agile one, teams have a clearer view of dependencies, and work can continue in parallel. This allows problems to be identified while they are still manageable rather than during a high-stakes review.
Where traditional delivery begins to break down
The SCALE Guide was developed by OES based on over 15 years of working with institutions. In that time, we’ve seen the same patterns emerge from delayed content and changing requirements to variable academic staff availability.
The Agile Execution chapter explores how institutions can redesign those workflows and shows how institutions can create momentum without stripping out the reflection that quality depends on.
An agile project reorganises the work so teams can:
- Keep design, media production and quality assurance moving in parallel, reducing unnecessary waiting between teams.
- Gather and apply feedback throughout development, rather than relying on a single high-stakes review at the end.
- Identify risks and bottlenecks earlier, before they spread across the wider programme.
- Respond to changing priorities or delays without losing momentum, visibility or control.
- Protect academic and quality standards at every stage, rather than treating them as final checks before launch.
“Leaders should be wary of treating every delay as a performance problem,” says Andrea Burrows, Managing Director of OES UK. “Sometimes the real issue is the operating model.”
The link between agility and quality
One of the most valuable benefits of applying the lessons in the Agile Execution chapter of SCALE is that more agility is often a strong foundation for better quality.
When reviews, multimedia improvements, accessibility checks, and technical testing are postponed until delivery is almost complete, problems become more expensive and disruptive to fix. A seemingly small issue in an assessment or media asset may already have been repeated across an entire programme.
Agile delivery brings those checks forward. By developing in manageable stages and gathering feedback throughout the build, academic staff can engage with tangible examples rather than abstract plans, while design, media and quality teams can refine their work before inconsistencies spread.
This is how Agile Execution builds naturally on the earlier pillars of SCALE. If strategy defines the intended outcome, and Collaborative Design ensures optimal academic expertise, agility then creates repeated opportunities to test whether that shared intent is being translated into the learning experience.
This lays out the groundwork for the next pillar, Learner-Centric Quality. Quality is not a separate layer applied once delivery is complete. It is the cumulative result of decisions made throughout the process.
Case study: Agile Execution in practice
The SCALE guide brings agility to life through a high-stakes project involving a globally renowned business school.
The institution needs to move its flagship MBA and Executive MBA programmes into a digital format under significant time pressure. The resulting student experience has to preserve the academic rigour and reputation associated with a premier institution.
Rather than treating the work as one large, high-risk build, the project is delivered in phases. Priorities are aligned with cohort launch dates, essential student entry points are established early and more complex course elements move through structured development and review.
Between September 2020 and March 2021, more than 25 full course builds are completed while meeting every key academic milestone. The online programme becomes a flagship for the institution.
The result demonstrates what becomes possible when delivery is designed for complexity rather than forced through a rigid sequence.
Could your process absorb disruption?
The SCALE guide encourages institutions to assess not only whether a project plan exists, but whether that plan can withstand real-world conditions.
Can work continue when an academic approval is delayed? Are teams able to identify risks before they affect launch? Can priorities shift without derailing the wider programme? Are quality and accessibility built into the process, or left until the end?
The guide’s Agile Execution checklist helps leaders and delivery teams examine these questions across workflow design, academic engagement, quality safeguards and adaptability. Rather than prescribing one fixed methodology, it offers a way to identify where current processes may be creating avoidable delays.
Agility turns intent into momentum
Imagine the same high-stakes launch under a different operating model. Content is still evolving. Academic approvals still require care. Priorities still shift. But the project is no longer dependent on a single linear sequence where one delay slows everything that follows.
Instead, teams can see dependencies early. Design, media production and quality assurance move in parallel. Feedback is gathered while changes are still manageable. Accessibility and quality checks are built into the process rather than compressed at the end. When pressure rises, the work bends without breaking.
That is what Agile Execution makes possible. It turns strategic intent and shared ownership into visible momentum without treating speed and quality as competing priorities.
But it is still only one part of the framework. Speed without learner-centred quality can produce inconsistency. Efficient delivery without adaptability can create systems that date quickly. The value of SCALE lies in how its five pillars operate together.
Download the full Leading with SCALE guide to explore the Agile Execution chapter and discover how all five pillars combine to create digital learning that can move at pace without compromising quality.
