# Reopen the problem when the first assumption dies

- Category: mindset
- Author: Titus Nicolae (https://indie.md/people/titus-nicolae/)
- Source: https://indie.md/journeys/titus-hausjam/
- Canonical URL: https://indie.md/advice/reopen-the-problem-when-the-assumption-dies/

Titus's working habit, carried from Intel, Ring, and Smilecloud into HausJam, is to treat a broken output as evidence that the problem was mis-stated, not as a request for a prettier model. If the floor is wrong, the task is no longer "place the sofa," it is "why did we believe this plane was the floor?" That sounds philosophical and is in fact operational: it stops a team from spending a month fine-tuning their way around a bad prior. The general rule for anyone shipping vision or geometry is to keep the original problem statement on a short leash. When the demo lies, rewrite the job, add the measurement you skipped, or change the input, two photos instead of one, before you buy another training run. Stubbornness belongs to the user outcome, not to last week's framing.