Skip to main content
Meytal Dahan
Back to insights

Visualizing a Shelving Configuration Without Requiring CAD

Zammit — Designed the Retail Shelving Planning System - the platform's most demanding configurator, where every dimension, shelf, edge profile, and placement rule is defined - into a spatial design tool retail professionals could use without CAD knowledge.
The flagship surface at Zammit was the Retail Shelving Planning System — a spatial configurator where users set overall dimensions, shelf count, edge profiles, per-shelf depth, and placement. The hard part, from an R&D standpoint, is that this is genuinely spatial data, and the user base explicitly does not have CAD knowledge. So the visualization had to represent a real, manufacturable object faithfully enough to be trusted, while abstracting away everything that makes CAD intimidating. I designed the visual representation to update in step with the configuration, so a change to per-shelf depth or shelf count read immediately as a change in the thing being built — not as numbers in a table. That tight coupling between input and visual is the engineering interesting bit: the picture is bound to the same constrained model the DriveWorks engine enforces, so what the user sees can't drift from what the factory can actually fabricate. For your team, the lesson is that data visualization in a configurator isn't a chart layer bolted on top — it's a faithful, real-time projection of the constrained product model. Get that binding right and the visualization becomes the user's confidence that their custom order is correct before they commit.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Zammit
Project ManagersUsability Testing

Testing a Spatial Configurator Without CAD

On Zammit's shelving configurator, we asked people to lay out custom shelving — dimensions, shelf count, depth, placement — with zero CAD knowledge. That is a usability risk you cannot hand-wave. So I ran testing as a recurring checkpoint tied to delivery milestones, not a one-off before launch. The payoff is for project managers as much as designers: testing turns a scary, vague risk ('can buyers do this without a salesperson?') into specific, scheduled, fixable issues. And inside an engine with real constraints, testing early tells you which problems are worth engineering time and which a better sequence solves for free. Predictability beats surprises.

Read
Zammit
Product ManagersMicro-interactions & Animation

Micro-interactions That Made an Engine's Rules Feel Like Feedback

Rule-heavy configurators feel like the system is fighting you — unless feedback shows why. On Zammit, micro-interactions turned the engine's logic into a conversation: a value recalculating, the summary shifting, an invalid option visibly settling out of reach instead of vanishing. PMs, the test for every animation: does it explain the system's behavior, or just decorate it? Only the former protects flow completion.

Read
Zammit
Project ManagersDelivery & Handoff to Development

Handing Off 40 Configurators Without Losing the Thread

Handing off ~40 configurators, 25 e-commerce flows, and 6 onepagers — solo, over ~2 years — taught me that handoff isn't an event, it's a rhythm. At that volume the real risk a project manager loses sleep over is drift: checkout behaving one way here, another way there. My defense was deliberate pattern reuse and handing off the decision logic, not just visuals — especially for configurators bound to the DriveWorks engine's rules. Shared patterns are schedule insurance: estimates hold, review cycles shrink, and developers implement without guessing. Clear intent plus clear constraints beats a backlog of clarifying questions every time.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.