Study together for Georgia Tech in Tampa

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

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

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

Define the exact output for Georgia Tech 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 Tampa

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

Midday reset in Tampa

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

Evening wrap in Tampa

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