When I moved from India to Los Angeles for my MSBA at UCLA Anderson, I didn't just leave behind my colleagues and my comfort zone. I left behind my wife. For a year, we navigated a 13-hour time difference, spotty WiFi calls, and the particular agony of eating dinner alone when you're used to eating together. It was, in the best possible way, a masterclass in product management.
Alignment Without Presence
When you're in the same room as your stakeholders — your engineering lead, your designer, your business partner — misalignment gets corrected in real time. A raised eyebrow, a pause, a "wait, what do you mean by that?" catches the problem before it compounds.
Long distance removes that safety net. You learn to over-communicate. You learn to ask "did we actually agree, or did we just both say yes?" You start sending written summaries after conversations, not because you're paranoid, but because you've learned that memory is reconstructive, and two people can leave the same call with entirely different understandings.
PMs who've done this in distributed teams know exactly what I mean.
Prioritization Under Scarcity
When you have two hours on a Saturday evening call and a list of twelve things to cover, you learn ruthless prioritization fast. You don't talk about everything. You talk about the things that require you, together, now.
"The most valuable product skill isn't knowing what to build. It's knowing what not to build — and being okay with that."
The same logic applies to your roadmap. You have finite engineering time, finite design bandwidth, and a backlog that grows faster than you can groom it. Long-distance taught me that saying "we'll get to that later" is sometimes the kindest, most strategic thing you can say.
Trust Is the Product
Here's the deepest lesson: in a long-distance relationship, you can't manage by observation. You can't "check in" by walking past someone's desk. The relationship only works if both parties trust the other to do what they said they'd do, care about what they said they care about.
Product management is the same. You will never have full visibility into your engineering team's daily decisions. You will never know every tradeoff your designer made. The product you ship is a function of trust compounded over hundreds of small interactions.
Build that trust like a relationship — through consistency, honesty, and showing up when it matters. Because the alternative — micromanagement, endless check-ins, approval bottlenecks — is the product management equivalent of a controlling partner. And nobody ships great products that way.
The Happy Ending
My wife is with me in Los Angeles now. The distance is over. And while I wouldn't recommend a long-distance marriage as a PM training program, I'm a better product thinker for it. Sometimes the hardest constraints teach you the most useful habits.