I have spent over 25 years of my 40+ year career managing remote and distributed engineering teams. Long before the 2020 lockdowns, I was building systems with engineers spread across time zones and continents.
And yet, in 2026, I still see leaders struggling with the "Remote vs. Onsite" debate. Usually, when a leader demands that everyone return to the office, it’s not because the work isn't getting done—it's because they don't know how to manage the work without the physical presence of the workers.
Here is the mentor's perspective: managing remote teams is fundamentally the same as managing onsite teams. The only difference is that remote work forces you to be a better manager.
1. Stop Counting Hours, Start Measuring Work
The greatest trap in management is the "butts in seats" metric. In an office, it’s easy to confuse presence with productivity. You see someone at their desk, they look busy, and you assume they are producing value.
Remote work strips away that illusion. It forces you to focus on the only thing that actually matters: the work produced.
To manage a high-performance remote team, you must have clear, quantifiable KPIs for both quality and quantity. Whether it's pull requests merged, tickets closed, or architectural milestones reached, the focus must remain squarely on the output. If the work is being delivered at a high standard, the location of the engineer is irrelevant.
2. Walking the Floor in Slack
One of the common complaints about remote work is the loss of "serendipitous" communication—the water cooler chat or the ability to "walk the floor" and see how the team is doing.
But you can walk the floor in a remote environment. You just do it in Slack (or Discord, or Teams).
As a leader, I make it a point to be visible in the project channels. I'm not there to micromanage; I'm there to observe the "vibe" of the team. Is there a healthy debate happening? Are people helping each other solve problems? Is there a lot of silence where there should be activity? "Walking the floor" digitally allows you to spot friction points and provide support long before a project starts to drift.
3. The Global Salary Arbitrage
One of the most powerful advantages of a remote-first culture is the ability to leverage global salary structures. When you are no longer limited to the 50-mile radius of a physical office, you can find incredible talent anywhere in the world.
This isn't about "outsourcing" to the cheapest bidder. It's about finding high-quality candidates who are often overlooked because they don't live in a "tech hub." By hiring globally, you can build a team that is not only more cost-effective but also more diverse in its thinking and experience.
In my experience, an engineer in a "lower-cost" region who is treated as a first-class member of the team will often outperform a Silicon Valley engineer who is distracted by the local hype cycle and high cost of living.
4. Building an Engaged Culture
Remote work does not mean disconnected work. In fact, some of the most engaged teams I've ever led were 100% remote.
Engagement comes from clarity of mission, autonomy in execution, and a shared commitment to quality. When people feel that their work is valued and that they are trusted to manage their own time, they become more invested in the outcome.
Use AI-accelerated tools like Kaigents to remove the drudgery from their day-to-day. When an engineer can spend 80% of their time solving interesting problems and only 20% on "process," their engagement sky-rockets.
The Verdict on Remote
If you can't manage a remote team, you likely aren't managing your onsite team as well as you think. You’re just relying on physical proximity to mask a lack of clear process and accountability.
Remote work is the ultimate test of a leader's ability to communicate, delegate, and trust. If you embrace it, you gain access to a global pool of talent and a level of operational flexibility that a physical office can never match.
Focus on the work, not the chairs.
John K. Johansen is a VP of Software Engineering and Venture Architect who has led global engineering teams for over 25 years.