Work With Older People

Getting the job done when your team isn't getting any younger

I've spent the better part of fifteen years managing mixed-age teams across a few different industries. The short version: working effectively with older people isn't about walking on eggshells or suddenly changing how you do everything. It's about recognizing where real friction points are and addressing them directly, instead of making assumptions based on age. This isn't a formal methodology or a certified program. It's more of an operational reality that hits companies when they don't prepare for it. You hire older workers. They bring institutional knowledge, stability, and generally strong work ethic. Then you realize your documentation, your communication tools, your onboarding process, and sometimes even your office culture are built around people who graduated from college five years ago and never needed to update their glasses. Here's what nobody tells you about Work With Older People: the biggest problem is rarely their ability to do the job. It's the gap between how you communicate expectations and how they understand them. A twenty-six-year-old manager writing a Slack message with three acronyms and a linked document expects efficient information transfer. The forty-eight-year-old senior engineer on the team sees fourteen minutes of their day vanish while they decode what actually needs to happen. That's not an age problem. That's a clarity problem that just happens to hit different demographics harder.

The practical stuff that actually moves the needle

I learned this the hard way on a project around 2019. We had three people over fifty on a new product development team using Jira, Confluence, and a Discord channel I'd set up because that's what the younger folks were comfortable with. Our first two-week sprint produced approximately nothing that shipped. Not because they didn't know their jobs. Because nobody had written down what "done" actually looked like for each ticket, they were all communicating in different channels, and half the documentation was three versions outdated. The fix wasn't training. It was standardization. I created a single source of truth document for the project. Every task had one definition of done, every decision went in one place, and we held a twenty-minute standing call at the same time every Monday and Thursday. No fancy software. No Agile ceremony bloat. Just predictability. Our velocity doubled within three weeks. The older team members weren't struggling with the work. They were struggling with the chaos. Once the chaos dropped, the work was fine. So the core approach to Work With Older People comes down to a few concrete habits:

Write things down explicitly. Assume nothing is obvious. What seems like basic context to someone who's been here two years might genuinely be missing from someone who joined six months ago or came from a different department. This applies to everyone regardless of age, but the impact is uneven. Give advance notice for changes. A surprise pivot in priorities costs a younger person maybe an hour of realignment. It can cost an older worker half a day because they've built stronger mental models of how everything connects. Neither is wrong. They're just different costs. Use multiple communication channels for important information. Email, chat, and a brief verbal confirmation catch different people in different ways. This isn't about accommodating age. It's about reducing the chance that critical information gets lost in a thread someone doesn't check regularly.

Where people mess this up

The most common mistake I see is treating older workers as liabilities that need protection. You'll hear managers say things like "let's not give her the presentation, she might get overwhelmed" or "he doesn't need the high-visibility project right now." This is career damage disguised as kindness. Older people on your team are rarely asking for lighter loads. They're usually asking for respect and the resources to do solid work. Another trap is assuming technology discomfort equals incompetence. I had a senior analyst who barely used Excel beyond SUM and VLOOKUP and couldn't figure out how to share a Google Doc. But that same person could tear apart a regression model and spot data issues faster than anyone else in the room. The tech gap was real but narrow. The judgment gap was enormous and valuable. Don't conflate them. There's also the reverse bias that some companies fall into, where older workers get lumped together and treated as if they all share the same needs. My experience across dozens of teams has shown that a fifty-three-year-old marketing director and a sixty-one-year-old software architect usually have almost nothing in common beyond their birth years. Don't group them. Don't assume. Just ask what works for each individual.

What doesn't work

Don't rely solely on informal mentoring pairings. These sound good in theory but tend to fail when the older person is already stretched thin and the younger person is too intimidated to push back on unclear guidance. If you pair people, make it structured with clear objectives and time boundaries. Don't invest heavily in expensive diversity training programs focused on age. Most of them are generic, poorly delivered, and create more defensiveness than understanding. Direct, specific conversation between individuals costs nothing and actually changes behavior. Don't wait until someone is already frustrated to address communication gaps. The pattern I keep seeing is that older workers absorb confusion for weeks or months before speaking up, by which point morale has already dipped and productivity has stalled. Check in early and often, and make it clear that asking for clarification is expected, not a sign of weakness.

The reality of Work With Older People is that it's just work. The kind of work that comes with any team that has diverse backgrounds, experiences, and working styles. The gains from getting it right are substantial. Institutional knowledge retention, lower turnover in key roles, stronger decision-making from people who've seen similar problems before. The costs of ignoring it are worse.