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

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.

Comments

Usecase Scenario development and User Stories

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this: Typical Software Development Life-cycle explained Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development. "A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives. " Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a s...

Games People Play in context to Projects

Games People Play in context to Projects: Contextually life and projects full of games, work on dynamics of human relationships by Dr. Eric Berne guides us not only in many social but relationship situations in corporate world also. In Todays concurrent world where we are living in a global village with Orkut, Facebook, Linkedin, Twitter and other social media leads to discounts of information in social network, where more of transactional games played knowingly(conscious) or unknowingly(unconscious). Precede to this let us understand game, A game full of transactions played with different roles by players changing their roles for a outcome in different ego states like Parent, Adult and Child ego states that will payoff. Continuing with Payoff, specifically in context to Project teams where transactions happen at concrete or transformational levels where people not necessarily behaving rationally and motivat...

Understanding Business Value of IT(Information Technology)

Is IT driven by business? I believe its a good question to be asked at this point in time after the doom of financial markets allover world. When top investment banks collapsed in USA and Europe everybody is asking a question how it is possible if the system in place. IT in general supposed to be driven by business requirements so its natural process that, as other component in business, this is also adding value to business, but is that benefits realized to business? Is IT a hype from time and again? Business value of IT measured in different metrics and methodologies that may or may not give true picture of IT value to business, so the contradiction lies in the hypothesis itself that IT is driven by business which is adding no value but continuing. In the concurrent world where businesses are competing for survival and existence IT is invaluable from intangible perspective. Making sense of PM triangle The infamous scope, cost and schedule trio can be realized for IT bus...

Project Portfolio-Program Management

Search This Blog