Forget everything you've read about async communication AI. I’m about to share a secret that will change how you work forever.
I remember the day it all clicked. We were a few years into building RemoteTeam, my company that was later acquired by Gusto. We were fully remote, and I was obsessed with making async communication work. I’d read all the books, tried all the tools, and implemented what I thought were all the best practices. But something was still broken. My team was burning out, information was getting lost, and our fancy new AI tools were spitting out garbage. We were working asynchronously, but we weren't working effectively.
One afternoon, I was on a call with a potential investor. He asked me a simple question about our customer acquisition cost for a specific channel. I froze. I knew the data was somewhere in our system, but I had no idea where. I mumbled something about getting back to him and spent the next two hours frantically digging through Slack messages, Notion docs, and email threads. I eventually found the number, but it was too late. The investor had moved on. We lost the deal. That failure cost us a $2 million seed round. It was a painful, expensive lesson, but it forced me to confront the real problem. The tools weren't the issue. My entire philosophy was wrong.
The Myth of the Magic Tool
So many founders I talk to are making the same mistake I did. They believe that if they just find the right project management software, the right AI chatbot, or the right internal wiki, all their async problems will magically disappear. They spend a fortune on software licenses, hoping to buy their way to productivity. But it never works.
Why? Because they're trying to build a skyscraper on a foundation of sand. They're layering complex AI and automation on top of a chaotic, unstructured, and fundamentally broken communication culture. An AI is only as good as the data it can access. If your company’s data is a mess of private conversations, undocumented decisions, and conflicting sources of truth, your AI will be useless. It’s the classic garbage-in, garbage-out problem. You can't automate a process that you don't understand and can't control.
Culture is Your AI's Operating System
The hard truth is that async communication isn't a software problem. It's a culture problem. You need to build an AI-first culture before you can successfully implement an AI-powered async strategy. Your culture is the operating system for your AI. Without the right OS, your expensive AI software is just a pile of useless code.
So what does an AI-first culture look like? After years of trial and error, I’ve boiled it down to three core principles.
1. Radical Transparency: The Glass Office
At RemoteTeam, we had a rule: all work, communication, and data were public by default. I called it the
Frequently Asked Questions
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.
Do all experts agree with this view?
No, and that's fine. The best ideas in business are often contrarian. I share my perspective based on my experience and data, but I encourage you to seek out opposing viewpoints and form your own conclusions.
What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.