top of page
Writer's pictureFellow Traveler

Agility shares an Expected Utility Problem. Here's a Solution.

Updated: Oct 13

Starting from the early 2000s, agile practices have transformed the face of software development and project management. Frameworks like Scrum, Kanban, SAFe, LeSS, Nexus, (1) promise flexibility, enabling teams to collaborate effectively and operate successfully in a changing market. Yet as we probe deeper into these methods, within them emerges a problem rooted in the same flawed assumption leading to paradoxes in rational economic expected utility theory: rational choice.



Expected Utility Theory is a way of thinking about how people make choices when they don’t know for sure what will happen. People make choices by thinking about how much happiness (or utility) different outcomes might give them, even when you don't know for sure what will happen. It's like a Product Manager choosing to build out Feature A ahead of Feature B because the team believes "A" returns the best value from its expected utility.


Agile practices are based on a foundation of empirical, scientific, rational process. The key assumption is that individuals will act rationally to optimize outcomes and processes. Good interpersonal relations inside a team may allow for effectiveness of communication flow, collaborating harmoniously and decision making based on empirical data.


In fact, Agile relies upon iterative cycle aimed at continuous improvement; regular feedback loops along with retrospectives serve as its driving force. At its core, agility rests on many assumptions about rationality shared with traditional economic models including utility because “in general people will make decisions to maximize their own benefit.”


How do human organizations optimize work in scaled teams to solve complex problems with AI, software and engineers?

However human behavior often steps away from these ideal rationalities due to cognitive biases or emotional influences. Prospect Theory, by behavioral economists Daniel Kahneman and Amos Tversky, shows that our decisions do not rely only on objective assessments. People think about relative gains and losses rather than absolute ones, according to decades of research in economic reasoning and decision-making. In 2002, Kahneman received the Nobel Memorial Prize in Economic Sciences for his work in prospect theory.


For example, Loss Aversion might prevent agile teams from embracing innovative solutions necessary for growth due to fear of failure or believed losses if such solutions fail. Additionally Framing Effect can manipulate team decision making by how changes or challenges are presented to us explaining why humans tend to be inconsistent in preferences over time (Kahneman & Tversky).


Anchoring bias makes another case where initial estimates or assumptions affect planning and decision-making resulting into unrealistic timelines and expectations while confirmation bias may lead teams focus only on positive information reinforcing their current practices thus overlooking inefficiencies.


Availability Heuristic causes distorted judgments among teams because of high confidence in their strategies or too much caution after recent successes or setbacks. Therefore, agile practices are usually derailed by emotions such as stress, fear and enthusiasm.


The Tragedy of the Commons, a good example of the effect of cognitive bias on agile teams. This metaphor focuses on excessive utilization of shared resources within a team or organization. The tragic story unfolds where individuals act selfishly and exhaust the shared resources at the detriment of the community.


Cognitive biases play a role in several aspects of this tale including Social Loafing whereby people put less effort thinking someone else will make up for them and the Free Ride Problem where some individuals benefit from others’ efforts without contributing proportionately.


Temporal Discounting i.e. the tendency to prefer immediate gains over long-term sustainability can result in consuming unnecessary amount of resource by team which fails to take into account future repercussions. Overconsumption is often justified under the belief that one’s individual contribution to resource depletion is negligible thus reinforcing this cycle.


It is necessary to change how we handle agile practices to deal with bias and irrational tendencies. It requires a deeper understanding of human beings and the cognitive biases that shape our decision-making processes. By promoting consciousness and providing training sessions, we enable teams to realize and counterbalance such biases thus creating an environment where vibrant discussion can take place. Encouragement of psychological safety encourages experimentation and adaptability among teams thereby enabling them to cope better with the intricacies of modern work.


Agile practices need to go beyond being stuck in procedures by having a more nuanced grasp of human behavior as well as team dynamics. In doing so, it will be possible for us to make agile methodologies more effective and bring them into line with real world decision-making scenarios. This ensures continued relevance and efficacy on the part of agile methods


Paradoxes in EUT and Organizational Agility


Expected Utility Theory (EUT) has several paradoxes and dilemmas that are meaningful to organizations, specifically those dealing with complex problems using scaled teams, software and engineers. These paradoxes are indicative of the challenges that come with making rational decisions in complex, uncertain environments and have implications for agile practices as well as organizational behavior.


The Allais Paradox shows that people's choices often violate the independence axiom of EUT. Often people prefer certain outcomes even when the outcomes are against what is expected from utility maximization.


Organizational Implication: In scaled teams, decision-makers might prefer "safe" or known strategies over potentially better but uncertain approaches. This can lead to risk-averse behavior where teams would shy away from innovative solutions involving uncertainty thus stifling innovation and adaptability.


The Ellsberg Paradox demonstrates ambiguity aversion, where people prefer known risks over unknown risks showing a preference for certainty in probability estimates.


Organizational Implication: Teams may avoid projects with ambiguous outcomes or uncertain parameters, opting instead for projects with more predictable outcomes. This can limit exploration of new opportunities and impede an organization’s ability to adapt to changing conditions or technologies.


Status Quo Bias: Although not a formal paradox, status quo bias refers to the tendency toward preferring the current state of affairs rather than embracing change even if it promises greater utility.


Organizational Implication: Scaled teams might resist adopting new technologies, methodologies, or processes preferring instead to maintain existing practices. This can hinder the organization's ability to evolve and optimize performance in response to external pressures or innovations.


