Skip to main content
Meytal Dahan
Back to insights

First Run in a Role-Based System: Onboarding Without a Tour

Menora Insurance — Multi-Surface Design Work for Menora Insurance
First-run onboarding usually conjures a coach-mark tour. In Menora's Agent Zone, that instinct fails fast, because there's no single first run — an agent, a district manager, and an underwriter each meet the system in a different role, with different functionality and different data in front of them. A generic welcome flow would be wrong for four of the five. So onboarding here is less about a guided overlay and more about the first screen being self-evident for whoever you are. The work goes into defaults, sensible empty and initial states, and a clear entry point so a new user in any role immediately sees what's theirs to act on. On the B2C side it's the same philosophy applied to self-service: a customer reaching profile settings or a form for the first time should understand what to do without a manual. For PMs, the reframe is this — onboarding isn't a feature you bolt on at the end; it's a property of how clear the core screens already are. If you need a tour to explain a screen, that's usually a signal the screen, not the user, needs work. The best first run is the one nobody notices they had.

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.