21 Aug Happiness Theater: Why a “People-First Culture” Doesn’t Make Companies Better
Maybe your company is running one of these culture programs right now: workshops, new values, some feel-good initiatives. A scene you’ll probably recognize, maybe even one you’ve lived through yourself.
Does this sound familiar?
This is a pattern I see constantly in my work: A mid-sized company with 200 employees has been fighting rising turnover for two years. Leadership decides the company needs a people-first culture. Four company values come out of a full-day workshop. The company creates a Culture Manager role. There’s a fruit basket, two remote days a month, a summer party, and an employee survey planned for the fall.
Eighteen months later, the new values hang framed on the wall. Survey scores ticked up slightly, but the decision architecture hasn’t moved an inch. People closest to the customer still have no authority to decide anything. Middle management is still measured on control metrics, project accountability still sits at the top, the consequences still land at the bottom. The best people are gone after two years, and survey scores are trending negative again.
This isn’t an outlier. It’s the most common outcome of well-intentioned culture programs.
It has a name: Happiness Theater.
Most companies that think they have a culture problem actually have a structural one. That’s the difference.
Contents
What “People-First Culture” Gets Wrong About Real Culture Work
Happiness management theater means chasing a people-first culture while losing sight of the working conditions that actually make people want to do good work in the first place.
The difference sounds subtle. It isn’t.
Real culture work is structural work. What actually shapes an organization isn’t its mission statement. It’s what decisions actually run on: who gets to decide, on what criteria, and how a decision reaches the place it’s needed. These conditions shape how people behave long before any list of values does. Happiness management theater leaves those conditions untouched. It changes how the work feels, not how it actually works.
What Structural Work Actually Looks Like
The question is never whether a company does enough “for its people.”
The question is whether three things are true:
➡️ Who makes the call, and are they close enough to the problem to make it well?
➡️ What criteria does the decision run on, and do they still fit how the work actually looks today, or are they leftovers from a different era?
➡️ How does a decision reach the place it’s needed, and how many detours does it take along the way?
If those three questions go unanswered, no list of values fixes it. The instinct behind New Work was right. Its execution mostly wasn’t.
The actual causes of bad working conditions are rarely bad intentions. More often, they come down to:
❌ Over-management
❌ Watered-down accountability
❌ Centralized structures
❌ Control mechanisms that kick in exactly where judgment is needed
These are Taylorist leftovers, built for a time when work was predictable, repeatable, and controllable. They don’t hold up in complex, fast-moving environments. New Work correctly named the problem, but many organizations responded to a structural problem with a cultural fix. They turned humanizing the workplace into a program, instead of letting it emerge from real structural change.
That makes things worse. Announcing values without changing structure breeds cynicism. Employees spot the gap between what’s claimed and what’s real faster than leadership does. Company culture can’t simply be decided. The same goes for the satisfaction it’s supposed to produce.
Why “People-First” Companies Still Turn Inward and Lose Touch
Happiness management theater isn’t just the wrong answer. It changes the questions an organization asks itself.
One distinction helps here:
Internal reference: The organization’s attention turns inward. A pencil gets ordered through an IT ticket that needs three rounds of approval. A meeting gets scheduled to prepare for the next meeting. A metric gets optimized because it looks good on the dashboard, not because it says anything about the actual work. The standard for good work lives inside the organization.
External reference: The organization’s attention turns outward, toward the difference it makes beyond its own walls. An employee makes the call in a customer conversation because it’s needed there, not because a process dictates it. A product changes because users have a problem with it, not because an internal roadmap says so. The standard for good work lives outside the organization, with the people it serves.
Both directions sound harmless enough at first. The difference only shows up in how an organization actually measures success once things get tight.
Organizations that function well orient primarily outward, because external reference keeps them in touch with the reality they depend on. They ask: What do the people we serve actually need? What does our work actually achieve?
When internal reference takes over that function, something gets lost. Not suddenly, not dramatically. Gradually. The organization starts managing itself, instead of managing the work. Moods get managed, atmosphere gets curated, the next survey score becomes the priority, while the quality of the work fades into the background. What sounds good on the inside isn’t necessarily what’s needed on the outside.
Here’s what that looks like in practice: a leadership team spends two hours discussing the results of the latest employee survey. Five items on the agenda, all internal. The customer complaint that landed in the inbox three days ago is still waiting for a reply. Nobody put it on the agenda. That’s not indifference toward customers. It’s the pull internal reference creates once it takes hold.
Often, customers notice something’s off before leadership does.
Why Structural Work Alone Isn’t Always Enough
Structure is the stronger lever. Focus there, and you’ll change more than any culture program ever will. But there’s one case where structural work alone isn’t enough: when the person at the top is the reason the structure never changes.
A CEO who avoids conflict won’t hand over decision authority. For her, that would mean giving up control and risking friction. A founder who can’t tolerate losing control keeps decision-making centralized, even when he knows it no longer works. In these cases, the problem isn’t the organizational design. It’s a psychological pattern blocking the design from working.
This is exactly where happiness theater steps in, not as deliberate deception, but as the easier way out. A culture program asks nothing of the leader personally. Nobody has to give up control. Nobody has to face a conflict. The organization rewards that too, because things look calm on the surface. The psychological pattern and the structure reinforce each other: fear of conflict seeks out a structure that avoids conflict, and the structure confirms that avoidance works.
Organizational consultant, executive coach, and author of several books, Klaus Eidenschink calls it self-amputation when consulting only addresses structure and treats psychological patterns as a private matter. His point lands squarely here: a new decision architecture on its own won’t change a CEO who’s supposed to give up control structurally but can’t do it psychologically. It takes both: work on the design and work on the person carrying it.
What It Means to Put Value Creation at the Center, and What It Doesn’t
Value creation and profit aren’t the same thing, though in practice the two get conflated constantly.
Profit is one possible outcome of value creation. Value creation is the actual work: whatever makes a real difference for someone outside the organization. A product that solves a problem. A service that makes something possible for the first time. A decision in a customer conversation that builds trust, because the person making it actually has the authority to make it. That’s value creation, and it’s an organization’s real job, not its profit and not its employees’ satisfaction, even though both can follow from it.
Putting value creation at the center means asking different questions.
Not: “How do we boost employee satisfaction?”
Instead:
❓ What does the work itself need to succeed?
❓ Who decides what, close enough to the situation to decide well?
❓ Where does accountability start, and does that person actually have the means to act on it?
❓ Where does the organization over-manage to the point that the people doing the work can no longer respond to what they’re actually seeing?
These are structural questions, and they have structural answers. Why organizational development rarely works at scale comes down to the same root cause: interventions stay on the surface because the decision premises underneath are too uncomfortable to actually touch.
Focus on the structural conditions of the job instead: decision architecture, how accountability is distributed, the underlying management logic. That’s what creates the conditions for people to actually be effective.
Effective, in concrete terms, means:
✅ being able to respond to what they’re actually seeing
✅ deciding without routing through five layers of approval
✅ being accountable for something they can actually influence
That’s not a promise to employees. It’s the basic condition for work to succeed at all.
And effectiveness is exactly the feeling happiness theater tries to manufacture with fruit baskets and summer parties.
Nobody’s banning the fruit basket. It’s just not an answer to a structural question.
Conclusion: Happiness Theater Solves the Wrong Problem
The goal isn’t to produce unhappy employees, and this isn’t about pitting value creation against human needs. It’s the opposite.
People thriving at work is an outcome, not a target. Aim for it directly and you’ll miss it. Build the structural conditions that make good work possible, and you get it as a consequence.
That’s not a harder stance toward people. It’s a more honest one. Build structures where people can actually be effective, and you don’t need to engineer satisfaction on top, because it comes from the work itself. That’s the difference between an organization that looks after its people and one that takes them seriously. And it’s the difference between happiness theater and leadership.
Get in Touch
If you want to find out where happiness theater is crowding out the structural questions in your own organization, before the next culture program launches, that’s worth a closer look at your actual decision-making paths first. Organizational culture development doesn’t start with a culture program. It starts with the right diagnosis.
In an initial conversation, I look together with you at where the real leverage points are in your organization. No charge, no pitch, no obligation.