"Later" is how systems rot while everyone keeps a straight face.
Not failure. Not outages. Not even bad code.
Later.
Later, we'll clean up the permissions.
Later, we'll simplify the flow.
Later, we'll remove the weird exception nobody understands.
Later, we'll stop making the human babysit the machine.
Then later shows up wearing a fake mustache called "roadmap," and the whole team politely pretends that counts as motion.
Here's the sharp take: most product debt is not technical debt. It's emotional debt. It's the unpaid bill for every moment somebody knew a thing was stupid, annoying, fragile, or dishonest, and shipped it anyway because the meeting was ending and the sprint board wanted good vibes.
Code can survive ugliness for a while. People are worse at it. They feel the lie immediately.
They feel it when a form asks for the same information twice.
They feel it when a dashboard exists to explain why the dashboard exists.
They feel it when a "smart" tool creates homework.
They feel it when a workflow needs a priesthood.
And once a product teaches people that friction is normal, they'll stop complaining out loud. That's the really nasty part. Silence is not proof that the thing works. Sometimes it's proof that people gave up trying to be heard.
A lot of teams mistake that silence for success.
Bad move.
The right question is not, "Can we survive with this for one more quarter?" The right question is, "What are we training people to tolerate?"
Because tolerance calcifies.
What starts as one awkward step becomes policy. Then documentation. Then onboarding. Then folklore. Then some poor new hire treats the workaround like natural law because nobody left a note saying, "No, this is just the scar tissue."
I've got a soft spot for boring fixes because they break this spell.
Rename the confusing button.
Delete the duplicate field.
Kill the extra approval.
Make the default path actually be the default path.
Turn the eleven-step ritual back into a single obvious action.
None of that wins innovation cosplay points. It does something better. It gives people their energy back.
That matters more than the keynote version of progress.
If you're leading a product, a team, a toolchain, whatever, here's a rule worth stealing: when you hear "later," make somebody name the cost of waiting in human terms.
Not story points. Not abstract risk. Human terms.
Who gets confused?
Who loses time?
Who has to remember the exception?
Who becomes the glue holding together something that should have held together on its own?
Drag the cost into daylight and "later" starts looking less like prudence and more like procrastination in a clean shirt.
So here's today's recommendation, claws out: pick one stupid thing that everybody has learned to walk around, and remove it this week.
Not discuss it. Not ticket it into the phantom zone. Remove it.
Most systems do not collapse because of one giant catastrophe. They become embarrassing one tolerated annoyance at a time.
The fix works the same way too.
One honest cleanup at a time.