If you have people, start there
Add everyone to the team or plan first if that is the list you trust. You can assign them later, split responsibilities later, and add shared people only once plans overlap.
Principle
Start with what you have.
Weeks is optimized to pull you into planning mode. You do not have to model the whole operation before the work becomes useful. Start with the information that is already clear, then let the plan grow from there.
If you have work, start there
Lay out the jobs first when the work is already known. Slots, times, quantities, and people can follow after the shape of the work is visible.
Ways in
Pick the interaction that matches your starting point.
Plan
Start with the structure
Create a plan when you already know the structure you want to work inside: one department, one quarter, one event, one venue area, one sprint, or any other planning boundary people recognize.
Slots
Start with the containers
Add slots first when the schedule is the clearest part: often one slot is one day, but it can also be a shift, location, stage, room, route stop, or any other unit where jobs and people meet.
Jobs
Start with the work
Add jobs inline when you are thinking in tasks: check-in, setup, inspection, handoff, greeting, driving, packing, cleanup.
People
Start with names
Add people first when the roster is the known thing. A person does not need an assignment before they can become part of the plan.
Next captures
Interactions this principle still needs.
The gallery should show more starting points than the default plan-to-slot path.
Team-first setup
Record adding several known team members before any plan exists, then show one of them flowing into planning later.
Job-first planning
Record laying out a list of jobs before slots are complete, then assigning those jobs into slots once the timeline is clearer.
Slot date helpers
Record the slot helpers as separate interactions: creating slots on subsequent days, and turning day names into concrete dates.