💻IT: Standardization (Definitions)

"The imposition of standards which, in turn, are fixed ways of doing things that are widely recognized." (Roy Rada &  Heather Holden, "Online Education, Standardization, and Roles", 2009)

"Formulation, publication, and implementation of guidelines, rules, methods, procedures and specifications for common and repeated use, aimed at achieving optimum degree of order or uniformity in given context, discipline, or field; standards are most frequently developed on international level; there exist national standardization bodies cooperating with international bodies; standards can be either legally binding or de facto standards followed by informal convention or voluntary standards (recommendations)." (Lenka Lhotska et al,"Interoperability of Medical Devices and Information Systems", 2013)

"A framework of agreements to which all relevant parties in an industry or organization must adhere to ensure that all processes associated with the creation of a good or performance of a service are performed within set guideline." (Victor A Afonso & Maria de Lurdes Calisto, "Innovation in Experiential Services: Trends and Challenges", 2015)

"The development of uniform specifications for materials, products, processes, practices, measurement, or performance, usually via consultation with stakeholders and sanction by a recognized body, providing for improvements in productivity, interoperability, cooperation, and accountability." (Gregory A Smith, "Assessment in Academic Libraries", 2015)

"A process of developing and implementing technical standards based on consensus among various stakeholders in the field. Standardization can greatly assist with compatibility and interoperability of otherwise disparate software components, where consistent solutions enable mutual gains for all stakeholders." (Krzysztof Krawiec et al, "Metaheuristic Design Patterns: New Perspectives for Larger-Scale Search Architectures", 2018)

"The process through which a standard is developed." (Kai Jakobs, "ICT Standardization", 2018)

"Is a framework of agreements to which professionals in an organization must accept to ensure that all processes associated with the creation of a product or service are performed within set guidelines, achieving uniformity to certain practices or operations within the selected environment. It can be seen as a professional strategy to strengthen professional trust and provide a sense of certainty for professionals or it can be interpreted as a way to lose professionalization and as an adjustment to organizational demands." (Joana V Guerra, "Digital Professionalism: Challenges and Opportunities to Healthcare Professions", 2019)

"The process of making things of the same kind, including products and services, have the same basic features and the same requirements." (Julia Krause, "Through Harmonization of National Technical Regulations to More Sustainability in Engineering Business", 2019)

💻IT: Product Information Management [PIM] (Definitions)

"The management of product master data, usually via a PIM hub, to avail a single version of the truth about product data to the business." (Evan Levy & Jill Dyché, "Customer Data Integration", 2006)

"MDM Systems that focus exclusively on managing the descriptions of products are also call PIM systems." (Martin Oberhofer et al, "Enterprise Master Data Management", 2008)

"Processes and technologies focused on centrally managing information about products, with a focus on the data required to market and sell the products through one or more distribution channels. A central set of product data can be used to feed consistent, accurate, and up-to-date information to multiple output media such as websites, print catalogs, ERP systems, and electronic data feeds to trading partners. PIM systems generally need to support multiple geographic locations, multilingual data, and maintenance and modification of product information within a centralized catalog to provide consistently accurate information to multiple channels in a cost-effective manner." (Janice M Roehl-Anderson, "IT Best Practices for Financial Managers", 2010)

"Processes and tools used to predict and evaluate success of products through marketing and sales efforts." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"Product Information Management (PIM) is the process, techniques and technology of gaining control over a company's product marketing information. The objective of PIM solutions is to remove inefficiency in the marketing supply chain by delivering information to sales channels more quickly and with fewer mistakes." (Digital Asset Management)

"Product information management (PIM) is the process of managing all the information required to market and sell products through distribution channels." (Wikipedia) [source]

"Product information management (PIM) is the software-based orchestration of data dissemination related to a business’s products and its suppliers’ products. PIM coordinates changing product information across all channels of communication, thus ensuring that a business’s entire ecosystem has consistent and up-to-date information." (Informatica)

"The processes and tools for managing product information, including: 1) data centralization and governance; 2) data onboarding from partners; 3) data and content creation and enrichment; and 4) content distribution/syndication." (Forrester)

🚧Project Management: Product Lifecycle (Definitions)

"The period of time, consisting of phases, that begins when a product is conceived and ends when the product is no longer available for use. Since an organization may be producing multiple products for multiple customers, one description of a product life cycle may not be adequate. Therefore, the organization may define a set of approved product life-cycle models. These models are typically found in published literature and are likely to be tailored for use in an organization. A product life cycle could consist of the following phases: (1) concept/vision, (2) feasibility, (3) design/development, (4) production, and (5) phase out." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"The period of time that begins when a product is conceived and ends when the product is no longer available for use. This cycle typically includes phases for concept definition (verifies feasibility), full-scale development (builds and optionally installs the initial version of the system), production (manufactures copies of the first article), transition (transfers the responsibility for product upkeep to another organization), operation and sustainment (repairs and enhances the product), and retirement (removes the product from service). Full-scale development may be divided into subphases to facilitate planning and management such as requirements analysis, design, implementation, integration and test, installation and checkout." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A term to describe a product, from its conception to its discontinuance and ultimate market withdrawal." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"a model of the sales and profits of a product category from its introduction until its decline and disappearance from the market; focuses on the appropriate strategies at each stage." (Gina C O'Connor & V K Narayanan, "Encyclopedia of Technology and Innovation Management", 2010)

