Engaged Employees - Five Things That Actually Move the Needle

Here are five things that have worked. I'm not sure they always work, and I'm pretty sure sometimes they backfire. Take what fits.

Burn the 9-to-5

There was this agency in Calgary. Nine people, creative for outdoor brands. The founder, Marcus, wouldn't let anyone work from home. "I need to see the work happening," he'd say, which meant he needed bodies in chairs to feel like he was getting his money's worth. 

We tried an experiment. Two days remote, flexible starts, core hours 11 to 3 for collaboration. The rest? Their problem. Marcus called me twice in the first three weeks to complain people weren't responding to Slack fast enough. They were responding. He just couldn't walk over and loom anymore, and that felt like absence.

Month two, something shifted. Keisha, a copywriter who'd been quietly mediocre for a year, started producing work that made the room go quiet in reviews. She's not a morning person. At all. Her brain doesn't turn on until noon. Under the old system she spent her best hours pretending to look busy. Under the new one she slept until ten, worked until seven, and delivered a campaign that won an industry award six months later.

Marcus never admitted the policy was wrong. He just stopped talking about it. Stopped defending in-person work. Started leaving the office at two on Fridays. I ran into him at a coffee shop six months later, laptop open, looking almost embarrassed. "Don't tell my team," he said. I told him they already knew.

Flexibility isn't a perk. It's an admission that people are different, that their lives don't stop when they walk through your door, that your system was designed for a kind of worker who maybe never existed outside of industrial-era imagination. Kids get sick. Parents age. Depression doesn't check your calendar. Give people room to sort their actual lives and they don't exploit it. Mostly. A few will, and that's a management problem, not a policy problem. Fire the people you can't trust. Structure the rest of your organization around trusting everyone else.

Is that naive? Maybe. I've seen it fail: a consulting firm where two people genuinely did nothing for six weeks. But I've seen the alternative fail way more often. The alternative is Marcus, hovering over Keisha at 8:45 a.m. while her best ideas are still two hours away.

Tell them the truth, especially when it sucks

Denise ran a small education nonprofit, maybe twenty staff, running on fumes financially. She wouldn't tell anyone. She thought transparency would panic people, so she said nothing for eight months. In the silence, her staff constructed a nightmare; the org was folding, mass layoffs were coming, their entire mission was a lie. The stories they invented were so much worse than the actual situation, which was "we're tight for about a year and need to diversify funding." survivable. Manageable. But by the time Denise finally said something, the trust was splintered. People she'd worked with for years looked at her like a stranger.

Rebuilding that took fourteen months. Not speeches. Consistency. Weekly open forums where she answered whatever people asked, including questions that made her defensive. She had to learn to sit with "I don't know yet" as a complete sentence. It was awkward as can be for everyone at first. Then gradually it wasn't.

The thing about silence is it doesn't stay empty. It fills with whatever people are most afraid of. Bad news you can respond to. Speculation you can't. This seems obvious when I write it down, but I keep meeting leaders who treat information like it's theirs to ration. It isn't. Your team's capacity to help solve problems is directly tied to how much they actually understand about what's happening.

One caveat — and this matters — transparency without context is just dumping anxiety on people. "We're in trouble" without "and here's what we're doing" is worse than saying nothing. I watched a startup CEO do this whole radical honesty thing where he'd Slack the whole company his raw fears at 2 a.m. That's not transparency. That's emotional outsourcing. The bar is higher than just "say everything." You have to say it coherently, when people can absorb it, with some indication of what comes next. Even if what comes next is "we figure it out together."

Actually see people

Six years. That's how long one woman, call her M, stayed at a company without her manager once describing her specific contribution in any detail. Six years of good work, the kind that keeps operations running but doesn't make decks or win awards. She covered for people who were out. She fixed processes that were breaking. She remembered client preferences that nobody else bothered to learn.

One generic "thanks for all you do" at a holiday party. That was it. She left for a competitor for the same money. Actually slightly less, if you count the worse commute.

I think about this differently now than I used to. Early in my career I thought recognition meant bonuses and promotions and big speeches. Those are fine. But they're events. What M needed wasn't an event. It was evidence that anyone was paying attention to the day-to-day texture of her work. A specific note about a thing she did well. A mention in a meeting that named the actual thing, not just "great job everyone." Someone noticing that she stayed late to fix a client problem that wasn't technically hers.

This is hard for a lot of managers because it requires paying attention to work you didn't personally do, at a level of granularity that takes actual cognitive load. It's easier to throw an appreciation lunch. But the lunch doesn't stick. What sticks is being seen.

