Let me tell you about a team I worked with not long ago. They were smart, dedicated, and drowning in a tangle of inboxes and chat apps.
Every project, every request, every status update ran through a combination of email and chat. There were long email chains with many people CC’d, an attachment from two weeks ago that nobody could find, and a thread that started as “Re: Project Update” but somehow needed a completely different conversation in a Slack channel. The same piece of work might have three separate email threads (different people, different subject lines) and a Slack discussion that spun off into yet another channel. If you needed the full story on a task, you had to search your email, scroll through Slack history, check the missed DMs, and then ask someone to fill in the gaps.
If you’ve lived this, you already know: there is no great way to keep up with everything when your work lives in email and chat across multiple places.
Now, could someone keep a personal to-do list in Outlook? Sure. But that’s a solo system. It’s not clean, and it’s certainly not collaborative. It doesn’t let everybody see the same work, comment on it, update it, or know what’s coming next. You can track your own tasks, but you can’t track the team’s — not really.
That’s the pain point this team was stuck in. And it’s a familiar one.
The problem with email and chat as your work management platform
Email is brilliant for communicating with people outside your organization. That’s what it was designed for. Chat tools like Slack and Teams are great for quick questions and informal updates. But using both of them together to run projects internally? That’s where things start to fray.
When you have a question about a task, you fire off an email. Someone else replies. A third person chimes in on chat with a related question. The conversation splits between two places. A few days later, you’re scrolling back through threads and channels trying to remember what was decided. Or worse, someone new joins the project and has to read through thirty messages and five channels just to get up to speed.
Compare that with a work management platform like Asana. There, you communicate directly about work, and that conversation stays right next to the task it relates to. Questions get asked and answered in context. No digging. No forwarding. No “Can you resend that?”
It’s a small shift that saves a disproportionate amount of time.
One source of truth ends the scavenger hunt
Here’s the real payoff: when you move everything related to work into a single platform, you stop hunting for information. Nick Sonnenberg calls it “the scavenger hunt” — that feeling of checking your email, then Slack, then a shared drive, then a sticky note on your monitor, just to figure out where a project stands.
Instead of things living in email threads, chat messages, and random documents, everything lives in Asana. The task. The conversation about the task. The file attached to the task. The due date. The owner. It’s all in one place.
The team I worked with started to experience something they hadn’t felt in months: certainty. They knew where to look for an answer. They knew where to post an update. They stopped wasting mental energy remembering where something was filed and started spending that energy on the work itself.
The adoption piece: it takes gentle persistence
Of course, getting there required a transition — and that’s the part that trips a lot of teams up.
You can’t just flip a switch and declare “no more email” or “chat only for non-work stuff.” People have habits. Deep ones.
What worked for this team was a steady, gentle approach. Every time someone sent an email or a chat message with a work-related question or update, someone would reply with something like, “Good question — let’s move this into the Asana task so we can track it there.” Not scolding. Just redirecting.
Up front, that feels like extra work. It’s an extra step. You have to stop, open Asana, and put the communication where it belongs.
But here’s the thing: on the tail end, it saves a boatload of time, energy, and effort. Once the habit sticks, you stop chasing information. You stop repeating yourself. And when management asks for a status report, the data is already there — clean, current, and organized.
And it’s important to remember: Asana has to be both set up well and actually adopted. Setup gives the structure — the right projects, workflows, and fields. But without adoption, the data won’t be accurate, and the chaos will creep back in. Both have to be true.
What changed for the team
Here’s what that shift looked like in practice:
-
For individual contributors: No more digging through email or chat to find the latest decision. All communication is in context with the work it relates to. You open a task, you see the whole conversation. It’s right there.
-
For people managers and top leaders: Everything is much easier to keep up to date. Instead of waiting for a status update email or chasing people in chat, you can look at the work itself and see where things stand — who owns what, what’s overdue, what’s on track.
It’s similar to the benefit we talked about in the last post on “Asana vs. Chaos.” But the migration story adds a layer: the journey from old habits to new ones is real. It takes intention, patience, and a little bit of gentle persistence.
What’s next for you?
If reading this feels familiar — if you’re tired of the email and chat scavenger hunt and ready to see what a single source of truth looks like for your team — let’s talk.
I help teams make this transition. Not with a big bang, but step by step, in a way that actually sticks.
Ready to see what this structure could look like for you? Schedule a Free Intro Call.
No pressure. Just a conversation about where you are, where you want to be, and what it would take to get there.
Read the full article on Substack →
From the SmartWork Bulletin