How intentional communication, culture, and protected innovation can help distributed product teams do more than simply execute.
GUEST COLUMN | by Vishal Gupta
Most remote work advice applies broadly to sales teams, customer service, and marketing. Product development is different. It’s messy by design. The best ideas often come from a hallway conversation, a sketch on a whiteboard, an engineer overhearing a customer call and thinking, “wait, that’s not how we built it.” Strip out physical proximity and you risk something worse than inefficiency: teams that execute perfectly and innovate not at all.
‘Strip out physical proximity and you risk something worse than inefficiency: teams that execute perfectly and innovate not at all.’
That was our real threat. The teams building GoGuardian Admin and Beacon are not writing code in a vacuum. They’re solving problems that show up in real classrooms, for real kids. A filtering decision affects whether a student can access a resource they need. An alert threshold in Beacon determines whether a counselor gets notified in time to help a struggling student. That kind of work demands constant feedback between educators, students, and our own people. We had to figure out how to keep that loop alive without a shared physical space.
The first thing we changed was the reflex toward real-time everything. Being responsive was quietly killing our ability to do deep work. Every initiative now starts with a short written brief covering the problem we’re solving, the student and staff outcomes we’re targeting, and the metrics that will tell us if we got it right. That document is the source of truth, not the last video call. We also got explicit about decision rights, so that someone working late in one time zone does not have to wait until morning somewhere else to keep moving.
Culture Does Not Travel by Osmosis
In an office, culture spreads whether you’re intentional about it or not. You absorb it from watching how a senior leader handles a tense conversation, from what gets celebrated and what gets quietly ignored. Remote teams do not have that. If you do not deliberately build and reinforce culture, you end up with something polite and transactional, people who do good work but do not really know each other.
We took two specific steps to build a cohesive culture across distance. The first was a regular recognition forum — one designed not just to celebrate wins, but to highlight the process behind them and reinforce our commitment to customer-centricity. We now recognize product and engineering team members at both the company and department level each quarter, always paired with context on why they’re being recognized.
The second action we took was around building a regular offsite model that enabled product and engineering leaders to build trust and strong relationships with each other, and use those opportunities for collaborative problem solving. By rotating the locations of the offsites, we are able to get participation and build cohesion not just between leaders, but also individual contributors who are based in that location and are able to build a stronger relationship with each other.
We also got serious about our values as operational language rather than wall art. “Student-Centered Curiosity” shows up in sprint retros, in how we recognize teammates publicly, in how we hire.
Protecting Space for Innovation
The biggest structural risk in remote product work is defaulting to pure execution. Backlog, sprint, ship, repeat. While that cadence is efficient, it will slowly hollow out your product. Due to our heavy focus on delivery, GoGuardian had not held a dedicated innovation hackathon for several quarters. During our last offsite, we decided to implement hackathons twice a year and establish a formal process to incorporate those innovations into our products.
To ensure a successful innovation hackathon, we had to solve three challenges. First, we had to give team members dedicated time so they could focus on creating something great. Second, we wanted directed innovation that could be incorporated into our products, so we had our product leaders identify the biggest challenges our customers were facing. Third, we wanted collaborative innovation, so we mandated that participants work in teams and encouraged them to form teams with people they don’t usually work with. The result was a breakthrough innovation hackathon that we finished last month with 80 participants across 18 teams. Our target was to find three innovations to incorporate this year in our products. We found five.
What Works
– Documentation: Writing everything down, as if it’s not documented, it effectively didn’t happen.
– Async Design Reviews: Using a set review window instead of live critiques, which ensures quieter voices are heard.
– Dedicated Overlap Time: Scheduling time when the team is available for live collaboration, shifting all other work to async.
What Does Not Work
x Mimicking Co-located: Treating remote work like co-located work (using video calls instead of informal ‘hallways’).
x Inconvenient Standups: Forcing a standup at a single time that works for one hemisphere and punishes the other.
x Neglecting Informal Connection: Remote teams go transactional faster than expected when informal connections are neglected.
We’ve also built a more rigorous recruiting process to ensure we’re hiring talented, authentic candidates in a remote environment where in-person verification isn’t possible.
How This Shapes What We Build
The discipline required to make remote work actually work has made us better at building for our users. Our reliance on async communication and transparent documentation deepens our instinct to design tools that work for every classroom, not just the well-resourced ones. The empathy we’ve developed for teammates working in difficult circumstances — a parent coding after their kids are asleep, a designer on spotty internet — shows up directly in how we build for educators facing similar realities.
What I Would Tell Other Product Leaders
Design for async first and protect synchronous time for relationships and real creative work. Write your culture down and then actually live it publicly. Protect innovation structurally, because it will never just happen in the margins. Measure things that tell you how the team is actually doing: not just velocity, but how connected people feel, how fast decisions are getting made, and how quickly new people find their footing.
The goal is to build something better than the office ever was. The students and teachers depending on what we build are reason enough to keep getting it right.
—
Vishal Gupta is Global Chief Technology and Product Officer at GoGuardian. Connect with Vishal on LinkedIn.
0 Comments