The best decisions I made and the ones I would change are usually closer together than people think. A decision can be right in direction and still cost more than it needed to. A mistake can hurt and still buy a lesson that later saves the company.
The through-line is Systems & Soul: useful architecture, human judgment, and a standard that can be tested after the applause is gone. That is why this essay sits beside Hands Up and the operating arguments I keep making in public.
Definition
A good decision is not one that feels good in the moment. It is one that compounds toward the company you are trying to build. Sometimes that means betting early. Sometimes it means cutting what you love. Sometimes it means admitting the model that got you here cannot take you there.
I define it this directly because vague language is where leaders hide from decisions. If a concept cannot change a calendar, a budget, a hiring conversation, or a customer experience, it is probably not a strategy yet.
When this matters
This matters when entrepreneurs turn their own history into either a trophy case or a courtroom. Neither helps. The better use of history is pattern recognition. What did I see early? Where did I wait too long? Which instincts were wisdom, and which were fear dressed as prudence?
The point of reviewing decisions is not to prove you were right. It is to become harder to fool next time.
Failure mode
The failure is protecting the story. If I only tell the decisions that make me look smart, I rob the next owner of the useful part. If I only rehearse regret, I miss the proof that conviction matters. Both are ego in different outfits.
The pattern is almost always the same: leaders protect the familiar story longer than the facts justify. They wait for certainty, outsource judgment, or use a new tool to preserve an old behavior. That is how companies end up busy, expensive, and still behind.
Proof
The best decisions include betting on the trades, investing early in digital, rebuilding around AI, writing Hands Up, and choosing legacy over ego. The ones I would change live in the delays: waiting too long on certain people, tolerating theater, and underestimating the cost of unclear systems.
My proof standard is not perfection. It is receipts. What did we build? What did we learn? What broke? What changed in the room, the team, the customer experience, or the scoreboard after the idea met reality?
Action
Make a decision ledger for your own company. Not just wins and losses. Capture what you knew, what you ignored, what it cost, and what you would do next time. Then read Twenty Years of Entrepreneurship for the broader pattern.
And do not make this philosophical if the next move is practical. Write the question down. Assign an owner. Put a date next to the bet. Then compare what happened to what you believed would happen. That is how a business gets wiser instead of just older.