Every year around this time I still get asked the same question by HR teams. Can you come in and run a fitness session for the office? I say yes, because a good session is worth doing. But I have started asking a question back. What happens the week after?
For a long time, that question did not really need an answer. A wellness program could call itself successful by pointing at attendance. How many people came to the seminar, how many mats were laid out for the fitness day, how many people picked up a fruit basket on their way out. The photo told the story, and the photo looked good.
That is changing. The conversations I am having with HR and leadership teams now are less about the event itself and more about what it is actually meant to produce. Better sleep. Fewer sick days. People managing stress instead of just absorbing it until they burn out. A single afternoon cannot answer any of those questions, no matter how well it is run.
A wellness program that only shows up once looks like an event. A wellness program that runs like a strategy looks like infrastructure. The difference is not the budget. It is whether there is a plan behind it, checked in on, adjusted, and connected to something the business actually cares about.
What that looks like in practice is less dramatic than a big kickoff day. It is a cadence, not a moment. Regular sessions instead of a single event. Movement and recovery built into how the week is structured, not bolted onto a calendar as a one-off. Actual tracking of what changed, even if that tracking is simple, so a program can be defended with something more than a good feeling.
I understand why the one-off event still happens. It is easier to plan, easier to budget for, and it photographs well for the internal newsletter. But if you are the person in HR who has to justify a wellness budget this year, "we did a yoga day" is a much harder sentence to defend than "we ran a program and here is what moved."
This is the shift I try to have with every corporate client now, before we even talk about what a session looks like. Not what event do you want to run, but what outcome are you actually trying to produce, and how do we build something that keeps producing it after the first Tuesday.
