Timebox Rabbit Holes Before They Eat the Week. A Build Next Stack field guide for learners shipping small projects.
Define rabbit hole versus research
Research answers a question blocking this week’s artifact. Rabbit holes answer interesting questions that feel urgent because Twitter argued about them. Research has a ticket; rabbit holes have momentum.
Write the distinction on a sticky:
- Research: Which auth provider fits single-user MVP by Thursday?
- Rabbit hole: How does every OAuth provider compare on edge-case PKCE flows?
Both involve reading. Only one serves the finish line. Mislabeled holes steal weeks because they produce notes that look like work.
Elena tracked a week where OAuth comparison notes ballooned to six pages while invoice CSV import sat unmerged. Relabeling the OAuth block as a hole—not research—let her cap it without guilt and ship import Friday.
The ninety-minute exploration cap
Allow rabbit holes—they spark skill—but cap at ninety minutes per hole per week. Timer visible, phone in another room. When timer fires, write a return ticket and stop mid-paragraph if needed.
Ninety minutes is enough to learn whether a hole deserves promotion to research. Less time breeds FOMO continuation; more time breeds accidental thesis writing.
Track holes in a list: date, topic, minutes spent. If weekly total exceeds three hours, you are hole-hopping, not building.
Elena sets phone alarm labeled Return at cap end—label matters more than sound; generic timers get snoozed as five more minutes until midnight.
Write a return ticket before diving
Before the timer starts, fill three lines:
- Return to: file name or task—invoice import PR
- Stop signal: timer or first working minimal example, whichever first
- Capture: one note titled PKCE skims with link list
Return tickets prevent the classic Monday discovery that you never returned to the branch. Paste the ticket in the editor or terminal tab you will reopen—visual breadcrumb beats memory.
Elena writes return tickets on sticky notes stuck to her laptop bezel—physical notes survive alt-tab storms better than another digital tab.
Calendar color for deep dives
Mark exploration blocks in a distinct calendar color—orange or purple, not default blue meeting color. Color trains others and yourself: this block is optional curiosity with a cap, not movable focus time.
Schedule holes after primary build blocks, not before. Morning belongs to artifact motion; afternoon holes reward progress instead of replacing it.
If holes regularly spill from calendar into evenings, caps are too generous or return tickets are missing—fix process before blaming discipline.
Evening holes often follow guilt from skipped morning Build blocks—protect morning ship time first; holes are reward, not substitute.
When to promote a hole to a project
Promote when the hole repeats three weeks, connects directly to next month’s artifact, and has a demo spec one paragraph long. Promotion means a branch, a finish date, and removal from hole list—not unlimited reading.
Demote when the hole produced notes but no code twice—archive notes, delete bookmarks, accept sunk curiosity. Demotion is success; it protects shipping.
Not every fascinating topic deserves a repo. Most deserve ninety minutes and a graceful exit.
Promotion checklist: repeating timer sessions, link to failing build or test, demo spec under one hundred words, finish date within two weeks. Missing any item keeps the topic in Explore column.
Friday audit of unclosed holes
During learning review, list open holes—explorations without return tickets or with tickets never executed. For each: close with capture note, schedule one more capped session, or promote. Unclosed holes older than fourteen days default to archive unless promoted.
Audit prevents tab graveyards from becoming guilt shrines. Closed holes with notes still contribute—they inform future decisions without owning the calendar.
Elena posts weekly hole minutes next to shipped PR count in learning review. When hole minutes exceed ship count, next week gets stricter caps—not shame, adjustment.
Hole list versus task list on one page
Keep two columns in a single note—Build and Explore. Build items have branch names; Explore items have timers. Never mix them in one bullet list; mixed lists let holes masquerade as tasks because they share checkboxes.
At day start, pick one Build item before any Explore timer may start. Morning Build protects afternoon curiosity from eating prerequisites.
When Explore produces a actionable fix, move the line to Build with a concrete next step within five minutes—do not let Explore notes absorb implementation.
Review the column split each Friday. If Explore column has more lines than Build, the week already tilted—schedule extra Build blocks before new holes.
Elena once promoted a hole—custom lint rules—to a two-day project after three capped sessions proved lint was blocking merges daily. Promotion with a demo spec beat endless reading.
She also banned just reading docs as an Explore line unless it links to a failing test in Build column—docs without a failing test are usually holes wearing a work costume.
Cap total Explore list length at five open items—longer lists mean you are collecting topics, not timeboxing them.
Set one exploration timer tomorrow
Pick the curiosity nagging you today. Write a return ticket. Set ninety minutes tomorrow afternoon after a build block. When the timer ends, stop and open the return file—even if the blog post mid-scroll promised the answer in the next section.
Rabbit holes fuel builders; unchecked holes feed them. Timeboxes keep the fuel useful.
Draw the Build and Explore columns on paper tonight if digital lists keep merging. Physical separation trains the habit faster for some solo builders.
Log total Explore minutes in Friday review next to shipped work. Visible ratios beat willpower lectures when holes feel justified in the moment.
When a hole produces only bookmarks, delete the bookmarks after capture note—otherwise you re-enter the hole next week through saved tabs without the timer’s guardrails.
Protect the first morning Build hour like a meeting with your future self—holes scheduled after lunch rarely steal the week when that hour ships something real.
Name your timer alarms after the return file—back to import PR beats generic clock sounds your brain learns to ignore.