Before you start, and why a team needs a rhythm
Before this course: Daily Business Habits (course 2.2.2). Before that: The Show Up Every Day System (course 2.2). You already have a daily move, a few honest numbers, a 30-minute weekly review and a one-page routine. Now imagine a band. One musician can play alone, but a band needs a beat that everyone follows. A team rhythm is the beat.
- This course assumes you finished courses 2.2 and 2.2.2: you have a daily move, 3 to 5 numbers, a weekly review with a decision log, if-then plans and a one-page Daily, Weekly, Monthly checklist.
- "Team" here can be one part-time helper, a family member, a volunteer, a freelancer or an employee. The same ideas apply.
- When work is shared, three things break first: people do not know what they own, how the work is done, and when to talk. This course fixes those three, one at a time.
- Google's team research (Project Aristotle) found that how a team works together mattered more than who is on the team. It named five dynamics: psychological safety, dependability, structure and clarity, meaning and impact. Structure and clarity (clear roles, goals and processes) is the part you can build with paper and a calendar.
- Your routine from course 2.2.2 does not disappear. It becomes the owner's routine. The team rhythm sits on top of it.
- Rule for this course: write it down once so you do not have to explain it ten times.
- Open your one-page Daily, Weekly, Monthly checklist from course 2.2.2.
- Highlight every step that must be done by you (for example, setting prices, final decisions).
- Underline every step that someone else could learn (for example, packing orders, replying to common questions, posting).
- Write the number of hours per week the underlined steps take you.
- Write one sentence: "If I had a helper for ___ hours a week, I would use the time to ___."
- Check: you have two lists, "only me" and "could be shared", and an hours number.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
Read the video script
[Host] "One person can run on habits. A team needs a rhythm."
[Text on screen: What. How. When.] "Three things break first when work is shared: who owns what, how it is done and when we talk."
[Text on screen: Structure and clarity] "Google's research on teams listed clear roles, goals and processes as one of five key dynamics."
[Screen: a checklist with two highlighted columns] "Start by marking which steps only you can do, and which someone else could learn."
[Host] "Write it once, so you do not explain it ten times."
Make your two lists ("only me" and "could be shared") and write the weekly hours for the shared list.
ClaudeStuck? Copy a ready-made prompt for Claude
Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.
For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.
I'm learning "Building a Team Rhythm: delegate, document and scale" on The Future Market. Lesson 1: "Before you start, and why a team needs a rhythm".
What the lesson teaches:
- This course assumes you finished courses 2.2 and 2.2.2: you have a daily move, 3 to 5 numbers, a weekly review with a decision log, if-then plans and a one-page Daily, Weekly, Monthly checklist.
- "Team" here can be one part-time helper, a family member, a volunteer, a freelancer or an employee. The same ideas apply.
- When work is shared, three things break first: people do not know what they own, how the work is done, and when to talk. This course fixes those three, one at a time.
- Google's team research (Project Aristotle) found that how a team works together mattered more than who is on the team. It named five dynamics: psychological safety, dependability, structure and clarity, meaning and impact. Structure and clarity (clear roles, goals and processes) is the part you can build with paper and a calendar.
- Your routine from course 2.2.2 does not disappear. It becomes the owner's routine. The team rhythm sits on top of it.
- Rule for this course: write it down once so you do not have to explain it ten times.
The exercise I'm working on:
Make your two lists ("only me" and "could be shared") and write the weekly hours for the shared list.
I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.I'm a parent helping my child (about 8 years old) with a lesson called "Before you start, and why a team needs a rhythm" from the course "Building a Team Rhythm: delegate, document and scale".
Here's what the lesson says:
Before this course: Daily Business Habits (course 2.2.2). Before that: The Show Up Every Day System (course 2.2). You already have a daily move, a few honest numbers, a 30-minute weekly review and a one-page routine. Now imagine a band. One musician can play alone, but a band needs a beat that everyone follows. A team rhythm is the beat.
The activity:
Make your two lists ("only me" and "could be shared") and write the weekly hours for the shared list.
Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.Sources
- Google re:Work, Understand team effectiveness: rework.withgoogle.com/intl/en/guides/understand-team-effectiveness
Write a simple procedure (SOP) and a checklist
This lesson is part of full access: every course and every level for one payment.
Delegate a task, not just a chore
This lesson is part of full access: every course and every level for one payment.
Roles, owners and hiring help (with Canadian examples)
This lesson is part of full access: every course and every level for one payment.
Set the team cadence: huddle, weekly, monthly
This lesson is part of full access: every course and every level for one payment.
One-to-one check-ins, feedback and trust
This lesson is part of full access: every course and every level for one payment.
Scale without breaking: bottlenecks, limits and rest
This lesson is part of full access: every course and every level for one payment.
Final project
This lesson is part of full access: every course and every level for one payment.
Quiz
What are the three things that break first when work is shared?
Who owns what, how the work is done and when the team talks.
What is an SOP?
A short written guide that shows how a routine task is done, step by step.
How do you test an SOP?
Let someone who has never done the task follow it, and fix every place they get stuck.
Name the six parts of a good delegation note.
Outcome, deadline, limits, resources, check-in and why.
Which tasks should you hand off first?
Repeatable, written, low-risk tasks.
What does a who-does-what table show for each task?
The owner, a backup and who to ask first.
Does a written contract alone decide if a worker is self-employed?
No. Tax agencies look at the real working relationship.
Where can you find official rules about working hours?
On your country's or region's labour department website.
How long is the Scrum Guide's Daily Scrum?
15 minutes.
What does psychological safety mean?
Team members trust they will not be punished or embarrassed for admitting mistakes, asking questions or offering ideas.
What are the three parts of a good feedback sentence?
What happened, why it matters and the next step.
What is a bottleneck?
The one step that limits how much work gets done.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.