Earlier this year, I was trying to align a cross-functional team on the direction for a new product. We were four weeks in, still in the ambiguity phase, and I could feel the team drifting. In the old world, I would have pulled everyone into a room with a whiteboard and we'd have hashed it out in an afternoon. Instead, I was staring at a grid of Zoom faces, trying to read body language through laptop cameras, and realizing that the consensus that used to happen organically now requires deliberate architecture.
That moment crystallized something I've been thinking about all year. Remote work isn't new anymore. But building something from zero, remotely, still is.
The shift is real
ProductPlan's 2021 report surveyed over 2,200 product managers and found that 67% now choose fully remote work. A year ago, 70% preferred the office. That's a complete reversal. But the top challenge hasn't changed much: 26% of PMs say getting consensus on product direction is their biggest struggle, with working across departments and communicating strategy close behind.
For a team iterating on an existing product, those challenges are manageable. You have a baseline. You have shared context. You have a product people can point to. For a 0-to-1 team, where the product doesn't exist yet and the direction changes weekly, every one of those challenges is amplified.
What 0-to-1 demands
Building from zero requires high-bandwidth communication, rapid iteration, and comfort with ambiguity. In a room, you resolve disagreements in real time. You sketch an idea, someone pushes back, you revise on the spot. Remote strips all of that away. The whiteboard is gone. The hallway conversation is gone. The ability to read whether someone is confused or convinced, mostly gone.
So what replaces it?
Three things that actually work
Write more than you present. The remote 0-to-1 PM writes constantly. Decision briefs. Weekly async updates. Lightweight specs that invite feedback before meetings, not during them. A colleague told me she started sending a one-page "here's what I'm thinking and why" doc before every key meeting. "The meetings got shorter," she said. "And the decisions got better, because people had time to actually think before reacting."
Smaller milestones, faster feedback. Ambiguity is the defining feature of 0-to-1. The temptation is to wait until you have something polished to share. Don't. Break the work into the smallest testable pieces and ship them. A prototype. A research finding. A hypothesis written on a single slide. The faster you get something in front of real people, the faster the ambiguity shrinks.
Build trust outside of standups. Trust doesn't form in status meetings. It forms in 1:1s. In the PM admitting what they don't know. In asking an engineer about their weekend before diving into the sprint. I've started blocking 30 minutes every week with each person on my team, no agenda, just conversation. It felt indulgent at first. It turned out to be the most productive thing I do.
What remote actually revealed
Remote didn't make 0-to-1 harder. It made the hard parts visible. The alignment problems, the communication gaps, the trust deficits that used to get papered over by physical proximity are now impossible to ignore. And that's actually useful, because you can't fix what you can't see.
The PMs leading successful new products in 2021 aren't the ones who replicated the office on Zoom. They're the ones who built new habits around clarity, trust, and writing things down.