An employee persona is a profile of a group of employees who share a way of working: how often they come to the office, what they do when they’re there, which tools and spaces they depend on, and what gets in their way. Workplace and HR teams build personas from attendance, booking, and survey data so that decisions about space, schedules, and amenities are made for real groups of people instead of an imagined average employee. A hybrid company usually ends up with four to six.
A persona describes a segment, not a person. It typically includes the group’s role types, where they work on a normal week, how much of their day is collaborative versus focused, what they book (desks, rooms, parking, coworking), and the friction they report. Each persona gets a short label and a one-page description that anyone planning a floor, a policy, or a program can pick up.
The idea comes from product design, where personas keep teams from building for themselves. Applied to employee experience, it does the same thing: a workplace lead who comes in five days a week designs a different office from one who thinks about the engineer who comes in on Tuesdays for a team day. Personas also feed employee journey mapping, where each group’s week is traced from commute to desk to meeting to departure, with the pain points marked.
Good personas are built from behavior first and opinion second:
The behavior data sets the segments; the interviews name them. Gallup reports that 52% of remote-capable employees now work hybrid and spend about 2.3 days a week on site on average, and that average hides groups who come in four days and groups who come in once a month. Workplace analytics tools pull the badge, booking, and HR data into one view so the segments show up without a spreadsheet project; Gable’s workplace intelligence does this by combining access control, Wi-Fi, booking, and HRIS data per team and location.
Most hybrid workforces sort into a handful of recognizable groups. The attendance figures below are illustrative; yours will come from your own data.
Personas turn “how many desks do we need?” into “how many desks does each group need, on which days?” The decisions they inform:
Revisit the personas once or twice a year. Attendance drifts, teams reorganize, and a persona built in 2024 often no longer describes anyone.
Four to six covers most hybrid companies. Fewer than three and the personas describe everyone, which is the average you were trying to escape. More than seven and planners stop using them. Start from the attendance and booking segments in your data, then merge any two that would lead to the same decisions.
Share the personas as descriptions of how people work, not as labels on individuals. Publishing them helps employees understand why a floor is laid out a certain way or why team days exist. Assigning a named persona to each person in an HR record adds little and makes people feel sorted.
Usually the workplace or real estate team owns them, because the data (badge, bookings, utilization) and the decisions (floors, seating, schedules) sit there. HR contributes the HRIS attributes, survey design, and the employee experience lens. One owner keeps the personas maintained; a shared committee usually lets them go stale.
Yes, if they’re built from assumptions about departments or generations rather than from behavior. Base each persona on observed attendance and booking patterns, test it against the data every six months, and keep demographic attributes out of the definition. A persona should describe what a group does, never who they are.
Below about 100 people, a workplace lead usually knows every team’s pattern without formalizing it. Personas start paying off when a company has multiple offices, a hybrid workforce with uneven attendance, or a lease decision coming up, because that’s when planning for an average employee starts costing real money.