24 Future Trends in Employee Experience

Learning Objectives

You will be able to:

Design hybrid work deliberately, deciding what the office is for and engineering against its known failure modes.
Analyse the gig economy and the blended workforce, and specify what employee experience means for people who are not employees.
Explain the employee-centric ecosystem, in which experience is built around the person’s whole working life rather than around a single employer’s boundary.
Synthesize the book: connect agile HR, organization design, and experience design into one coherent practice, and identify the enduring tensions that will not resolve.

24.1 Introduction

This closing chapter looks forward, and does so under a discipline the book has argued for throughout: treat predictions as hypotheses to be tested, not plans to be defended (Kent Beck et al., 2001). Three shifts are already far enough advanced to design for rather than speculate about. Hybrid work has settled as the dominant knowledge-work arrangement, converting place from a default into a decision. The gig economy and the blended workforce have made the employment contract itself variable, so that experience design must reach people who are not employees. Employee-centric ecosystems describe the destination both shifts point toward: value propositions organized around a person’s whole working life, including its portions spent elsewhere.

Each trend sharpens the same tension the book has carried since Chapter 3. Autonomy and alignment, personalization and fairness, flexibility and belonging: these are not problems awaiting a solution but permanent trade-offs requiring continuous design. The organizations that will do well are not those that resolve the tensions but those that hold them consciously, sense their movement early in the Chapter 13 manner, and adjust in short cycles (Katharina Harsch & Marion Festing, 2020).

flowchart LR
    H["Hybrid work:<br>place becomes<br>a decision"] --> EC["Employee-centric<br>ecosystems"]
    G["Gig and blended<br>workforce:<br>contract becomes<br>variable"] --> EC
    EC --> Q["Experience designed<br>around the person's<br>whole working life"]
    style H fill:#e3f2fd,stroke:#1976D2
    style G fill:#fff8e1,stroke:#F9A825
    style EC fill:#e8f5e9,stroke:#388E3C
    style Q fill:#ede7f6,stroke:#7E57C2

24.2 Hybrid Work

24.2.1 Deciding What the Office Is For

Chapter 22 established the evidence: remote work delivers productivity and retention gains, the shift is structural rather than temporary, and employees value it enough to trade pay for it, while carrying a promotion penalty for those who use it (Jose Maria Barrero et al., 2021; Nicholas Bloom et al., 2015). Hybrid design begins where that evidence leaves off, with a question most organizations answered by default rather than by decision: what is the office for? Once presence is no longer the price of employment, the building must earn attendance, and the activities it wins at are specific, forming trust with people you do not yet know, resolving conflict, transmitting the tacit craft that Chapter 17’s socialization requires, and the collective moments of Chapter 21’s peak creation. Focused individual work, by contrast, is the activity offices do worst and commutes subsidize least defensibly.

The design that follows is anchored rather than uniform: teams choose overlapping days for the collaborative work that benefits from co-location, individual work distributes, and policy is set per team within organizational guardrails rather than by a single company-wide day count, the contingency logic of Chapters 4 and 13 applied to place. The guardrails matter because two failure modes are now well documented. Proximity bias, from Chapter 22, quietly allocates careers to the visible. And hybrid asymmetry: meetings with most participants in a room and some on a screen systematically disadvantage the remote, which is why mature practice adopts hybrid-first conventions, everyone on their own screen when anyone is remote, decisions written down in the Chapter 17 externalization sense, so that the record rather than the room carries authority.

Common Misconception: Hybrid Is a Policy Question

The mandate-versus-choice debate treats hybrid as a rule to be set, and this misdiagnoses the work. Hybrid is an operating-model change: it alters how decisions are made and recorded, how managers observe and coach, how belonging is built, how careers are evaluated, and how workspace is designed and paid for. An organization that issues a three-day rule without changing meeting practice, evaluation evidence, onboarding, or workplace design has changed attendance, not its operating model, and will experience the costs of both arrangements without the benefits of either.

Practitioner Insight: Redesign Onboarding First

