Sixteen principles that guide every design and engineering decision at JM Family. They are organized from foundational mindset to specific craft, grounded in established UX laws, and written to be actionable — not aspirational.
These are not slogans. Each principle includes a concrete application note that connects it to the tools, tokens, and processes in this design system. When a design review surfaces a disagreement, these principles are the tiebreaker.
Every design decision should be grounded in validated user needs, not personal preference, stakeholder opinion, or technical convenience. When in doubt, go back to the research.
Conduct research before proposing solutions. A well-defined problem eliminates half the wrong answers before design begins. Skip this step and you risk building the right solution to the wrong problem.
Treat every release as a hypothesis. Measure behavior, identify friction, and iterate. Design is never finished — it converges toward the right answer through cycles of build, measure, and learn.
Interfaces should follow established conventions so users never have to wonder whether something is clickable, where navigation lives, or what happens next. Cognitive effort spent on the interface is effort stolen from the task.
Interface copy should be as clear and concise as possible. Avoid jargon, internal acronyms, and technical terminology that assumes domain expertise the user may not have.
Users scan before they read. Prioritize scannability through clear headings, short paragraphs, bullet lists, and visual cues that let users find what they need without reading everything.
Users bring expectations from every other product they have used. Respect those assumptions for basic interactions — reserve innovation for solving real problems, not reinventing the back button.
Guide user attention through deliberate ordering. Size, color, weight, spacing, and position all communicate importance. If everything looks the same, nothing stands out and users cannot scan.
Points, lines, and planes create relationships. Proximity groups related items. Similarity signals shared function. Closure lets users fill in gaps. These are not aesthetic choices — they are how the brain parses layout.
Similar elements should behave and look the same throughout the product. Consistency reduces learning cost, builds trust, and makes the interface predictable. It operates at three levels: visual (same styles), functional (same behavior), and external (same conventions as the platform).
White space is not empty space — it is a structural tool. It improves readability, directs attention, and gives the interface room to breathe. Crowded layouts feel overwhelming even when each element is well-designed.
Every user action must produce clear feedback about what happened and what to do next. Silence is the worst response an interface can give — it forces users to guess whether their action worked.
Users should feel empowered to undo actions, navigate back, and exit processes without penalty. Feeling trapped erodes trust and increases error anxiety, which slows people down.
Anticipate mistakes through constrained inputs, sensible defaults, and inline validation. When errors do occur, explain what went wrong in plain language and tell the user exactly how to fix it.
Show users only the information and options they need at each step. Advanced features should be available but not in the way. Simplicity on the surface, power underneath.
Accessibility is not a feature — it is a quality of the work. Products must be usable by everyone, including people with visual, motor, cognitive, and auditory disabilities. WCAG 2.2 AA is the minimum standard, not the aspiration.
The principles above are grounded in these established laws and heuristics. Understanding the research behind a principle makes it easier to apply in novel situations and defend in reviews.
