DRY Principle
Don't Repeat Yourself (DRY) is a software development principle for reducing repetition and redundancy. Essential for creating efficient, maintainable, and scalable code in digital product design.
Don't Repeat Yourself (DRY) is a software development principle for reducing repetition and redundancy. Essential for creating efficient, maintainable, and scalable code in digital product design.
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.
A programming paradigm aimed at improving the clarity, quality, and development time of software by using structured control flow constructs. Essential for writing clear, maintainable, and efficient code in digital product development.
The high-level structure of a software application, defining its components and their interactions. Essential for designing robust, scalable, and maintainable digital products.
3-Tiered Architecture is a software design pattern that separates an application into three layers: presentation, logic, and data. Crucial for improving scalability, maintainability, and flexibility in software development.
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 design approach that divides a system into smaller parts or modules that can be independently created, modified, replaced, or exchanged. Crucial for creating flexible, scalable, and maintainable systems.
The structural design of a product, defining its components, their relationships, and how they interact to fulfill the product's purpose. Important for ensuring that a product is well-organized, scalable, and maintainable.
Domain-Driven Design (DDD) is an approach to software development that focuses on modeling the business domain and its logic. Essential for aligning software development with business needs and creating maintainable systems.
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.
The practice of designing and implementing processes, systems, or business solutions in a way that ensures their long-term viability, efficiency, and maintainability. Crucial for creating durable and efficient designs that remain practical and effective over time, ensuring the ongoing success and feasibility of digital products and operations.
The practice of preserving a user's data and settings between sessions in an application. Crucial for enhancing user experience by providing continuity and personalization.
Redundant, outdated, or unnecessary code or design elements that accumulate over time in a system. Important for identifying and removing to maintain clean, efficient, and maintainable systems and interfaces.
A repository for team members to submit and collect innovative ideas, reflecting a commitment to fostering creativity and shared ownership of product development. Crucial for maintaining an open culture of innovation and capturing diverse perspectives that contribute to the product's evolution and success.
Detailed, Estimated, Emergent, and Prioritized (DEEP) is an agile project management framework for a well-maintained product backlog. Important for maintaining a clear and actionable backlog in agile methodologies.
The practice of managing and resolving incidents that disrupt normal operations, ensuring minimal impact on business activities. Essential for maintaining service reliability and managing operational disruptions effectively.
A collection of reusable components, guided by clear standards, that can be assembled to build any number of applications, ensuring consistency and efficiency. Crucial for maintaining design consistency and efficiency across products.
The systematic process of capturing, evaluating, and implementing ideas to drive innovation, reflecting a collective commitment to continuous improvement and product excellence. Essential for harnessing team creativity and maintaining the entrepreneurial spirit that characterizes successful product development.
The principle that elements in a digital interface maintain consistent appearance, position, and behavior across different pages and states to help users maintain orientation and familiarity. Important for creating a stable and predictable user experience, reducing disorientation and enhancing usability.
A document that outlines the guidelines for how a brand should be presented, including visual identity, messaging, and tone. Essential for maintaining brand consistency and integrity.
A quick and often temporary fix applied to a software product to address an urgent issue without going through the full development cycle. Essential for maintaining the stability and functionality of digital products in the face of critical issues.
Guidelines that dictate how a brand should be presented across various media to ensure consistency. Crucial for maintaining brand integrity and ensuring uniformity in brand communications.
Actions, messages, or visuals that are consistent with the established brand identity and values. Essential for maintaining brand integrity and ensuring all communications align with brand standards.
The process of making small, continuous improvements to products, services, or processes over time. Important for sustaining growth and maintaining competitiveness through ongoing improvements.
A system of design variables used to maintain consistency in a design system, such as colors, fonts, and spacing. Crucial for ensuring uniformity and scalability in design across different platforms and products.
A set of rules and standards that define how a brand should be represented across all media and platforms. Crucial for ensuring brand consistency and maintaining brand integrity.
A team responsible for developing and maintaining the foundational systems and services that support other teams and products. Crucial for ensuring scalability and efficiency across the organization.
The process of maintaining, updating, and improving a product or system after its initial deployment to ensure its continued functionality, performance, and relevance to users. Crucial for ensuring long-term user satisfaction, product reliability, and adaptation to changing user needs and technological advancements.
Actions, messages, or visuals that do not align with the established brand identity and values. Important for identifying and correcting deviations from brand standards.
The accumulated consequences of poor design decisions, which can hinder future development and usability. Crucial for understanding and addressing the long-term impact of design choices.
A prioritized list of ideas and potential features for future product development, embodying a collective vision for innovation and improvement. Essential for managing creative input and maintaining an innovation pipeline that aligns with the team's entrepreneurial spirit and shared commitment to product excellence.
Large-Scale Scrum (LeSS) is a framework for scaling agile product development to multiple teams working on a single product. It provides a minimalist, large-scale agile approach that maintains the simplicity and effectiveness of Scrum while addressing the challenges of coordination and integration in multi-team environments.
A symbol, word, or words legally registered or established by use as representing a company or product. Crucial for protecting brand identity and ensuring legal rights to brand elements.
The principle that ensures user interface elements maintain their size and proportion across different screen densities. Essential for creating a consistent user experience across various devices.
A design principle that ensures a system continues to function at a reduced level rather than completely failing when some part of it goes wrong. Crucial for enhancing system reliability and user experience in adverse conditions.
Tell, Don't Ask (TDA) is a design principle in software engineering that promotes encapsulation by having objects handle their own data and actions. Essential for maintaining object-oriented integrity and reducing dependencies in the code.
A tool in Google Search Console that allows webmasters to instruct Google to ignore certain backlinks, typically used to combat negative SEO. Crucial for maintaining a healthy backlink profile and protecting against negative SEO practices.
The process of developing and maintaining a brand to ensure it meets business goals and customer expectations. Crucial for sustaining brand equity and achieving long-term success.
Content designed to attract clicks by using sensational or misleading headlines. Important for recognizing and avoiding practices that can harm user trust and content quality.
A dark pattern where questions are worded in a way that tricks the user into giving an answer they didn't intend. Recognizing the harm of this practice is important to maintain clarity and honesty in user interactions.
An evaluation process that assesses the effectiveness, efficiency, and alignment of product management practices and strategies with organizational goals. Essential for identifying areas for improvement and ensuring alignment with business objectives.
A programming paradigm that uses objects and classes to structure software design, promoting reusability and scalability. Crucial for developing maintainable and scalable software systems.
A type of software testing that ensures that recent changes have not adversely affected existing features. Essential for maintaining software quality and reliability.
The practice of being open and honest about operations, decisions, and business practices, fostering trust and accountability. Essential for building trust with users and stakeholders and ensuring ethical business practices.
A market space that is already crowded with competition, where companies fight for market share, leading to intense rivalry and lower profitability. Important for understanding competitive dynamics and market saturation in strategic planning.
Plan, Do, Check, and Act (PDCA) is a four-step management method used for continuous improvement of processes and products. Essential for implementing and maintaining continuous improvement in business and design processes.
The ability of a system to maintain its state and data across sessions, ensuring continuity and consistency in user experience. Crucial for designing reliable and user-friendly systems that retain data and settings across interactions.
A clear and concise list of criteria that a product or task must meet to be considered complete, ensuring alignment and understanding within a team. Essential for maintaining quality and consistency in agile project management.
The process of anticipating, detecting, and resolving errors in software or systems to ensure smooth operation. Important for creating reliable and user-friendly software applications.
A mindset and approach that embodies the entrepreneurial spirit, passion for improvement, and deep sense of ownership typically associated with a company's founders. Essential for maintaining agility, innovation, and customer-centricity as organizations grow and mature.
The observed tendency of humans to quickly return to a relatively stable level of happiness despite major positive or negative events or life changes. Useful for designing experiences that maintain user engagement and satisfaction over time.
The ability of an organization to adapt quickly to market changes and external forces while maintaining a focus on delivering value. Essential for fostering an adaptable and resilient design and development process.
A short, daily meeting (separate from Standup) for the development team to sync on progress and plan for the day, part of the Scrum agile framework. Crucial for maintaining team alignment and momentum in agile projects.
A dark pattern where repetitive notifications or prompts are used to wear down user resistance. Recognizing the annoyance of this tactic is important to maintain respectful user interactions and avoid interruptions.
A Japanese word meaning excessive strain on people or processes. Crucial for preventing burnout and maintaining sustainable work practices.
The process of reviewing, prioritizing, and updating items in the backlog to ensure they are ready for development. Crucial for maintaining an organized and prioritized list of tasks to improve project efficiency.
The implied cost of additional rework caused by choosing an easy or limited solution now instead of using a better approach that would take longer. Essential for understanding and managing the long-term impacts of short-term technical decisions.
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.
A dark pattern where a product sneaks an additional item into the user's shopping cart, often through a pre-selected checkbox. Designers should avoid this practice and ensure users have full control over their purchases to maintain trust.
Ensuring that user experiences are consistent across different platforms, such as web, mobile, and desktop. Essential for creating a seamless and cohesive user experience across multiple devices.