Hybrid’s sharpest experience failure lands on new joiners, who have no existing network to draw on and cannot absorb tacit norms from a room they rarely share. If you make one hybrid investment, make it the first ninety days: front-loaded in-person time, a named buddy in the Chapter 20 journey pattern, explicit norm documentation that veterans never needed written down, and deliberate introduction to the informal network. Every subsequent experience for that person compounds from this base, and the Chapter 20 journey map will show you exactly where it currently breaks.

24.3 The Gig Economy and the Blended Workforce

24.3.1 When the Contract Becomes Variable

Organizations increasingly staff work through a portfolio: employees, contractors, freelancers, platform workers, agency staff, and alumni returning for projects. The forces are familiar from Chapter 2, the pursuit of scarce skills, demand volatility, and the desire for flexibility on both sides of the relationship, and the workforce’s own preferences have shifted, with many skilled professionals choosing portfolio careers over the standard bargain. The consequence for this book’s subject is uncomfortable: a discipline built around the employee lifecycle of Chapter 19 now confronts populations who never enter it.

The experience question therefore becomes a question of principle before it becomes a question of design. A contractor sitting in the same squad as an employee, in the Chapter 11 sense, contributes to the same outcome and encounters most of the same touchpoints, badge, tools, stand-up, feedback, and yet is routinely excluded from the systems that make those touchpoints work: no learning access, no development conversation, no listening survey, no recognition, no offboarding beyond an expired badge. Two costs follow. The practical one is performance: excluding a squad member from its feedback and learning loops degrades the squad. The ethical one is plainer, and organizations should state their position explicitly rather than let procurement policy decide it by default. Between the extremes of full parity and pure transaction, most organizations settle on a defensible middle, equal experience for anything affecting the work, the tools, the team, the safety, the feedback, with employment-specific benefits necessarily remaining employment-specific, and they document where the line falls and why.

Blended Workforce: Which Experiences Extend Beyond Employees?

Experience element	Typical practice	Defensible design
Tools and access	Delayed, partial	Same as employees, day one
Team rituals and stand-ups	Ad hoc	Full inclusion where they do the work
Feedback and recognition	Excluded	Included; work-relevant feedback flows both ways
Learning	Excluded	Access to work-relevant capability building
Listening and voice	Excluded	Included, with results segmented by population
Benefits, equity, tenure rewards	Employment-specific	Legitimately employment-specific; be explicit
Offboarding and alumni relationship	Badge expires	Designed exit and re-engagement path

24.4 Employee-Centric Ecosystems

24.4.1 Designing Around the Person, Not the Boundary

The two preceding trends converge on a third. If place is chosen and contract is variable, the stable unit of design is no longer the job or even the organization; it is the person’s working life, of which any single employer occupies a portion. An employee-centric ecosystem organizes the proposition accordingly: skills portable and verifiable beyond the firm’s boundary; internal talent marketplaces of the Chapter 23 kind extended to project work, alumni, and partners; career paths that anticipate departure and return rather than treating exit as failure; wellbeing and financial support designed for a whole life rather than a role, in the Chapter 22 manner; and communities of practice, from Chapter 16, that cross the corporate boundary into the professional field.

The strategic logic is not altruism, and stating it plainly is more persuasive than moralizing. In a transparent labour market, the employer that maximizes a person’s long-term value, including value realizable elsewhere, is the one people choose, recommend, and return to; the employer that maximizes short-term capture is the one they leave quietly and describe accurately on the platforms Chapter 7 identified as the employer brand’s real channel (Jacob Morgan, 2017; Ben Whitter, 2019). Ecosystem thinking is the experience-era answer to a question the utility era never had to ask: what does an organization owe someone whose relationship with it is one chapter of a longer story?

24.4.2 The Tensions That Will Not Resolve

Three tensions run through everything in Part IV, and it is more useful to name them than to pretend a framework dissolves them. Personalization versus fairness: fit for the individual versus consistency across the workforce, managed by Chapter 22’s constant-rule principle rather than solved. Flexibility versus belonging: autonomy over time and place versus the shared context in which trust, tacit learning, and culture form, managed by deliberate design of the moments that require presence. Data-driven experience versus privacy: better design requires evidence, and evidence collection is experienced as surveillance without the governance of Chapters 12 and 23. Each tension is a permanent design conversation, and an organization that claims to have solved one has usually just stopped listening to one side of it.

