Skip to main content
Meytal Dahan
Back to insights

Personalization Is How a Mandated App Starts Feeling Like Mine

CEOs sometimes hear 'personalization' and picture a marketing engine. In B2E, it's something more strategic: it's how an app the company mandated starts to feel like the employee's own. A frontline worker doesn't want the same generic home screen as head office. They want their shift, their site, their pay, their tools — surfaced first, in their language, tuned to their role. That role- and context-aware tailoring is the clearest expression of Reciprocity Design: the product adapts to the person instead of demanding the person adapt to it. Practically, this means tailored models of the user — role, location, shift pattern, device, connectivity — driving what each person sees and does first, so a technician's app and a dispatcher's app feel like different products built for them. It has to respect Offline Mode, so personalization is computed from cached context, not a live profile fetch in a dead zone. And it has to draw cleanly from your legacy HR data without becoming a privacy liability — personalize on role and need-to-know, not surveillance. The business case is straightforward: relevance drives the adoption that justifies the whole investment. People protect the tools that feel built for them.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Enterprise Mobile
Engineering LeadersIndustry-Specific Accessibility

Accessibility in the Field Means Gloves, Glare, and One Free Hand

WCAG is the floor for frontline apps, not the ceiling. The real accessibility test is the field: gloves that defeat small tap targets, sunlight that erases low-contrast text, one free hand on a noisy loading dock. Situational and permanent disability collapse into the same requirements out there. Big targets, glare-proof contrast, camera/QR over forms, a single confirming tap. Bonus for R&D: fewer input errors at the source means cleaner data into payroll. Design for the glove and the glare — you'll clear WCAG along the way.

Read
Enterprise Mobile
CEOsSpecific Feature ROI

The ROI Hides in the Feature Nobody Mandated

CEOs often ask me to justify a B2E feature in isolation. Wrong frame. The mandated features get compliance, not adoption. The feature that gives the field worker something back — offline schedules, a camera report that kills minutes of typing, a payslip without a call to HR — is what makes them open the app at all. And once they open it, your mandated workflows finally get used. Don't price a feature by its own ROI. Price the adoption it unlocks across the whole product.

Read
Enterprise Mobile
Engineering Leaders

B2E Apps With Complex Integrations: How Do You Design Mobile-First So It Doesn't Break on Legacy Systems?

Engineering leaders on B2E apps: the challenge isn't the build – it's the integrations with legacy systems. In our enterprise mobile app project, we designed "Cached Display" for latency situations and full Offline Mode for field workers. Design + technical reality = an app that works in production.

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.