Skip to main content
Meytal Dahan
Back to insights

Designing Data Viz for a Phone in a Field Worker's Hand

Most data visualization advice assumes a dashboard on a wide screen with a stable connection. In B2E field work, neither holds. When I design data viz for enterprise mobile, the constraint that drives everything is context: a small screen, a moving user, and data that may be hours stale because it synced over a weak signal. For an R&D leader, that reframes the problem from 'render a beautiful chart' to 'show a defensible truth under bad conditions.' I design visualizations that are honest about freshness — a clear 'as of last sync' marker so a technician never makes a decision on stale numbers they assumed were live. I favor a few large, glanceable indicators over dense charts, because the field user needs a decision, not an analysis. Technically, I push for visualizations that render from cached data in Offline Mode and reconcile cleanly when the device reconnects, which means the data layer and the viz layer have to be designed together. I also keep encodings accessible — never relying on color alone, sized for real thumbs. Good field data viz isn't a shrunk-down dashboard; it's a decision tool engineered for the worst connection you'll ever see.

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.