Three weeks into her new role, Jenna had completed every onboarding checklist her company threw at her. She'd set up her laptop, enrolled in benefits, watched the compliance videos, and even attended the "Welcome to the Team!" virtual lunch. On paper, she was fully onboarded. In reality, she had no idea that her manager preferred Slack over email, that her closest collaborator shut down when given feedback publicly, or that the engineer she relied on did his best work after 2pm and hated being pinged before noon.
Jenna's experience isn't unusual. It's the norm. Research shows that 69% of employees who experience great onboarding stay at a company for three or more years. Yet 68% of organizations admit they struggle to personalize onboarding at scale. The gap between those two numbers reveals something uncomfortable: most companies know onboarding matters, but they've been optimizing the wrong parts of it.
The Spreadsheet Knows Your Benefits. It Doesn't Know Your Team.
Traditional onboarding is transactional. It's designed to get someone operational: here's your tech stack, here's your org chart, here are your quarterly goals. What it almost never does is answer the questions that actually determine whether someone succeeds in their first 90 days. Questions like: How does my manager prefer to communicate? What does my teammate need when they're stressed? Who on this team processes information by talking out loud, and who needs silence to think?
These aren't soft questions. They're operational ones. When a new hire doesn't know that their project lead prefers written proposals over verbal pitches, they're going to spend weeks misreading signals. When a manager doesn't realize their new report shuts down under direct confrontation, they'll mistake silence for agreement. The cost isn't just awkwardness. For 20.5% of companies, half their new hires leave within 90 days. Twenty-three percent of new hires quit within six months, and poor onboarding is the most frequently cited reason.
Enter the Personal User Guide
A Personal User Guide, sometimes called a PUG, is a short document that tells your colleagues how to work with you effectively. Not your resume. Not your personality type label. A practical, living guide to your communication preferences, stress responses, feedback style, work rhythms, and collaboration needs.
GitLab pioneered a version of this with their "personal README" concept, where every employee writes a document describing how they work best. Atlassian has a similar practice baked into their team playbooks. The idea is simple: if every piece of software ships with documentation, why don't people?
A solid PUG typically covers five areas:
How I communicate best. Do you prefer Slack or email? Do you like small talk before business, or do you want to get straight to the point? Are you someone who thinks out loud in meetings, or do you need time to process before responding?
What I need from my team. Some people thrive with daily check-ins. Others feel micromanaged by anything more than a weekly sync. Some people want to be included in every decision; others want you to bring them the final call.
How I handle stress. This one matters more than most people realize. Some people get quiet when overwhelmed. Others get louder. Some withdraw from the team; others lean in harder. Knowing this about a colleague can prevent a week of misinterpretation.
How I prefer to receive feedback. Direct and blunt? Wrapped in context? Written first, discussed later? This alone can prevent dozens of friction points per quarter. (For more on this, see Feedback That Actually Lands: Matching Delivery to Personality.)
What drains me vs. what energizes me. Back-to-back meetings might fuel one person and flatten another. Ambiguous projects might excite a creative thinker and paralyze a structured one.
Why PUGs Work Better Than Personality Labels
If you've ever had someone say "Oh, I'm an INTJ, so I need alone time" and then watched the room nod politely without knowing what to do with that information, you've seen the limitation of labels. Personality assessments like DISC and MBTI are valuable for self-awareness, but they often stop at categorization. You get a type. A quadrant. A color. And then you're expected to figure out the rest on your own.
PUGs take a different approach. Instead of telling your team what you scored, they tell your team what to actually do. Instead of "I'm a high-D," it's "When you need a decision from me, give me the options and a deadline; I'll pick fast." Instead of "I'm an introvert," it's "I do my best thinking in writing. If you need my input on something complex, send me a doc before the meeting."
That specificity is what makes PUGs actionable. A label describes who you are. A PUG describes how to work with you.
From Manual to Automated: How AI Changes the Equation
The catch with traditional PUGs is that they require self-awareness, writing ability, and time. Not everyone is good at articulating their own work style. Some people don't know their stress responses until they're already stressed. Others write a PUG once and never update it.
This is where AI-powered approaches are shifting the model. Platforms like AlignWithMe use a combination of personality assessments and voice interviews to generate PUGs automatically. A ten-minute conversation reveals patterns that a written survey might miss entirely: how someone's tone shifts when discussing conflict, whether they speed up or slow down when they're uncertain, what topics make them light up versus go flat. (For more on this, read Voice Interviews vs. Surveys: What 10 Minutes of Conversation Reveals.)
The AI synthesizes these signals into a readable, practical guide that the employee can review, adjust, and share with their team. It's still their PUG. But the starting point is richer and more accurate than what most people would produce on their own.
The Ripple Effect on Time-to-Productivity
When effective onboarding can improve new hire productivity by over 50%, the business case for PUGs writes itself. But the impact goes beyond the new hire.
Think about what happens when an entire team has PUGs. A manager onboarding a new report doesn't need three weeks of observation to figure out their communication style. A project lead assembling a cross-functional team can read five PUGs in fifteen minutes and know who needs detailed briefs versus who prefers a quick conversation. A remote team that's never met in person can build relational context on day one instead of waiting months for it to develop organically.
This is especially powerful for managers in their first 30 days. When 82% of managers are "accidental managers" who received no formal training, giving them a PUG for every team member is like handing them the cheat sheet they never got.
Making PUGs Part of the Culture, Not Just the Process
The teams that get the most from PUGs treat them as living documents, not onboarding artifacts. They update them. They reference them in 1:1s. They use them to prepare for difficult conversations. They bring them into project kickoffs.
Some practical ways to embed PUGs into your team culture:
Make them visible. Link PUGs in Slack profiles, team wikis, or project channels. If someone has to dig through three folders to find yours, nobody will read it.
Review them quarterly. People change. What drained you six months ago might energize you now. A PUG that's a year old is worse than no PUG at all, because it creates false confidence.
Use them in conflict resolution. When two people are clashing, their PUGs often reveal the root cause faster than a mediation session. One person gives feedback publicly because that's their preference. The other shuts down when called out in front of others. The PUGs would have flagged that mismatch before it became a problem.
Model vulnerability. When leaders share their own PUGs openly, including their stress responses and weaknesses, it signals that self-awareness is valued. That sets the tone for psychological safety across the team.
The Onboarding Experience Your Team Actually Needs
The global onboarding software market surpassed $1.34 billion in 2025 and continues to grow. That's a lot of money being spent on checklists, compliance training, and "culture decks" that gather dust after week one. The companies pulling ahead aren't the ones with the fanciest onboarding portals. They're the ones that answer the question new hires actually care about: who am I working with, and how do I work well with them?
Personal User Guides aren't a silver bullet. But they're the closest thing to compressing months of relationship-building into a single readable document. And when they're powered by AI, voice analysis, and personality science, they stop being a nice-to-have and start being the backbone of how modern teams get to know each other.
References
- SHRM. "Don't Underestimate the Importance of Good Onboarding." Society for Human Resource Management, 2023.
- Gallup. "Why the Onboarding Experience Is Key for New Employees." Gallup Workplace, 2023.
- BambooHR. "The Definitive Guide to Onboarding." BambooHR Research, 2022.
- GitLab. "GitLab Team Member README." GitLab Handbook.
- Atlassian. "Team Playbook: My User Manual." Atlassian Team Practices.