Skip to main content
Meytal Dahan
Back to insights

Managing a B2E App Project: Aligning HR, IT, and Field Teams

Enterprise MobileProject ManagersHR Tech / Enterprise Mobile
Project managers leading a B2E app project deal with a unique work culture: the stakeholders are internal departments (HR, IT, operations) that aren't always accustomed to working on digital projects. The end product serves employees – field staff, service reps, department heads – whose time is limited and whose involvement in the project is minimal. In the B2E app project, our working methodology was built around "Employee Voice Sessions" – short, structured conversations with real workers from the field. Instead of hour-long requirements meetings that demand a big time commitment from the employee, we created focused 20-minute sessions. The employee describes their daily workflow, we show them a prototype of a feature, and they give immediate feedback. This approach let us gather deep insights from field workers without disrupting their day-to-day work. On top of that, we created communication tracks with the internal stakeholders (HR, IT) that mirrored the division of responsibility within the organization – HR focused on the employee experience, IT on security and integration. Each group got its own piece and wasn't flooded with irrelevant information. For project managers on B2E apps, internal enterprise systems, or any project that serves employees, the insight is this: adapt your methodology to the organization's culture and the reality of its workers. Short, focused sessions and tailored communication for each stakeholder are the keys to success.

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.