Study together for Deep Work in Baltimore

Where to anchor sessions

• Anchor around clear norms that work across mixed learner backgrounds.
• Publish one shared room playbook so every host follows the same structure.
• Use concrete task definitions at kickoff to prevent passive attendance.

Scheduling reality

• Pre-day block (7:00-8:30 local): commit one measurable output before the day ramps up.
• Mid-cycle block (12:00-2:00 local): reset focus and close one high-friction task.
• Wrap block (6:30-9:00 local): close loops, capture wins, and set tomorrow's first action.

Host prompts that work

• Midpoint prompt: Are room norms still being followed?
• Wrap prompt: What is the next committed block?
• Kickoff prompt: What concrete deliverable are you moving?

0-5 min: setup and intent

Open the room, silence distractions, and write one measurable goal for Deep Work collaboration.

5-30 min: first focus sprint

Run a shared timer and stay in one task only. Keep chat for blockers, not multitasking.

30-35 min: reset

Take a short break, hydrate, and log progress so your cohort can keep context.

35-60 min: second sprint and recap

Finish one concrete deliverable, share a quick recap, and queue the next block.

Launching without explicit collaboration norms

Set one-line norms at kickoff: task clarity, camera optional, recap required.

Letting check-ins turn into long status chatter

Keep check-ins to one blocker and one next move per person.

Using one pace for mixed workloads

Allow parallel sprint goals, but synchronize break and recap timestamps.

Ending without shared accountability

Close with each member posting one shipped output and next start task.

Pre-commit window in Baltimore

Start with a 20-25 minute block on one measurable outcome before meetings or classes.

Transition window in Baltimore

Use mid-day transitions for one short accountability sprint instead of fragmented multitasking.

End-of-day closure in Baltimore

Reserve one block for cleanup, recap, and tomorrow's priority setup.