The Tools of Modern Work

Ask most people what tools they use for work and you’ll get a list: a laptop, a phone, email, a chat app, a video conferencing app, a handful of SaaS products, a password manager they may or may not actually use, and a VPN they complain about. It’s a list, not a system. And that distinction is the whole story.

The tools of modern work aren’t a shopping list. They’re a stack — four layers that either reinforce each other or quietly fight each other all day long.

Layer One: The Device

The device is the front door. It’s the first thing a new hire touches and the thing every employee touches thousands of times a year. It’s also the layer most organizations treat as a purchasing decision rather than an experience decision.

A modern device should arrive already knowing who it belongs to. Zero-touch provisioning — Apple Business Manager with a modern MDM, or Windows Autopilot with Intune — means a laptop can ship straight from the vendor to an employee’s home, and the first login enrolls it, applies policy, installs the right applications, and hands over a working machine. No imaging bench. No shipping laptops to head office first. No IT technician spending three hours on setup.

The device layer also carries most of your security posture: disk encryption, patch compliance, and the signal that tells your identity provider whether this machine is trusted. Done well, security becomes a property of the device rather than a series of interruptions in the employee’s day.

Layer Two: Identity

If the device is the front door, identity is the key — and ideally, it’s exactly one key.

We’ve written about single sign-on before, and it remains the single highest-leverage investment in the modern work stack. One identity, protected by phishing-resistant multi-factor authentication, granting access to every application an employee needs. Groups drive entitlements. Entitlements drive provisioning. Provisioning happens the moment someone joins a team and reverses the moment they leave.

The organizations that get this right rarely think about it. The organizations that don’t spend their days on password resets, orphaned accounts, licence audits nobody can reconcile, and offboarding checklists that miss three applications.

Identity is also where mixed ecosystems get resolved. Plenty of companies run Microsoft 365 for mail and Google Workspace for collaboration, or the reverse — and that’s fine, as long as one directory is authoritative. We’ve published a practical guide to integrating Microsoft 365 and Google Workspace for exactly this situation.

Layer Three: Collaboration

Collaboration tools are where tool sprawl becomes visible. Three chat platforms. Two video conferencing products. Files in a cloud drive, a wiki, a project tool, and someone’s desktop. Every one of these was adopted for a good reason by a team solving a real problem. Collectively, they cost the organization more than anyone measures.

The cost isn’t licensing — it’s context switching and search. When a decision could be in any of five places, people either stop looking or stop writing things down. Both are expensive.

The fix isn’t austerity. It’s choosing a centre of gravity — usually Microsoft 365 or Google Workspace — and being deliberate about what’s allowed to live outside it. AI assistants like Copilot or Gemini make this decision sharper, not softer: an assistant is only as useful as the content it can reach, and content scattered across unconnected tools is content the assistant can’t help with.

Layer Four: The Workflow Layer

The fourth layer is the least glamorous and the most neglected: the small, repeated processes that surround the work. Requesting access. Approving an expense. Onboarding a contractor. Reporting a broken laptop. Getting a new licence.

These are the moments where employees form their real opinion of IT. Nobody notices a well-run identity platform. Everybody notices waiting four days for access to a system they needed on Monday.

Modern platforms handle most of this natively — self-service access requests, automated provisioning from HR events, a service desk that lives inside the chat tool people already have open. The technology is not the hard part. The hard part is deciding that these workflows deserve design attention at all.

The Fabric Test

Here’s a simple diagnostic. Walk through the first two weeks of a new employee and count the number of times a human has to intervene manually for something that should be automatic.

In a fragmented environment, that number is usually somewhere between fifteen and forty. In a well-designed one, it’s close to zero — and the interventions that remain are the human ones you actually want: introductions, context, mentorship.

That’s the difference between a collection of tools and a fabric. Same products, often the same spend. Completely different experience.

Where to Start

If your stack feels more like a list than a system, start with identity. It’s the layer everything else depends on, and it’s the layer where the compounding returns are largest. Device management comes next, because a trusted device is what makes modern identity policies practical. Collaboration consolidation and workflow automation follow naturally once the foundation holds.

None of this requires a transformation programme. It requires someone senior enough to see all four layers at once and make decisions that hold up as the organization grows — which is exactly the kind of work we do.

If you’re looking at your own stack and recognizing more of the list than the system, schedule time with us. We’ll walk your four layers with you.