"A collection of generally sequential, non-overlapping product phases whose name and number are determined by the manufacturing and control needs of the organization. The last product life cycle phase for a product is generally the product's retirement. Generally, a project life cycle is contained within one or more product life cycles." (Cynthia Stackpole, "PMP® Certification All-in-One For Dummies®", 2011)

"The series of phases that represent the evolution of a product, from concept through delivery, growth, maturity, and to retirement." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

♜Strategic Management: Competitive Advantage (Definitions)

"The relative advantage that one product or product line has over those products offered by other companies." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"An advantage a company has over its competitors, which is gained by providing consumers with greater value through product or service offerings." (Linda Volonino & Efraim Turban, "Information Technology for Management 8th Ed", 2011)

"A strategic advantage held by one organization that cannot be matched by its competitors. This advantage may or may not be sustainable and, if not, may eventually be replicated by its competitors." (Evan Stubbs, "Big Data, Big Innovation", 2014)

"A strategy whereby companies position themselves ahead of competitors either by charging less or by differentiating their services or products from those of their rivals. " (DK, "The Business Book", 2014)

"The characteristics of an organization that differentiate it from other organizations in the same sector and that cannot easily be replicated. This differentiation may potentially provide the basis for competitive advantage. From a strategic management perspective it is the differentiated competences that are significant because they can be most easily managed strategically through training and development. Thus it is usually a distinctive network of competences that are most likely to provide competitive advantage. These distinctive competences are usually also core competences, but core competences are not necessarily distinctive." (Fran Ackermann et al, "Visual Strategy: Strategy Mapping for Public and Nonprofit Organizations", 2014)

"A sustainable, strategic advantage that an organization possesses over its industry rivals." (Andrew Pham et al, "From Business Strategy to Information Technology Roadmap", 2016)

"The unique set of assets, capabilities, positions and environmental circumstances that enable an organisation to consistently out-perform its competitors in its chosen strategic outcomes." (Duncan Angwin & Stephen Cummings, "The Strategy Pathfinder 3rd Ed.", 2017)

"A firm possesses a competitive advantage over its direct competitors when it earns (or has the potential to earn) a persistently higher rate of profit." (Robert M Grant, "Contemporary Strategy Analysis" 10th Ed., 2018)

🚧Project Management: Products (Definitions)

"An output of a process." (Requirements Engineering Qualifications Board, "Standard glossary of terms used in Requirements Engineering", 2011)

"A product is an output of a process." (IQBBA, "Standard glossary of terms used in Software Engineering", 2011)

"An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item. Additional words for products are material and goods. Contrast with result." (Cynthia Stackpole, "PMP Certification All-in-One For Dummies", 2011)

"Also called deliverable or output, the thing that the project produces (physical thing or event)." (Mike Clayton, "Brilliant Project Leader", 2012)

"An input or output, whether tangible or intangible, that can be described in advance, created, and tested." (Paul C Dinsmore et al, "Enterprise Project Governance", 2012)

"An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item. Additional words for products are material and goods. Contrast with result." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

🚧Project Management: Deliverables (Definitions)

"An identifiable, required result of a task. Deliverables usually are part of an overall project completion plan." (Microsoft Corporation, "Microsoft SQL Server 7.0 Data Warehouse Training Kit", 2000)

"Any measurable, tangible, verifiable outcome, result, or item that needs to be produced to complete a project or a phase of a project." (Margaret Y Chu, "Blissful Data ", 2004)

"The tangible or intangible work product from a functional team member." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"A work product completed within a project phase by members of a project thread; the defined output of one or more related IT tasks." (Janice M Roehl-Anderson, "IT Best Practices for Financial Managers", 2010)

"Also called product or output, the thing that the project produces (physical thing or event)." (Mike Clayton, "Brilliant Project Leader", 2012)

"Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project." (For Dummies, "PMP Certification All-in-One For Dummies, 2nd Ed.", 2013)

"Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. Often used more narrowly in reference to an external deliverable, which is a deliverable that is subject to approval by the project sponsor or customer. See also product and result. " (Cynthia Stackpole, "PMP® Certification All-in-One For Dummies®", 2011)

 "Any (work) product that must be delivered to someone other that the (work) product’s author." (Software Quality Assurance)

"Something that must be provided to meet a commitment in a SLA or contract." (ITIL)

🚧Project Management: Project Governance (Definitions)

