Skip to main content
Meytal Dahan
Back to insights

Color as a Trust Signal When You Remove the Salesperson

ZammitFoundersColor & PsychologyManufacturing / B2B Procurement
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.
Zammit's whole bet was removing the sales intermediary: let engineers, architects, contractors, and retail professionals configure complex laser-cut products and order on their own. As a founder, you should care that when you take the human out of the loop, the interface has to carry the trust the salesperson used to provide — and color is one of the most direct tools for that. I treated color as a system of meaning, not mood. A restrained, confident palette signalled that this was a serious manufacturing partner, not a consumer gadget store. Within the configurators, color did functional work: guiding attention to the active decision, confirming valid selections, and flagging constraints the user couldn't violate given how the product is actually fabricated. Across six segment onepagers, color helped each audience feel addressed without fragmenting the brand. The psychological goal was steadiness — a buyer committing to a made-to-order order needs to feel the system is in control, especially through quote, OTP, and checkout where hesitation costs you the sale. Color won't fix a weak product, but for a self-serve procurement platform it's a quiet, constant reassurance that the buyer is in capable hands.

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.