Designing a Structured Onboarding System for SV4C’s Teaching Staff

Replacing static documentation with an interactive onboarding platform

Intro

I built this onboarding to take something that was heavy on policy and turn it into something staff could actually use in real situations.

The goal wasn’t just to explain procedures. It was to help new hires make the right decisions without needing someone standing next to them the whole time.

This interaction shows the core product loop. The learner is placed in context, makes a decision, and immediately sees the impact of that choice. The goal was to remove ambiguity and make expectations clear through action, not explanation

Experience Flow

Product Flow: Scenario → Decision → Feedback

Overview

New hires at SV4C’s are expected to learn a lot quickly. Safety, procedures, classroom setup, reporting. Most of that was coming from documents or verbal explanations, which meant people were interpreting things differently depending on who trained them.
I wanted to build something that removed that guesswork

The Problem

New hires were being handed a PDF and expected to figure it out on their own.

Everything technically existed in that document, but it didn’t help them understand what to actually do once they were in the classroom. There was no sense of order, no prioritization, and no connection to real situations.

So what ended up happening was people coming in unsure. Not just about big things, but basic expectations, procedures, and who they were supposed to go to.

The gap wasn’t the information. It was how it translated to action.

Who This Was For

This was built for new hires coming into EHS and HS classrooms, but also for the people supporting them.

In a lot of cases, there isn’t someone walking them through everything step by step. They’re expected to get up to speed quickly and start operating.

So the system needed to work without assuming extra support. It had to carry that on its own.

What I Designed

I didn’t approach this like a course. I treated it more like something that walks someone through how the job actually works.

Instead of reading through policies, the learner moves through situations that mirror what they’re going to run into. They have to make a choice, and then see how that plays out.

The structure does a lot of the heavy lifting. It introduces things in a way that builds, instead of dropping everything on them at once.

Across the experience, that looks like:
Scenarios based on actual classroom situations
Decision points instead of passive content
Interactions that force sequencing and process thinking
Built-in guidance so they’re not stuck figuring things out
A final piece that ties everything together
A completion screen that actually confirms they finished it

The goal was to make it feel closer to doing the job than reading about it.

Interactive Learning Beyond Multiple Choice

This isn’t just clicking through. The learner has to think through what comes first and what actually makes sense in the moment

Designing for non-experts

I assumed no one was going to be there walking them through this.

So instead of relying on explanation, I built support directly into the experience. The idea was that if someone got stuck, they shouldn’t have to leave the screen to figure it out.

Overview

Embedded Coaching System (SV4Cs Coach)

Guidance is built into the screen so the learner doesn’t have to guess or wait for help.

Structuring decisions instead of content

The biggest shift was moving away from “here’s the information” to “here’s what you need to do.”

Once everything was framed as a decision, it changed how the experience flowed. It also made it easier to connect what they were seeing to what they’d actually be doing

Using visuals to support understanding

Visuals were designed intentionally to support comprehension and context.

Custom characters and graphics were created in Canva and used within scenarios to make situations easier to recognize and interpret quickly. Instead of relying on text-heavy explanations, visuals carry part of the instructional load.

An infographic was also used to simplify more complex information into something learners can reference and understand at a glance.

Building something that actually gets used

The certificate and completion piece wasn’t just for show. It gives directors something they can point to and say, “yes, this person completed onboarding.”

System Thinking

The onboarding functions as a simple but consistent product loop:

Context is introduced
A decision is required
Feedback is provided
The learner moves forward with more clarity.

This structure reduces reliance on external support and ensures the experience holds, regardless of who is facilitating it.

Additional controls were built into the experience to support usability and navigation, including JavaScript-enabled elements that allow learners to adjust how they view and move through the content.

Impact

This shifted onboarding from passive content to an active system.

Learners are making decisions instead of reading policies
Expectations are reinforced through use, not memorization
The experience stays consistent across sites
Leaders have a clear way to verify completion

The result is a system that supports both the learner and the organization

End-to-End Learning Experience

Completion is tracked and confirmed, giving leadership a clear record of onboarding.

Before vs After

Before

New hires were given a PDF and expected to work through it on their own.
There wasn’t a clear structure for how to approach it or what to focus on first. Most of the information was there, but it was hard to translate into what actually needed to happen in the classroom.
That showed up pretty quickly. People were unsure about expectations, procedures, and even basic things like who to go to or what steps to follow.

After

The onboarding now walks new hires through what they’ll actually experience.
Instead of reading through policies, they’re put into situations where they have to make decisions and see how those decisions play out.
Expectations, roles, and procedures are built into the flow, so they’re not trying to piece things together on their own. The structure does that for them.
The difference is that they’re no longer guessing what the job looks like before they step into it.

What I Learned

One thing that stood out while building this was how quickly people check out if they’re just reading through information.

The moment the experience asked them to make a decision, they leaned in more. Not because it was more interactive, but because it actually felt relevant to what they’d be doing.

It made it clear that engagement isn’t about adding more to the screen. It’s about making sure what they’re doing feels useful.

Positioning

This is how I tend to approach this kind of work.

I’m not focused on building out content for the sake of it. I’m thinking about what someone actually has to do once they’re in the role, and then designing the experience around that.

If the system is set up right, it shouldn’t depend on a strong facilitator or extra explanation. It should hold on its own.