Most engineering teams don't fail because they lack process. They fail because they mistake process for progress.
Sam Altman said:
"Outcomes are what count; don’t let good process excuse bad results."
This quote really stuck with me. It's easy to agree with, but so hard to implement and live by day-to-day.
When launches miss their mark or velocity stalls, the temptation is to defend the process. We followed the checklist. We held the right meetings. However, outcomes don’t care how diligently you followed the script. Customers only experience the result.
The danger is when process becomes a shield. Teams stop asking the uncomfortable questions. Did we ship the right thing? Did we learn fast enough? Would we choose the same path again if we started today? Instead, they settle into doing the wrong thing more efficiently, which is...not good.
I'm not saying process doesn’t matter. It absolutely does. It creates structure, reduces chaos, and gives people a rhythm to follow. But process is a tool, not the point. If your outcomes aren’t getting better, then the process isn’t working.
Don’t treat process as sacred. Treat learning as sacred. I care less about whether a sprint felt smooth, and more about whether my team uncovered something new, delivered something useful, or got closer to solving the real problem.
Have a process. Just don’t mistake it for progress.