A founder asked me last week about 12 counterintuitive lessons i learned managing a remote. My answer surprised them, and it might surprise you too.
Managing an AI team is hard. Managing one remotely is even harder. After 12 years of trial and error, here are my most surprising and effective lessons for leading a distributed team of AI experts.
The Counterintuitive Truth
Here's what surprised me most about 12 counterintuitive lessons i learned managing a remote: the best practitioners do less, not more.
When I was building MovieLaLa, we tried to do everything at once. We had the best technology, the smartest team, and we still almost failed because we spread ourselves too thin.
The lesson I took from that experience, and from watching hundreds of other companies, is that you need to move fast and break things. It sounds simple. It's incredibly hard to execute.
The Framework That Actually Works
I'm going to share the exact framework I use when evaluating 12 counterintuitive lessons i learned managing a remote. It's not complicated, but it requires discipline.
Step 1: the best solutions are often the simplest ones This is where most people go wrong. They skip this step entirely and jump straight to execution. Don't do that.
Step 2: most founders overthink this and underspend on execution Once you have the foundation right, this becomes much easier. I've watched founders struggle with this for months when the answer was staring them in the face.
Step 3: Iterate relentlessly Nothing works perfectly the first time. The companies in my portfolio that nail 12 counterintuitive lessons i learned managing a remote are the ones that treat it as an ongoing process, not a one-time project.
Real Talk: What Actually Matters
I'm going to cut through the noise and tell you what actually matters when it comes to 12 counterintuitive lessons i learned managing a remote.
First, execution speed beats perfection. Every time. I've never seen a company fail because they moved too fast on 12 counterintuitive lessons i learned managing a remote. I've seen plenty fail because they moved too slow.
Second, measure everything. If you can't measure it, you can't improve it. Set up tracking from day one, even if it's basic.
Third, talk to your users. This sounds obvious but you'd be amazed how many founders build their 12 counterintuitive lessons i learned managing a remote strategy in a vacuum. Get out of the building. Talk to real people.
This connects to broader themes around AI transformation leadership, AI change management, AI leadership skills that I've been thinking about a lot lately.
Final Thoughts
After two exits, 200+ investments, and more mistakes than I can count, here's what I know for sure about 12 counterintuitive lessons i learned managing a remote: there are no shortcuts, but there are smarter paths.
The smartest founders I work with treat 12 counterintuitive lessons i learned managing a remote as a competitive advantage, not a checkbox. They invest in it early, measure it obsessively, and never stop improving.
If you're just getting started with 12 counterintuitive lessons i learned managing a remote, don't be intimidated. Everyone starts somewhere. The key is to start with the right mindset and the right framework, and then execute like your company depends on it. Because it probably does.
Frequently Asked Questions
Which item on this list has the highest impact?
It depends on your stage and context, but in my experience, the items near the top of the list tend to have the broadest applicability. That said, sometimes the less obvious items create the biggest breakthroughs for specific situations.
Are these recommendations still relevant in 2026?
Absolutely. While specific tools and tactics change, the underlying principles remain consistent. I update my thinking regularly based on what I'm seeing in the market and across my portfolio companies.
How were these items selected?
Each item on this list comes from direct experience, either from building my own companies or from patterns I've observed across the 200+ startups I've invested in. I prioritize practical, actionable items over theoretical concepts.