Study together for Deep Work in Lima

Where to anchor sessions

• Keep recap artifacts searchable so repeated confusion gets addressed quickly.
• Use short accountability loops with explicit next-session commitments.
• Anchor around clear norms that work across mixed learner backgrounds.

Scheduling reality

• Early block (7:00-8:30 local): high-value deep work before schedule fragmentation.
• Midday block (12:00-1:30 local): recovery sprint for stalled tasks and review loops.
• Evening block (7:00-9:30 local): strongest overlap window for recurring Lima cohorts.

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-8 min: setup and friction removal

Define the exact output for Deep Work collaboration and remove one likely distraction before the timer starts.

8-33 min: deep sprint

Commit to one high-friction task. Capture blockers in one line instead of context switching.

33-40 min: reset and diagnose

Take a short break, review what slowed you down, and adjust the next block for your local timing.

40-60 min: finish and recap

Ship one concrete output and write the first action 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 Lima

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

Midday reset in Lima

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

Evening wrap in Lima

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