[ eLearning - Graphic design - Web design - Multimedia ]
Let's build a course.
You have the storyboard. Now you need to build. the course. Get the development support to turn it into a polished, functional Storyline course.
The next step...
Okay, you've done all the hard thinking. You've defined the learning objectives, the storyboard is signed off, and the content is ready for the next phase. The only thing missing is someone who'll take it from there, and actually build something that does all your work justice.
Coming from a background in graphic design and with my focus on eLearning + multimedia development, I genuinely care about what things look like, how interactions feel, and whether the finished course reflects all that went into designing it. I don't cut corners on the details, because the details are usually what your audience will notice.
Here's who I typically work with
Instructional designers and eLearning agencies with an approved storyboard and a build to deliver.
Teams looking for a developer they can trust to get on with the work without needing to manage every step.
Professionals whose clients expect a polished course and who need someone who cares about the details.
Teams at capacity who need an extra pair of hands to keep a project moving.
People who value both design and development and want a developer who understands both.
What you can expect from me
The course will look polished.
I notice when something is two pixels off, when colors aren't quite consistent, or when a font weight throws off the hierarchy.
The course will function properly.
I don't just build what's on the screen. I pay attention to how interactions behave, how the course flows, and whether everything works as intended.
The project will stay on track.
Your deadline is my deadline too. I keep projects moving, communicate early when something needs attention, and deliver work that's ready for review.
I won't add to your plate
You don't need to check in constantly. I work independently, communicate when it matters, and flag issues before they become problems.
How we work together
This is my usual process, but I know every team has its own way of working. If there’s already a process in place that works well, I’m happy to fit into it. I’m adaptable, but I like to keep the things that make a project run smoothly: a clear scope, good communication, and a process that allows me to do the work properly.
01
Brief
Share your storyboard, assets, brand guidelines, and any technical requirements. The more context you give me upfront, the smoother the build.
02
Scope + Estimate
I’ll review everything, flag any questions, and come back with the scope, timeline, and project rate. Once we’re agreed on the details, we’re ready to get started.
03
Proof of Concept
Next, I present a proof of concept to make sure we're on the same page before I move into the design. If we're not, here's where we fix that and come again. This step saves us both time and money.
04
Build
I develop to the storyboard and share progress at agreed milestones.
05
Review + Iteration
I’ll pass the build on to you to review and share your feedback, then I’ll make the necessary changes before we move on to final QA.
06
QA + Delivery
Before delivery, I run through the course to check the interactions, navigation, audio, visuals, and functionality. Then I’ll hand over the final files, neatly organized and in the formats we agreed on.
Selected works
