UX
Actor Mapping
A practical UX and service design method for identifying the roles, systems, and interactions that shape how an experience actually works.
How to use actor mapping to understand who is involved, clarify responsibilities, and improve coordination across people, teams, and systems.
What it is
Actor mapping is a UX and serviceService DesignMap what happens across teams, systems, and touchpoints so services feel more joined up for users and easier to deliver internally.Open service method used to identify and visualise all the people, roles, and glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term involved in an experience.
It focuses on who is involved, what they do, and how they interact with each other.
Actors can include users, internal teams, third-party glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term, support staff, and automated glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term.
Unlike guideStakeholder MappingIdentifying and organising stakeholders so influence, priorities, relationships, and potential conflicts are clearer.Open guide, which focuses on influence and interest, actor mapping focuses on roles and glossaryInteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term within a glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term or service.
The goal is to understand how different actors contribute to the experience and where coordination is required.
Actor mapping is most useful when the experience depends on multiple roles and systems working together, not just a single user moving through a flow.
When to use it
Use this method when multiple roles are involved.
It is most useful when:
It is less useful when:
Actor mapping is often used alongside service blueprinting and workflow mapping.
Key takeaway
Use actor mapping when better design depends on understanding who is involved, how they interact, and where responsibilities or dependencies break down.
How to run it
Set up properly
Be clear on the scope and what the map is for. Actor mapping is a component of ecosystem and glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term work, so it needs a decision it feeds.
Include actors who are not people (glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term, glossaryAlgorithmAn algorithm is a set of rules or instructions used to solve a problem or perform a task.Open glossary term, third parties) where they meaningfully act on the experience.
Run the method
Actor mapping identifies everyone and everything involved in delivering or receiving a glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term, and how they relate. It answers who is in play before anybody designs.
- Identify all the actors, including the ones nobody thinks of as part of the glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term.
- Define roles and responsibilities for each, as they actually operate rather than as documented.
- Map how actors interact, and in which direction information and value flow.
- Highlight glossaryDependencyA dependency is a component or system that another part of the system relies on to function.Open glossary term and handoffs, marking where one actor cannot proceed without another.
- Group actors where it clarifies: by organisation, by proximity to the user, by influence.
Include the actors you do not control. Third parties and regulators shape the experience as much as your own teams and are routinely left off the map.
Capture and make sense of it
The value comes from knowing who is involved. After mapping, document:
- Every actor and their role
- glossaryDependencyA dependency is a component or system that another part of the system relies on to function.Open glossary term between actors
- Handoffs where responsibility transfers, which is where things get dropped
- Actors with influence over the experience but no ownership of it
Use this as an input to glossaryService BlueprintA service blueprint is a visual map that shows how a service is delivered, including frontstage and backstage processes.Open glossary term and ecosystem maps. On its own it is a starting point rather than a finding.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If roles aren’t clear, neither is the experience.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you design systems that work across people and processes.
Get in touch
If this sounds like something you need, we can help you map your actors and design systems that work across people, teams, and tools.
No guesswork. No assumptions. Just clarity on how everything connects.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is actor mapping in UX?
It is a method used to identify and map roles involved in an experience.
When should you use actor mapping?
Use it when multiple people or systems are involved.
How is it different from stakeholder mapping?
Actor mapping focuses on roles and interactions, while stakeholder mapping focuses on influence.
What does an actor map include?
Actors, roles, interactions, and dependencies.
Does actor mapping improve UX?
Yes. It helps clarify roles and improve coordination.
Quick take
If you want to understand everyone involved in an experience, map the actors.
Related Services
