In the book Antifragile: Things that Gain from Disorder, Nassim Nicholas Taleb shared insights on optionality that can be expanded to include new product development environments.
This post provides an introduction to the non-linear gains associated with antifragile systems that may be realized by designing new product development environments that help individuals improve their capability to synthesize many new options continuously and enhance their proficiency to exercise options that are attractive. This post includes a comparison to concepts represented in Boyd’s OODA Loop sketch.
Fragile, Robust, Resilient, and Antifragile Development Environments
Taleb’s classification of systems as fragile, robust, resilient, and antifragile may be used to characterize development environments. Every development environment can be characterized in terms of its fragility, robustness, resilience, and antifragility.
Antifragile: Things that Gain From Disorder by Nassim Nicholas Taleb
A development environment that tends to be fragile does not welcome disorder. When uncertainty is injected, the results may be unpleasant.
In a fragile development environment, one obstacle can prevent the realization of value. Examples of harmful conditions include:
Incorrect, incomplete, or misleading information
A problematic handoff between functional groups
Disagreements among functional groups
Unpleasant results may include delays, cost overruns, and insufficient adoption of the product. Individuals tend to be frustrated. The more fragile the development environment, the less likely it is to thrive.
From project-to-project, a robust development environment tends to survive unchanged. Processes tend to be preserved. Individual contributors tend to retain their employment status.
From project-to-project, a resilient development environment survives changes from external factors. After a project is complete, there may be changes such as a re-arrangement of the organizational chart. New tools may be incorporated. The organization survives to serve the needs of the next project.
The word ‘antifragile’ is an adjective created by Taleb. It can be defined as the exact opposite of fragile. According to Taleb, “Antifragile is beyond resilience or robustness.”
An antifragile system thrives and grows when exposed to a moderate amount of volatility, randomness, disorder, and stressors. An antifragile system benefits from a moderate amount of adventure, risk, and uncertainty.
Iatrogenesis
In Chapter 7, Taleb described the concept of iatrogenics as “damage from treatment in excess of the benefits.”
Iatrogenesis: preventable harm resulting from the treatment or advice of a healer.
The word iatrogenesis is not common in product development but harmful inputs may come from multiple sources. These include:
Specialists that assume that solutions to development problems relate to their area of expertise.
Innovation pundits, consultants, and vendors that offer their favorite tools and techniques as solutions
Interventionalists that believe that their contributions will improve outcomes
Status quo
It may be difficult to recognize the harmfulness associated with specific sources because of cognitive biases or unvalidated claims. Recognizing harmfulness is more difficult in development environments that isolate individuals of different functional specialties.
New product development efforts can suffer from iatrogenesis. Approaches to recognize potentially harmful inputs and reduce potential damage from harmful inputs include:
Requisite Variety
Disintermediation
Pair Development
Requisite Variety
The concept of requisite variety can be used to emphasize the importance of having a diversity of potential responses in a development environment.
Requisite Variety: For a system to be viable, only a variety in responses can force down the variety due to disturbances.
The Law of Requisite Variety was formulated by W. Ross Ashb[...]