Your Inbox Is Drowning Because Email Was Never Built for This

The tools you're already paying for, finally put to work.

I still remember getting letters in the mail.

Not packages, not bills — actual letters. Someone sat down, wrote out their thoughts on paper, put it in an envelope, addressed it, stamped it, and dropped it in a mailbox. A few days later it showed up in yours. You read it, thought about your response, and wrote one back. The whole exchange might take two weeks.

That's what email is. It's a digital version of that. Faster, obviously — seconds instead of days — but the same fundamental idea. A composed, considered communication from one person to another, delivered asynchronously, waiting for a reply.

Email is a letter management system. That's what it was built to be. That's what it's genuinely great at.

The problem is that somewhere along the way, we started using it for everything else.

The Tool Mismatch Nobody Talks About

Quick questions. Project updates. Approval requests. Internal announcements. Document handoffs. Team check-ins.

None of those are letters. Not a single one. Before email existed, none of them would have been. You'd handle a quick question with a phone call or a sticky note on someone's monitor. You'd track a project in a shared folder or a whiteboard. You'd announce something at a team meeting or post it on the break room bulletin board.

When email came along, we didn't replace those communication channels. We just routed everything through the letter system because it was convenient and we already had it open.

That's where the breakdown comes from. It's not that you have too much email. It's that your inbox is full of things that were never letters in the first place. You're asking a letter management system to handle sticky notes, phone calls, hallway conversations, and filing cabinets all at the same time. Of course it feels like you're drowning.

Here's the test I give clients when they're trying to sort this out:

If email didn't exist, how would you handle this communication?

If the answer is "I'd write a letter" — that's an email. Send it.

If the answer is anything else — a text, a phone call, a sticky note, a hallway conversation, a bulletin board post — that belongs somewhere else.

Email Owns External. Teams Owns Internal.

Before we go any further, there's one distinction worth making clearly.

Email owns your external communications. Your clients, your vendors, your accountant, your attorney — anyone outside your organization should hear from you in email. That's the appropriate channel, it creates the right kind of paper trail, and it meets people where they already are.

Teams owns your internal communications. Everything happening between the people inside your organization is a candidate for Teams — and most of it is a better fit there than in email.

Once that line is clear, the rest of this gets a lot simpler.

What the Switch Actually Looks Like

I worked with a psychotherapy practice toward the end of the COVID-19 pandemic. Forty people total — ten internal staff, about twenty providers, and ten researchers. Two distinct sides of the practice that needed to stay coordinated but operated almost independently. Patient care on one side, active research programs on the other.

They were running everything through email. All of it. Internal questions, scheduling coordination, announcements, research updates, clinical communications — every conversation landing in the same inbox as patient-related correspondence and outside vendor messages. All forty people drowning in the same way.

The timing was actually useful. The pandemic had forced a lot of organizations into Teams for video conferencing whether they were ready for it or not. This practice had the tool. They just hadn't thought about using it for anything other than calls.

We sat down with their leadership and walked through the same question I ask every client: what in your inbox was never supposed to be a letter? The answer was most of it. Internal communications — anything moving between staff, providers, and researchers — moved to Teams. We built out channels structured around how their practice actually operated. Clinical operations. Research coordination. Administrative. Direct messages for quick back-and-forth. Email stayed, but it went back to its original job: correspondence with patients, with outside partners, with anyone who wasn't already on their team.

The hardest part wasn't the technology. It was the commitment.

The Part Nobody Warns You About: It Only Works If Everyone Does It

Here's the thing about a system like this. It depends entirely on a shared agreement.

If half the team moves their internal communications to Teams and the other half keeps sending internal emails, you haven't solved anything. You've created two inboxes. Now people have to check both, and the whole point — getting the noise out — is gone.

More than that: if I'm expecting internal communications in Teams and they aren't arriving there, my assumption isn't that they're in email. My assumption is that they didn't happen. I operate on incomplete information, open my inbox, and find them buried under everything else. That's not just inefficient. It erodes trust in the system fast.

This is a culture decision as much as a technology decision. The team has to make a social contract with each other: this is how we communicate now. Not some of us. All of us.

