Its true that "analysis paralysis" is a common plague historically, but in software engineering for example, modern Agile or iterative development paradigms address it.
Older traditional development paradigms often referred to as "waterfall" development have fallen out of favor these days in most any progressive development organization.
Waterfall development depended on thorough analysis of the problem up front to determine a plan for development. That approach fails as problems become too complex to assess completely and accurately up front, leading to either analysis paralysis ie doing nothing until the analysis is complete or heading down a poorly understood path doomed to fail.
Iterative development is more agile because you attempt to build something based on the key known requirements regularly, like once every few weeks and then stop and reassess so what was learned can be applied effectively to the next iterative phase of development.
So analysis paralysis can certainly still exist but is far less problematic as a whole these days than in years past.
Today's complex and fast moving world has no room for "analysis paralysis" in product development.
Older traditional development paradigms often referred to as "waterfall" development have fallen out of favor these days in most any progressive development organization.
Waterfall development depended on thorough analysis of the problem up front to determine a plan for development. That approach fails as problems become too complex to assess completely and accurately up front, leading to either analysis paralysis ie doing nothing until the analysis is complete or heading down a poorly understood path doomed to fail.
Iterative development is more agile because you attempt to build something based on the key known requirements regularly, like once every few weeks and then stop and reassess so what was learned can be applied effectively to the next iterative phase of development.
So analysis paralysis can certainly still exist but is far less problematic as a whole these days than in years past.
Today's complex and fast moving world has no room for "analysis paralysis" in product development.