Researching the Frontline: Why B2E User Research Starts in the Field

When PMs hand me a B2E brief, the requirements usually come from the systems the app must integrate with — payroll, scheduling, the legacy HR stack. What's missing is the person holding the phone in a parking lot at 6am. So I anchor enterprise mobile research in the field, not the conference room. The questions I bring are different from consumer work. Frontline employees didn't choose this app; their employer did. That changes everything. I'm researching where coverage drops, where gloves make tapping hard, where a manager is watching over a shoulder. I'm mapping the moments where the app demands something — clock in, submit a form, scan a code — and asking what the employee gets back. For a PM, this reframes the roadmap. The highest-value feature is often the one that earns trust, not the one that satisfies a back-office requirement. I deliver research as workflow maps tied to real conditions, plus a clear read on which 'mandated' tasks could become genuinely useful. That lets you prioritize on evidence, defend scope to stakeholders, and stop shipping features the field quietly ignores.