Why Most Engagement Programs Don't Survive Year Two (A 25-Year Perspective)

After 25 years in People Operations, Tam Koo explains the real reason engagement programs collapse — and the structural fix most HR leaders overlook.

WHITEPAPERS & GUIDES

Tam Koo

6/19/20264 min read

In 25 years running People Operations, I have watched a reliable pattern play out at least a dozen times across four companies and multiple leadership regimes: a new engagement program launches with real energy in year one. Scores improve. Leadership celebrates. The program gets a case study in the internal newsletter. And then, somewhere between month 14 and month 24, it quietly stops working — or stops being used at all.

I was wrong about what caused this for most of my career. I thought it was program design. I thought if we just built a better recognition platform, a smarter survey cadence, a more rigorous action-planning process, we'd break the pattern. We didn't. The design was never the primary failure point. The problem was structural — and it was almost always the same problem.

The Real Reason Engagement Programs Collapse

Engagement programs die when they are treated as HR programs rather than operational systems. That distinction sounds semantic. It is not.

When an engagement initiative lives in HR, it depends on HR for its energy and accountability. HR sends the survey. HR interprets the results. HR builds the action plan. HR presents findings to leadership. And when HR's priorities shift — and they always shift — the program loses its champion and begins to atrophy. The managers who were nominally involved never had real ownership, so they don't notice when things slow down. The senior leaders who endorsed the program at launch have moved on to the next strategic priority.

Contrast this with organizations where engagement metrics are embedded in operational review cycles — where a department head reviews engagement data the same way they review throughput numbers or budget variance. In those organizations, engagement scores are a management problem, not an HR problem. That shift changes everything about how quickly issues surface and how seriously they're addressed.

A Framework for Building Engagement That Outlasts Its Launch

After getting this wrong several times, here is the architecture that actually holds up:

1. Anchor engagement to a business outcome, not a culture outcome. "We want people to feel better at work" is a noble goal that disappears when the board asks about margin. "We want to reduce voluntary turnover among employees in their first three years, because replacing them costs us $18,000 per head" is a business case. Build your engagement strategy around the second framing, even if the first is what motivates you personally.

2. Transfer accountability to line managers within the first six months. HR can own the infrastructure — the survey tool, the reporting, the coaching resources. Managers must own the response. This is non-negotiable. An engagement score that lives on an HR dashboard but never appears in a manager's quarterly review will not be taken seriously. One that shows up in their performance conversation will.

3. Separate diagnostic measurement from pulse measurement. Annual engagement surveys are useful for trend analysis and benchmarking. They are poor tools for identifying what's happening right now on a specific team. Build a shorter, more frequent listening mechanism — team check-ins, stay conversations, informal observation — that doesn't depend on a survey cycle to surface problems. By the time a problem shows up in an annual survey, you've usually had it for six months.

4. Design for the 80th percentile manager, not the exceptional one. Most engagement programs are implicitly designed around the assumption that managers will go above and beyond to use them. The exceptional managers will do this regardless of what you build. The 80th percentile manager — well-intentioned, genuinely busy, not deeply trained in culture work — needs systems that make it easy to do the right thing. Recognition that requires three clicks instead of fifteen. Action-planning templates that take 30 minutes, not two hours. The complexity you add for the sake of comprehensiveness is often what kills adoption.

5. Communicate transparently about what you're doing with the data. The single fastest way to kill survey participation is to run a survey and do nothing visible in response. Employees don't need to see every recommendation implemented — they need to see that someone read the results and is responding honestly, even if that response is "here's why we can't address that this year." The organizations with the highest survey participation rates I've seen are not the ones with the best scores. They're the ones with the most transparent feedback loops.

What This Means Practically

If your engagement program is in year one and performing well, this is the moment to make structural changes — while leadership attention and goodwill are still available. Socialize the business case to your CFO, not just your CHRO. Get engagement language into manager performance criteria before year two. Build the operational review integration now, while the program has momentum.

If you're reading this because your program has already stalled — that's recoverable. But it usually requires an honest conversation about ownership that HR leaders are sometimes reluctant to have. The conversation sounds like this: "We built something HR can manage, and it worked for a while. To make it work long-term, we need managers and operations to own this alongside us." Most good operations leaders will respect that framing. The ones who don't were never going to sustain it anyway.

I've watched programs that looked like failures in month 18 become genuinely embedded practices by year three — but only when someone made the structural fix. The design almost never needed to change. The ownership model did.

Questions? Reach out anytime.

WorkPlayEngage is a product of Dieza Publishing. © 2026 WorkPlayEngage. All rights reserved.

Privacy & Security Note: WorkPlayEngage templates are native Google Sheets. We do not host your data, and we never have access to your employee names or internal metrics. Your engagement remains 100% private within your organization’s Google Drive.

Play:
Baby Pool
NFL Survivor Pool (Coming Soon)
Super Bowl Squares (Coming Soon)
Office Bingo (Coming Soon)

Help