Time Inconsistency and Hyperbolic Discounting: Individuals tend to prefer smaller immediate rewards over larger delayed ones even if delaying leads to a better outcome which contradicts consistent time preferences assumed by EUT.


Organizational Implication: Teams may prioritize short-term gains or immediate results, such as quick fixes and rapid releases, over long-term strategies that require more time and resources but could lead to significant improvements. This can result in technical debt, rushed deployments, and sustainability issues.


Framing Effects: The way choices are presented can significantly influence decisions leading individuals to make inconsistent choices based on the framing of outcomes rather than their intrinsic utility.


Organizational Implication: In decision-making processes how options are framed can affect team choices leading to suboptimal strategies. For example, presenting a decision as a potential loss rather than a gain might lead to resistance or a conservative approach affecting the team’s ability to pursue innovative solutions.


Addressing Paradoxes in Organizational Contexts


To address these paradoxes and biases within organizations, specifically ones handling complex problems with scaled teams, several strategies can be deployed:


  • Promote Risk Awareness: Encourage teams to recognize and understand their risk preferences making conscious efforts evaluating options based on their potential long-term value rather than short term certainty.


  • Foster a Culture of Experimentation: Create an environment where teams feel safe to experiment and innovate even when outcomes are uncertain. This can help teams become more comfortable with ambiguity and uncertainty.


  • Implement Decision Frameworks: Use structured decision-making frameworks that account for cognitive biases and emphasize empirical data. This can help teams evaluate options more objectively and make informed choices.


  • Embrace Diverse Perspectives: Engage team members from various backgrounds and specializations in the process of making decisions. Different perspectives can help eliminate negative biases such as status quo bias and enhance problem solving.


  • Align Incentives with Long-Term Goals: Construct incentive systems that match with long-term organizational goals, encouraging teams to emphasize on sustainable strategies rather than immediate but short-lived successes.


By acknowledging these paradoxes and biases and implementing strategies to mitigate their impact, organizations can enhance their decision-making processes and improve their ability to solve complex problems effectively.


Call to Action: Embrace the Human Side of Agile


If we are to break free of "Fragile Agile", we need to acknowledge the gremlin in the OODA loop: it is necessary to recognize the human side of agility. We work in empirical, rational agile practices. It is time that we got out of the assumption that people always act rationally and adopt a more all-rounded approach to agility. We need to define an "Agile Mind Pattern" that considers emotional inclinations and various cognitive biases behind our agile decisions and actions.


To Agile Leaders and Teams:


  • Educate and Empower: Train your teams about the effects of cognitive biases on decision making. Give them tools for identifying these biases and reducing their impact so as to foster critical thinking and create a learning culture.

  • Create a Safe Environment: Establish workplace environments that encourage open discussions and different opinions. Innovation and adaptability rest on psychological safety which allows teams to try new ideas without fear of failure or ridicule.

  • Focus on Data-Driven Insights: Lead the teams into relying more on empirical data and metrics while making decisions. Explain why evidence-based methods should be employed rather than intuition or personal preferences.

  • Align Goals and Incentives: Make sure that team goals and incentives are based on sustainability in addition to long-term success. Encourage sharing collective responsibility over common resources with collaboration being highly stressed than competition.


To Organizations and Industry Leaders:


  • Promote Agile Evolution: Accept that today’s dynamic conditions require an evolution in agile practices. Support initiatives that transpose behavioral insights into agile frameworks thereby keeping them relevant.

  • Champion Rational Diversity and Inclusion: Diverse, persistent teams bring a wealth of ideas, counteract biases, drive innovation, and change things for better within your organization. Let rational problem-driven diversity together with inclusion become core values in your organization.


To Agile Leaders and Scrum Master


Another role which Agile Leaders and Scrum Masters can establish is that of a “Cognitive Bias Scout”. This position entails actively pinpointing cognitive biases that can impair team’s decision making and productivity. By being aware of and challenging such predilections as anchoring, confirmation bias and groupthink, the Scrum Master assists the team through intricacies of human behavior by building critical thinking culture and fostering adaptability.


As a Cognitive Bias Scout, the Scrum Master also plays a vital role in teaching both the team and organization about these biases with an emphasis on acknowledging them so as to foster collaboration and innovation. The appreciation for these skills does not only enhance teamwork but also ensure that agile practices are carried out more effectively and thoughtfully.


Conclusion


By taking these steps, we can enhance the effectiveness of agile methodologies, creating resilient, innovative teams capable of thriving amidst uncertainty. Let’s unlock the full potential of agile together, turning all our companies into hubs where flexibility, collaboration, as well as continuous improvement dominate life.”


  1. A more complete list would include: Scrum, Kanban, SAFe, LeSS, Nexus, Disciplined Agile, Extreme Programming, Scrum@Scale, Spotify Model, Enterprise Scrum, DA Flex

Here are some of the most respected sources on human cognitive bias, which provide comprehensive insights into how cognitive biases affect decision-making and behavior:


Nobel Prize-winning Research by Daniel Kahneman


Amos Tversky and Daniel Kahneman's Work on Heuristics and Biases


Behavioral Economics by Richard Thaler


The Work of Gerd Gigerenzer


Books by Dan Ariely on Predictably Irrational Behavior


Cognitive Bias Codex


Stanford Encyclopedia of Philosophy


These sources offer valuable insights into understanding cognitive biases and their impact on decision-making and behavior. If you need more specific information or additional resources, feel free to ask!you need more specific information or additional resources, feel free to ask!

14 views0 comments

Comentários

Avaliado com 0 de 5 estrelas.
Ainda sem avaliações

Adicione uma avaliação
bottom of page