Our process is three weeks. But here’s the thing that surprises people: only one of those weeks is us building.
The other two weeks are you reviewing and we’re refining based on your feedback.
The Standard Industry Problem
A lot of people will create a storyboard, then a prototype, then a draft. With you giving feedback at each point. You might get a few days and have to scramble to get feedback from everyone. You might get a week to review each thing they send you. That blows out your project timeline.
What we’ve found to work best for everyone is creating the draft up-front. A storyboard doesn’t give you an ida of the look and feel. A prototype isn’t a complete representation of what your course will look like.
So we build the draft and give to you to review the whole thing in context. We give you more than enough time (two weeks!) where you can review and request changes.
Changes we’ll make during that time so you’re always looking at the most recent version.
Why Two Weeks Actually Matters
Get real feedback. Gather all the stakeholders. Bring in SMEs. Give it to some of the people who’ll actually take it.
Catch the real problems. One week isn’t enough time to actually review something properly. It may sound like it but you have other things on your plate. No one’s full time job is reviewing eLearning. You need time to go through it. Show it to your team. Let it sit for a day. Follow up on questions with internal teams. Come back and look again. Two weeks give you flexibility for all of this and let’s you fit the review around your schedule.
Think about what’s missing. It’s not just “does this explain the topic correctly?” It’s “does this make sense for how our people actually work?” “Is this missing a scenario we deal with every day?” “Should we add an example?” These questions take time to answer.
Make actual decisions. Stakeholders are busy. Getting three people in a room to decide on something takes time. Two weeks gives people time to think, consult, decide.
The Unlimited Revisions Part
Here’s where it gets interesting: during those two weeks, you get unlimited revisions.
Not “one round of feedback and that’s it.” Unlimited.
You send feedback on Monday. We implement it. One you see it you realise you forgot something else needs to be added. We add it.
This is how you actually get a course that works. Not through a vendor reading your mind on day one. But through iteration. Testing ideas. Seeing what lands and what doesn’t.
Why This Actually Works
Two weeks of review time and unlimited revisions means:
You get a course that actually solves your problem. Not what we think you need. What you actually need.
Your team is invested. They’ve been in the process. They’ve seen changes happen based on their feedback. They’ve contributed. When it’s done, they actually want it to succeed.
You catch problems before launch. Real testing happens in those two weeks. You find the confusing parts. You find the gaps. You find the tone issues. You fix them before people start taking the course.
It actually ships on time. Because we build for one week and refine for two, we finish on week three. No delays. No extensions. The review time is baked into the timeline.
The Real Reason We Do This
We give you two weeks of review time because we’re not trying to optimise to spend the least amount of time on your course. We’re optimising for course quality.
One week to build. Two weeks for you to make sure you get exactly what you want.