Employee experience was one of the big transformation reviews of the 2010s. Emerging in the wake of customer experience, it promised a more human, consistent, and engaging approach to work. Businesses saw it as a way to combine performance and well-being, engagement and efficiency. On paper, everything was perfect: aligning employee expectations with the needs of the organization to streamline execution, reduce turnover, and make management a vehicle for engagement.

But over time, the concept became diluted in discourse and mood indicators. Feelings were measured without questioning the causes, engagement was discussed without considering the quality of work design, and investments were made in survey tools, recognition apps, and inspiring offices, while the operational mechanics of everyday life were allowed to deteriorate.

In other words, the work experience was confused with how people felt at work.

Employee experience has never been an added bonus. It is an architecture that connects processes, systems, and behaviors around the reality of work. This report offers a structured reading of the concept: understanding how it has been weakened, identifying the root causes of this drift through everyday irritants, and then exploring the conditions for a reconciliation between human capital, management, and performance.

NB: Everything that follows reflects my own experience validated in the field, that of an employee experience director who, in the end, even combined this role with operations management. I’ll leave you to draw your own bottom line about its operational validity.

The concept’s success was due to its apparent obviousness. Who would be against the idea of improving the employee experience? However, from the outset, there was a lack of clarity: was it about comfort, meaning, management, or productivity? Businesses adopted the term, but rarely its logic. The employee experience was taken up by HR departments, when it should have been embraced by management and operations as a whole.

In Employee experience is useless (if it is not linked to the business), I explained that the most common mistake is to disconnect the approach from any operational purpose. An employee experience that is not rooted in real work becomes an image product: it produces discourse, not results, and it flatters the culture without improving execution.

This is the source of enormous confusion: the employee experience has been designed as an end in itself, when it should be a means to an end.

This ambivalence is reflected in the findings of the 2023 Employee Experience Barometer: businesses say they are attentive to the experience of their employees, but few of them link this attention to the quality of work or organizational fluidity.This disconnect explains the stagnation of the subject: we talk about “well-being” when we should be talking about “conditions for efficiency”.

Finally, in From employee experience to operational excellence: HR not so well equipped!, I discussed the difficulty for HR departments to drive this transformation. Not because of a lack of will, but because of a lack of tools and legitimacy in the field. The real driver of employee experience is not HR policy, but the very design of work.

This semantic shift has emptied the concept of its substance. By focusing on treating the symptoms (disengagement, frustration, misalignment), businesses have forgotten the diagnosis: the very design of work is often flawed. The employee experience is therefore not a lever for internal communication, but a manifestation of organizational maturity, a maturity that is measured less by overt benevolence than by the ability to eliminate the irritants that undermine everyday life.

This semantic shift has emptied the concept of its substance. By focusing on treating the symptoms (disengagement, frustration, misalignment), businesses have forgotten the diagnosis: the very design of work is often flawed. The employee experience is therefore not a lever for internal communication, but a manifestation of organizational maturity, a maturity that is measured less by overt benevolence than by the ability to eliminate the irritants that undermine daily life.

In 2020, I set out to map what degrades the employee experience in organizations. These fourteen “irritants” are structural symptoms: they describe the friction that arises when systems, tools, and managerial practices cease to be aligned.

Taken together, they outline an implicit theory of disorganization.

The first observation is complexity.

