Share conventions, not priorities
Creators and learners can reuse familiar components while still seeing information ordered around their different jobs.
WordPress LMS product design
Masteriyo
One LMS, different mental models for the people building a course and the people trying to learn from it.
- Role
- Product design contribution
- Product
- WordPress LMS product design
- Users
- Course creators, learners, and administrators
Shared data does not mean shared hierarchy.
Course creators think in curriculum, settings, publishing and repeatability. Learners think in progress, comprehension, feedback and what comes next. Administrators need oversight. The product needed reusable conventions without letting the underlying content model dictate the interface for every role.
My contribution. I contributed within a larger product team, working on course and quiz flows, learner states, hierarchy and reusable interface patterns. The work had to fit an established WordPress LMS, existing conventions and a collaborative design process.
Where the design judgment mattered.
Reveal authoring complexity progressively
Course and quiz setup is broken into meaningful decisions instead of exposing every configuration option at once.
Keep learner feedback close to the next step
Progress, attempt state and completion are presented in the context of what the learner should do next.
Screens, shipped material and public references.
The artifacts sit inside the story because proof is more useful next to the decision it supports than in a ceremonial section at the end.
Experience model
One system, two different journeys
The work demonstrates how to add features inside a mature product and a multi-designer team: respect established patterns, make contribution boundaries clear and document enough behavior for another person to continue the work.
- 01
Creators move from structure into progressive configuration.
- 02
Learners move from content into feedback and continuation.
- 03
Shared components reduce relearning without forcing equal density.
- 04
Empty, error and completion states stay inside the same product language.
What this work demonstrates
A contribution that fits the product instead of competing with it
The work demonstrates how to add features inside a mature product and a multi-designer team: respect established patterns, make contribution boundaries clear and document enough behavior for another person to continue the work.
Collaborative product designComplex authoring UXDesign-system discipline