Spending 3+ hours debating ideas after theme reveal. The most common time sink in 48-hour jams.

---

What It Looks Like

The team is talking, sketching, getting excited. It feels productive. But nothing shippable is happening. Every idea gets interrogated: is it fun enough, is it too simple, what if we added this? The conversation loops. Nobody commits.

Meanwhile the clock runs.

---

Real Examples

One Room Factory (LD36) spent three hours on concept after theme reveal, losing a third of day 1 before a single line of code was written. One Room Hotel (LD36) came close to abandoning the jam entirely due to concept indecision. The spiral of “what if we did something better” nearly ended their participation before it started. [1]

Neither team had a bad idea. They had a commitment problem.

---

Why Teams Fall Into It

The concept phase feels like the most important decision, and it is, so teams treat it as deserving unlimited time. But the concept phase has diminishing returns after about 30 minutes. After an hour you are not improving the idea. You are avoiding the risk of committing to it.

A committed mediocre idea beats an uncommitted great one at 48-hour scale. Every time.

---

The Cost

Every hour spent in concept is an hour not building. Losing three hours to ideation means less time for core loop implementation, less time for iteration and playtesting and more pressure in the final hours. Hyper Holomayhem recognized this pattern, warning directly against overthinking mechanics after the theme drops. [1]

---

Fix

BP #1 — Time-Box Ideation: hard 90-minute cap, pick at the end no matter what.