Businesses should focus on creating repeatable, scalable systems for daily operations rather than fixating on lagging indicators like closed deals. By refining the process—how you qualify leads, run meetings, and follow up—you build predictability and rely on strong habits, not just individual 'heroes'.

It is a common human fallacy to blame the tool or technique when a first attempt fails. More often, the problem lies not with the method but with its execution. Before concluding a strategy 'doesn't work,' you must first re-evaluate your own steps, identify potential errors, and try again. This shift towards personal accountability is essential for genuine skill development.

The immediate question "What did I do wrong?" after a failure is flawed. It falsely assumes you control all outcomes and that a "right" process guarantees success. Start with the more neutral question, "What happened?" to separate analysis from premature self-blame.

A good outcome does not automatically validate the decision-making process, as luck plays a significant role. Howard Marks stresses the importance of intellectual humility in recognizing that a successful result could have stemmed from wrong reasons or randomness, a crucial distinction for repeatable success.

Rather than a vague aura, luck should be defined as a specific event with three criteria: 1) you didn't cause it, 2) it has a potentially significant consequence (good or bad), and 3) it was a surprise. This framework transforms luck from a passive concept into something you can analyze and respond to strategically.

Instead of fixating on lagging outcomes like final scores, leaders should identify and replicate "golden hours"—periods where inputs, behaviors, and strategies were working perfectly. This shifts focus from results to the controllable process that creates them.

Leaders often fail to separate outcome from process. A good result from a bad decision (like a risky bet paying off) reinforces poor judgment. Attributing success solely to skill and failure to bad luck prevents process improvement and leads to repeated errors over time.

Treat your goal as a hypothesis and your actions as inputs. If you don't get the desired outcome, you haven't failed; you've just gathered data showing those inputs were wrong. This shifts the focus from emotional failure to analytical problem-solving about what to change next.

This quote from quality guru Edwards Deming posits that undesirable results are a feature of a perfectly designed system, not a bug or human error. To improve outcomes, product leaders must analyze and redesign the underlying processes rather than blaming their teams.