Your team is spread out
Some people start work as others are finishing, and decisions wait a day.
Make priorities, decisions and progress visible when nobody shares a room.
Remote teams run on what is written down and on deliberate contact. The course covers recording priorities and decisions where everyone can find them, choosing between messages and meetings, using time zone overlap well, one-to-ones and noticing when someone is struggling.
Type this when Cadence asks what you want to learn
I lead a team that works remotely, with some of us in different time zones. I want people to know what matters, get decisions made without endless calls, and still feel like a team rather than names on a screen.
Change any word so it fits your situation. The course is built from what you type and a few setup questions.
Start today
Useful on their own. The course is for when you want the whole skill, not just the first move.
Original example: one person works 9am to 5pm in London and another 9am to 5pm in New York, usually five hours behind. Their shared hours are 2pm to 5pm London time, three hours. Put live discussion there and leave the rest of the day for focused work.
After a call, post three lines: what was decided, who owns the next step and by when. Original example: "Decision: launch moves to 3 March. Owner: Priya. Next update: Friday." Someone who missed the call can catch up in a minute.
Original team norm: "Reply to messages within one working day; phone for anything urgent." Without an agreed norm, some people answer at midnight and others feel ignored.
Ask: "What's one thing slowing you down that I might not see from here?" Problems in a remote team often stay invisible until someone is asked directly.
Before the course is built
Lesson 1 opens on the moment you describe, and the examples use your role. For this request, expect questions like these.
Right for now
Some people start work as others are finishing, and decisions wait a day.
Your calendar is full of meetings that could have been a written update.
In an office you would notice. On a screen, people go quiet.
Course arc
Cadence writes the lessons for you, so the exact path follows your answers. This is the ground a course built from this sentence covers.
01 / 06Fewer chance conversations, more reliance on writing and on agreed norms.
Keeping one place that answers what matters now and what was decided.
Agreeing response times and using shared hours for what needs live discussion.
Regular conversations that cover the person, not only the task list.
Judging work by results rather than by visible activity.
Small, deliberate ways to build relationships without forced fun.
What changes
Record priorities and decisions somewhere the whole team can find them.
Decide what needs a meeting, a message or a written proposal.
Use regular one-to-ones to spot problems early.
An online status shows presence, not progress. Agreed outcomes are a better measure of work.
Written decisions that people can return to often align a team better than another call.
Course questions
Find your real overlap. Original example: one person works 9am to 5pm in London and another 9am to 5pm in New York, usually five hours behind. Their shared hours are 2pm to 5pm London time, three hours. Put live discussion there and leave the rest of the day for focused work. Write decisions where people can find them. After a call, post three lines: what was decided, who owns the next step and by when. Original example: "Decision: launch moves to 3 March. Owner: Priya. Next update: Friday." Someone who missed the call can catch up in a minute. Agree response times out loud. Original team norm: "Reply to messages within one working day; phone for anything urgent." Without an agreed norm, some people answer at midnight and others feel ignored. Add one question to every one-to-one. Ask: "What's one thing slowing you down that I might not see from here?" Problems in a remote team often stay invisible until someone is asked directly.
No. Cadence builds the course when you type the sentence and answer a few setup questions, so the lessons follow your situation. This page describes what a course built from this request covers. You see the whole path before Lesson 1.
Remote teams run on what is written down and on deliberate contact. The course covers recording priorities and decisions where everyone can find them, choosing between messages and meetings, using time zone overlap well, one-to-ones and noticing when someone is struggling. It sits under Leadership in the Work & ambitions part of the library.
No. Setup asks what you already know and where you want to use it, and the course starts from there. Bring a real situation if you have one; the examples are built around it.
Courses run 7 to 30 lessons of about 10 minutes, sized to what you asked for. One lesson a day is the intended pace, and you can go faster. Lessons can be read or played as audio.
No. Cadence is for practical self-learning and does not award accredited degrees or professional certification.
Start today
The sentence to type
I lead a team that works remotely, with some of us in different time zones. I want people to know what matters, get decisions made without endless calls, and still feel like a team rather than names on a screen.