A usability testing approach where designers assume that users are easily confused and distracted, focusing on simplicity and clarity in design. Crucial for ensuring that interfaces are intuitive and easy to use under various conditions.
The core principles that underpin agile methodologies, focusing on collaboration, flexibility, and customer satisfaction. Crucial for guiding agile practices and ensuring effective project delivery.
A declaration of the values and principles essential for agile software development. Foundational for understanding the ethos of agile methodologies.
A problem-solving method that involves asking "why" five times to identify the root cause of a problem. Useful for designers and product managers to uncover underlying issues and improve processes and solutions.
A focus on the results or benefits of a project rather than the activities or deliverables produced. Crucial for ensuring that efforts are aligned with achieving meaningful results.
A methodology for building software-as-a-service apps that emphasizes best practices for development, deployment, and scalability. Important for creating scalable, maintainable, and efficient digital products.
A prioritized list of tasks, features, and technical debt items that need to be addressed by the engineering team. Essential for managing and organizing work in software development projects.
A set of ten general principles for user interface design created by Jakob Nielsen to improve usability. Essential for evaluating and improving user interface designs.
An agile framework for managing work with an emphasis on software development, characterized by sprints and iterative progress. Essential for improving productivity and delivering incremental value in development projects.
A simple description of a feature from the perspective of the user, typically used in Agile development to capture requirements and guide development. Crucial for ensuring that development efforts are aligned with user needs and priorities.
A prioritized list of work items or tasks that need to be completed, commonly used in agile project management. Essential for managing tasks and ensuring that development teams focus on the most important work items.
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.
A team structure focused on delivering value streams, often organized around a specific business capability or customer need. Crucial for enhancing delivery efficiency and aligning with business goals.
Feature Driven Development (FDD) is an agile methodology focused on designing and building features based on client-valued functionality. Essential for delivering client-valued features efficiently and effectively.
A visual representation of the user or customer journey, highlighting key interactions, emotions, and pain points. Essential for identifying opportunities to improve user or customer experiences.
The practice of designing products, services, and environments with a focus on the overall user experience. Essential for creating holistic and meaningful interactions.
Any process or administrative barrier that unnecessarily complicates transactions and creates friction, discouraging beneficial behaviors. Important for identifying and eliminating unnecessary obstacles that hinder user experiences.
The act of designing and implementing subtle interventions to influence behavior in a predictable way. Crucial for guiding user behavior effectively without limiting freedom of choice.
Not Invented Here (NIH) syndrome refers to the aversion to using or buying products, research, or knowledge developed outside an organization. This mindset can hinder innovation and collaboration.
Business Process Execution Language (BPEL) is a language for specifying business process behaviors based on web services. Important for defining and automating complex business processes in digital product workflows.
Dynamic Systems Development Method (DSDM) is an agile project delivery framework focused on delivering business value early and continuously. Essential for ensuring that projects align with business goals and user needs through iterative processes.
SAFe is a framework designed to scale agile practices across large organizations by integrating agile and lean principles. It is widely used but criticized for its rigidity, bureaucratic structure, and potential to stifle true agile culture.
A Japanese word meaning excessive strain on people or processes. Crucial for preventing burnout and maintaining sustainable work practices.
CSM (Customer Success Management) is a business methodology focused on ensuring customers achieve their desired outcomes while using a product or service. Crucial for driving customer retention and satisfaction.
Numeronym for the word "Modularization" (M + 12 letters + N), dividing a system into separate, interchangeable modules that can be developed, tested, and maintained independently. Important for improving maintainability and scalability of systems.
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
Program Increment (PI) Planning is a cadence-based event that serves as the heartbeat of the Agile Release Train, aligning teams on goals and priorities for the next increment. Crucial for aligning teams, setting goals, and planning work.
A user research technique where participants organize information into categories to inform information architecture and design. Essential for creating intuitive information architectures and improving user experience.
A brief daily meeting in Agile project management where team members share updates on their progress, plans for the day, and any obstacles they face. Essential for maintaining communication, transparency, and coordination within Agile teams.
Enterprise Resource Planning (ERP) are integrated software systems that manage business processes across various departments, such as finance, HR, and supply chain. Essential for improving operational efficiency and providing a unified view of business operations.
An approach to design that considers the entire user journey and all touchpoints, ensuring a seamless and cohesive experience. Crucial for creating integrated and satisfying user experiences across multiple channels and interactions.
A strategic management template for developing new business models or documenting existing ones, detailing elements like value proposition, infrastructure, and customers. Important for understanding and designing business strategies that align with product and user experience goals.
Entity Relationship Diagram (ERD) is a visual representation of the relationships between entities in a database. Essential for designing and understanding the data structure and relationships within digital products.
A graphical representation showing the amount of work remaining versus time, used in agile project management to track progress. Crucial for managing project progress and ensuring timely completion of tasks.
A time-boxed period during which specific work must be completed and made ready for review, used in Agile project management. Crucial for managing workload and ensuring continuous delivery and improvement in Agile projects.
The phenomenon where people follow the direction of another person's gaze, influencing their attention and behavior. Important for understanding visual attention and designing more effective visual cues in interfaces.
eXtreme Programming (XP) is an agile software development methodology focused on customer satisfaction and continuous improvement. It enhances software quality and responsiveness to changing requirements through frequent releases of functional software.
Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes in a workflow, using standardized symbols and notations. Essential for creating clear, standardized diagrams that facilitate understanding and communication of business processes in digital product design.
A leadership philosophy where the leader prioritizes the needs of the team, empowering and supporting members to achieve their full potential and fostering a collaborative, inclusive environment. Important for building strong, motivated teams, enhancing collaboration, and promoting a culture of trust and respect within an organization.
A set of metadata standards used to describe digital resources, facilitating their discovery and management. Important for ensuring effective organization and retrieval of digital assets in product design and development.
Voice User Interface (VUI) is a system that allows users to interact with a device or software using voice commands. Essential for creating hands-free, intuitive user experiences.
A role in Agile project management responsible for ensuring the team follows Agile practices, facilitating meetings, and removing obstacles to progress. Essential for supporting Agile teams and ensuring successful implementation of Scrum practices.
A dark pattern where availability is falsely limited to pressure users into making a purchase. Awareness of this deceptive practice is important to provide honest information about product availability.
Model-View-Controller (MVC) is an architectural pattern that separates an application into three main logical components: the Model (data), the View (user interface), and the Controller (processes that handle input). Essential for creating modular, maintainable, and scalable software applications by promoting separation of concerns.
Behavior-Driven Development (BDD) is a software development approach where applications are specified and designed by describing their behavior. Important for ensuring clear communication and shared understanding between developers and stakeholders.
Adaptive Software Development (ASD) is a software development methodology that focuses on continuous adaptation to changing requirements and environments. Essential for managing changing requirements and ensuring agile project delivery.
Mutually Exclusive, Collectively Exhaustive (MECE) is a problem-solving framework ensuring that categories are mutually exclusive and collectively exhaustive, avoiding overlaps and gaps. Essential for structured thinking and comprehensive analysis in problem-solving.
Agile Release Train (ART) is a long-lived team of Agile teams that, along with other stakeholders, incrementally develops, delivers, and operates one or more solutions in a value stream. Important for coordinating Agile development and delivery at scale.
A software development practice where code changes are frequently integrated into a shared repository, with each change being verified by automated tests. Essential for catching errors early and improving the quality of software.
Also known as "Maslow's Hammer," a cognitive bias where people rely too heavily on a familiar tool or method, often summarized as "if all you have is a hammer, everything looks like a nail.". Important for designers to recognize and avoid over-reliance on familiar methods in problem-solving and design.
Capability Maturity Model (CMM) is a framework for improving and optimizing processes within an organization. Essential for assessing and enhancing the maturity and efficiency of processes in product design and development.
A decision-making tool that helps prioritize tasks or projects based on specific criteria, such as impact and effort. Essential for effective project management and resource allocation.
A unit of measure used in Agile project management to estimate the relative effort required to complete a user story or task. Crucial for planning and managing workload within Agile teams.
A strategic framework that designs user experiences to guide behavior and decisions towards desired outcomes. Crucial for creating effective and ethical influence in digital interfaces.