Something interesting happened when the job market tightened up. Companies that had poured energy into their employer value propositions quietly went quiet on the topic. Not because the EVP work was done. Because some leaders concluded the urgency had passed. That conclusion is understandable. It is also wrong, and it points directly to the most common reason EVP projects fail in the first place.
An EVP is not a recruitment promotion.
Nor is it a response to a hot labor market.
It is the answer to a question that never goes away: Why would a talented person choose to work here, and keep choosing it? That question exists in every market condition.
It exists when candidates have options and when they don’t. It exists when organizations are growing headcount and when they are cutting it.
For example, the argument for a well-grounded EVP gets stronger as organizations shrink their human workforce. If you are deploying AI to handle more of the work, the people who remain carry more weight. The bar for the talent you need in those roles goes up, not down. So does the cost of getting it wrong: missed delivery targets, stalled product cycles, revenue at risk because the wrong people are in critical seats or the right ones have left. Competition for that talent sharpens as organizations across every sector rationalize headcount simultaneously.
Leaders who treat the EVP as a fad have misidentified what it is. That misidentification is the thread running through every failure mode described below.
Why EVP Projects Fail #1: The EVP Was Built to Please Leaders, Not Reflect Reality
This is still the most common way EVP projects go wrong, and it has been since before the term “EVP” was in wide use.
The pattern is familiar. A small team, sometimes just one person, gets handed the assignment of writing the EVP. They interview a handful of senior executives. They produce a draft that goes through rounds of review until everyone at the top is satisfied. It's published.
And then nothing happens. Recruiters do not use it naturally. Employees do not recognize themselves in it. The organization moves on.
The problem is not that the writing was bad. Rather, the process treated the EVP as a creative output instead of what it really is: a discovery exercise. The goal became executive approval rather than organizational truth. Those are different targets, and they produce different documents.
A well-built EVP requires hearing from people across the organization about why they joined, why they stay, and what they would miss if they left. It requires willingness to surface things that are complicated or unflattering, because those are often the same things that make the organization genuinely distinctive. It requires someone in the room willing to call out claims that do not hold up.
When that work is skipped, you get language that sounds like every other EVP in your industry. Which brings us to the newest version of this problem.
The AI-Generated EVP: Faster, Smoother, and Just as Disconnected
Generative AI has made it possible to produce a polished EVP in a fraction of the time it used to take. It has also made it easier than ever to produce one entirely disconnected from your organization’s reality.
We have reviewed AI-generated EVPs that are grammatically clean, structurally sound, and sound quite nice. AND: completely interchangeable with the output of any competitor who fed the same prompts into the same tools. Red flags include: “We are committed to your growth.” “Our people are our greatest asset.” “Together, we build something meaningful.” These statements are not wrong. They are simply not about anyone in particular.
The issue is not AI itself; AI can be a genuinely useful tool in EVP development, particularly for research synthesis and rapid prototyping.
The risk is using AI to skip the real listening. An EVP built on model-generated approximations of what employers tend to say is not an EVP. It is a placeholder.
Only 31% of employees say their organization offers a unique employee experience.
Why EVP Projects Fail #2: The EVP Was Built But Never Lived
Some organizations do the research. They conduct the interviews. They build something real. Then they publish it to the careers page and move on.
This is an activation failure and the data on it is striking.
Only 16% of employees can describe what makes up their organization’s EVP. Only 33% say their organization consistently delivers on its EVP promises.
These numbers are not about poorly designed EVPs. They describe EVPs that were designed and left on a shelf.
The EVP is not just a document. It is a set of promises that need to be built into the daily experience of working at your organization: how managers talk about the work, how leaders communicate during change, how new hires are onboarded, how performance conversations are framed. An EVP that only lives on the careers site is not functional - that's just marketing copy without real experience behind it.
Gartner’s 2024 research found that employees who hear about their EVP through multiple channels are 24% more likely to believe their organization actually delivers on it. That is not a marketing insight (well, that's useful to know from a marketing perspective too). But, more powerfully, that's a leadership and management insight. The EVP has to be communicated and embodied throughout the employee experience, not just at the point of recruitment.
Managers are a critical part of EVP activation. They are the day-to-day proof point. An EVP that senior leadership believes in but middle management cannot articulate (or live by) is still a broken EVP.
Why EVP Projects Fail #3: Leadership Lost Interest — or Never Had It
A third failure mode does not get discussed enough because it is uncomfortable to name: a lot of EVP projects die because the people with the authority to champion them quietly stop caring.
This happens for different reasons. Sometimes the original champion leaves. Sometimes a new CHRO wants to put their own stamp on the organization and the prior EVP gets deprioritized. Sometimes the labor market softens and a leader who was never fully bought-in decides the investment no longer makes sense.
And sometimes, unfortunately: a leader decides that since they have the power to set expectations rather than meet them, the whole exercise of understanding what employees value is beside the point.
All lead to the same outcome: An EVP was developed but never institutionalized. The research sits in a folder. The messaging is inconsistently applied. The activation plan was never funded. Three years later, someone new is commissioned to start over.
The only durable solution to this failure mode is making the EVP a business asset rather than an HR deliverable. When the EVP is framed in business consequences it is harder to abandon: recruiting cost, time-to-fill, early attrition, revenue at risk from critical-role vacancies, and the downstream cost to customers and delivery when the wrong people are in the wrong seats. When it is framed only as “our employer brand messaging,” it is easy to deprioritize.
Organizations with a strong EVP reduce annual employee turnover by up to 69% and cut cost-per-hire by up to 50%.
What Still Works: A Cross-Functional, Reality-Grounded Process
The antidote to all three failure modes is the same: treat EVP development as an organizational discovery process, not a writing assignment.
That means involving the right people from the start: a C-suite sponsor, a strong operational project leader, and a cross-section of employees who represent real range across roles, tenures, and locations. It means doing the listening before doing the writing. It means having someone in the room whose job is to push back on claims that do not hold up to scrutiny.
The mechanics of this process have evolved. AI-assisted research tools can now compress timelines significantly; they synthesize interview themes, benchmark competitor messaging, and generate early-stage drafts for stakeholder review. That last point matters. Faster prototyping means stakeholders can react to real language earlier in the process, which tends to reduce the extended wordsmithing cycles that slow projects down and drain momentum.
The tools are only as good as the inputs. AI can accelerate the process. It cannot replace the listening that makes the output real.
The team structure we have recommended for years still holds:
- A C-suite sponsor, often the CHRO or Chief Communications Officer, who can frame this as a priority initiative rather than an HR task, and who can open doors with senior leadership when needed.
- Selected executives for input at key moments and final approval: typically CEO, CHRO, CCO, and division heads.
- A strong operational project leader from Communications or Talent Acquisition who keeps the work moving and the stakeholders informed at each stage.
- A cross-section of employees representing different roles, tenures, and locations, both for listening sessions and for reality-checking drafts. These are the people who will call out a claim that does not hold up.
- An EVP working team spanning HR, Talent Acquisition, and Communications to analyze research, draw conclusions, and participate in structured writing and review sessions.
This approach takes more time and more organizational will than a writing exercise. We have never seen it fail.
A NOTE FOR EXECUTIVE LEADERS
If you are a CHRO, CEO, or CMO reading this, the EVP conversation belongs on your agenda. Not because the talent market is tight right now, but because the answer to “why work here” is a business question, not just an HR question.
Your EVP connects directly to recruiting cost, time-to-fill, and early attrition. It also connects to revenue. Unfilled critical roles delay product launches, extend sales cycles, and create service gaps that reach your customers. When the wrong person is in a high-stakes seat, the cost shows up in delivery, in quality, and eventually in retention of the clients and customers who depend on your team performing. A well-grounded EVP helps you put the right people in those seats and keep them there. When it is not grounded in reality, you pay more to hire people who leave faster and deliver less.
The most important thing you can do for an EVP project is stay engaged with it. Sponsor it visibly. Hold it to the same rigor you would apply to a product value proposition. Make sure activation, not just development, is funded and measured.
An EVP that lives only on the careers page is a missed opportunity. An EVP that becomes the way your organization talks about itself, to candidates, to employees, and to the market, is a durable business asset.
Frequently Asked Questions
Why do most EVP projects fail?
The most common reasons: the EVP was built by a small group without adequate employee input; it was never activated beyond the careers page; or leadership lost interest before the work was institutionalized. In each case, the root cause is treating the EVP as a communications document rather than an organizational truth-finding exercise.
What is the difference between an EVP and an employer brand?
The EVP is the substance: the actual reasons a talented person would choose your organization and stay. The employer brand is how that substance is expressed and communicated externally. A strong employer brand built on a weak or generic EVP will not perform. The EVP has to be real before the brand can be credible.
Does an EVP still matter when the job market favors employers?
Yes. The question an EVP answers does not become less important when candidates have fewer options. Organizations that deprioritize EVP during softer markets consistently find themselves rebuilding from scratch when conditions shift. More immediately: if your organization is reducing headcount and relying on a smaller team of high-performers, the stakes for attracting and keeping the right people go up, not down. So does the revenue and delivery risk of getting it wrong.
Can AI be used to build an EVP?
AI tools can be valuable in EVP development, particularly for research synthesis, competitive analysis, and generating early-stage language prototypes. What they cannot replace is the listening: the employee interviews, focus groups, and cross-functional review that make an EVP reflect organizational reality rather than industry convention. An EVP built primarily from AI-generated language will tend to sound like every other EVP in your space.
Who should be involved in an EVP project?
At minimum: a C-suite sponsor, a strong operational project leader, a representative cross-section of employees for listening and draft review, and a working team from HR, Talent Acquisition, and Communications. The specific structure can be scaled up or down depending on organization size, but the principle holds. The more the EVP is co-developed with the people it describes, the more likely it is to be accurate, adopted, and sustained.
Ready to Get It Right?
If your organization is realizing that it needs to tackle the employee experience with intention, or is revisiting its EVP, or wondering why the last one did not land, we would be glad to talk through what we are seeing and what tends to work.