There's this moment that keeps happening in workplaces right now where someone older will say "I just want my tools to work" and someone younger will say "I want my tools to do more" and they're both completely right, which is the problem.
The generational split on workplace technology isn't about whether software is good or bad. It's about whether good software is supposed to be invisible or indispensable. Those are fundamentally different philosophies about what a tool even is.
Older workers tend to think of technology like they think of electricity. It should be there, reliable, not require attention. You flip the switch and the light comes on. You don't want to think about electricity. You want electricity to stay out of your life so you can think about what you're actually trying to do. This is why you hear "I just want to send an email and have it work" so often. It's not a technophobe stance. It's a completeness stance. The thing should do its job so thoroughly that you forget it's there.
Younger workers, meanwhile, seem to view technology differently. Not as infrastructure that disappears, but as surface where work lives. A platform that consolidates information, surfaces context, connects things that need connecting. They're more likely to want Teams to do more, not less. They're thinking about integration points, data flows, what lives where. The tool itself is part of the thinking process.
This matters because it means the two groups are solving for different problems. One side is thinking "we're drowning in tools, consolidate and simplify." The other is thinking "tools should anticipate what we need next." One values friction reduction. The other values ambient awareness.
Take the way people experience Microsoft Teams. Older workers often see it as sprawl that happened to their email. Another place notifications come from. They remember when communication had clear channels: email meant something specific, a meeting invitation meant something specific. Teams collapsed those into the same space, which saved software switching but created this muddy middle where you're never quite sure what mode you're in. The instinct is to make Teams behave more like email did. Cordoned off. Boundaried.
Younger workers often see Teams as the beginning of something that should keep integrating. Plug in your sales data. Give me summaries of what happened in channels I'm not actively watching. Tell me when something in here connects to something I was working on yesterday. Make it smarter. The tool as a layer of ambient context around the actual work.
Neither of these is wrong. They're just different theories about what reduces friction versus what prevents mistakes. Invisible infrastructure keeps you focused. Smart infrastructure keeps you informed. You could argue both reduce friction in different ways.
The tension is that companies have to build for both groups at once. And because younger workers typically enter organizations fresh and adapt quickly to whatever system is there, while older workers bring accumulated preference for how things used to work, there's often this underlying frustration in both directions. Older workers think new features are bloat that make things harder to use. Younger workers think the resistance to new features is resistance to getting better information. Both are describing the same product through completely different lenses.
This isn't generational stubbornness. It's that your formative experience with tools shapes what you think good tools should do. And right now, the two formative experiences are so different that "good workplace technology" doesn't mean the same thing anymore. That's the actual split.