The moment you ship, your hypothesis becomes an asset you can lose

An essay published on dev.to argues that founders become harder to move after they build than before they build, and that the driver is ownership rather than ego ^[1][5]. That relocates the problem for anyone running a team: if what keeps a dead product alive is a bias about current states, it is a governance question, not a character question. The setup is familiar. Starting a company reads as an act of openness to change: leaving the predictable job, choosing uncertainty over stability, building something that does not exist yet ^[2]. Months later, the essay notes, the same person can resist changing the product, switching markets, abandoning a business model, or admitting the original idea does not work ^[3]. The mechanism it proposes is simple. A startup begins as a hypothesis, and once you build it, it becomes something you can lose ^[5]. Before you build, there is no status quo; after six months of work, there is ^[6]. The essay grounds this in Samuelson and Zeckhauser's 1988 work on status quo bias, in which people were disproportionately likely to keep an option when it was presented as the existing state ^[7]. Then the worked example: pick idea A over idea B, spend eight months building it, hire people, raise money around it, acquire users, tell investors the market is enormous, and then watch evidence start favouring B ^[8]. The question that should be asked is which path has the highest expected future value given everything known today ^[9]. The question actually being asked is keep what I have versus give up what I have for something uncertain ^[10]. Two further mechanisms are stacked on top. Prospect theory (Kahneman and Tversky, 1979) showed people evaluate outcomes against reference points, and that losses relative to those points can carry different psychological weight from gains ^[11]. The essay declines the usual shortcut here, calling the claim that losses always hurt twice as much too simplistic to treat as a universal rule ^[12], which is more restraint than this genre normally shows. The endowment effect experiments (Kahneman, Knetsch and Thaler, 1990) found that people given objects such as mugs tended to demand more to give them up than others would pay to acquire them ^[13]. And Barry Staw's research on escalation of commitment (1976, 1981) showed people continuing to commit resources after negative feedback, particularly when they felt responsible for the original decision ^[14]. Four named mechanisms, all pointing the same way ^[17]. The operationally dangerous part is the identity shift. The founder becomes responsible for defending the idea to employees, investors and themselves, and the question drifts from "Is this working?" to "Was I right?" ^[15]. That drift is visible in artefacts: which metrics get to the board deck, which roles get hired, which experiments quietly stop being run. The counter-example offered is Instagram, which began as Burbn, a broader mobile app built around location check-ins, plans and social features; its founders saw users concentrating on photo sharing and rebuilt around that behaviour ^[18][19]. The essay's point is that the hard part was accepting that user behaviour was more informative than the original thesis ^[20], and its best line is that the code may be reusable but your certainty is not ^[21]. Two cautions. This is a synthesis of decades-old laboratory findings ^{[7][11][13][14]} plus one much-retold case ^[18], not new evidence, and the material supplied here breaks off mid-sentence on sunk cost ^[22]. Also worth noting: the build horizons in the essay's own illustrations are six, eight and nine months ^[23], so the asset frame forms well inside the first year. What to watch inside your own company: whether kill criteria were written before the build, and who is permitted to declare the thing dead. If that authority sits only with the person who authored the hypothesis, the loss frame is baked into the org chart.