flowchart TD
    P1["Personalization"] <--> F1["Fairness"]
    P2["Flexibility"] <--> B["Belonging"]
    D["Data-driven design"] <--> PR["Privacy"]
    P1 --> M["Managed continuously,<br>not resolved once"]
    F1 --> M
    P2 --> M
    B --> M
    D --> M
    PR --> M
    style M fill:#e8f5e9,stroke:#388E3C
    style P1 fill:#e3f2fd,stroke:#1976D2
    style P2 fill:#e3f2fd,stroke:#1976D2
    style D fill:#e3f2fd,stroke:#1976D2
    style F1 fill:#fff8e1,stroke:#F9A825
    style B fill:#fff8e1,stroke:#F9A825
    style PR fill:#fff8e1,stroke:#F9A825

24.5 Bringing the Book Together

24.5.1 One Practice, Four Parts

The book’s four parts describe one practice viewed at four magnifications. Part I supplied the mindset and methods: the manifesto’s values translated into transparency, collaboration, adaptability, and customer-centricity, and the Scrum and Kanban disciplines that put them to work (Kent Beck et al., 2001; Natal Dank & Riina Hellström, 2020). Part II applied them to HR’s own functions, rebuilding recruitment, performance, learning, teams, and engagement around short loops and employee-as-user thinking. Part III widened to the organization, its structures, culture, leadership, learning systems, and change capability, because HR practices cannot outrun the operating model that surrounds them (Stephen Denning, 2018). Part IV closed the loop by asking what all of it feels like, and made that feeling a designed object with its own methods and evidence (Emma Bridger & Belinda Gannaway, 2021; Jacob Morgan, 2017).

The connecting thread is a single reversal, stated once more at the end: work is designed around people rather than people around work, and the design is never finished, because the evidence keeps arriving. That is why agility and experience belong in one book. Agility without experience design optimizes a system nobody wants to work in; experience design without agility produces a beautiful programme that the next quarter’s reality invalidates. Together they describe an HR practice that senses, tests, and adapts, in service of an organization that can do the same.

24.6 Case Studies

24.6.1 Case Study 1: Atlassian, Team Anywhere as an Operating Model

The Australian software company Atlassian committed in 2020 to a distributed-first model it calls Team Anywhere: employees choose where they work, including which country, within a set of approved locations, with no minimum office attendance, and offices repositioned as gathering places rather than daily destinations. What distinguishes the case from a remote-work policy is the operating-model work behind it. Atlassian funds and orchestrates deliberate in-person “intentional togetherness” gatherings for teams several times a year, aimed precisely at the trust-forming and craft-transmitting activities this chapter identifies as the office’s comparative advantage. It rebuilt meeting and documentation practice around asynchronous defaults and written decisions. It published its own research on the results, reporting that hiring reach widened dramatically once candidates were no longer filtered by commute radius, that retention and applicant volumes improved, and that team connection depended on the designed gatherings rather than on ambient office time. And it committed to studying its own model publicly, iterating rather than declaring the answer, the Chapter 18 change discipline applied to the workplace itself.

Discussion Questions:

Atlassian replaced ambient office time with funded, designed gatherings. Analyse this using Chapter 21’s peak-creation strategy and Chapter 17’s socialization mechanism.
Distributed hiring widens the talent pool and complicates pay, tax, and equity across locations. How would you design a location-independent proposition that survives Chapter 22’s fairness test?
The company publishes its own findings, including unfavourable ones. Argue the employer-brand and internal-trust value of this using Chapters 7 and 15.

24.6.2 Case Study 2: Unilever’s U-Work, Employment Reimagined

In 2019 Unilever launched U-Work in the United Kingdom, a contract model designed for people who want the flexibility of gig work without its insecurity. U-Workers are employed by the company but work in assignments across the business, receive a modest monthly retainer between assignments plus pay for the assignments they take, and retain core employment benefits including pension and health coverage. The model targets populations the standard contract serves badly, parents and carers, semi-retired specialists, people combining work with study or caring, and gives the company a flexible, pre-vetted internal pool for peaks and projects, an internal talent marketplace of the Chapter 23 kind expressed as a contract rather than a platform. Unilever has since extended and studied the model, positioning it within a broader future-of-work agenda that includes large-scale reskilling commitments. U-Work is the clearest available answer to this chapter’s central question about the blended workforce: rather than accepting the trade-off between flexibility and security as given, redesign the contract so that the person, not the boundary, is the unit of design.

