Was human-centered design all wrong?
No, but it fails to capture the whole picture.
Don Norman introduced human-centered design (HCD), the approach of putting people and their needs at the center of the design process, in the 1980s and almost 50 years later at DDX San Diego 2026, he challenged the philosophy.
Human-centered design gave the industry an important shift in perspective, paying close attention to the people who would actually live with what we create, but there’s tension. Design can create tremendous value for people while also creating unintended consequences for cultures, communities, organizations, and the world around them.
If we optimize for the person in front of us, what happens to everyone and everything outside the frame?
And as technology becomes increasingly agentic, that broader view becomes even more relevant. We're no longer designing only things that people interact with. We're increasingly designing systems that can act, make decisions, and influence what happens next.
Summary
- Human-centered design does not capture the whole picture
- New philosophies emerge including life-centered design, intelligence-centered, human-agent centered design, and agent-centered design
- Four shifts matter most in the age of agentic AI: design for the system, not just the user; turn frameworks into prototypes; study behavior over stated needs; and translate insights and decisions into the language of the business
- The future of design is about what you do with what you know
Emerging design philosophies
Life-Centered Design (LCD) expands the focus from the individual user to the larger living system that the product or service exists within. It seeks to align design decisions with global goals such as the United Nation’s Sustainable Development Goals.
Intelligence-Centered Design (ICD) and Human-Agent Centered Design (H-ACD) are extensions of HCD where AI plays an active role in the design process alongside human intelligence, each learning from, making decisions, and mediating the process.
Agent-Centered Design (ACD) puts AI agents at the center as the primary participant in the process, agents building for agents.
Key elements of design and innovation in an agentic world
Start with the people, not the product
Good experiences have always started with deep understanding of the people who use the product, service, or system. Needs, expectations, and priorities are shaped by environment, so what works in one market, organization, or culture can't automatically be treated as a universal truth for all.
That's why ethnography and other forms of contextual research remain so valuable. Before asking what we should build, we need to understand the world people are navigating.
Questions to ask:
- Who are we really designing for?
- What assumptions are we bringing from our own environment?
- What would happen if this design enters a different context?
- What are users' stated choices and how does that differ from their actual behavior?
The discipline of understanding people hasn't gone anywhere. It's just being asked to stretch further, to the systems, risks, and impacts beyond individuals.
Design for the system around the human
Behavior is shaped by systems, organizational structures, constraints, and the decisions made around you, so those factors are part of what we are designing for. Agentic AI makes this deep understanding of context even more important.
When AI can act, make decisions, and influence what happens next, it becomes a key part of the system. Therefore, design has to account for the relationship between humans and their agents including how they work together, what artifacts are created along the way, how do they communicate, what decisions does AI make and what are its responsibilities.
Questions to ask:
- What happens outside the immediate experience?
- How might the system change over time?
- How do decisions get made? What's the logic behind them?
One practical takeaway is to spend more time understanding what people actually do, not just what they say they do. Diary studies, observation, prototype testing, and live site testing can all help surface what people may not be able to articulate themselves. Rather than simply asking “why,” ask, “What drove you to make that decision?” This is an open question to prompt an honest explanation of what influenced their thinking and led them to take a certain action.
Do more "design doing"
Design has no shortage of frameworks, methodologies, books, and white papers. While these give us useful ways to think, real change only happens when teams transform what they’ve learned into something tangible. In the end, impact isn't measured by the depth of your knowledge, but by what you actually create with it.
Question to ask: What's the smallest thing I could do to build or test this idea this week?
A simple prototype will reveal insights that hours of discussion never could. A real interaction exposes the hidden gaps between what people say and what they actually do. A quick experiment tells a team far more than another round of debate.
At its best, good design thinking must always lead to good "design doing."
Earn influence by translating value into the language of the business
Research and design often sits in the middle of an organization. Leadership sets direction, research gathers insight, design shapes the experience, then implementation follows. When each function speaks a different language, intent can get lost along the way.
Designers and researchers are inherently connectors. We bring together different perspectives, make sense of complexity, and help people see how decisions affect one another. But we aren't often in the room when the decisions themselves are being made. Policy, process, business models, and organizational structures are all forms of design, yet designers are often brought in after those choices have already been made.
There is an opportunity and a need for design thinking and "design doing" to move further upstream, and that starts with speaking the language of the people making those decisions: finances and margins.
Questions to ask:
- What does this insight or design mean for productivity, adoption, risk, growth, for the people working inside the system and for the people affected by it?
- What would this save, generate, or protect, in dollars, time, or risk?
- Can we connect the human story to a number?
- How can I socialize this upwards in my organization?
Business decisions are design decisions.
Designing for what comes next
The next era of design is expanding what we consider when we design.
As systems become more autonomous, designers have an opportunity to shape not only experiences, but the policies, services, and the systems around them.
The future of design is less about finding the right framework and more about what we choose to do with what we know.
Our monthly newsletter, User Tested is for product, design, and research teams who want to make UX research a strategic accelerator. Subscribe to User Tested.