"Systems and methods by which a program is monitored, managed, and supported by its sponsoring organization." (Project Management Institute, "The Standard for Program Management" 3rd Ed.., 2013)

"A document that describes the systems and methods to be used to monitor, manage, and support a given program, and the responsibilities of specific individuals for ensuring the timely and effective use of those systems and methods." (Project Management Institute, "The Standard for Program Management" 3rd Ed. 2013)

"The alignment of project objectives with the strategy of the larger organization by the project sponsor and project team. A project’s governance is defined by and is required to fit within the larger context of the program or organization sponsoring it, but is separate from organizational governance." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"Project governance helps make sure that a project is executed according to the standards of the organization performing the project. Governance keeps all project activities above board and ethical, and also creates accountability." (Chartered Institute of Building, "Code of Practice for Project Management for Construction and Development" 5th Ed., 2014)

"The framework, functions, and processes that guide project management activities in order to create a unique product, service, or result to meet organizational, strategic, and operational goals." (Project Management Institute, "A Guide to the Project Management Body of Knowledge (PMBOK Guide)", 2017)

"Governance is the framework by which an organization is directed and controlled. Project governance includes, but is not limited to, those areas of organizational governance that are specifically related to project activities." (ISO 21500:2012)

🌁Software Engineering: Validation (Definitions)

"An independent test process whereby the performance of the neural network is tested against the acceptance requirements." (Joseph P Bigus, "Data Mining with Neural Networks: Solving Business Problems from Application Development to Decision Support", 1996)

"Confirmation that the product, as provided (or as it will be provided), will fulfill its intended use. In other words, validation ensures that 'you built the right thing'." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"Confirmation or corroboration of something, such as a business need or an identified opinion or recommendation." (Teri Lund & Susan Barksdale, "10 Steps to Successful Strategic Planning", 2006)

"the process of checking that a system meets the user needs." (Bruce P Douglass, "Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development", 2009)

"The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. Contrast with verification." (Cynthia Stackpole, "PMP® Certification All-in-One For Dummies®", 2011)

"Testing if a development result fulfills the individual requirements for a specific use." (Tilo Linz et al, "Software Testing Foundations" 4th Ed., 2014)

"Determines if the product provides the necessary solution for the intended real-world problem." (Adam Gordon, "Official (ISC)2 Guide to the CISSP CBK" 4th Ed., 2015)

"Validation is the process of verifying that a document or data structure conforms with its schema or schemas." (Robert J Glushko, "The Discipline of Organizing: Professional Edition" 4th Ed, 2016)

"The assurance that a product, service, or result meets the needs of the customer and other identified stakeholders." (Project Management Institute, "A Guide to the Project Management Body of Knowledge (PMBOK® Guide )", 2017)

"The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers." (Jeffrey K Pinto, "Project Management: Achieving Competitive Advantage" 5th Ed., 2018)

 "activity that ensures a new or changed service, process, plan or other deliverable, meets the needs of the business." (ITIL)

"Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled" [ISO 9000]

"Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled." (NIST SP 800-160)

"Confirmation (through the provision of strong, sound, objective evidence) that requirements for a specific intended use or application have been fulfilled." (NIST SP 800-161)

"Confirmation (through the provision of strong, sound, objective evidence) that requirements for a specific intended use or application have been fulfilled (e.g., a trustworthy credential has been presented, or data or information has been formatted in accordance with a defined set of rules, or a specific process has demonstrated that an entity under consideration meets, in all respects, its defined attributes or requirements)." (CNSSI 4009-2015)

"The process of determining that an object or process is acceptable according to a pre-defined set of tests and the results of those tests." (NIST SP 800-152)

"The process of demonstrating that the system under consideration meets in all respects the specification of that system." (INCITS/M1-040211)

🖌️Nir Eyal - Collected Quotes

"Companies leverage two basic pulleys of human behavior to increase the likelihood of an action occuring: the ease of performing an action and the psychological motivation to do it." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"For an infrequent action to become a habit, the user must perceive a high degree of utility, either from gaining pleasure or avoiding pain." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"Like flossing, frequent engagement with a product, especially over a short period of time, increases the likelihood of forming new routines." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"Many innovations fail because consumers irrationally overvalue the old while companies irrationally overvalue the new." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"Reducing the thinking required to take the next action increases the likelihood of the desired behavior occurring unconsciously." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"To change behavior, products must ensure the user feels in control. People must want to use the service, not feel they have to." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014) 

"User habits are a competitive advantage. Products that change customer routines are less susceptible to attacks from other companies." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"Users who continually find value in a product are more likely to tell their friends about it." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014) 

"When designers intentionally trick users into inviting friends or blasting a message to their social networks, they may see some initial growth, but it comes at the expense of users' goodwill and trust. When people discover they've been duped, they vent their frustration and stop using the product." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)

"You'll often find that people's declared preferences - what they say they want - are far different from their revealed preferences - what they actually do." (Nir Eyal, "Hooked: How to Build Habit-Forming Products", 2014)