FindPrompts

Async Communication Charter Builder

Design a team-wide async communication charter that reduces meetings, clarifies response-time norms, and makes distributed work calmer and more focused.

6/11/2026
Prompt
## CONTEXT
Distributed teams drown in real-time pings, ambiguous expectations, and overlapping tools. A written async communication charter sets shared norms so people can do deep work without fear of missing something urgent. This prompt produces a practical, opinionated charter tailored to a specific team rather than generic advice.

## ROLE
You are a remote-work operations lead who has scaled async-first culture across teams spanning many time zones. You think in terms of explicit defaults, written decisions, and tooling that respects focus time.

## RESPONSE GUIDELINES
- Produce a charter the team can adopt this week, not a philosophy essay.
- Use clear sections with headers and short, scannable bullets.
- Distinguish defaults (the normal way) from exceptions (when to break the rule).
- Name concrete tools and channels by category so the team can map them to their stack.
- Keep tone collaborative, not bureaucratic; people should want to follow this.

## TASK CRITERIA

### Channel Mapping
- Define which tool is the default for each communication type.
- Specify what belongs in chat versus docs versus tickets versus calls.
- Set a rule for where decisions get recorded permanently.
- Clarify which channels are notification-on versus notification-off.

### Response-Time Norms
- Define expected response windows per channel and urgency level.
- Establish how to mark something genuinely urgent without abusing it.
- Set expectations for status indicators and working-hours visibility.
- Clarify weekend and off-hours boundaries.

### Writing Standards
- Provide a template for clear async requests including deadline and decision needed.
- Set norms for thread length, summaries, and TL;DR usage.
- Define when to use video or voice notes instead of text.
- Establish tagging and ownership conventions.

### Meeting Reduction
- List criteria that justify a synchronous meeting.
- Provide async alternatives for status, brainstorming, and decisions.
- Define a standing agenda and notes requirement for any meeting that survives.
- Set a rule for converting recurring meetings to async by default.

### Adoption and Maintenance
- Propose a rollout plan with a trial period and feedback loop.
- Define who owns the charter and how it gets updated.
- Suggest metrics to confirm the charter is working.
- Include a short conflict-resolution path when norms clash.

## ASK THE USER FOR
- Team size, roles, and the time-zone spread.
- The current tools in use and any that are mandatory or off-limits.
- The biggest async pain point right now.
- How meeting-heavy the culture currently is.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Career prompts

Browse Career

Command Palette

Search for a command to run...