AI and the rise of hybrid work are rewriting the rules of persona-based provisioning. Equipping the workforce by persona used to be a straightforward exercise: the org chart supplied the groups, a stereotype supplied the requirements, and the model held because most people worked roughly the same way. Not anymore. AI keeps redrawing what roles need, and hybrid work has scattered where they need it. Together, they’ve changed the inputs persona building runs on.
The inputs changed; the principle didn’t. Sorting employees into representative types and equipping each accordingly is still how smart device fleets get provisioned. But the old build — a role, a department, a rough sketch — was drawn from a workplace that no longer exists. The new build starts from the work: where it happens, what it demands, what it costs when it stops.
Reading the work, not the org chart
The new build reads each role against the factors that actually determine what a device needs to do. Where does the work happen — headquarters, home offices, client sites, a hospital floor? What does it demand of hardware at peak, not on an average Tuesday? How much of the day runs through a camera and a headset? What data does the role touch, how fast is the role itself changing, and what does an hour of downtime cost — because an hour is not the same hour for a field engineer and a back-office coordinator.
Run that reading across a workforce and the real groupings surface — roles with nothing in common on paper making identical demands of their devices, each pattern anchoring a standard configuration with a defensible reason behind it. The fleet gets simpler, not more complicated: fewer configurations, better matched, easier to support.
Those questions aren’t a checklist — they’re a sample. The full reading runs eight dimensions deep.
The eight dimensions of a persona built right
- Mobility & Environment. Where does the work physically happen — and how often does it move? The answer drives connectivity, durability, battery, and form factor before a single spec sheet gets opened.
- Work Demands. What does the role ask of hardware at peak — and where does its AI actually run, on the device or in the cloud? Averages hide exactly the moments that determine whether a device fits.
- Collaboration Load. How much of the day lives in calls, meetings, and screen shares? For some roles, the camera, audio, and bandwidth are the job, and the device should be chosen accordingly.
- Digital Dexterity. How self-sufficient is the role with technology, and how much support does it generate? Some people turn extra capability into output; others turn it into tickets — and neither answer is a judgment, but both are provisioning facts.
- Data & Access Footprint. What systems and data does the role reach, and from where? Two roles with identical hardware needs can carry entirely different access risk — and the device has to reflect it.
- Cost of Disruption. What does an hour of downtime actually cost this role? Reliability spend should follow that math — concentrated where the work stops hurting most, not spread evenly across the fleet.
- Volatility. How fast is the role itself changing — new tools, new workflows, new AI in the mix? Fast-moving roles need headroom; stable ones don’t need to pay for it.
- Security & Compliance. What does the role’s risk profile require the device to enforce, not merely support? Compliance sets a floor that no amount of raw performance can substitute for.
Read a role across all eight, and the right device stops being a debate.
Personas are a lifecycle discipline
A persona isn’t finished at rollout — that’s where it starts earning its keep. The match has to hold as roles evolve: watched for drift, corrected when the work outgrows the configuration, and closed out cleanly when devices come back at end of life. That’s lifecycle work, and it’s the part most provisioning models never plan for. It’s also where MCPC has spent more than twenty years — managing devices from planning and provisioning through support, refresh, and recovery, so the fit that was right on day one is still right in year three.
The bottom line
Persona-based provisioning didn’t get harder. It got deeper — and the organizations that read the work instead of the org chart will run fleets that cost less, support easier, and fit the people using them. The ones that don’t will keep buying good hardware for the wrong desks.
Our new guidebook — built with HP, Microsoft, and Intel — turns this from argument into method: all eight dimensions in depth, the key questions to ask of every role, and the step-by-step process for building personas your fleet can actually run on. Download it here.
Read More from This Article: AI and hybrid work are rewriting the rules of persona-based provisioning
Source: News
