A decision and its result are related, but they are not the same thing. A carefully considered business choice can encounter an unexpected event, while a poorly considered choice can benefit from luck. Poker offers a compact illustration of this distinction because a player acts without seeing all the available information.
The comparison has limits. A card game has agreed rules and a contained objective. Business decisions involve customers, colleagues and responsibilities beyond a single contest. Maritime operations also have safety requirements that cannot be treated as chips at a table. The useful connection is a way of asking questions about information and judgement.
Record what was known at the time
Imagine a manager choosing between two equipment suppliers. One offers a lower price but a less certain delivery date; the other costs more and provides clearer delivery arrangements. A later delay does not, on its own, explain whether the original choice was reasonable. The review needs the information available before the order was placed.
Write down the objective, the alternatives, important assumptions and the consequences of a delay. Identify which statements are supported by evidence and which are estimates. This makes a later review more useful than asking only whether the choice turned out well.
Separate a result from the reasoning behind it
In a poker hand, a player can make a considered choice and still lose when another card is revealed. Conversely, a weak choice can happen to produce a favourable result. Those observations are illustrations, not instructions to take more risks at work.
For readers unfamiliar with the game, the introduction to poker as a social card game explains the private cards, shared cards and sequence of play. Understanding that structure makes the analogy clearer without requiring money to be wagered.
Update a view when information changes
A supplier may report a production problem, a customer may revise a requirement or a previously assumed resource may become unavailable. A useful review asks whether the new information changes the options. Continuing with the original plan simply because time has already been spent on it can hide a change in circumstances.
One practical approach is to define review points before committing. Specify which event would prompt another discussion, who should be involved and what information is needed. The aim is to make revision a deliberate part of the process rather than a response to embarrassment about changing course.
Use a short decision review
- What was the objective, and which constraints were fixed?
- What information was available when the decision was made?
- Which alternatives were considered, and why were they rejected?
- What uncertainty remained, and what new information emerged?
- What should change in the next decision process?
These questions are a suggested discussion framework rather than a validated operational procedure. For actual work, use the organisation’s applicable processes, responsibilities and professional advice.
Keep the analogy in perspective
Bluffing at a card table is not a model for communicating with a crew or a customer. Transparent reporting, agreed responsibilities and truthful information have a different purpose in working relationships. The strongest lesson from this comparison is modest: review the process as well as the outcome, and be clear about what was uncertain.
The historical Topaz vision and mission provides archive context on service, leadership and organisational priorities. This article is a new editorial discussion and does not attribute poker-based practices to the former company.