Incident File for Commute Sunk Cost
Someone stays later than needed at the office because leaving shortly after a long commute makes the trip feel inefficient.
Incident date: July 13, 2023. Classification: recurring.
The commute took fifty-three minutes. This is within normal range for a Tuesday office day. The work completed before lunch totaled approximately three hours of meaningful output. An opportunity to leave at 4:15 was identified.
The opportunity was not taken.
The rationale, reconstructed: leaving at 4:15 would mean fifty-three minutes of travel for six hours and fifteen minutes of office time. This ratio felt insufficient. The commute had cost something. The office day needed to earn it back.
Commute Sunk Cost adds one coordination step to the day. The step is staying. Staying is not a plan. It is the avoidance of a calculation that produces an uncomfortable answer.
Coworkers start planning around that step because the subject is present at 5:30 and available for conversations that would not otherwise occur on this day. The conversations are not the reason the subject stayed. They become the evidence the subject offers for why staying was correct.
The day is called flexible while requiring extra location planning to feel worth it. The flexibility promised by hybrid work is real, in the sense that there is no rule against leaving at 4:15. The flexibility is constrained by the commute, which is not a rule but has equivalent force.
Under the governing rule, commute sunk cost becomes procedure once repetition feels safer than reconsidering it. The subject has not reconsidered. The subject has instead optimized the 5:30 departure by stopping at a grocery on the way to the station.
Flexibility hardens into an unwritten schedule, and the commute is the mechanism by which it does.
Incident classification: no action required. Recurring status retained.