The Human Being Behind the User Persona
The Human Being Behind the User Persona
Modern design practice has made enormous progress in understanding users. We have personas, journey maps, empathy interviews, ethnographic research, accessibility standards, and inclusive design principles. These are genuine and valuable advances.
But they have a blind spot.
Almost all contemporary user research focuses on horizontal dimensions of difference: demographics, behaviors, preferences, pain points, contexts of use. These are important. But they exist on a single plane — the plane of what people want, do, and experience.
Stage-Sensitive Design adds a vertical dimension: how people make meaning. This is not another variable to add to the persona template. It is a fundamentally different axis of understanding — one that cuts across all the horizontal variables and reshapes how every one of them is experienced.
Consider: two people may both be thirty-five-year-old professionals with similar incomes, similar education levels, and similar stated preferences on a survey. But if one makes meaning primarily through the expectations and norms of the groups they belong to (what Kegan calls the socialized mind) and the other makes meaning through self-authored values and independent analysis (what Kegan calls the self-authoring mind), they will experience the same product, the same training program, the same organizational structure in profoundly different ways.
The socialized-mind user will look for clear guidance, social proof, and alignment with trusted authority. The self-authoring-mind user will look for customization, autonomy, and evidence-based reasoning. Neither is wrong. But a design that serves one beautifully may alienate the other.
This is not a niche concern. Research by Kegan and others suggests that the majority of the adult population is in transition between or within the socialized and self-authoring orders of meaning-making. A significant minority operates from earlier or later developmental positions. Any product, program, or policy designed for "adults" is, in reality, designed for a developmentally diverse audience — whether the designer knows it or not.
Case Study: The Employee Feedback Platform
A human resources technology company built a performance feedback tool designed around the principle of radical transparency. Employees could give and receive anonymous, real-time feedback from anyone in the organization. The design team believed deeply in the value of open feedback and had extensive research showing that feedback improves performance.
The tool launched to enthusiastic adoption among about thirty percent of the workforce — predominantly employees who were already comfortable with self-reflection, autonomous evaluation, and the ambiguity of receiving unfiltered opinions. These users loved the tool.
The remaining seventy percent had a very different experience. Some found the anonymous feedback threatening and destabilizing. Others used the tool to reinforce social hierarchies rather than challenge them. A significant group simply ignored it, finding the entire premise confusing — why would you want unfiltered feedback from people who might not understand your role?
The design team's error was not in valuing feedback. It was in assuming that everyone values and processes feedback in the same way. A stage-sensitive redesign would have offered multiple pathways into the feedback experience: structured, guided feedback for users who needed more scaffolding; mentor-mediated feedback for users whose meaning-making was organized around trusted relationships; and the original open format for users who thrived in autonomous, self-directed environments.
The company eventually implemented something close to this — after a painful year of declining engagement and a near-revolt from the engineering department. They learned the hard way what this book aims to teach before the damage is done.
The Luminous Commitment: Design as Developmental Hospitality
The Luminous Prosperity framework brings a specific ethical and philosophical orientation to the practice of stage-sensitive design. It is captured in a single phrase: developmental hospitality.
Hospitality, in its deepest sense, is the art of making a stranger feel at home. Not by pretending the stranger is the same as you, but by creating conditions in which their difference is welcomed, honored, and provided for. A good host does not serve only their own favorite food. A good host asks: What do you need? What would nourish you? How can I make room for you as you actually are?
Stage-Sensitive Design is hospitality extended to the cognitive and meaning-making dimension of human diversity. It asks designers to move beyond the unconscious assumption that their own way of making sense of the world is the universal way — and to create products, programs, and environments that make room for the full range of human development.
This commitment rests on five foundational principles that we will explore in depth in Chapter 2, but which we can briefly introduce here:
Principle 1: Every Stage Deserves Respect
Developmental stages are not a hierarchy of human worth. The person who makes meaning through concrete rules and trusted authority is not less valuable, less intelligent, or less human than the person who makes meaning through self-authored principles or post-conventional paradox. Each stage has its own gifts, wisdom, and essential contributions to the human community. Stage-Sensitive Design honors every stage — not with condescension ("We'll simplify it for them") but with genuine respect ("We'll design something that meets them where they are and serves them beautifully").
Principle 2: Invitation, Not Imposition
Stage-Sensitive Design does not attempt to develop people. It does not use design as a covert mechanism for pushing users toward "higher" stages. Instead, it creates environments that meet people where they are while offering gentle scaffolding toward the next edge of their development — scaffolding that can be accepted or declined without penalty. Growth is always an invitation, never an imposition.
Principle 3: The Designer's Own Development Matters
You cannot design with stage sensitivity if you are unconscious of your own developmental position. Every designer has a characteristic way of making meaning, and that characteristic way inevitably shapes the designs they create. Stage-Sensitive Design requires developmental self-awareness — the honest acknowledgment that your perspective is a perspective, not a universal truth.
Principle 4: Complexity Is Not Superiority
One of the most insidious dangers of developmental frameworks is the temptation to equate greater cognitive complexity with greater human value. The Luminous approach explicitly and fiercely rejects this equation. A person who can hold paradox and multiple perspectives simultaneously is not "better" than a person who needs clear rules and dependable structures. They are different — and a well-designed system needs both.
Principle 5: Context Shapes Everything
Developmental stage is not a fixed attribute that a person carries unchanged through every situation. People operate at different levels of complexity in different domains of their lives and under different conditions. Stress, trauma, unfamiliarity, and threat can all temporarily shift a person's meaning-making toward earlier, more concrete modes. Stage-Sensitive Design accounts for this contextual fluidity rather than treating development as a static label.
<aside>
✨
The Luminous Stance: We design the way a wise host prepares a table — with enough variety to nourish every guest, enough beauty to signal care, and enough spaciousness for each person to find what they need without being told what to eat.
</aside>
The Three Promises of This Book
This book makes three promises to its readers:
Promise 1: We will be honest about what developmental psychology does and does not know. The research base for stage models is genuine and substantial — but it is also incomplete, culturally situated, and subject to legitimate critique. We will present the science fairly, name the uncertainties, and resist the temptation to claim more certainty than the evidence supports. Where we are extending beyond established research into Luminous innovations, we will say so explicitly.
Promise 2: We will be practical. This is not an academic treatise on developmental theory. It is a design book — a practitioner's guide to creating better products, programs, and policies. Every chapter includes real-world case studies, actionable frameworks, and Luminous Invitations that you can begin implementing today.
Promise 3: We will be ethical. Developmental knowledge is power, and power can be misused. We will explicitly address the risks of developmental elitism, manipulation, and condescension throughout the book. We will provide guidelines for using stage-sensitive approaches in ways that empower rather than diminish, and we will be transparent about the limits and dangers of the framework itself.
How to Use This Book
The book is organized in three parts:
Part I: Foundations (Chapters 1–2) provides the developmental knowledge and design principles you need before applying stage-sensitive thinking. If you are new to developmental psychology, do not skip these chapters — they establish the conceptual foundation that everything else builds on.
Part II: Domains of Application (Chapters 3–7) applies stage-sensitive thinking to specific design domains: products, programs, communication, organizations, and policy. Each chapter can be read independently, though they are enriched by reading in sequence.
Part III: Practice and Future (Chapters 8–9) addresses the practical questions of how to assess your audience's developmental range, how to integrate developmental data into design processes, and where the field is headed.
Each chapter concludes with three elements:
- ✨ Luminous Invitations: Small, immediate practices you can try today.
- 🔍 Reflection Questions: Prompts for deeper personal and professional reflection.
- 🛠️ Practical Exercise: A hands-on activity that applies the chapter's concepts to your own work.
A Word About Language
Throughout this book, we use terms like "developmental altitude," "meaning-making stage," and "center of gravity." These are descriptive terms — ways of pointing toward observable patterns in how people organize their experience. They are not rankings, grades, or evaluations of human worth.
We have chosen the word "altitude" deliberately, rather than "level" or "tier," because altitude carries a useful metaphorical quality: at different altitudes, you see different landscapes. A person at a mountain's base sees the meadow in intimate detail — the wildflowers, the insects, the texture of the soil. A person at the summit sees the entire valley and the surrounding ranges. Neither perspective is wrong. They are different vantage points, each with its own gifts and limitations.
The goal of Stage-Sensitive Design is not to move everyone to the summit. It is to design experiences that serve people beautifully wherever they stand on the mountain — and, when appropriate, to offer gentle trails toward the next vantage point for those who are ready and willing to walk.
A Word About Humility
We must be transparent about something from the very beginning: we do not fully understand human development. No one does. The models we will explore in this book — Piaget's, Kegan's, Loevinger's, Cook-Greuter's, Spiral Dynamics — are the best maps we currently have. But they are maps, not territories. They are simplified representations of an astonishingly complex, culturally embedded, individually unique, and fundamentally mysterious process.
This book will be most valuable if you hold it the way a skilled navigator holds a chart: with respect for what it reveals, awareness of what it cannot show, and readiness to adjust course when the actual waters don't match the markings.
We are not offering a perfect system. We are offering a better system — one that, we believe, can reduce unnecessary suffering, increase genuine inclusion, and bring more wisdom to the profoundly consequential act of designing the experiences, environments, and institutions that shape human lives.
<aside>
⚠️
Ethical Caution: Developmental frameworks have historically been used to justify hierarchies, exclude marginalized communities, and rationalize cultural imperialism. We are aware of this history and take it seriously. Throughout this book, we will explicitly address the ethical risks of stage-sensitive work and provide guidelines for navigating them with integrity. If you find yourself using developmental knowledge to rank, dismiss, or manipulate others, something has gone wrong — and we invite you to return to the foundational principle: every stage deserves respect.
</aside>
The Invitation
You are holding a book about design. But at a deeper level, you are holding a book about attention — about what we notice and what we miss when we create things for other human beings.
The developmental dimension of human diversity has been hiding in plain sight. It explains why the most well-intentioned products sometimes alienate the people they were meant to serve. It explains why organizational change efforts that seem self-evidently good to their architects are experienced as threatening or meaningless by significant portions of the workforce. It explains why public policies that work brilliantly in one community fail spectacularly in another, despite identical demographics.
Once you learn to see developmental diversity, you cannot unsee it. It changes how you observe meetings, how you read user feedback, how you listen to disagreements, how you interpret resistance, and how you design for the full, magnificent, irreducibly complex range of human meaning-making.
This seeing does not make design easier. It makes it harder — because you can no longer pretend that your own perspective is universal, and you can no longer design in the comfortable bubble of your own developmental altitude. But it also makes design better — more inclusive, more effective, more humane, and more aligned with the luminous reality of what human beings actually are.
Welcome to Stage-Sensitive Design.
Let us build something worthy.
✨ Luminous Invitations
These are small, immediate practices you can begin today. Choose one that resonates.
- The Invisible Assumption Audit: Think about a product, program, or experience you have recently designed (or are currently designing). Without judgment, ask yourself: What am I assuming about how my users make meaning? Am I assuming they value autonomy — or belonging? Am I assuming they can hold ambiguity — or that they need clear structure? Am I assuming they want to be challenged — or that they want to feel safe? Write down your assumptions. We will return to this list.
- The Memory of Mismatch: Recall a time when you encountered a product, a training, a policy, or an environment that felt subtly wrong for you — not because it was poorly made, but because it seemed to assume a different kind of person than you were at that moment. What was the experience like? What did you do? What did you wish the designer had understood about you?
- The Developmental People-Watch: Spend one day observing how the people around you — colleagues, friends, family members — respond differently to the same situation. A meeting. A piece of news. A change in routine. Notice: are they responding to different content, or are they responding from different architectures of meaning-making? Do not label or classify — simply notice.
🔍 Reflection Questions
- Before reading this introduction, had you ever considered that your audience might differ not just in preferences and demographics, but in how they make meaning? What implications does this have for your work?
- Which of the three opening failure scenarios resonated most with you? Have you witnessed or participated in a similar developmental mismatch? What happened?
- The introduction argues that "designing for everyone" often means "designing for people who think like the designer." Can you identify an example of this in your own experience — either as a designer or as a user?
- How do you respond to the idea that developmental stages are "descriptions, not rankings"? Does this feel genuinely true to you, or do you notice a pull toward hierarchy? What might that pull tell you about your own relationship to developmental frameworks?
- The Luminous commitment is described as "developmental hospitality." What does this metaphor evoke for you? How might it change the way you approach your next design project?
🛠️ Practical Exercise: The Design Autopsy
This exercise invites you to perform a "developmental autopsy" on something you have designed or are currently designing.
Step 1: Choose a Design
Select a product, program, policy, curriculum, communication, or experience that you have helped create. It can be something that succeeded, something that failed, or something currently in progress.
Step 2: Map the Assumed User
Without consulting any formal developmental framework (we will learn those in Chapter 1), describe the kind of mind your design assumes. What does it assume about how the user processes information? What does it assume about how much ambiguity the user can tolerate? What does it assume about the user's relationship to authority, rules, and social norms? What does it assume about the user's capacity for self-reflection?
Write this description in plain language. Be as honest as possible.
Step 3: Map the Actual Range
Now think about the actual people who encounter your design. Are they all the "assumed user" you described in Step 2? Or is there a wider range? Describe the range as best you can — from the people for whom the design works beautifully to the people who seem to struggle, disengage, or resist.
Step 4: Identify the Gap
Where is the gap between your assumed user and your actual range? What does your design not provide for the people who fall outside the assumed profile? What might they need that your design currently does not offer?
Step 5: Generate One Hypothesis
Based on this exercise, formulate one hypothesis about how your design could be made more stage-sensitive. You do not need a complete solution — just a direction. We will build on this hypothesis throughout the book.
Keep this design autopsy. It will become the backbone of your practical learning throughout the chapters that follow.
In the next chapter, we step into the developmental landscape itself — the models, the research, the controversies, and the Luminous synthesis that will equip you to see what most designers miss.
Chapter 1: The Developmental Landscape — A Primer for Designers
The Map You Were Never Given
Imagine you have spent your entire career designing buildings — beautiful, functional, award-winning buildings — without ever having been taught that the people who use them have bodies. You know about aesthetics. You know about structural engineering. You know about light, proportion, and flow. But somehow, in all your training, no one ever mentioned that your users have knees that bend, lungs that breathe, eyes that fatigue, and spines that ache after too many hours in a poorly designed chair.
This is approximately the situation of most designers, educators, organizational architects, and policy makers when it comes to human development. They have been trained to think about their audiences in sophisticated ways — behaviorally, demographically, psychographically, culturally — but almost no one has handed them the map that shows how people grow. How the very architecture of human meaning-making shifts and reorganizes over the course of a lifetime. How adults are not a single category but a spectrum of meaning-making complexity, each point on that spectrum producing a qualitatively different experience of the same product, the same message, the same organizational structure.
This chapter gives you that map.
It is not a complete map — no map of human development could be. It is a practitioner's map: enough detail to transform your design practice, enough honesty to keep you humble about what the map cannot show, and enough Luminous nuance to ensure you never mistake the map for the territory.
<aside>
📍
A Note Before We Begin: This chapter synthesizes decades of developmental research into a form usable by designers. If you are a developmental psychologist, you will notice simplifications — necessary ones, made in the service of practical application. If you are encountering developmental theory for the first time, know that each model described here has generated hundreds of scholarly publications. We provide references for deeper exploration in the bibliography. Our goal here is not comprehensive academic coverage. It is design literacy.
</aside>