Remote Product Team Template for Product Managers

Define "urgent" clearly (production incidents, security breaches, customer-escalations that require immediate response). For urgent issues, use a phone call or text message, not Slack. For everything else, the response time expectations in the communication section should be sufficient. If you find yourself declaring things "urgent" more than once a month, the underlying process needs fixing.

No blanket requirement. Cameras on for retros (reading body language matters for process improvement) and 1:1s (relationship building). Camera optional for all other meetings. "Camera optional" means truly optional with no judgment. Some people have bad lighting, share a room, or simply focus better without a camera. The [Stakeholder Management Handbook](/stakeholder-guide) covers how to maintain strong working relationships regardless of communication medium.

Two mechanisms. First, response time expectations with escalation paths (posted in the team charter). Second, the "silent approval" rule for decisions: if you do not respond by the deadline, your vote is "approve." These create urgency without requiring synchronous presence.

At minimum: a messaging tool (Slack/Teams), a project board (Linear/Jira), a documentation hub (Notion/Confluence), a design tool (Figma), a video tool (Zoom/Meet), and a screen recording tool (Loom). The specific tools matter less than having explicit agreements about which tool is used for what purpose. The [product operations guide](/product-ops-guide) covers tool selection in depth. ---