Why you need a High-Level Design

Here's a scenario that plays out in organisations everywhere: a subject matter expert dumps a massive folder of content on your desk; policies, procedures, PowerPoints, PDF guides, maybe a few videos. "We need this as eLearning," they say. "How long will it take?"

If your first instinct is to open your authoring tool and start building slides.

Stop!

You're about to waste weeks of your life creating something that doesn’t work.

What you need first is a high-level design. Not detailed storyboards. Not polished prototypes. A strategic blueprint that answers the fundamental questions about what you're developing and why.

What Is a High-level design?

A high-level design is your architectural plan for the learning experience. It's where you make the critical decisions that will determine whether your eLearning succeeds or fails:

• Which content really needs to be included (and what can be cut)
• How that content should be sequenced to build understanding
• What instructional methods will work best for each learning objective
• Which media and interactions will support learning without creating distraction

Think of it as the bridge between your analysis and your development. Analysis tells you what the problem is and what learners need. High-level design tells you how you're going to solve it.

Why you can't skip this step

Without a high-level design, you're essentially building a house by nailing up whatever materials happen to be lying around. Sure, you might end up with something that looks like a house, but don't be surprised when the roof leaks and the doors don't fit.

You'll include too much (or the wrong things)

When you jump straight into development, every piece of content feels important. The SME says it's all essential. You don't have the framework to push back so you include everything, and your 20-minute course balloons into a 90-minute information overload that nobody finishes.

A high-level design forces you to be ruthless about content selection. What supports the learning objectives? What helps learners perform differently? If it doesn't serve a clear purpose, it doesn't make the cut, no matter how interesting the SME thinks it is.

Your content will be in the wrong order

Content that makes perfect sense to an expert often makes no sense to a learner. Experts think from years of experience; learners need to build understanding step by step. Without deliberately planning the sequence, you end up presenting information in whatever order it was given to you, which is rarely the order people need to learn it.

A high-level design lets you map out a learning journey that builds logically. You identify prerequisite knowledge, plan how concepts connect, and create a structure that moves from foundation to application. This isn't something you can figure out while you're developing, you need to see the whole picture first.

You'll default to the easiest method (not the best one)

When you design on the fly, you fall back on whatever's quickest: text slides with narration, followed by a knowledge check. Rinse and repeat. It's not that you don't know better methods exist, it's that you don't have time to think about them when you're already deep in development.

A high-level design gives you space to match methods to objectives. Does this need scenario-based practice? A branching simulation? A video demonstration? A simple checklist? When you plan this strategically, you can choose the approach that works instead of the one that's just convenient.

You'll waste time on the wrong media

Here's what happens without a high-level design: you spend three days creating an elaborate animated infographic that looks impressive but doesn't help anyone learn. Meanwhile, the critical practice activity gets five minutes and a basic multiple-choice quiz.

High-level design forces you to think about media purposefully. Where will visuals genuinely aid understanding? Where is audio necessary? Where would interactivity make a difference? You allocate your development time and budget to the elements that matter, not the ones that just look good in a demo.

What goes into a high-level design

A solid high-level design doesn't need to be elaborate, but it should answer these questions clearly:

Content selection and scope: What's included, what's excluded, and why. This is where you justify your decisions to stakeholders and show that you've made strategic choices, not arbitrary ones.

Learning architecture: How is the content organised? What's the overall structure? If you're breaking things into modules, what's the logic behind that division?

Sequencing and flow: What order will learners encounter content, and why does that order support learning? Where do you build foundational knowledge? Where do you introduce complexity?

Instructional approach: For each major section or objective, what method will you use? Presentation? Demonstration? Practice? Problem-solving? You're not writing detailed interactions yet, you're mapping out the strategy.

Media and interaction strategy: Where will you use video, animation, branching, or other rich media? What's the purpose of each? This keeps your development focused on what serves learning rather than what looks impressive.

Assessment approach: How will you know if learning happened? What will you measure, and how? This includes both formative checks throughout and any summative assessment at the end.

The payoff

When you invest time in high-level design, development becomes dramatically easier. You're not making it up as you go, you're executing a plan. You know what you're building and why. When stakeholders ask for changes, you can evaluate them against the design decisions rather than just accommodating whatever the latest request is.

More importantly, you end up with eLearning that works. The content is relevant. The sequence makes sense. The methods match the objectives. The media supports learning. Nothing is there by accident.

It's not extra work—it's essential work

Some people see high-level design as an extra step that slows them down. But it’s the step that keeps you from wasting weeks building the wrong thing or building the right thing badly.

Yes, it takes time upfront. But that time saves you from:

• Endless revision cycles when stakeholders realise the course doesn't work
• Massive rework when you discover halfway through that your structure is wrong
• Learners who disengage because the content is poorly sequenced or overwhelming
• Reviews where SMEs question why you included or excluded specific content
• Post-launch disappointment when completion rates are terrible

High-level design isn't about creating perfect documentation. It's about thinking strategically before you commit resources. It's about making informed decisions based on your analysis rather than gut feelings or convenience.

It's the difference between being a developer who builds what they're told and being an instructional designer who solves learning problems.

Start with strategy, not software

The next time a pile of content lands on your desk with a request to "turn it into eLearning," resist the urge to start building. Open a document instead. Map out what needs to happen. Make the hard decisions about content, sequence, method, and media while you still have the flexibility to get it right.

Because the best eLearning isn't developed, it's designed.

Need help creating a solid high-level design for your eLearning project? My Instructional Designer's Starter Pack includes templates, guides, and practical tools to help you move from analysis through storyboard to development with confidence. Stop winging it and start designing strategically.

Find out more about the Instructional Designer's Starter Pack and how it can transform your eLearning projects.