How to create Remote Team Management System Design prompt

As an expert in remote team management and organizational design, develop a comprehensive remote team management system. Tailor the system specifically for a {TEAM_SIZE}-person team operating within the {INDUSTRY} industry. Your output should be structured with clear headings and actionable bullet points, incorporating best practices for communication, collaboration, and team well-being in a remote environment.

Focus on the following key areas, providing specific recommendations and examples:

### 1. Communication Protocols:
- Async First (Default): Define guidelines for non-urgent communication, formal documentation, and video updates to minimize live meetings. Specify appropriate tools (e.g., Slack/Discord for non-urgent, Email for external/formal docs, Loom for video updates).
- Sync Only When Necessary: Outline specific triggers for synchronous communication (e.g., critical decisions needing >3 back-and-forths, brainstorming sessions, scheduled weekly/monthly meetings).

### 2. Meeting Structure:
- Daily Standup (15 min): Describe purpose, typical agenda (e.g., what was done yesterday, what will be done today, blockers with tags), and format (async option).
- Weekly Team Meeting (30 min): Detail agenda items (e.g., wins from last week, priorities this week, 1 deep dive topic, open floor) and suggest a consistent schedule (e.g., Tuesday 10 am).
- Monthly All-Hands (60 min): Outline key discussion points (e.g., company metrics, product roadmap, team shoutouts, Q&A).
- One-on-Ones (30 min): Specify frequency (e.g., weekly per person) and duration.

### 3. Recommended Tool Stack:
- Communication: Suggest primary platforms (e.g., Slack) with usage guidelines (e.g., dedicated channels for each project, utilizing threads for context, clear status updates like working/meeting/away).
- Project Management: Recommend tools (e.g., Asana/Trello/ClickUp) and outline a simple workflow template (e.g., To Do → Doing → Review → Done) for tasks and deadlines.
- Documentation: Propose a single source of truth platform (e.g., Notion/Confluence) and list essential required documentation (e.g., onboarding guides, process documentation, FAQs).

### 4. Remote Work Policies:
- Time Zone Management: Strategies for handling distributed teams, including defining core overlap hours (e.g., 4-hour daily overlap), rotating meeting times for fairness, and requiring working hours in status updates.
- Work-Life Balance: Guidelines to prevent burnout, encourage breaks, and maintain healthy boundaries for work hours.
- Onboarding & Offboarding: Key remote-specific steps for integrating new hires smoothly and managing departures professionally.

### 5. Standard Operating Procedure (SOP) Templates:
- Meeting Notes Template: Provide a structured example (e.g., [Date] - [Meeting Name], Decisions:, Action Items: [task] @person due [date], Next Meeting: [date]).
- Project Brief Template: Suggest essential components for project initiation (e.g., Objective, Scope, Deliverables, Team Roles, Timeline, Key Stakeholders).

### 6. Culture & Engagement Initiatives:
- Virtual Team Building: Ideas for fostering connection and camaraderie (e.g., virtual coffee breaks, online game sessions).
- Recognition & Feedback: Systems for acknowledging achievements and providing constructive performance feedback remotely.
- Growth & Development: How to support continuous learning and career progression in a remote setting.

Ensure all recommendations are scalable and adaptable to the specified team size and industry characteristics, emphasizing efficiency, transparency, and employee well-being.