Study together for Research Sprint in Milan

Where to anchor sessions

• Use concrete task definitions at kickoff to prevent passive attendance.
• Keep recap artifacts searchable so repeated confusion gets addressed quickly.
• Use short accountability loops with explicit next-session commitments.

Scheduling reality

• Morning block (7:30-9:00 CET/CEST): best slot for cognitively heavy work.
• Transition block (1:00-2:30 CET/CEST): short execution cycle between commitments.
• Night block (8:00-10:00 CET/CEST): consolidation + recap for next-session readiness.

Host prompts that work

• Kickoff prompt: What concrete deliverable are you moving?
• Midpoint prompt: What remains unclear and how will you resolve it?
• Wrap prompt: What proof of progress can you share now?

0-6 min: intent and baseline

Set one measurable target for Research Sprint 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 Milan

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

Midday reset in Milan

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

Evening wrap in Milan

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