The Problem

In my former career as a paralegal, I worked for a mid-sized family law firm with five geographically dispersed offices. Continuous expansion meant the firm was regularly hiring new paralegals, and new hires often struggled in ways that put client relationships at risk: errors in pleadings, difficulty handling client queries, inefficient work processes. These weren't minor issues. They cost clients money and cost the firm referrals and reputation.

A needs analysis pointed to the real gap: it wasn't knowledge, it was soft skills. Prioritizing tasks, attention to detail, and anticipating problems before they became client-facing failures.

The Solution

With paralegals spread across five offices and new hires joining continuously, a scalable eLearning solution made more sense than in-person training. A scenario-based, story-driven eLearning lets learners practice decision-making and experience the consequences of their choices in a risk-free environment. That is exactly the kind of judgment-building practice a lecture or manual couldn't provide.

Process

Action Mapping. I interviewed SMEs at the firm to build an action map centered on the business goal, prioritizing what we wanted new hires to do over what we wanted them to know. From seven identified actions and their sub-actions, we narrowed to the three highest-priority targets for the eLearning.

Storyboarding. The text-based storyboard had to read like a real story, not a quiz, so each consequence was written to land with weight, reinforcing what an incorrect choice actually cost. A mentor character, available on-demand throughout, kept the experience learner-driven rather than test-like.

Visual Design. Law firms tend to be conservative environments, so I built the visual language accordingly: clean lines, restrained fonts, a professional-but-approachable mentor character. A style guide came first, locking in colors and type before any individual slide. This approach paid off in consistency once full development started.

Prototyping. Before building the full course, I developed an interactive prototype through the first question's consequence slides, using it to test functionality and gather feedback on object states, button behavior, and timeline issues before those problems could compound across the full build.

Full Development. Feedback from the prototype shaped two key additions: sound effects to signal whether a consequence was positive or negative, and animated stars in the progress bar to reinforce the same feedback visually. I also redesigned the prompt slides mid-build after recognizing they were too text-heavy, adding visual context to reduce cognitive load rather than settling for a first pass that technically worked.

Outcome

The course was well received by peers and the broader learning and development community, with feedback specifically pointing to the sound design and positive-reinforcement mechanics as effective engagement drivers.

What I Took Away

Building this course early in my career taught me lessons that still shape how I work: that a style guide and a working prototype are worth the upfront time, since they buy consistency and confidence for everything built afterward, and that iteration doesn't stop just because a deadline is close. I'd already gathered feedback and moved on from the prompt slides when I recognized they still needed work; going back to fix them, rather than letting "good enough" stand, made the final course meaningfully stronger.