Build & Craft
New to eLearning Development? Build in Passes Instead of Perfecting Every Screen
A simple development workflow for instructional designers and eLearning developers who want to turn a storyboard into a working course without getting stuck in endless screen-by-screen polish.
When you are new to eLearning development, building a course can feel like a lot of decisions happening at once. You may be placing content, choosing layouts, building interactions, setting triggers, naming layers, checking visual consistency, and trying to make everything look polished before the full course is even built.
That can slow the project down quickly. If you try to perfect every screen as you build it, you may spend time polishing something that changes later.
Start with a simple build workflow
A good workflow helps you build the right things in the right order.
Development gets easier when you stop treating every screen like a final design on the first pass. Instead, think of the course as something you build in stages.
Before you start building, set up a few basic guardrails so you are not making the same decisions over and over again.
- Layouts: Choose a small set of screen types you can reuse.
- Components: Decide how common items will look, such as buttons, cards, callouts, tabs, and feedback panels.
- Design rules: Keep your type sizes, colors, spacing, and button styles consistent.
- File organization: Name assets, layers, and exports clearly so updates are easier later.
These choices create a simple build kit. The build kit does not need to be fancy. It just gives you a course system to work from before you start customizing individual screens.
Build in passes: rough first, refined later
Pass-based building helps you avoid polishing the wrong thing too early.
One of the easiest ways to lose time during development is to build and polish at the same time. You finish one beautiful screen, then the content changes. You spend time aligning a layout, then realize the interaction needs to be rebuilt. You adjust small visual details before the course structure is even stable.
A pass-based workflow helps you focus on one type of work at a time. First, you get the course structure in place. Then you make it function. Then you polish the experience.
Example: If a storyboard includes a scenario interaction, do not start by perfecting the colors, icons, and animation timing. First, build the basic screen structure. Next, make sure the choices, feedback, and branching work. Then polish the spacing, timing, and visual design.
Use this table as a practical development guide. Move through the course one build pass at a time, and let each pass have a clear purpose.
| Build pass | Goal | What to focus on | What to avoid |
|---|---|---|---|
| Pass 1: Structure | Get the course on the page or stage. | Screen order, rough layouts, placeholder media, basic navigation, content placement, and major screen types. | Do not spend too much time on perfect spacing, final animation, or tiny visual details yet. |
| Pass 2: Function | Make the course work. | Buttons, links, triggers, states, layers, branching, feedback, scoring, completion, and interaction logic. | Do not assume an interaction works because it looks right. Test the actual learner path. |
| Pass 3: Craft | Make the experience feel clear and consistent. | Alignment, spacing, typography, button consistency, image quality, motion, microcopy, audio timing, and visual polish. | Do not redesign every screen from scratch. Use your layouts, components, and design rules. |
| Pass 4: Prep for review | Get the course ready for meaningful feedback. | Basic cleanup, obvious bugs, missing instructions, incomplete screens, and anything that would distract reviewers. | Do not use review as the first time you check whether the course works. |
This approach keeps development moving. It also helps you know what “done for now” means at each stage, which is especially helpful when you are building under a deadline.
A quick build check before you move on
Use this when you are not sure whether to keep building or stop and fix something.
As you move through the build passes, you will find issues. Some need to be fixed right away because they affect the rest of the build. Others can wait until the craft or review-prep pass.
- Structure: Are all major screens, sections, and interactions represented?
- Function: Can the learner move forward, interact, receive feedback, and complete the experience?
- Consistency: Are repeated elements using the same styles and patterns?
- Clarity: Does each screen tell the learner what to understand or do?
- Cleanup: Is anything incomplete enough that it would distract a reviewer?
Wrap-up
eLearning development does not have to be a screen-by-screen perfection sprint. A simple build kit and a pass-based workflow can help you move from storyboard to working course with less rework.
Start rough, make it work, then craft the experience. That order protects your time and helps the final course feel more consistent, intentional, and ready for review.