The core idea
Employee experience concerns how people encounter work and the organisation over time. It includes joining and leaving, but also ordinary scheduling, tools, management and relationships. Armstrong and Taylor position it as a broad employment-practice concern. It should connect existing people practices rather than become a separate programme of perks or communications.
Source and attribution [1]Using it in practice
Choose a defined employee group and map a real journey, such as moving between sites or returning after absence. Ask employees what happened, what they needed and where effort was wasted. Compare that evidence with the intended process. Prioritise a small number of recurring friction points, assign owners across departments and test whether the experience improves.
An example, not a reported case
Worked example · illustrative
A new starter describes a warm welcome but spends two weeks borrowing equipment and repeating personal details to different teams. HR, IT and the manager agree one readiness check before arrival and a named contact for unresolved issues. Feedback focuses on being able to do the job, not only satisfaction with the welcome event.
What to watch for
There is no single employee experience. Role, contract, location, accessibility, personal circumstances and manager behaviour create different realities. Journey maps can conceal these differences if they describe an idealised average employee.
Distinguish the lifecycle from a person’s experience
AIHR’s employee-journey guidance distinguishes the stages of employment from the interactions and lived experience within them. The lifecycle is a useful organising map; it does not tell you what a particular person encountered. Two people can complete the same onboarding checklist while one receives patient support and the other spends days chasing access. Use the existing Employment Lifecycle page to locate a journey, then investigate how it actually works. The aim is not to manufacture a uniformly positive feeling but to make work understandable, usable and fair while dealing honestly with difficult decisions.
Choose a specific moment with a clear boundary
Start with one experience that can be investigated, such as moving to a new site, requesting equipment or becoming a manager. Define where the journey begins and what a satisfactory resolution would look like from the employee’s perspective. A transfer may begin when the change is first discussed and end when the employee can work independently in the receiving team. Keep recruitment, induction and later development connected, but avoid trying to redesign all of employment in one exercise. A manageable boundary makes it easier to identify ownership and see whether an improvement has helped.
Map what happened rather than an imagined average
Invite a small, varied group to describe recent instances. Ask what they were trying to do, what information they had, what they did next and where they needed help. Distinguish the event from their interpretation without dismissing either. Include differences in shifts, location, digital access and familiarity with the organisation. Do not invent a persona from demographic stereotypes or assume that one employee speaks for everyone with a similar background. Check the emerging map with another participant and compare it with process records where appropriate. Mark gaps in evidence instead of filling them with a neat but untested story.
Worked example: a site transfer that appears complete
Invented case: HR records a transfer as finished when the payroll location changes. The employee still lacks access to the new site, does not know who approves expenses and receives messages from the old manager. The journey review identifies separate handovers involving the two managers, HR and the access team. The proposed improvement confirms the receiving contact, checks necessary access before the first shift and tells the employee where unresolved questions go. Success means being able to work and obtain a correct answer, not merely completing an administrative transaction. A short follow-up checks whether the old communications have stopped.
Find the operating cause behind the frustrating moment
A confusing email may be the visible symptom of unclear responsibility. Before rewriting the message, ask who owns the answer, who has the information and what causes the delay. For a pay query, a quick acknowledgement can help, but it is not a substitute for investigation and correction. Give the journey an accountable owner who can coordinate the contributing teams, while keeping specialist decisions with appropriately authorised people. Agree how an exception moves between teams without making the employee repeat the whole account. Preserve safeguards that protect accuracy and privacy while removing avoidable repetition.
Test with people who use different routes
Ask whether someone on a night shift, without a work computer or using assistive technology can complete the journey and get help. Include the managers who receive requests, because an apparently simple employee form may create an unworkable manual process elsewhere. Test a straightforward case and an exception using invented information. Observe where instructions are misunderstood and revise them before a wider release. These are good-practice design checks; specific accessibility, equality and adjustment duties require current guidance for the situation. Do not treat a successful test with one office-based user as evidence that the service works for everyone.
Use listening proportionately and explain the response
Choose a few questions tied to the moment, such as whether the person knew the next step and could get a useful answer. Avoid repeatedly asking employees for views when nobody is responsible for responding. Explain the purpose, who can see the information and how themes will be reported. A unique account can identify its author even after a name is removed, so use care with small teams and free text. Return a concise account of what changed, what did not and why. If an individual concern needs a separate route, explain that rather than letting it disappear into aggregate feedback.
Measure useful outcomes without promising causation
For a site transfer, track readiness for the first shift, repeated contacts and unresolved issues alongside a short account of the employee’s experience. Define what counts as ready and use the same definition over time. A lower contact count is not automatically better if people have stopped asking for help. Look at the quality of resolution and whether an issue returns. Improved retention or engagement may be consistent with better experiences, but many other factors influence them. Do not claim that changing one email or checklist caused a broader workforce outcome without stronger evidence.
Connect the improvement to the promise and the wider system
Compare the experience with what the organisation promises in recruitment, policies and manager communications. If a promise cannot currently be delivered, correct the underlying practice or explain the limitation honestly. Feed recurring problems into the organisation-design guide when they reveal unclear authority or incompatible systems, and into organisation development when a bounded change needs diagnosis and testing. Use employee voice to challenge whether the improvement works in ordinary conditions. Keep the journey under an identified owner so that a later system or policy change does not silently recreate the original friction.
Take it into your next conversation
Three useful questions.
- What would a resolved journey look like from the employee’s perspective?
- Which handover causes repetition, delay or an unclear answer?
- Whose experience have we not yet tested?
Related terms
Go to the evidence
Sources & attribution
Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 29–33. Edition & reading notes ↗
Further reading: Emma Bridger (2018), Employee Engagement: A practical introduction, 2nd edition, PDF pp. 80, 150 and 215. Edition & reading notes ↗
Further reading: AIHR (Undated), HR Business Partner Resource Library, Resource list, PDF pp. 3, 9, 13–14 and 17. Edition & reading notes ↗
[1] Armstrong & Taylor (2023), 16th edition, chapters 29–33 — reading notes ↗
[2] Acas: discrimination and the law ↗
[4] AIHR, Employee Experience Design: All HR Needs to Know; consulted 29 September 2026 ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Original ADM HR teaching guide with attributed background reading. Practical guidance expanded on 29 September 2026. The worked cases, diagnostic questions and suggested decision records are original editorial illustrations, not validated assessment instruments or reproductions of member templates. Source links distinguish further reading from the original authorship of models. The overview review date is retained; this expansion does not establish a new legal review date for linked guidance.
Published 2026-09-25 · Reviewed 2026-09-25. Editorial approach