Order inside an operational system
Designing a SaaS ERP for Rubix Designs across all three surfaces, building dense, data-heavy interfaces that operators can actually move through quickly.
- Role
- UX Design, UI Design, Web Design
- Discipline
- UX / UI
- Year
- 2023
- Headline
- 3 Surfaces, one system
Context
Shopworks ERP is enterprise resource planning software built for Rubix Designs: the operational backbone of the business. The deliverable spanned the whole product, the front-facing website, the main SaaS, and the admin-side back end. These are tools people live inside all day, where density isn't a flaw to remove but a reality to organize.
The problem
ERP interfaces fail when they treat every piece of data as equally urgent. The screens needed to be comprehensive without being exhausting, so that experienced operators were carried by the layout instead of fighting it, and so the marketing site and the admin back end read as part of the same considered system.
Process
- 01
Designed for the daily user
I optimized for the person who uses this for the hundredth time, not the first, prioritizing speed, scannability, and muscle memory over hand-holding.
- 02
Imposed a clear structure
Consistent patterns for tables, forms, and actions, so that learning one screen meant understanding the next across the product and the admin back end alike.
- 03
Connected site to system
The front-facing website carried the same visual logic as the product, so the promise on the marketing side matched the tool a customer signed up to use.
Outcome
The interfaces hold a lot without feeling heavy. Operators can find and act on what matters faster, and the system reads as organized rather than merely complete, from the marketing site through to the back end.
- Faster Day-to-day task flows
- End-to-end Site, product, and admin
Dense by necessity, clear by design: proving that even the most demanding enterprise tools deserve real craft.