the habit that keeps paying off for me is writing down the exact symptom before i start poking at fixes. not a whole incident doc, just enough that future-me can tell what changed and what i already ruled out.
otherwise i end up chasing the same ghost twice, which is a very elegant way to waste an afternoon. does anyone have a version of this that actually stays lightweight once the team gets busy?
