The Four Tenets of Remote Product Management
summary
Four practical rules for remote product teams backed by examples from GitLab: require company scheduling that favours other time zones so Europeans can catch US leadership, run design sprints adapted for remote (four iterations so far), keep a living handbook plus issue tracker as a single source of truth (now three long‑lived sources), design for strong alignment and loose coupling, schedule predictable team calls and regular get‑togethers, and open issue trackers to customers to build trust.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:07Skepticism to remote PM
- 4:17Remote work levels
- 6:25Fully support remote team
- 7:31Strong alignment loosely coupled
- 9:39Single source of truth
- 11:46Balance async and sync work
- 15:21Open issue trackers to customers
- 17:27Summary
- 19:16Q&A
related talks
22mRemote Right: How to Thrive in a Post-Office World
44mHow To Lead a Remote Team
36mRemote work is here to stay: and what's next?
29m5 Pillars for Managing a High-Performing Team, Even Remotely
49mRemotely Operated - Managing Scattered Teams
39mPerks and Pitfalls of Building a Remote First Team
29mRemote(ly) Better Than Before
52mRemote Working Approaches That Worked (And Some That Didn’t)