They know who ships fast, who needs reminders, who panics before deadlines, and who mysteriously disappears when strategy conversations start.
What they don't know is why.
Why one designer lights up when talking about mentoring juniors. Why another feels drained by the same task but energized by complex problem-solving. Why feedback lands well with one person and completely backfires with another.
This is where life stories come in.
Life stories are a simple, structured way to understand your team's motivations and values, without turning your 1:1s into therapy sessions or personality quizzes with questionable accuracy.
This article breaks down a lightweight framework you can use with your direct reports (or even your manager) to build clarity, trust, and better growth plans.
Beyond surface-level team management
What are life stories in a work context?
Life stories are guided reflections on past experiences, both personal and professional, that help surface what someone genuinely cares about.
Not what their job title says. Not what their performance review implies. But what actually drives their behavior.
When people reflect on moments they felt proud, stuck, stretched, or fulfilled, patterns start to appear.
Those patterns reveal:
Motivators (what pulls them forward)
Values (what they use to judge what matters)
Understanding these two things helps managers set better goals, personalize feedback, avoid accidental demotivation, and stop guessing why someone is disengaged.
Or, at the very least, stop assuming “they just don't care.”
Why understanding team motivation matters for managers
Understanding life stories helps managers move from generic management to intentional leadership. When people feel understood, they stop performing for approval and start working with clarity.
This also reduces common management mistakes, such as:
Pushing leadership tracks on people who value craft mastery
Rewarding output when someone values learning
Mistaking quiet for disengaged
♠️
This framework is part ofUX Management Playbook—made for first-time managers building healthier and happier design teams.
Motivators are the reasons people do what they do, even when no one is watching. They often show up in moments of pride, frustration, flow, or resistance.
The goal here isn't self-optimization. It's pattern recognition.
Answer reflection questions
Ask the person to answer the following questions. One answer per sticky note.
What are key life moments you felt most proud of?
What feels most rewarding in your current role?
What feels most frustrating in your current role?
Do you feel challenged or stretched? What would make it more challenging?
What feedback do you hear repeatedly from others?
What areas do you want to improve?
What helps you stay grounded?
Quantity matters more than quality at this stage. Messy notes are fine. You should have a chaotic cluster of thoughts. That's expected.
Now we organize.
Group answers into motivators
Use affinity diagramming to group related answers together. If you've used this in UX research, the process will feel familiar.
Motivators aren't personality traits. They're contextual. They can evolve.
How to run this exercise
Step 2: Identify employee values
Motivators explain what pulls someone forward. Values explain how they judge what matters. They act as internal filters. They influence decisions, reactions, and priorities, especially under stress.
If two designers clash, it's often not a skills issue. It's a values mismatch.
Group motivators into values
Now repeat the affinity process, but one level up. Group motivators into broader themes and name them as values.
One motivator can support multiple values. Duplicate it if needed. Aim for 3–4 core values, not a life manifesto.
Here's how raw reflections connect to values:
"I felt proud mentoring a junior designer"
Motivator: helping others grow
Value: contribution
"I hate vague feedback"
Motivator: clarity
Value: integrity
"I love tackling impossible problems"
Motivator: challenge
Value: mastery
Using life stories in real management situations
1. During onboarding of new team members
Instead of waiting six months to "figure someone out," use this framework in their first month. You'll save time and misunderstandings later.
2. During growth planning with direct reports
Life stories pair naturally with goal-setting frameworks like Goals & Growth Plans.
Values help answer:
What growth actually means to this person
Which opportunities will energize vs drain them
3. During team conflict
When tension arises, values give you a neutral lens: "This looks like a difference in what you prioritize, not effort or intent."
That reframing alone can lower defensiveness.
Common mistakes managers make with this framework
Turning this into a performance evaluation. This isn't about judging performance. It's about understanding what drives someone.
Treating values as fixed forever. People change. Their values can shift. Revisit this conversation every 6-12 months.
Rushing the reflection step. Give people time to think. The best insights come from reflection, not quick answers.
Collecting insights and never using them. Life stories only work if insights influence how you manage. Otherwise, it's just sticky notes with feelings.
Start small, learn fast
Using life stories in real management situations
Life stories don't require psychological training or expensive tools. They require attention and the willingness to slow down long enough to understand people as humans, not just roles.
When you surface motivations and values, decisions become clearer. Conversations become easier. Growth plans stop feeling generic.
Start with one person. Spend 30 minutes. See what you learn.
👉
Whenever you're ready, there are 4 ways I can help you: