Paralysis by Analysis

The term "Paralysis by Analysis" though popular in the soft ware companies, was not heard more earlier because ENGLISH people dont get traped into it ususaly (in my perception). But in India, its usual . . . Probably thats the reason thousands of years ago they had delacred even the outcome of this phenomenon - दीर्घ सूत्री विनश्यन्ती - Those who plan long . . . will meet destruction! Relatively english outcome very mild - only paralysis!

Analysis paralysis" or "paralysis of analysis" refers to over-analyzing (or over-thinking) a situation, so that a decision or action is never taken, in effect paralyzing the outcome. A decision can be treated as over-complicated, with too many detailed options, so that a choice is never made, rather than try something and change if a major problem arises. A person might be seeking the optimal or "perfect" solution upfront, and fear making any decision which could lead to erroneous results, when on the way to a better solution.

The phrase describes a situation where the opportunity cost of decision analysis exceeds the benefits that could be gained by enacting some decision, or an informal or non- deterministic situation where the sheer quantity of analysis overwhelms the decision-making process itself, thus preventing a decision. This is often phrased as paralysis by analysis, in contrast to extinct by instinct (making a fatal decision based on hasty judgment or a gut-reaction).

Software development
In software development, analysis paralysis typically manifests itself through exceedingly long phases of project planning, requirements gathering, program design and data modeling, with little or no extra value created by those steps. When extended over too long a timeframe, such processes tend to emphasize the organizational (i.e., bureaucratic) aspect of the software project, while detracting from its functional (value-creating) portion.
Analysis paralysis often occurs due to the lack of experience on the part of business systems analysts, project managers or software developers, as well as a rigid and formal organizational culture.
Analysis paralysis is an example of an anti-pattern. Agile software development methodologies explicitly seek to prevent analysis paralysis by promoting an iterative work cycle that emphasizes working products over product specifications.


Analysis paralysis can be used to describe the way that information affects workplace productivity. An overload of physical mail, email, internet websites, voicemails, instant messaging, telephone and cellphone calls, memos, faxes, and interpersonal communication can make it difficult or impossible for employees to make decisions.


In India, its our culture. And we are proud of it!