To make a decision you typically need to implement an analytic process based on facts to see clearly the problem and individuate the most rational and close solution to what you identify as needed.
Even if it looks quite complicated, it is a process that each of us do every day, every time we make a decision. It is rather different from an instinctive reaction that is when we react to external factors immediately and without involving any thinking process. Instinctive reactions are important to help us to make immediate decisions in situations that can put as in danger, but in all other cases we should be able to use our brain.
“Decision Maker” is one of the most requested skills for great responsibility roles, and it is clearly not just about making decision, but about doing the good ones.
Most of us do not realize that we make hundred of decisions every day; we go by metro? We just decided to not take the car. We eat in a restaurant? We just decided to don’t go home for cooking…
Indeed what is the difference between a good and a bad decision maker?
In my career it took me some time to understand and be convinced of the importance of doing analysis. I still remember my first job experience, I just wanted to quickly write some code and refactor it n-times to get better results. Did not you?
Things are different today and I am writing this post to share with you my personal approach to analysis. It is not something new, it is just my tailored method based on experience and well known methodologies.
In general you get as input a problem domain (the observed system with all the entities and rules involved) and must produce as output a solution domain (the designed system that solve the original analysis problem). So a good start is to:
- Get a clear view of the problematic to solve,
- Reduce the problem domain to a minimum knowledge space