Skip to main content
Meytal Dahan
Back to insights

Where AI Belongs in a Field-Heavy Product

Menora Insurance — Multi-Surface Design Work for Menora Insurance
Every founder I talk to wants an AI story. After working across Menora's flows, my honest view is that the most valuable place for AI in a product like this isn't a chatbot bolted onto the homepage — it's in taming complexity the user shouldn't have to carry. Think about the agent zone: many fields, many roles, many conditional rules. The cognitive load isn't in finding information, it's in knowing which slice of a multi-axis space applies to the decision in front of you. That's precisely the kind of narrowing a well-scoped AI layer could assist — surfacing the relevant fields for a given role and context, suggesting the filter path, flagging a combination that doesn't add up. The strategic discipline is to keep AI inside the boundaries of the real domain rather than inventing capabilities the product was never meant to have. I'm wary of AI features that ask users to trust opaque output in a regulated, high-stakes setting like insurance. The strategy I'd advocate to founders: use AI to reduce the distance between a user and the right answer they could have reached themselves — and keep them able to verify it. Augment the expert; don't replace their judgment.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Menora Insurance
Engineering LeadersIndustry-Specific Accessibility

Accessibility in Field-Dense Insurance Flows

Most accessibility talk stops at contrast on landing pages. In insurance, the hard surface is the field-dense internal tool. On Menora's agent zone — many fields, conditional rules, five role lenses — WCAG means keyboard order through multi-axis filters, screen-reader announcements as conditional fields appear, focus that survives constant state changes. That's architecture, not a finishing pass. The deepest a11y debt hides in the internal tools everyone assumes are 'just for power users.'

Read
Menora Insurance
Project ManagersDocumentation & Organizational Handoff

Documentation That Outlives the Engagement

As an outsource designer on Menora, I knew I'd eventually leave. So I documented for the people who'd stay. Not pretty specs — the reasoning. Why a field appears for an underwriter but not a team lead. Why the fee flow's rules are shaped the way they are. For a PMO: with outside contributors, documentation isn't admin. It's how the work becomes something the organization actually owns.

Read
Menora Insurance
Project Managers

Managing UX in Enterprise Giants: Owning Milestones and Integrating Multi-Stakeholder Requirements

Project managers (PMOs), how many times has your enterprise project stalled because legal or marketing suddenly remembered to weigh in at the 90th minute? The work with Menora Insurance demanded a structured approval method. You lock down a smooth architecture in Figma, get sign-off from every department, and only then run forward. That's how you protect the Gantt.

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.