More Project Post-Mortems Needed

The usual culprit -- "we just don't have time to do it" is the phrase heard all too often. As if you can run a project over schedule and budget by hundreds of thousands of dollars and weeks of labor but heck no! We don't have an afternoon to talk about what went wrong! We've got more late projects to be working on!
It's astounding. As a process teacher, most people tell me "we really don't have time to do a process" -- which always blows my mind. You're writing code now, aren't you? How is that happening? Magic? Certainly you have some kind of process in place, even if it is just "show up at work and start playing around"
I was once reviewing some java code for a startup company I was consulting with. I asked the programmer, "Why did you name this function this strange name. It doesn't make sense?"
He looked me straight in the eye, and in a serious tone said, "Well. I don't ever know what the function is going to do when I start writing it, so I'm not sure what to name it."
Yikes!
I think what people are saying to me is, "We don't have time to do extra process that is unnecessary."
Look. Nobody is saying do things that don't make sense to your project. Perhaps you are looking at it the wrong way: what are you forgetting that taking 15 minutes might help you remember?
Doing the wrong things, and just doing them harder, is what I see way too often. It reminds me of the lumberjack who was working everyday cutting trees. Finally one day he took the day off. When he came back to work the next day, he was cutting trees better than any other man at the camp. Soon he had caught up for the day he missed and shot far ahead of the group.
"What did you do?" the other lumberjacks asked, "did you go to town, see a movie, read a book? What is your secret to recharging your batteries?"
The lumberjack looked around and smiled.
"I sharpened my saw," he said.
So many times I see shops full of smart, hard-working people who are working day and night, never bothering to sharpen their saw.