# Balanced cognitive load Maintaining a balanced cognitive load challenges team members without overwhelming or under-stimulating them. Focusing on cognitive load not only promotes individual job satisfaction, but also yields improved performance by teaching them to process information effectively, learn from their experiences, and retain knowledge. In a DevOps environment, a balanced cognitive load supports a healthy environment for innovation and adaptability, directly contributing to the overall success of the organization. **Topics** + [ # Indicators for balanced cognitive load ](indicators-for-balanced-cognitive-load.md) + [ # Anti-patterns for balanced cognitive load ](anti-patterns-for-balanced-cognitive-load.md) + [ # Metrics for balanced cognitive load ](metrics-for-balanced-cognitive-load.md) # Indicators for balanced cognitive load Maintain a balance where team members are adequately challenged without feeling overwhelmed, improving job satisfaction, innovation, and organizational success. **Topics** + [ # [OA.BCL.1] Clarify purpose and direction to improve cognitive well-being ](oa.bcl.1-clarify-purpose-and-direction-to-improve-cognitive-well-being.md) + [ # [OA.BCL.2] Automate repetitive tasks to reduce toil ](oa.bcl.2-automate-repetitive-tasks-to-reduce-toil.md) + [ # [OA.BCL.3] Reduce troubleshooting and technical debt through continuous improvement ](oa.bcl.3-reduce-troubleshooting-and-technical-debt-through-continuous-improvement.md) + [ # [OA.BCL.4] Boost team efficiency by limiting work in progress ](oa.bcl.4-boost-team-efficiency-by-limiting-work-in-progress.md) + [ # [OA.BCL.5] Establish clear escalation paths and encourage constructive disagreement ](oa.bcl.5-establish-clear-escalation-paths-and-encourage-constructive-disagreement.md) + [ # [OA.BCL.6] Provide teams the autonomy to make decision that align with organizational objectives ](oa.bcl.6-provide-teams-the-autonomy-to-make-decision-that-align-with-organizational-objectives.md) + [ # [OA.BCL.7] Cultivate a psychologically-safe culture for experimentation ](oa.bcl.7-cultivate-a-psychologically-safe-culture-for-experimentation.md) + [ # [OA.BCL.8] Determine team sizes based on cognitive capacity ](oa.bcl.8-determine-team-sizes-based-on-cognitive-capacity.md) + [ # [OA.BCL.9] Use guiding principles to make consistent team decisions ](oa.bcl.9-use-guiding-principles-to-make-consistent-team-decisions.md) + [ # [OA.BCL.10] Make informed decisions using data ](oa.bcl.10-make-informed-decisions-using-data.md) # [OA.BCL.1] Clarify purpose and direction to improve cognitive well-being **Category:** FOUNDATIONAL Verify that every individual feels aligned with the organizational goals and sees the impact of their contributions. A motivated workforce that is driven by a sense of purpose can lead to enhanced cognitive well-being, reduced burnout, and improved retention rates. Regularly communicate a clear strategy, and communicate the organization's business objectives it to all team members. Align individual goals and targets with the business objectives so that every member understands their unique role and contribution. Provide frequent updates on organizational progress towards achieving business goals to keep the team informed and involved. Implement a structured feedback mechanism and recognize the efforts of team members in contributing to the organization's success. **Related information:** + [Amazon's approach to security during development: Ownership](https://youtu.be/NeR7FhHqDGQ?t=632) # [OA.BCL.2] Automate repetitive tasks to reduce toil **Category:** FOUNDATIONAL Identify repetitive, time-consuming tasks, referred to as toil. Assess the potential for automation, setting a high standard for automation with limited allowance for manual work. Continually review and reduce this allowance as more tasks are automated. Implement automation tools and processes to reduce toil and improve overall team efficiency. Encourage team members to identify opportunities for automation, and provide the necessary training and resources to support automation efforts. **Related information:** + [AWS Well-Architected Cost Optimization Pillar: COST11-BP01 Perform automations for operations](https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/cost_evaluate_cost_effort_automations_operations.html) # [OA.BCL.3] Reduce troubleshooting and technical debt through continuous improvement **Category:** FOUNDATIONAL Proactively reducing the frequency of interruptions and addressing technical debt can have a significant positive impact on overall DevOps adoption. Allocating budget and a portion of the team's time to improve existing processes, environments, and workloads can yield a net improvement to overall development speed, code quality, and system stability. This can be achieved by implementing tools, processes, and team norms to identify, track, and manage technical debt, as well as regularly assessing and prioritizing process improvement opportunities.  To focus teams on impactful improvements, encourage teams to factor in time and effort towards these initiatives. Establish metrics to measure their impact. Prioritizing addressing technical debt as part of regular work can also reduce the likelihood of production issues, ultimately resulting in more stable and reliable systems. # [OA.BCL.4] Boost team efficiency by limiting work in progress **Category:** FOUNDATIONAL Provide ample capacity to accomplish goals on time by reducing work in progress (WIP). Prioritize finishing tasks over starting new ones, which helps to reduce context-switching and impacts overall team efficiency. Continually monitor and adjust WIP limits to prioritize tasks that align with business outcomes. Encourage teams to use agile project management tools and rules, such as Kanban or Scrum, to manage work in progress and complete tasks in a timely manner. # [OA.BCL.5] Establish clear escalation paths and encourage constructive disagreement **Category:** FOUNDATIONAL Optimize issue resolution by establishing clear escalation paths and making it part of every team's norms. Define and communicate processes for how and when to escalate issues, and identify the individuals or groups responsible for making decisions. The escalation process should be documented, data-driven, and shared broadly so that everyone is aware of the steps involved. Encourage open communication and a culture of constructive disagreement, where team members can respectfully challenge decisions while still committing to a strategy as a team once a decision has been made. Escalation should not be feared, but instead expected to be frequent and fully supported by leadership. Once a decision is made through the escalation process, everyone should commit to the decision that is made. Introduce the concept of the *Andon cord*, inspired by Toyota's manufacturing process and adopted by companies like Amazon, as an actionable step to help team members raise concerns and stop processes when problems arise. The Andon cord serves as a mechanism for team members to escalate issues quickly, addressing problems promptly and effectively. # [OA.BCL.6] Provide teams the autonomy to make decision that align with organizational objectives **Category:** FOUNDATIONAL Provide teams with the autonomy to make decisions and changes at the lowest level possible. Provide the necessary information, policies, and tools to make informed decisions aligned with the organization's goals and objectives. Establish clear guardrails to guide decisions and achieve consistency with the overall strategy while avoiding adverse impacts on other teams or the organization. Encourage a culture of empowerment, where team members feel confident in making decisions and taking action. **Related information:** + [Amazon's approach to security during development: Ownership](https://youtu.be/NeR7FhHqDGQ?t=632) # [OA.BCL.7] Cultivate a psychologically-safe culture for experimentation **Category:** FOUNDATIONAL Encourage experimentation and learning from failures by establishing clear guidelines and hosting sharing sessions for both successful and failed experiments. Foster a psychologically-safe environment where team members feel encouraged to share their ideas and speak up without fear of negative consequences. Recognize and celebrate successes, while also recognizing individuals who take risks and contribute to innovation. Cultivate a culture that values open communication, feedback, and continuous learning. Provide support for team members who are willing to experiment and think big. **Related information:** + [Amazon's approach to security during development: Technical fearlessness](https://youtu.be/NeR7FhHqDGQ?t=1031) # [OA.BCL.8] Determine team sizes based on cognitive capacity **Category:** FOUNDATIONAL Determine team size using [Dunbar's number](https://en.wikipedia.org/wiki/Dunbar%27s_number) and the [7 ± 2 rule](https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two), which state that teams should be composed of no more than 7 to 10 individuals. With smaller teams, they require the autonomy and resources necessary to be successful within their value stream. Keep team sizes manageable, and foster effective communication, collaboration, and decision-making. Regularly assess the team's composition and structure, making adjustments as needed to maintain efficiency and effectiveness. Provide teams with the necessary tools and resources to support collaboration and communication in small group settings. Larger organizations might have teams of teams, often referred to as guilds, chapters, or squads. The name used here is completely dependent on the organization's preference and culture. In this scenario, Dunbar's number advises that the number of people not exceed 150. Having a team of teams allows smaller teams to work together towards common goals that align to related business outcomes, while maintaining the benefits of smaller team sizes and scaling effectively within a larger organization. **Related information:** + [Dunbar's number](https://en.wikipedia.org/wiki/Dunbar%27s_number) + [The Magical Number Seven, Plus or Minus Two](https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two) + [Two-Pizza Teams](https://docs.aws.amazon.com/whitepapers/latest/introduction-devops-aws/two-pizza-teams.html) # [OA.BCL.9] Use guiding principles to make consistent team decisions [OA.BCL.9] Use guiding principles to make consistent team decisions **Category:** RECOMMENDED Establish team guiding principles. These guiding principles should be created collaboratively and should outline the team's purpose, goals, values, and operating principles. Verify that the charter is well understood by all team members and regularly referenced in decision-making processes. Periodically review and update the guiding principles to ensure they remain relevant and aligned with the team's evolving goals and values. Encourage team members to use these guiding principles as a framework for making decisions and resolving conflicts, ensuring consistency and alignment across the team. **Related information:** + [Tenets: supercharging decision-making](https://aws.amazon.com/blogs/enterprise-strategy/tenets-supercharging-decision-making/) # [OA.BCL.10] Make informed decisions using data [OA.BCL.10] Make informed decisions using data **Category:** RECOMMENDED Encourage teams to shift from relying solely on intuition or personal experience to using data to inform their decisions so that they become more objective than subjective. Teams should consider what to measure (and why), how to measure it, and how to effectively present the data for informed decision making. Provide training on data analysis and visualization, and aim to make data easily accessible and up-to-date. Use tools to collect, store, analyze, and visualize data effectively, allowing teams to make data-driven decisions. Incorporate the *build-measure-learn* feedback loop and *validated learning* concepts from Eric Ries' [The Lean Startup](https://theleanstartup.com/principles) to enhance decision-making capabilities and alignment with organizational goals. Use the build-measure-learn loop and validated learning to make data-driven decisions, test assumptions, and adapt quickly to changing conditions to foster a culture of continuous learning and improvement. By partnering with customers throughout the innovation process, teams can better align their efforts with organizational objectives while remaining agile and responsive to evolving requirements. Doing so confirms that solutions are built with customer empathy, measured for impact, and refined through collaborative learning. **Related information:** + [The Lean Startup Methodology](https://theleanstartup.com) # Anti-patterns for balanced cognitive load Anti-patterns + **Imbalanced workload**: Both overloading team members with too many tasks or responsibilities and underutilizing them by assigning insufficient responsibilities or challenges can lead to reduced productivity. An imbalanced workload can hinder an individual's ability to learn and retain knowledge, ultimately impeding the effectiveness of DevOps adoption. Strike the right balance between challenging team members and avoiding burnout to foster a productive and engaged team. + **Oversized teams**: Forming excessively large teams that exceed the cognitive limit of effectively managing relationships as described by [Dunbar's number](https://en.wikipedia.org/wiki/Dunbar%27s_number) (approximately 150 people). As teams grow beyond this size, there is a risk that communication, collaboration, and decision making will suffer, reducing the team's overall effectiveness. Create smaller teams that can communicate more effectively, make better decisions, and deliver higher-quality products and services. This is especially important in the beginning stages of product development; try to keep your teams as small as you can for as long as you can. + **Lack of autonomy and psychological safety**: Cultivating an environment that lacks autonomy and intolerance to failure can lead to risk aversion and an unwillingness to experiment and innovate. In environments that micromanage or over prioritize being risk adverse, individuals tend to shift focus from delivering value to avoiding failure, resulting in sub-optimal outcomes and slower delivery. Embrace a culture of psychological safety that encourages autonomy, experimentation, and risk-taking. Allowing individuals to make decisions and experiment can lead to significant breakthroughs and innovations, as well as higher job satisfaction and performance. # Metrics for balanced cognitive load Metrics + **Team size ratio:** Comparing the actual team size against the recommended team size based on cognitive limits. To measure this metric, compare the current team size to the recommended team size to calculate the ratio based on cognitive limits, for example, less than 10 people in individual teams, and less than 150 in a team of teams. + **Burnout assessment scores:** Evaluate team members' well-being using a burnout assessment survey. For example, the [Maslach Burnout Inventory](https://en.wikipedia.org/wiki/Maslach_Burnout_Inventory) general survey delves into exhaustion, cynicism, and professional efficacy as indicators of burnout. Distribute the questionnaire to team members on a regular basis, such as quarterly or biannually, to monitor trends and respond proactively to burnout indicators. Over time, track changes to help ensure that interventions are effective and that overall team well-being is trending positively. Encourage open communication and feedback, allowing teams to voice concerns or provide suggestions to improve the work environment. Consider working with human resources (HR) professionals or occupational psychologists to interpret the results and develop appropriate interventions.