Organizational complication (irritant #1) opens the series with an endemic problem: businesses are constantly adding procedures, validations, and exceptions. Work is diluted in the management of work.

Added to this are processes designed for the wrong people (irritant #2), which reflect the logic of control rather than that of use. The result: employees spend more time circumventing than executing.

Next comes excessive standardization: A mass experience (irritant #3) highlights that “one size fits all” approaches kill the uniqueness of work. When everything is standardized, nothing is relevant anymore.

Organizational fragmentation amplifies the problem: The compartmentalized enterprise (irritant #4) and A desynchronized organization (irritant #13) show how verticality slows down coordination. Employees then live in an ecosystem where everything is connected, except the business.

Information is another area of friction.

Retention and difficulty accessing information (irritant #5) describes the cognitive fatigue caused by information overload and scattered tools. Accessing data becomes a challenge, and knowledge is lost in silos.

Similarly, A complicated IT experience (irritant #7) shows that digital tools, which are supposed to streamline work, often complicate it by adding layers of technology.

The third block concerns managerial consistency.

Management (irritant #9) remains a blind spot: too many managers rely on reporting instead of orchestrating real working conditions.

Employees lost in HR processes (irritant #8) illustrates the disconnect between HR systems and operational experience. Mobility and training policies clash with rigid practices that are inconsistent with the pace of business.

And when the organization becomes too informal (irritant #14), responsibility becomes diluted: everything relies on goodwill, nothing is structured.

Finally, the material and customer context directly influences the internal experience.

The workplace (irritant #11) shapes behavior: poorly designed or symbolically inconsistent spaces create imperceptible but very real tensions.

And in Customers and projects (irritant #12), we see how poorly regulated customer pressure deteriorates the quality of internal work.

Even so-called “customer-centric” businesses forget that the employee experience determines the quality of service.

These irritants form the empirical basis of a methodology: they indicate where action needs to be taken even before a program is launched. This is the whole point of What methodology to build an employee experience program.

It is not enough to add a cross-functional project: you have to start with the actual work, prioritize friction points, measure the teams’ ability to solve problems, and embed the approach in operations. The employee experience is not “built” but shaped by the constraints of the field.

The most advanced businesses in this area have understood that employee experience is not a policy, but a system. It is no longer a question of measuring satisfaction, but of designing work in a way that is consistent with market expectations, available tools, and human capabilities.

Employee experience then becomes a question of business design.

It connects three dimensions:

• identity, which forms the basis of the company’s purpose and values
• experience, what employees experience on a daily basis
• operations, how the organization produces and delivers.

This triptych corresponds to the EDGY model that I presented in EDGY: a common language to align identity, experience, and operations. It is in this alignment that consistency lies, not in engagement campaigns.

Just as Human capital? Less well endowed than technological capital shows, most organizations invest in technology without rethinking their structures. However, poorly integrated technology reinforces irritants instead of resolving them.

The employee experience thus becomes a field of convergence between HR, operations, and IT: it is the only space where tools, practices, and interactions can be considered simultaneously. As I wrote in HR and Operations: the only viable duo for driving employee experience, regardless of who is in charge of the subject, success will require cross-functional collaboration.

Managers play a key role here. As I wrote in To manage is to design, their job is no longer to supervise but to design a working environment that allows teams to perform smoothly. Managers become designers of the local system in which their employees operate. They are the link between strategic intent and operational reality.

This approach shifts the employee experience from a declarative logic to a constructive one.

It is no longer a question of satisfaction, but of capacity for action.

A good employee experience is a system that allows everyone to do their job with fluidity, clarity, and consistency.

This is what I explored in Do we need a chief of work?

The idea of a “Chief of Work” is not to create yet another function, but to highlight what connects all the others, namely work itself. Between HR, operations, and management, this role symbolizes the need to govern work, not just supervise it.

In a world where organizations are becoming more complex and tools are multiplying, someone must take responsibility for consistency: that of work as a system.

Employee experience has been a victim of its own success: too much talk, not enough design, and even less execution.

Its value lies not in what it promises, but in what it makes possible.

When it is based on the reality of work, it becomes a lever for operational excellence, but when it strays from this reality, it is reduced to a communication program.

The transformation of businesses will require a redefinition of the relationship between work, technology, and management, and in this relationship, employee experience is not an added bonus of goodwill, but a principle of operation. It does not aim to make work enjoyable, but to make it possible, in conditions where performance and purpose can coexist.

“A good employee experience does not make you love work.

It makes you love working well.”