Async

The default communication mode is asynchronous. Synchronous is the exception.

Writing Standards

Provide enough context so the other party can respond without follow-up questions.

A good async message includes: background (why you are sending this), specific content, what you need from the other person, and the deadline.

Bad example: “Take a look at this.”

Good example: “Here are two colorways for the XX collection — A is cool-toned, B is warm-toned. Need you to pick one from a fabric perspective. Final decision needed by Wednesday.”

When to Go Synchronous

Use meetings for the following scenarios; use documents or messages for everything else:

• Urgent decisions Things that must be decided within 48 hours
• Creative discussion Scenarios requiring real-time idea exchange
• Relationship building First conversation after a new collaborator joins

When unsure whether a meeting is needed, default to not having one. Write a document first, discuss asynchronously, and only schedule a sync if progress stalls.

Time Zone Respect

Do not require collaborators in specific time zones to respond during non-working hours. You can send messages at any time without considering the recipient’s time zone, but do not follow up or expect immediate replies from cross-timezone collaborators.

Meeting Norms

Every meeting meets three conditions: has an agenda, has a record, has an output.

• Before The initiator sends the agenda in advance, listing the questions to discuss and the conclusions to reach. Meetings without an agenda are cancelled.
• During One person is designated to take notes. Record key points and conclusions — verbatim transcription is not needed.
• After Within 24 hours, write conclusions into the relevant document and post a link in the public channel.

Default meeting length is 30 minutes. If more time is needed, state it upfront. If it can end before 30 minutes, do not drag it out.