Discussion Questions:

U-Work sits between the employment and gig models. Which risks does it move from the individual to the organization, and what does the organization gain in return?
Which populations from the personalization analysis of Chapter 22 does this contract serve, and which does it still leave unserved?
Assess U-Work as an employee-centric ecosystem intervention. What would extending it to alumni and partners require, and where would it strain?

24.7 Summary

Chapter Summary

Three shifts are advanced enough to design for. Hybrid work makes place a decision, requiring organizations to determine what the office is for, trust formation, conflict resolution, tacit transmission, collective moments, and to engineer against proximity bias and hybrid asymmetry through anchored team-level design, hybrid-first conventions, written decisions, and rebuilt onboarding (Jose Maria Barrero et al., 2021; Nicholas Bloom et al., 2015). The gig economy and blended workforce make the contract variable, forcing an explicit position on which experiences extend beyond employees, with work-affecting elements defensibly extended and employment-specific benefits explicitly bounded. Employee-centric ecosystems follow: experience designed around the person’s whole working life, portable skills, marketplaces reaching alumni and partners, careers that anticipate return, on the transparent-market logic that the employer maximizing long-term personal value is the one people choose and recommend (Jacob Morgan, 2017; Ben Whitter, 2019). Three tensions, personalization against fairness, flexibility against belonging, evidence against privacy, are permanent design conversations rather than solvable problems. Atlassian shows distributed work as an operating model with designed togetherness; Unilever’s U-Work shows the contract itself redesigned around the person. The book closes on its single reversal: design work around people, test everything, and keep adapting, because the evidence keeps arriving (Kent Beck et al., 2001; Natal Dank & Riina Hellström, 2020).

Key Terms

Hybrid work · Anchored days · Hybrid asymmetry · Hybrid-first conventions · Proximity bias · Blended workforce · Gig economy · Extended experience principle · Employee-centric ecosystem · Portable skills · Alumni re-engagement · Permanent design tensions

Summary

Concept	Description
Hybrid Work
Predictions as hypotheses	Treating forecasts as testable claims rather than plans to defend
Hybrid work	Distributed and on-site work combined, making place a decision rather than a default
What the office is for	Trust formation, conflict resolution, tacit transmission, and collective moments
Anchored team design	Teams choosing overlapping days within guardrails rather than a company-wide day count
Hybrid asymmetry	The systematic disadvantage of remote participants in room-dominated meetings
Hybrid-first conventions	Everyone on their own screen when anyone is remote, with decisions written down
Proximity bias	Careers quietly allocated to the physically visible
Hybrid onboarding priority	Front-loading investment in the first ninety days, where hybrid fails newcomers hardest
Operating-model fallacy	Setting an attendance rule without changing meetings, evaluation, onboarding, or space
Blended Workforce
Blended workforce	A staffing portfolio of employees, contractors, freelancers, agency staff, and alumni
Gig economy	Work organized as assignments and platform tasks rather than continuing employment
Extended experience principle	Extending work-affecting experiences to everyone who does the work
Employment-specific boundary	Benefits, equity, and tenure rewards legitimately reserved, but stated explicitly
Ecosystems
Employee-centric ecosystem	Experience organized around a person's whole working life, not one employer's boundary
Portable skills	Capability made verifiable and useful beyond the current employer
Alumni re-engagement	Designed exit and return paths treating departure as a chapter rather than a failure
Transparent-market logic	The argument that maximizing long-term personal value wins in transparent labour markets
Enduring Tensions
Personalization versus fairness	Individual fit against workforce consistency, managed by a constant rule set
Flexibility versus belonging	Autonomy over time and place against the shared context where trust and culture form
Evidence versus privacy	Better design requiring data whose collection reads as surveillance without governance
The book's reversal	Design work around people, test everything, and keep adapting as evidence arrives
Case Evidence
Atlassian Team Anywhere	Distributed-first work with funded intentional gatherings and published self-research
Unilever U-Work	An employment contract blending assignment flexibility with retainer and core benefits