What does it mean that post-decision review?

After a decision plays out review whether your framework served you well.

Example: You chose to hire a contractor instead of a full-time employee. Six months later the project is over budget and behind schedule. Your instinct says 'bad decision.' But when you review your decision journal, you find that the information you had at the time — budget constraints, uncertain scope, a three-month timeline — made the contractor choice reasonable. The outcome was bad. The decision process was sound. The real lesson is that your scope estimation model needs work, not that you should never hire contractors.

Try this: Pick one significant decision you made in the last 90 days where you now know the outcome. Write down: (1) what you decided and why, (2) what actually happened, (3) whether the outcome was due to your process or to factors you could not have known. Separate the verdict on your process from the verdict on the result. If the process was good but the outcome was bad, identify what new information would have changed your thinking — and add it to your decision framework for next time.