Skip to main content

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of "Six Thinking Hats"
Cover of Six Thinking Hats

Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming, mischievously known as blame storming.

To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits.

Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be discussed here, Devil's advocate is someone who, given a certain argument, takes a position he or she does not necessarily agree with, just for the sake of argument to test the quality of the original argument and identify weaknesses in its structure, and to use such information to either improve or abandon the original, opposing position. So a devils advocate helps in testifying the strength of the opinion and justified to be relevant, which can be of importance in brain storming process, it may or may not create lateral arguments, or form synergies. 

Any thoughts during brain storming process can be presented it may be of relevance or not. Decisions cannot be made during this process. Obviously during discussions, participants ideas should be connected to the problem areas. Edward de bono's technique of six thinking hats for discussions in which each participants wears different hats of thought to think in different ways to the same problem with a different perspective with different roles for solution approaches helps a lot for a healthy brain storming session.
Enhanced by Zemanta

Comments

Popular posts from this blog

Porter's outside-in and Hammel - Prahald's Inside-out

Over the years inspiration and motivation to out do something which creates spark in the genre of concurrent times is always been challenge for all of us, to make things happen requires a plan, an out of the box solution to rationalize its existence. More often than not inspiration are unknown to us, which may leads to different scenarios of multiple ways of looking at things differently and indifferently also, anyways there are always n-1 degrees of freedom to think differently for n+1 different ways looking at things. Inspired by a spiral which is coincidentally a galaxy in our spatial system gives us views like --if one start from a point from outer end to reach at center, will reach from outside-in and if one starts from the center and circle outwards move than that will be inside-out thinking. So again its up to individuals, which way move. Traveling by we see stars and other objects binding each other with gravitational forces. Galaxy One of the many management stra

Frisking out project risk

Risk Management road sign (Photo credit: Wikipedia ) So what is a risk ? First understands and identify a risk is most important part of risk management.A risk is a probability of uncertainty associated with executing certain item/task/process/work etc.  A risk generates out as soon as we initiates a task. A critical resource in terms of skill set, in a team is a potential  risk of leaving the project in between because of unavoidable reasons. So a risk is inevitable, only thing we can do is ; manage and mitigate. Just like handling/catching error in software program . Always plan for the element of risk in project from the start and reiterate control over it for any contingencies. Steps to assess risk: Identify---------->Analyze--------------> Set priority to each risk Steps to control risk: Mitigate------------>Plan for contingency----------> Quantify it and Set a control process Design a Solution process at the team level: Taking help of the experts inv