Study room for Thesis Lab in Columbus

Where to anchor sessions

• Publish one shared room playbook so every host follows the same structure.
• Use concrete task definitions at kickoff to prevent passive attendance.
• Keep recap artifacts searchable so repeated confusion gets addressed quickly.

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 Columbus cohorts.

Host prompts that work

• Wrap prompt: What is the next committed block?
• Kickoff prompt: What concrete deliverable are you moving?
• Midpoint prompt: What remains unclear and how will you resolve it?

0-5 min: setup and intent

Open the room, silence distractions, and write one measurable goal for Thesis Lab work.

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.

Picking a room but no specific task

Start each block with one concrete outcome such as a section, set, or commit.

Leaving timer settings at default for every task

Adjust block length by workload: quick review for short tasks, longer blocks for deep work.

Switching rooms too often

Stay in one room for at least two cycles before changing format.

Ending sessions without a recap

Log one win and one next step so returning is frictionless.

Pre-commit window in Columbus

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

Transition window in Columbus

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

End-of-day closure in Columbus

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