Document 07 of 10
Rhythms & Standards
The daily and weekly cadence, the standards that protect culture, and a lean tool stack.
Culture is not slogans on a wall. It is the behaviours you repeat and the ones you refuse to let slide. On a remote team, culture lives almost entirely in communication: how you check in, how you meet, where you talk, and when you log off.
This document is the operating cadence: the daily and weekly rituals that keep everyone aligned, the standards that protect the culture, and the lean tool stack that runs underneath all of it.
Type
System
Cadence
Daily and weekly
Owner
Every manager
Next doc
Paying Your Team
Section 00
The Daily Standup
The daily standup is the backbone of remote visibility. Each person posts a 60-second update in a dedicated Slack channel. No meeting. You scan the channel in a minute and know exactly where everyone is.
Field 01
Yesterday
What you completed in the previous working day. Specific deliverables, not general activity.
Field 02
Today
What you are working on today. Specific tasks, not general plans.
Field 03
Blockers
Anything in your way. If nothing is blocking, write None. Silence is not a default.
Standup example
Section 01
Friday Wins
Friday Wins closes the week on a high. Each person shares one thing they accomplished. It builds momentum and a culture that notices progress, which matters more on a remote team where nobody sees the effort behind the work.
Friday win example
Section 02
Weekly Context and Asks
At the start of each week, the manager posts the top priorities and asks everyone to reply with their own. Two minutes of writing prevents a week of quiet misalignment.
Weekly context post
Section 03
Meeting Protocol
Meetings start and end on time, always with an agenda and notes. No exceptions. The test is simple: if you cannot state the purpose of a meeting in one sentence, cancel it.
| Phase | What happens |
|---|---|
| Before | Post the agenda 24 hours ahead. State the goal and the expected outcome. Assign a note-taker. |
| During | Start on time even if people are late. Follow the agenda. Document decisions as they happen. |
| After | Post notes within 1 hour. Tag action items with owners and due dates. Archive in a shared location. |
Run every meeting from the same note structure. Copy or download the template below.
Meeting Notes
Header
- Meeting
- Date
- Attendees
- Note-taker
Agenda
- Topic 1
- Topic 2
- Topic 3
Discussion
- Topic 1 key points
- Topic 2 key points
- Topic 3 key points
Decisions made
- Decision 1
- Decision 2
- Decision 3
Action items
- Action 1
- Owner ___ Due ___
- Action 2
- Owner ___ Due ___
- Action 3
- Owner ___ Due ___
Next
- Next meeting
Section 04
No Private DMs
Work conversations happen in public team channels, not direct messages. A private DM creates a silo: the answer helps one person and then disappears. The same answer in a public channel helps everyone and stays searchable.
A private DM
- Manager DMs a teammate: can you send me that report?
- Only two people ever see it
- Context is lost the moment it is sent
- Nobody else learns from it
A public channel
- Posted in #reporting: can you post the latest client report here?
- The whole team can see and use it
- It stays searchable for later
- Everyone learns from the exchange
Section 05
Setting Boundaries
Remote workers need boundaries or they burn out, and a burned-out team is a slow team. Protect your people's off-hours as deliberately as you protect the standup.
- State it plainly: I do not expect you online outside your working hours. If I message you at 8pm my time, you reply on your next workday.
- Model it: when you work late, schedule the message to send in the morning so nobody feels pressure to reply after hours.
- Respect time zones by default. Use scheduled send. The goal is a team that rests, not a team that performs being always-on.
Section 06
The Lean Tool Stack
Less is more. Every tool you add is another login, another habit, another point of failure. Before adopting anything new, ask: can we do this with what we already have? Add a tool only when a clear, repeatable process demands it.
| Category | Default | Why |
|---|---|---|
| Communication | Slack or Teams | One home for real-time and async. Pick one and commit. |
| Project management | Asana, Jira, or Trello | A single source of truth for tasks and deadlines. Never run two. |
| File storage | Google Drive or Dropbox | One organised place for documents, SOPs, and assets. |
| Passwords | 1Password or LastPass | Secure access, and the reason a new hire can log in on Day One. |
| Async video | Loom | Screen recordings and quick walkthroughs for coaching and SOPs. |
| Video calls | Zoom | Live calls and screen shares. Record the important training. |