1 · Overview

PatternLab builds real-time production planning and scheduling software for manufacturing companies. As the core product moved into rollout, the client raised an adoption problem: thousands of factory operators — with wildly different literacy, language, and comfort with digital tools — would need to learn the new system, and there weren't enough trainers to do it in person, repeatedly, at scale.

The client's ask was direct: build a learning platform that lives with the product, so operators can train themselves. No manuals to lose, no dependency on a trainer's schedule, and no data leaving their own systems — they explicitly did not want to evaluate or adopt a third-party LMS. Over five months, I designed and built EduSphere: an admin-authored, self-serve knowledge hub with video lessons, quizzes, certifications, and progress tracking for both operators and the managers overseeing them.

2 · The Problem

Why this needed to exist

• The manufacturing client was rolling out a new production planning platform to a large, distributed operator workforce.
• Most operators were unfamiliar with digital scheduling tools — some had never used software with this level of interactivity before.
• In-person training doesn't scale: new hires join continuously, shifts rotate, and trainers can't be everywhere at once.
• Hard constraint: operational data was sensitive, and the client would not adopt or trial an external LMS to hold it. Whatever was built had to be native to their own environment.

What “done” looked like

Operators should be able to onboard themselves from inside the platform — watch a lesson, get tested on it, and prove competency — without a live trainer, and admins needed a way to author and monitor all of it.

3 · Research & Discovery

Discovery here was narrower than a typical greenfield UX process, and that's worth being upfront about. Two constraints shaped the approach: the client would not consider or benchmark other LMS products, and competitor manufacturing-training tools kept their product experience closed off — there was little to ethically or practically inspect from outside. Research leaned on direct requirement-gathering with the client and reasoning from the end-user's actual working conditions, rather than comparative benchmarking.

Findings that actually shaped design decisions

• Varying literacy levels across the operator base — content couldn't assume comfortable reading of dense instructions.
• Language differences across the workforce — content needed to support more than one spoken/written language, not just UI copy.
• Low tech-comfort for a meaningful portion of users — the UI needed to be closer to “watch and tap” than “navigate and configure.”
• A split audience: operators needed a simple, linear path; managers/admins authoring content needed a full content-management system behind the same product.

4 · First Attempt — and Why It Didn't Hold Up

The first version of EduSphere was intentionally minimal: a video module where admins could upload a training video with a language preference, and operators could open it and watch. On paper it satisfied the brief. In practice it broke down almost immediately from either end of the workflow: