All 2 entries tagged Rdm
March 20, 2015
It has to take some time for me to have all emotions reduced so to switch my mind from system 1 to system 2 to make any valuable comments about presentation performance. For now I would like to analyse the working process, which have been happening during last working week.
It was a great idea to use several tools to underpin the decision making process such as SWOT, Decision Tree, Grid Analisys, & AHP. That made our team's results more weightened on one hand and gave a great opportunity to understand how they work, why they are used, and what are actual strngths and limitaions in comparing them.
Another thing that I got from the working process is that team shouldn't be just a sum of strong individuals, who make allocated tasks and then combine them into overall result. It has to be something more (that is why there are so many researches on corporate group responsibility in contemporary world as it is an important aspect in creating succsessful & profitable outcomes of an organsation).
Moreover, during most of modules we were taught that process of getting results is equally or sometimes is even more important comparing to results themselves. I can disagree with it now. Our team had a great process flow: wonderful understanding of goals, great team spirit, and proper task allocation. Unfortunatelly the outcome of this process was almost poorest I've had in the whole course. When such situations happen (outcomes don't show the process behind them) there are only two options (that's totally my subjective opinion):
- to take everithing uner control personally (without 100% relying on anyone else)
- make much less or no extra efforts (i mean working with passion) in further projects: only strictly do the required minimum of the task)
To conclude I would like to say that it was a great experince that showed that I still need to learn a lot about to not fall in such traps in future carrier.
March 13, 2015
Before the beggining of RDM module I had a clear engeneering understanding of what acually robustnes is in technical systems: it is an ability of system to save the given inventory of stability in case of variations of its parameters caused by change of loading the object by internal or external environment. By usining Nyquist criterion it was easy to come up with a decision about wheather the system is robust or not.
This module showed that it is impossible to use such type of approach for robust desicion making in business systems, where much more factors have to be considered (especially human factor). During monday session I totally understood how bias is human factor and to what extent it can influence to the whole system to be robust or not. I is also interesting to mention that human factor can be devided into several parts like individual bias, group thinking bias and company level bias. All of them can strongly influence on the level of system (decision making) robustness.
To avoid that people designed some methodologies that can help businesses in making such kind of decisions according to particular consitions. Still there is a problem of understanding WHAT ACTUALLY THE CONDITIONS ARE. Gathering appropriate for the conditions information and getting rid of inrellevant is a tough process (need also to be robust).
So what I really understood, the there is only one tool that works in such type of systems - EXPERIENCE. Going thruogh decision making time after time can teach us how to reach the extent of making robust decisions.