And here's something I didn't expect: when a manager starts doing this specifically, the team starts doing it with each other. Not because anyone asked them to. Just because recognition becomes part of how the group talks. It normalizes. I've watched teams transform in six months from competitive and guarded to genuinely celebratory of each other, and the only variable that changed was the manager started naming specific contributions out loud. That's it. One behavioural change.

Let them grow or let them go

There's a tech startup I won't name, the CEO is still a friend and he'd know this story immediately, that prided itself on having no titles, no hierarchy, everyone's equal. Sounds beautiful. Was a disaster. Nobody could figure out how to advance because there was nothing to advance to. No milestones, no skill ladders, no way to say "I've grown from X to Y." People stayed two years, learned everything the flat structure could teach them, and left for companies that would actually reflect their growth back to them.

The CEO was baffled. "They said they loved the culture," he told me, after his third senior departure in four months. "They did," I said. "They just loved their own future more."

Growth doesn't have to mean promotions. Sometimes there's nowhere to promote someone to, and that's honest. But growth has to mean something. A mentorship match with someone three years ahead. Tuition for a course that scares them a little. A project that's just beyond their current capability, with someone backing them who won't let them fall. The feeling, at the end of a hard week, that the person leaving on Friday is not identical to the person who arrived on Monday.

My worst career development failure: I had this brilliant junior researcher, Ana, who I kept giving "stretch opportunities" to without ever checking whether she wanted to stretch in that direction. I assumed growth meant upward and outward. She wanted to go deeper into a speciality I kept pulling her away from because I "needed her versatility." She left. She was right to. I still think about that. I got too enamoured with my own narrative of "I'm developing my people" to actually ask what development looked like for her.

So yeah. Help people grow. But also: ask them where they want to grow. The answer might not match your org chart.

This one still makes me uncomfortable

Okay. Workplace wellness. Five years ago I would have rolled my eyes at this section. Corporate yoga. Mindfulness apps with subscriptions the company buys and nobody uses. Fruit in the break room like that's going to fix a 60-hour work week. I thought the whole category was performative nonsense designed to make overwork seem caring.

Some of it is. A lot of it is.

But I've watched too many genuinely talented people hit walls I didn't see coming. Not dramatic collapses,just a gradual diminishing. The spark going out. The quality declining in ways that didn't match their capability. And when I got close enough to understand what was happening, it was almost always the same thing: they'd been running on empty for so long that empty started feeling normal. Nobody around them had given them permission to stop. Not even for a day.

The pandemic forced this conversation into the open, for better and worse. Mental health days went from joke to policy in about eighteen months. But policy isn't culture. I've been in organizations with generous PTO where nobody takes it because the unwritten rule; enforced by glances, by offhand comments about "dedication," by the example of leadership that never stops, is that real players don't rest. That's not wellness. That's wellness theatrics, and honestly it's worse than no wellness program at all because now you're lying about caring.

What actually seems to work, when it works? Leaders taking their own days off. Leaving visibly at five. Saying "I'm taking a mental health day tomorrow" in a meeting without hedging or joking. That kind of modelling does something no policy can. It gives people something they didn't know they needed: social proof that rest is allowed.

I don't have this figured out. I still work too much. I still struggle to tell whether I'm modelling healthy boundaries or just slacking off when I take a Friday. The line feels blurry to me in ways I'm not proud of. But I'm trying to get better at it, because I've seen the cost of pretending everything is fine when it isn't, and that cost is measured in people you lose, not to competitors, but to their own exhaustion.

So those are five things. They're not a framework. They're not exhaustive. They're just things I've watched matter, with real humans who had complicated lives and mixed motivations.

If I had to summarize, which I kind of hate doing, summaries always flatten too much, I'd say engagement comes down to whether your people feel like you see them as whole humans or as outputs. Not in your mission statement. In your week-to-week behaviour. In what you notice, what you reward, what you ignore, what you're willing to be honest about, whether you let them have lives outside your walls.

If something here landed wrong, ignore it. If something felt useful, try it this week. Not all five things, might be too much. Pick one. The one that made you slightly uncomfortable, probably. Do one thing about it. See what happens.

And if you're reading this thinking "okay but my situation is messier than any of these anecdotes", good. That means you're paying attention to reality. Most situations are messier. This isn't about getting it perfect. It's about caring, and doing something with that caring instead of just feeling it. Start somewhere. Start now, if you can. The week goes fast, and your people are already halfway through it.