Communication Contract

This contract sets baseline expectations for communication across the company. Its goal is to support autonomy and protect deep work while keeping alignment reliable.

Write messages with enough context that someone can take action without follow-up questions. If the message affects a decision, add a short summary at the top.

Response speed depends on the role and the work mode. General expectation:

• Non-urgent messages: reply within 1–2 working days.
• Urgent matters: state urgency explicitly and why it is urgent.
• Deep-work blocks: acknowledge within the day, resolve when ready.

Urgency should be exceptional, not default.

Use shared channels for work that needs visibility. Use direct messages only for quick clarifications or personal matters. Tasks go where tasks belong.

Move to a real-time conversation only when:

• the issue is blocking work,
• asynchronous attempts are looping,
• alignment requires rapid exchange,
• emotional nuance or conflict is involved.

Meetings should solve problems, not compensate for weak writing.

When you commit to an action or timeline, state it clearly. If circumstances change, update others proactively.

Default to kindness, directness, and brevity. Design communication so others can work without needing you in real time.

This contract evolves as our distributed practices mature.