Study together for Writing Club in Detroit

Where to anchor sessions

• Use short accountability loops with explicit next-session commitments.
• Anchor around clear norms that work across mixed learner backgrounds.
• Publish one shared room playbook so every host follows the same structure.

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

• Wrap prompt: What proof of progress can you share now?
• Kickoff prompt: One task, one timer, one done definition.
• Midpoint prompt: Are room norms still being followed?

0-6 min: intent and baseline

Set one measurable target for Writing Club collaboration and estimate what completion looks like.

6-26 min: first execution block

Run a short focused cycle to build momentum and surface uncertainty early.

26-30 min: quick checkpoint

Update progress, trim scope if needed, and queue the most valuable next move.

30-60 min: longer consolidation block

Use the second block to finish priority work and leave clean handoff notes for your next session.

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.

Before class/work in Detroit

Use a 25-minute prep sprint for flashcards or one problem set before your day starts.

Midday reset in Detroit

Run a short 20-25 minute block to clear one high-friction task and protect momentum.

Evening wrap in Detroit

Use a 30-35 minute block to close open loops and set tomorrow's first task.