And that social contract starts with whoever is at the top.

If the CEO keeps sending internal emails for everything — scheduling questions, quick updates, announcements — the team reads that as a signal. Either the new system is optional, or leadership doesn't actually believe in it enough to use it. Either way, the permission to fall back to old habits has been granted silently, without a single word being said about it.

The technology is only as robust as the people using it. Leadership can't just announce the change. They have to be the most visible example of it — using Teams for the same things they're asking their team to use it for, consistently, from day one. When the CEO's quick questions come through Teams, everyone knows this is real. When they don't, everyone knows it isn't.

With this practice, leadership committed to it completely. They set the expectation clearly with the whole team, held to it, and didn't let the old habits slide back in. That's why it worked.

Within two months, their inbox volume had dropped dramatically. More importantly, people knew where to look. Clinical staff could follow research updates without those updates competing for attention against patient correspondence. Researchers didn't have to sort through clinical scheduling noise to find what was relevant to them. Everyone was better informed about what was happening in the practice because the information had a home that made sense.

That was five years ago. They're still running the same system today.

And once the communication structure was working, we kept going — moving internal notifications, assignments, and workflows into Teams too. But that came later. The first move was just getting the communication right.

Where Teams Makes the Most Difference

Quick questions belong in Teams direct messages. "Did we ever hear back on that referral?" is not a letter. In Teams it's a ten-second exchange that never touches either person's inbox. The rule of thumb: if you'd walk to someone's desk to ask it, send a Teams chat instead.

Approvals get their own structure. Email is linear and passive — you send, you wait, you follow up, you forward, you hope. Teams has a built-in Approvals feature that sends the request, attaches the document, tracks the status, and notifies everyone when it's done. One place. No thread management. No "did you see my email?"

Document sharing is where the version control problem lives. Attaching a file to an email creates a copy. Every person who receives it has their own version. When three people edit their copy and send it back, you have four versions and no clear answer for which is current. Sharing a SharePoint link through Teams means everyone is working on the same file. Version history is automatic. This one habit change eliminates an entire category of confusion for most small teams.

Project and program threads get channels. A project update in email becomes a reply-all chain nobody wants to be on. A Teams channel organized around a program or workstream gives everyone a shared, searchable, persistent conversation. New team members can scroll back and understand the full history. Nothing gets lost in someone's archive.

Frequently Asked Questions

We already use email for everything and the team is used to it. Is the disruption worth it?

The disruption is smaller than most people expect and front-loaded. The first two weeks have some friction as habits shift. After that, the noise reduction is permanent. The clients who've made this move consistently say the same thing in retrospect: they wish they'd done it sooner.

Do we need to stop using email internally entirely?

No — and going cold turkey usually fails. Start with one category. Move quick internal questions to Teams direct messages for two weeks. Once that's a habit, move the rest gradually. The goal isn't to eliminate internal email overnight. It's to get the noise out of the inbox in a way that actually sticks.

What if some of our team resists making the switch?

Start with yourself. The most effective thing leadership can do isn't a policy memo or a training session — it's using the system the same way they're asking everyone else to use it, visibly and consistently from the beginning. If your team sees internal questions coming through Teams from the top of the organization, the social signal is clear: this is how we communicate now. If they see the CEO still defaulting to email for everything internal, the social signal is equally clear — and it works against you.

One-on-one time helping someone get comfortable with the tool matters too. But no amount of training overcomes a leader who treats the new system as optional for themselves.

Email is not the problem. It's a great tool that we've been asking to do jobs it was never designed for.

When you start treating it like what it actually is — a digital letter system, built for considered communication with the outside world — and give your internal communications a better home, everything gets quieter. The inbox gets manageable. Your team gets faster.

One tool for letters. Another for everything else.

That's it.

If you're not sure which Microsoft 365 plan gives you full Teams functionality for your team size, the plan comparison lays it out without the marketing language.

J. Scott Clark is the President and CEO of The 365 Collective, Inc., a Microsoft 365 consulting and training firm serving small and mid-sized businesses across healthcare, finance, construction, engineering, publishing, and retail.