Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

E-learning course UI design, prototyped and agreed before your developer builds it

We design the screens of custom e-learning courses: how each screen is laid out, how learners move through the course and see their progress, and how controls, questions and feedback respond to what learners do. Your team clicks through each course as a Figma prototype on desktop and phone before your developer builds it and packages it for your LMS.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml works as an outside design team on the course interface: layouts, interactive components and their states, motion specs, prototypes, the Figma handoff and a review of the build. Learning objectives, content and assessments stay with your instructional designers, and packaging and LMS setup with your developer.

What we design for each course

Your instructional designers decide what a course teaches and in what order. We work out how that plan looks and behaves on screen, and your team reviews each part in Figma before anything is built.

Solution
Websites
  • The course idea, sketched screen by screenWhen a course is built around one idea, such as a case to solve or a story told in chapters, we sketch how it plays out on screen: where learners start, what they do at each step, how they move on and how they know where they are. Sketches come before detailed screens, while changes are still quick to make.
    01
  • Layouts for each kind of course screenOpeners, content screens, activities, feedback, results and the closing summary each get a layout that sets where text, media, controls and progress sit. Layouts are drawn at desktop and phone widths, plus tablet when your learners use one, and sized for the window your LMS opens the course in.
    02
  • Interactive components in every stateNavigation, progress indicators, answer options, drag-and-drop items, hotspots and feedback panels are drawn in each state a learner can meet: default, hover, keyboard focus, selected, disabled, correct, incorrect and complete. Your developer can see what each click or answer should change on screen.
    03
  • A component library for course screensOne Figma library holds every component, built from your brand guidelines or your art director's visual direction. Colors, type sizes and spacing are saved in the file as variables and styles, each component has a variant for every state, and all course screens are assembled from the library.
    04
  • Clickable prototypes at desktop and phone widthsScreens are linked into a Figma prototype that follows the course's main path and every branch where a learner's choice changes what comes next. Filled with draft course text, it shows missing steps and unclear instructions while they can still be fixed in Figma.
    05
  • Motion specs with a reduced-motion versionFor screens that animate or reveal content as learners scroll, we specify what moves, what triggers it, how long it takes and what happens when a learner scrolls back up. Each animation has a reduced-motion version for devices set to show less movement, and every screen still makes sense when nothing moves.
    06
  • Keyboard routes and focus orderEach interaction that works with a mouse or a finger also gets a keyboard route: the focus order, what each key does and where focus goes after feedback appears. The file also shows where screen reader labels and text alternatives go, for your writers to fill in and your testers to check.
    07
  • Build notes and a walkthrough for your developerYour developer receives the Figma file with notes on states, spacing, motion and keyboard behavior, exported icons and images, and a walkthrough. We answer their questions while the course is built and review it before release.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What your course team provides

  • The learning planLearning objectives, the order of sections and activities, and draft text for each screen, from your instructional designers. The screens are designed around this text instead of placeholder copy.
    01
  • Visual directionBrand guidelines, fonts and any direction your art director has set for the course, such as mood boards or sample screens.
    02
  • Build and delivery detailsWho builds the course and with which tools, how it is packaged, for example as SCORM, and which LMS it has to run in. These decide the screen sizes, the window the course opens in and the progress it can show learners.
    03
  • Accessibility standard and testersThe accessibility standard and level each course has to meet, and who on your team will test the built course. Your standard decides which keyboard, focus and motion behavior we draw; testing the build and signing it off stay with your team.
    04
  • Courses already releasedIf you have released courses before, access to one or recordings of it, with any notes on where learners got stuck. We keep what works and build the library around the interactions you use most.
    05
  • Who signs off each roundSomeone with the final say on each design round, who gathers the course team's comments first, so each round closes with one decision.
    06

How we design a course with your team

  1. [Agree the first course]

    We go through the learning plan, visual direction and delivery details with your instructional designers and developer, and agree which screens, interactions and widths the first course needs.

    Step 01
  2. [Sketch the main path and branches]

    Sketches of how learners move through the course go to your instructional designers, who confirm that each step matches the plan before visual design starts.

    Step 02
  3. [Turn sketches into course screens]

    Approved sketches are redrawn as full course screens from the component library. Each screen shows its components' states and the keyboard route through it.

    Step 03
  4. [Prototype and revise]

    The screens are linked into a prototype at desktop and phone widths. Your team reviews it in rounds, and we revise after each round until your approver signs off.

    Step 04
  5. [Add specs and hand off]

    Motion specs and developer notes are added to the approved screens, and we walk your developer through the file.

    Step 05
  6. [Review the build]

    We go through the built course on desktop and phone, compare it with the prototype, including its motion and reduced-motion versions, and send your developer each difference with a screenshot and the expected result.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions about e-learning course UI design

Do you write the course content or design the assessments?
No. Learning objectives, course text, activities, assessment questions and their scoring rules come from your instructional designers. We design how each activity looks and responds, and tell them when an activity is hard to complete on screen.
Do you package the course as SCORM or set it up in our LMS?
No, your developer does both. Before design starts, we ask your developer how the LMS opens the course, how learners return to the screen where they stopped, and which progress and completion details the course reports, so the screens match what will be built.
Can one of your designers join our course team full time?
No. We take on agreed courses, or parts of a course, as an outside team. We design in your team's Figma files and join reviews with your instructional designers, art director and developer, but we don't fill a full-time or embedded seat on your team.
Can you confirm that a course meets WCAG?
No. We don't audit, test or certify courses against WCAG or any other accessibility standard. Your team names the standard each course has to meet and tests the built course against it. Our files show your testers what each interaction should do with a keyboard and with reduced motion, so they can compare the build with the design.
Who makes the animations, illustrations and video?
We specify motion and can show its timing in short prototype animations, and your developer writes the animation code. Illustrations, photos, audio and video come from your team or your art director, and we design the screens around them.
Can you design drag-and-drop, branching or scroll-based activities?
Yes, once your developer confirms they can be built with your course tools. We check each one with your developer before designing it in detail. If one can't be built, we propose a different interaction for the same activity, for your instructional designers to approve.
Can later courses reuse the first course's design?
Yes. Each new course starts from the component library made for the first one. Its new interactions are designed and added to the library, so learners who take several of your courses find the same controls in the same places.
Do you design course screens for phones?
Yes. Phone layouts are part of every course, and the prototype is reviewed on a real phone. How the built course behaves on a phone also depends on your LMS: some open courses inside their own app or in a smaller window, so your developer confirms how yours does before design starts.

Browse more of our interface and journey design

Read about the web apps, sales journeys and websites we designed, and how their screens and components were planned.

See all case studies