A colleague runs a tech team in Auckland. Last month his company installed a ping-pong table in the breakroom, added a subsidised gym membership, and announced "wellness Wednesdays" with a monthly yoga session. His team is still overworked, understaffed, and dealing with a toxic middle manager nobody will address. From a psychological perspective, this is a textbook case of treating symptoms while ignoring the condition. The ping-pong table is gathering dust.
What You Need to Know
- Wellbeing perks without structural change are performative and often counterproductive
- Real team wellbeing requires addressing workload, management quality, and growth opportunity
- Wellbeing is a delivery strategy: healthy teams deliver better software, sustain pace longer, and retain talent
- The investment is in management behaviour, not in amenities
The Perk Problem
The technology industry has conflated wellbeing with perks. Free lunch. Bean bags. Meditation apps. These are pleasant additions to a workplace. They're not wellbeing.
Wellbeing is whether the work is sustainable. Whether people are growing. Whether they feel respected and heard. Whether the demands on their time match the resources available. A yoga session doesn't address any of these things. It addresses the company's desire to appear like it cares about wellbeing without changing anything structural.
76%
of tech workers report experiencing burnout in 2021, up from 61% in 2019
Source: Blind, Workplace Burnout Survey, 2021
The burnout numbers are rising while the perk spending is at an all-time high. That's not a coincidence. The perks are a substitute for the harder work of fixing the conditions that cause burnout.
What Wellbeing Actually Requires
Manageable Workload
This is the foundation. If people are consistently working more than 40-45 hours per week, no amount of wellness programming will prevent the decline in performance, health, and engagement that follows.
Manageable workload isn't about being easy. It's about being realistic. If the team has capacity for 200 story points and the sprint plan contains 280, the plan is wrong, not the team. Adjusting the plan is a management responsibility. Asking the team to "stretch" every sprint isn't stretching. It's sustained overwork with a motivational label.
At RIVER, we track utilisation. Not to maximise it, but to cap it. When someone's utilisation trends above 85% for two consecutive sprints, we rebalance. Not as a punishment. As a correction. Because sustained high utilisation erodes the quality of everything that follows.
Growth Opportunity
People need to feel like they're getting better at something. Not just doing more of the same thing. When a developer spends twelve months building CRUD forms without exposure to new technologies, new domains, or new challenges, they stagnate. Stagnation leads to disengagement. Disengagement leads to turnover.
Growth doesn't require promotion. It requires variety. Different types of projects. Exposure to different parts of the stack. Opportunity to mentor or be mentored. The chance to present to a client, to lead a sprint, to investigate a new technology.
The question we ask every team member quarterly is: "Are you learning?" Not "are you happy." Happiness fluctuates. When someone says they've stopped learning, that's the intervention point.
Dr Gerson Tuazon
AI Strategy & Health Innovation
Honest Conversations
The wellbeing conversation that matters isn't "how are you?" It's "what's making your work harder than it needs to be?"
That question surfaces structural problems. A build process that wastes thirty minutes a day. A client relationship that generates anxiety. A team dynamic that creates friction. These are fixable problems, but they only get fixed if someone asks and someone listens.
Most teams don't have a mechanism for this conversation. The annual review is too infrequent and too formal. The daily standup is too brief and too focused on tasks. The gap between "everything is fine" and "I'm looking for another job" gets filled with silence.
We run monthly one-on-ones with a specific structure: what's going well, what's difficult, and what would make next month better. The third question is the one that produces actionable information. It gives the team member permission to identify a problem without it feeling like a complaint.
Management Quality
The most significant factor in team wellbeing is the direct manager. A good manager protects the team from unreasonable demands, creates space for growth, provides honest feedback, and addresses problems before they fester. A bad manager amplifies every other stressor.
Investing in management quality - training, coaching, feedback, and occasionally replacing managers who aren't effective - has more impact on wellbeing than any perk or programme. It's also harder and less photogenic than installing a ping-pong table, which is why many organisations avoid it.
The Business Case
Wellbeing isn't charity. It's strategy.
Retention. Replacing a developer costs 6-12 months of their salary in recruitment, onboarding, and lost productivity. Wellbeing investment that prevents one resignation per year pays for itself.
Sustained quality. Overworked teams produce more bugs, write less documentation, and cut more corners. The rework cost of a burned-out team exceeds the cost of managing workload proactively.
Client outcomes. Clients notice when the team is engaged and when they're going through the motions. The quality of client relationships correlates directly with team wellbeing. The research is clear, and so is our experience: burned-out teams do not deliver excellent client service.
Wellbeing is infrastructure, not a perk. Build it into how the team operates, not what the breakroom contains.