Skip to main content
Meytal Dahan
Back to insights

Researching Five Roles That Share One Screen

Menora Insurance — Multi-Surface Design Work for Menora Insurance
When I joined Menora's sales system as an outsource designer through code-oasis, the hardest research question wasn't "what do users want" — it was "who exactly is the user?" The same data set is consumed by five roles: agent, marketing, district manager, team lead, and underwriter. Each one looks at the same records through a completely different lens and asks different questions of them. For a PM, that's the crux of prioritization. I couldn't research a single persona and ship; I had to map where the roles overlap and where their goals diverge, then decide what to standardize versus what to specialize. So my research focused on jobs-to-be-done per role inside the Agent Zone — what a district manager scans for versus what an underwriter must verify before acting. The payoff was a clearer product spine: a shared data model with role-aware framing, instead of five disconnected screens fighting for roadmap space. Research here wasn't about novelty. It was about disambiguating an audience that looks like one user and behaves like five — and giving the roadmap defensible reasons to invest where the lenses genuinely differ.

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.