Skip to main content
Meytal Dahan
Back to insights

Industry 4.0 Startups: How Do You Crack the Reluctance of Manufacturing Plants to Adopt New Technology?

ZammitFoundersIndustry 4.0 / Manufacturing
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.
Founders in Industry 4.0 and industrial IoT face a unique go-to-market challenge: manufacturing plants are especially conservative, suspicious of new technologies, and afraid of production slowdowns caused by an unsuccessful rollout. Startups that show up with an excellent value proposition hit a glass wall: plant CEOs refuse to even try. My experience working on the manufacturing platform puts me in a unique position to understand what makes manufacturing plants connect with and adopt — or reject — new systems. The secret is in designing an experience that feels "familiar" to the veteran operator, even when the technology behind it is revolutionary. Instead of trying to "re-educate" the user, we take their existing paradigms and amplify them. For example, an action that used to require filling out a paper form at the plant becomes, in a digital app, designed to look visually similar to the original form — but with every tap it begins to save time and prevent errors. The operator doesn't feel they're "starting from scratch" — they feel that this technology "worked with them." For founders in Industry 4.0, the central insight is: the ability to crack the industrial market depends 50% on the technology and 50% on the design of the rollout experience. Invest in a product designer with experience in industrial domains — that's the difference between a startup that scales and a startup left holding a patent that no one buys.

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.