First-Run Onboarding Is Where a Mandated App Earns Consent

First-run onboarding in B2E is a different problem than in consumer apps, and PMs who copy consumer patterns get burned. Your user didn't choose to download this — IT pushed it to their device. So the onboarding's job isn't to excite, it's to answer two unspoken questions fast: 'why do I have to use this?' and 'what's in it for me?' When I design enterprise mobile onboarding, I lead with reciprocity — show the value the employee gets (faster timesheets, no more paper forms, getting paid correctly) before asking for a single permission. I sequence permission requests just-in-time and in context: ask for the camera at the moment they need to scan, not in a wall of prompts on launch. I keep text entry near zero on first run, because typing on a phone in the field is friction that kills momentum, and I make sure the very first task succeeds even in Offline Mode so a poor signal isn't a dead end. The metric I care about for your roadmap isn't 'completed the tour,' it's 'completed their first real task.' Onboarding that earns consent instead of demanding compliance is what turns a mandated rollout into genuine adoption.