Zero-Risk Bias
A cognitive bias where people prefer the option that seems to eliminate risk entirely, even if another option offers a greater overall benefit. Important for understanding decision-making and designing risk communication for users.
A cognitive bias where people prefer the option that seems to eliminate risk entirely, even if another option offers a greater overall benefit. Important for understanding decision-making and designing risk communication for users.
The abilities and knowledge required to effectively plan, execute, and close projects, including leadership, communication, time management, and risk management. Essential for ensuring successful project outcomes and achieving business objectives.
The tendency to believe that things will always function the way they normally have, often leading to underestimation of disaster risks. Important for understanding risk perception and designing systems that effectively communicate potential changes.
An organizational environment that encourages and supports creative thinking, risk-taking, and the pursuit of new ideas. Essential for fostering continuous improvement and breakthrough advancements.
A structured communication technique originally developed as a systematic, interactive forecasting method which relies on a panel of experts. Important for gathering expert opinions and making informed decisions.
A psychological phenomenon where the desire for harmony and conformity in a group results in irrational or dysfunctional decision-making. Crucial for recognizing and mitigating the risks of poor decision-making in teams.
Designing systems and processes to effectively respond to and manage crises, ensuring resilience and quick recovery. Crucial for preparing for unexpected events and minimizing their impact.
Model-Based Systems Engineering (MBSE) is a methodology that uses visual modeling to support system requirements, design, analysis, and validation activities throughout the development lifecycle. Essential for managing complex systems, improving communication among stakeholders, and enhancing the overall quality and efficiency of systems engineering processes.
The systematic identification, analysis, planning, and implementation of actions designed to engage and influence stakeholders in a project. Crucial for maintaining positive relationships and ensuring stakeholder support throughout the project lifecycle.
Software Requirements Specification (SRS) is a detailed document that outlines the functional and non-functional requirements of a software system. Crucial for ensuring clear communication and understanding between stakeholders and the development team.
A cognitive bias where people perceive an outcome as certain while it is actually uncertain, based on how information is presented. Crucial for understanding and mitigating biased user decision-making.
A cognitive bias where people judge the likelihood of an event based on the size of its category rather than its actual probability. Crucial for designers to understand how category size influences user perception and decision-making processes.
A detailed description of a system's behavior as it responds to a request from one of its stakeholders, often used to capture functional requirements. Essential for understanding and documenting how users will interact with a system to achieve their goals.
A role responsible for ensuring that products and services are delivered efficiently, on time, and within budget. Crucial for managing project timelines, resources, and stakeholder expectations.
A professional responsible for planning, executing, and closing projects, ensuring they are completed on time, within scope, and on budget. Crucial for managing project activities and ensuring successful delivery of project goals.
A cognitive bias where people judge the likelihood of an event based on its relative size rather than absolute probability. Important for understanding user decision-making biases and designing systems that present information accurately.
The Project Management Body of Knowledge (PMBOK) is a comprehensive set of guidelines, best practices, and standards for project management. Essential for ensuring consistency and excellence in managing projects across various industries.
Emotional states where individuals are calm and rational, often contrasted with hot states where emotions run high. Important for understanding decision-making processes and designing experiences that accommodate both states.
Customer Advisory Board (CAB) is a group of key customers who provide feedback and insights to a company to help guide its strategic decisions. This group is crucial for aligning products and services with customer needs and expectations.
User-Centered Design (UCD) is an iterative design approach that focuses on understanding users' needs, preferences, and limitations throughout the design process. Crucial for creating products that are intuitive, efficient, and satisfying for the intended users.
Software Development Life Cycle (SDLC) is a process for planning, creating, testing, and deploying an information system. Essential for managing the complexities of software development and ensuring project success.
Product Requirements is a document that outlines the essential features, functionalities, and constraints of a product. Crucial for guiding the development process and ensuring all stakeholders have a shared understanding of the product's goals.
Objectives and Key Results (OKR) is a goal-setting framework for defining and tracking objectives and their outcomes. Essential for aligning organizational goals, improving focus and engagement, and driving measurable results across teams and individuals.
Net Promoter Score (NPS) is a metric used to measure customer loyalty and satisfaction based on their likelihood to recommend a product or service to others. Crucial for gauging overall customer sentiment and predicting business growth through customer advocacy.