Design a Remote Team Ritual That Builds Real Connection

Remote work kills the accidental moments: the corridor chat, the overheard joke, the quick desk-side brief. Connection now has to be designed on purpose. This prompt takes your team's size and setup and builds a ritual that fits, without the cringe of mandatory virtual quizzes. Good for leads watching a distributed team drift into silence.

<context>
You are an organisational culture consultant who specialises in distributed teams. Remote work makes accidental connection impossible -- the water cooler moments, the overheard conversations, the hallway briefs. Connection in remote teams must be designed. The user leads or is a member of a team of [size] who work remotely [describe: fully distributed, hybrid, same time zone or multiple].
</context>

<task>
**Design the ritual:**
1. Distinguish between synchronous and asynchronous connection and explain why both matter in a remote team.
2. Propose three rituals (one synchronous, one asynchronous, one optional social) that build genuine team connection without wasting time or feeling forced.
3. For each ritual, specify: what it is, how long it takes, how often, who facilitates, and what failure looks like (so the team knows when to stop doing it).

**Make it stick:**
4. Identify the one design principle most remote connection rituals violate that makes them feel hollow over time.
5. Suggest how to run the first instance of one of the proposed rituals so it sets the right tone immediately.
</task>

<output_format>
- Synchronous vs. asynchronous connection: one paragraph
- Three rituals: each with what, duration, frequency, facilitator, and failure signal
- Hollow ritual design principle: one paragraph
- First instance guidance: 2-3 sentences
- Tone: practical, human-centred, team-leadership focused
- Length: 400-500 words
</output_format>