Plan the team in waves
Decide the roles, which need judgement and which follow the same steps, then set them up in the order their inputs arrive.
✦ Course · Intermediate
Set up flexible and strict workers in waves, run them from one team room, address a strict worker to run its steps, bring chats in, set when the team runs, and finish with an honest wrap.
Start courseYOUR OUTCOME
Decide the roles, which need judgement and which follow the same steps, then set them up in the order their inputs arrive.
Write the first job with a citation rule, then start marketing from a worker template.
New team puts workers and chats in one room, and the room is where you run the company.
A strict member runs its taught steps only when you pick it, then posts one result back to the room.
Add a chat to the team, pass its work in with Send to team, and give the team its own times.
Run a status round, steer one member, then ask the room to grade itself and list what is missing.
What each lesson covers
Decide the roles, which need judgement and which follow the same steps, then set them up in the order their inputs arrive.
A team is a set of roles with a flow between them: research feeds brand and finance, and brand and finance feed engineering and marketing. Roles that need judgement become flexible workers. A job that repeats the same steps, like a weekly supplier price check, becomes a strict worker. Set them up in waves so each one can read what the last produced. A team holds 1 to 8 members, and each worker or chat can be in one team at a time.
Practice. Write your own role table for a real project: name, flexible or strict, and which earlier role each one depends on. Order the roles into three waves.
Wave 1: Mia · Head of Research (flexible). Wave 2: Theo · Brand and Priya · Finance (flexible, both read Mia's brief), plus Price check (strict, every Monday). Wave 3: Sam · Engineering and Lena · Marketing (flexible, both read Theo's board and Priya's plan).
Write the first job with a citation rule, then start marketing from a worker template.
The first worker sets the standard for the rest: a goal with the deliverable, the sources and a finish line, plus a rule about evidence. "Never invent a figure; cite it or flag it" is the line that makes every later number trustworthy. Its output lands in Doc Manager, where the others can read it. Not every role needs writing from scratch: Lena can start from the Content calendar planning template, through Start from a template on the first question card or Marketplace, Worker templates. A template's suggested schedule arrives Not enabled until you ask for one.
Practice. Create your research worker with New worker and No, use its judgement, with a goal that names the format and the citation rule. Open the finished document and check one citation before you set up anyone else.
Name: Mia · Head of Research. Goal: I'm starting an online shoe store on dropshipping: everyday sneakers and casual shoes, Australia first, then New Zealand, from a $25,000 start. You are our head of research. Research this market with sources: size and growth of online footwear in Australia, the top five competitors and their price points, the realistic dropshipping supplier options with lead times to Australia and typical landed cost per pair, and the three biggest risks. Deliver a two-page opportunity brief as a Word document with every figure cited. Never invent a figure; cite it or flag it.
New team puts workers and chats in one room, and the room is where you run the company.
Teams replace group chats, and flexible workers answer in a team room as they did there. New team asks for a Team name and its members, listed as Flexible workers, Strict workers and Chats, each with an optional Role. Create team opens the room. The row at the top shows each member with its Strict or Flexible tag; on a computer, hover over a member to remove it, which never deletes it. The Members button adds or reorders members later. Address the whole room with @everyone, or pick members with the chips above the message box.
Practice. Create your team with Mia as its first member, then post a welcome that says what the company is building and what each member should post when it finishes.
@everyone Welcome to the launch team. We're building an online shoe store on dropshipping, Australia first, $25,000 to start. Mia is on the market brief. As each of you finishes, post what you made and what you'd flag.
A strict member runs its taught steps only when you pick it, then posts one result back to the room.
Strict members don't join in on every message. They answer only when you pick them: choose its chip above the message box, or name it with @, then send. The worker runs its taught steps with your message as its input and posts one result to the room. If a step is waiting for your approval, the room says which one and asks you to open the worker. @everyone reaches every flexible worker but never starts a strict one, and chats never answer. If nobody in the team would answer a message, the room tells you instead of sending it.
Practice. Teach a strict worker one repeatable check, add it with Members and Save members, then address it once by its chip and once with @, and read the result each time.
@Price check Run this week's check for the 12 launch products and flag any landed cost that rose more than 5%.
Add a chat to the team, pass its work in with Send to team, and give the team its own times.
A chat can sit in a team too. It never answers in the room, but its title menu gets Send to team, which opens a box with its last reply ready to edit and send. Add a chat with Add to team in its sidebar row's right-click menu, or after a task with Keep doing this, then Add to a team. The team runs on a schedule like a worker: the room's When it runs button holds up to 8 times, each saying what the team should do. With no @ names, every flexible worker answers. Name a strict member with @ to run it, and add @everyone if the flexible workers should answer too. Scheduled team runs make changes through connected accounts without asking, so connect only what the team needs.
Practice. Add one chat to your team and use Send to team to pass its result into the room. Then open When it runs in the room and add Mondays 9:00 with what the team should do.
When it runs, Add a time, Mondays 9:00. What should the team do? @everyone One line each on what changed for you this week. @Price check Run the weekly check.
Run a status round, steer one member, then ask the room to grade itself and list what is missing.
The company keeps working after you stop typing. A status round, "@everyone Where are we? One line each", shows the state in seconds. A steer, "@Sam change the button and republish", shows the model: you talk to a member, and it changes the work. Load earlier at the top of the room brings back older messages. The wrap is the most credible minute: each member grades its work against the checks it wrote first, and the room lists what is still missing before the store could take a paid order.
Practice. Run one status round in the room, steer one member, then ask the room to grade itself and list the gaps.
@everyone Grade what you built against the acceptance checks you wrote before you started, and give me one plain list of what's still missing before this store can take its first paid order.
Keep going
Make the learning stick
Open Oppermind beside the lesson, apply each step, and leave with something you can use.