Skip to main content
Meytal Dahan
Back to insights

Usability Testing for the Field: De-Risking the B2E Rollout

For a PMO, usability testing is risk management. A B2E rollout that fails adoption isn't a UX footnote — it's a stalled program, an angry sponsor, and a budget line that delivered nothing. So I design testing to surface adoption risk before launch, while it's still cheap to fix. The trap in enterprise mobile is testing in ideal conditions. A flow that's flawless on office Wi-Fi falls apart on a loading dock with one bar and Offline Mode kicking in. I test in context: degraded connectivity, one-handed use, sunlight on the screen, interruptions mid-task. I test the camera, GPS and QR paths under real friction, not just the happy path. I also test the reciprocity story directly — does the employee perceive value, or just obligation? That perception is the single best predictor of whether your rollout sticks. For planning, I give you findings ranked by adoption impact and effort, so you can sequence fixes against the go-live date rather than discovering blockers in week one of production. Testing becomes a schedule input, not a surprise.

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.