Appendices

A.1 Glossary of Stage-Gate and Development Governance Terms

Approval criteria: The conditions used by decision makers to determine whether a project is sufficiently mature and attractive to receive authorization for its next stage. Criteria may include technical, commercial, financial, operational, regulatory, quality, strategic, and resource requirements.

Assumption: A proposition used in planning or decision making that has not yet been demonstrated conclusively. Good governance distinguishes assumptions from established facts and requires the most consequential assumptions to be tested before major commitments become difficult to reverse.

Authorization: Formal permission to proceed with defined activities, expenditure, resource use, or external commitments. Gate authorization should specify what the project may do rather than simply recording general management support.

Business case: The integrated economic and strategic rationale for a development project. It normally connects customer demand, pricing, revenue, cost, investment, timing, risk, and strategic considerations so management can judge whether continued commitment remains attractive.

Capacity constraint: A resource whose limited availability restricts how many projects the portfolio can execute effectively. Examples include specialist engineers, laboratory facilities, regulatory professionals, pilot equipment, manufacturing engineers, software architects, or experienced program leaders.

Capacity planning: The process of comparing expected project-resource demand with available capability over time. In development governance, capacity planning helps leadership determine whether approved projects can actually be staffed and which initiatives must be sequenced, reduced, or paused.

Commitment: A use of money, people, capacity, reputation, contractual obligation, or another resource that increases the organization’s exposure to a project. Governance is particularly important where commitments are costly or slow to reverse.

Conditional approval: Authorization to proceed despite one or more unresolved requirements, subject to explicit conditions. Effective conditional approvals specify the deficiency, accountable owner, required closure date, and any activities that remain prohibited until the condition is resolved.

Decision authority: The individual or governing body formally empowered to make a defined project decision. Authority should correspond to the size, risk, strategic importance, and irreversibility of the commitment being considered.

Decision log: An authoritative record of important governance decisions. It typically captures the project, gate, decision date, outcome, authorized resources, conditions, exceptions, accountable owners, and next required decision point.

Decision rights: The allocation of authority among project leaders, functional experts, executives, committees, boards, and other participants. Decision rights clarify who recommends, who provides required evidence, who may challenge, who can approve, and who can escalate.

Development governance: The management system used to control how development projects progress, obtain resources, satisfy evidence requirements, and receive authorization. It encompasses stages, gates, decision rights, criteria, review forums, escalation rules, and links to portfolio decisions.

Development pathway: The sequence of stages, gates, evidence standards, and approval requirements applied to a particular category of project. Organizations often maintain different pathways for incremental development, standard projects, major platforms, or high-risk innovation.

Development portfolio: The complete set of active, planned, paused, and sometimes exploratory development initiatives competing for organizational resources. Portfolio governance evaluates projects relative to one another rather than solely on their individual merits.

Development stage: A defined period of work during which a team reduces specified uncertainties and increases project maturity. A stage should have a clear management purpose and culminate in evidence supporting a subsequent decision.

Entry criteria: Conditions that should be satisfied before a project enters a stage. Entry criteria confirm that prerequisites such as prior authorization, defined objectives, essential inputs, ownership, or minimum evidence are in place.

Evidence: Information that supports or challenges a proposition relevant to a development decision. Evidence can include experimental results, customer research, financial analysis, verification data, regulatory feedback, supplier qualification, production trials, or other decision-relevant facts.

Evidence pack: The structured material provided to gate decision makers before a review. A good evidence pack emphasizes the requested decision, applicable criteria, material findings, unresolved risks, changes since the prior gate, resource requirements, and recommendation.

Evidence standard: The level of rigor, representativeness, and confidence expected for a particular gate decision. Evidence standards should generally become stronger as projects mature and the organization’s financial or operational exposure increases.

Exception: An approved deviation from a standard governance requirement. Exceptions should identify the requirement being changed, rationale, risk created, compensating controls where applicable, decision authority, and any subsequent closure requirements.

Exit criteria: The maturity conditions a project is expected to satisfy by the end of a stage before progression can be considered. Exit criteria should describe required outcomes or demonstrated readiness rather than simply completed activities.

Fast-track path: An accelerated governance pathway used when the value of speed justifies compressing normal timing. Fast-tracking may combine reviews, overlap work, or accelerate selected commitments while maintaining explicit authority and risk acceptance.

Feasibility: The degree to which a proposed development concept appears capable of meeting critical technical, commercial, operational, economic, regulatory, and other requirements. Feasibility evidence is usually developed before full-scale commitment.

Funding release: The authorization of financial resources for a defined stage, activity, or commitment. Funding releases can be linked directly to gates so projects receive additional investment only after required evidence has been reviewed.

Gate: A formal decision point separating development stages. A gate determines whether a project may continue, pause, recycle, change direction, or stop and should have explicit consequences for resources and authorization.

Gate criteria: The specific requirements against which a project is evaluated at a gate. Criteria should correspond directly to the management decision being made and reflect the project’s maturity, risk, and expected next-stage commitment.

Gate owner: The individual accountable for maintaining the integrity and operation of a particular gate or gate process. Responsibilities may include ensuring readiness, confirming quorum, enforcing criteria, recording decisions, and tracking conditions.

Gate review: The meeting or formal decision process in which authorized leaders evaluate project evidence against applicable criteria and determine the project’s governance outcome. It should be distinguished from routine project status reporting.

Gate throughput: The number and flow of projects moving through governance decision points over a defined period. Throughput measures can help identify congestion, repeated recycling, scheduling bottlenecks, or unusual concentrations of upcoming decisions.

Governance architecture: The overall structure connecting stages, gates, project pathways, criteria, decision rights, funding releases, review forums, escalation thresholds, and portfolio interfaces. It defines how development decisions operate as an integrated system.

Governance charter: A document defining the mandate and operating rules of a governance forum. It typically addresses scope, authority, membership, quorum, decision rules, escalation, meeting cadence, and relationships with adjacent decision bodies.

Governance health check: A periodic assessment of whether the governance system remains effective. A health check examines decision quality, cycle time, criteria, exceptions, decision rights, portfolio linkage, management behavior, and project outcomes.

Governance pathway: A defined variant of the stage-gate process appropriate to a class of projects. Pathways can differ in stages, approval levels, evidence depth, or review cadence while preserving common decision principles.

Governance tier: A classification representing the level of governance rigor required for a project. Tiers may be based on strategic importance, complexity, investment, risk, regulatory exposure, or other materiality factors.

Hold: A formal decision to suspend normal project progression while preserving the opportunity. A hold should specify permitted activity, ownership, resource treatment, reactivation conditions, and a future review point.

Irreversible commitment: A project decision that is expensive, slow, legally difficult, or strategically damaging to reverse. Examples can include tooling, facilities, public launch announcements, supplier contracts, regulatory submissions, production inventory, or customer commitments.

Kill criteria: Conditions that indicate a project should be stopped because continued investment is no longer justified. Kill criteria may address technical failure, unacceptable economics, strategic misalignment, regulatory barriers, or other fundamental problems.

Launch readiness: The degree to which the product and organization are prepared for commercial release, production, deployment, or customer use. Readiness can include technical, manufacturing, quality, regulatory, supply, service, and commercial dimensions.

Materiality threshold: A predefined level at which a decision, variance, investment, risk, or change requires higher authority or additional governance. Thresholds help delegate routine decisions while preserving escalation for consequential commitments.

Must-pass criteria: Requirements that cannot be offset by strength elsewhere in the project. Failure to satisfy a must-pass criterion should prevent progression unless an explicitly authorized exception mechanism permits otherwise.

Out-of-cycle review: A governance review initiated between scheduled gates because a material event changes the basis of prior approval. Triggers can include major cost increases, technical failure, regulatory changes, strategic shifts, or significant scope expansion.

Portfolio governance: The decision system used to compare development initiatives, set priorities, allocate constrained resources, manage investment trade-offs, and determine which projects should continue, pause, accelerate, rescope, or stop.

Portfolio prioritization: The process of ranking or categorizing projects based on factors such as strategic fit, expected value, risk, evidence maturity, timing, and resource demand. Prioritization supports resource-allocation decisions rather than serving as an end in itself.

Progressive commitment: The principle of increasing organizational exposure gradually as evidence improves. Early stages typically receive smaller, more reversible commitments, while later stages receive greater resources after important uncertainties have been reduced.

Project classification: The process used to assign a development initiative to an appropriate governance pathway or tier. Classification should use explicit criteria and be reconsidered if scope, investment, complexity, or risk changes materially.

Project sponsor: The senior leader who advocates for the project, supports access to resources, and remains accountable for its business rationale. Sponsorship should be distinguished from independent authority to approve every stage of the project.

Quorum: The minimum required participation for a governance forum to make a valid decision. Quorum rules should identify which roles are indispensable and whether formal delegation is permitted.

RACI: A responsibility framework assigning roles as Responsible, Accountable, Consulted, or Informed. In governance design, RACI can clarify activities but should not replace explicit decision-rights definitions for material approvals.

Readiness evidence: Information demonstrating that a project, function, product, or operating capability has reached the maturity required for a particular decision. Readiness should be assessed against defined standards rather than subjective confidence alone.

Recycle: A gate outcome requiring specified additional work or evidence before progression can be approved. Recycling should identify the deficiency clearly and avoid forcing unnecessary repetition of work already accepted.

Redirect: A decision allowing continued investment while materially changing the project’s scope, technical approach, market focus, timing, or other central element. A redirect may require selected evidence or prior approvals to be refreshed.

Residual risk: The risk remaining after available evidence, controls, mitigations, and planned actions are considered. Gate decision makers should understand which residual risks they are accepting when authorizing further commitment.

Resource allocation: The assignment of funding, people, equipment, facilities, management attention, and other constrained capabilities to projects. Effective governance connects formal project approval with the resources required to execute the decision.

Rescope: To change a project’s boundaries, requirements, features, market, investment level, or deliverables in order to improve its value, manage risk, reduce resource demand, or respond to new evidence.

Risk: Exposure to an uncertain event or condition that can affect project value, timing, performance, compliance, or viability. Development governance commonly considers technical, commercial, financial, operational, regulatory, quality, supply, and execution risk.

Risk-adjusted value: An economic view that reflects uncertainty rather than relying solely on a single successful-outcome forecast. It can support comparison of projects whose potential returns and probabilities of success differ materially.

Stage: A bounded period of development activity undertaken to create specified outputs, reduce uncertainty, and increase maturity before the next governance decision. Stages should be designed around meaningful changes in project maturity.

Stage-gate: A development-governance approach in which work progresses through defined stages separated by formal decision gates. The approach supports progressive commitment, evidence-based decisions, and disciplined allocation of resources.

Stop: A formal decision to terminate normal project investment and release associated resources. A stop should also address external commitments, knowledge capture, intellectual property, stakeholder communication, and project closure.

Strategic fit: The degree to which a project advances specific organizational priorities such as strengthening a platform, entering an attractive market, protecting a customer position, developing a capability, or creating a strategic option.

Technical maturity: The degree to which a technology, design, or system has progressed from concept toward demonstrated and integrated performance. Evidence should become increasingly representative of final operating and production conditions as maturity increases.

Threshold criteria: Quantitative or qualitative minimum standards that a project is expected to meet before progression. Examples may include margin, performance, reliability, cost, investment, safety, or schedule requirements.

Validation: Evidence that the resulting product, system, process, or solution satisfies its intended use and relevant user needs under appropriate conditions. Validation addresses whether the organization has developed the right solution for the intended purpose.

Verification: Evidence that specified requirements have been met. Verification generally addresses whether the product, system, software, or component has been developed correctly against documented requirements or specifications.

Zombie project: An initiative that remains nominally active despite lacking sufficient evidence, priority, sponsorship, resources, or forward progress. Zombie projects consume capacity and management attention while avoiding an explicit pause or stop decision.

A.2 Common Acronyms and Abbreviations

R&D — Research and Development: The functions and activities responsible for creating, improving, testing, and maturing technologies, products, processes, or other innovations.

NPD — New Product Development: The end-to-end process used to convert an opportunity or concept into a new product that can be launched and supported commercially.

NPI — New Product Introduction: The activities required to transition a newly developed product into production, deployment, supply, commercialization, and routine operations.

PMO — Project Management Office: A coordinating function that can provide project standards, reporting, planning, governance support, or implementation management across multiple initiatives.

RACI — Responsible, Accountable, Consulted, Informed: A role-mapping framework commonly used to clarify participation in activities, deliverables, and selected governance responsibilities.

KPI — Key Performance Indicator: A measure used to monitor performance against an important operational, development, portfolio, or governance objective.

OKR — Objectives and Key Results: A goal-setting framework connecting qualitative objectives with measurable results. It may be used alongside, but should not replace, project governance criteria.

NPV — Net Present Value: The present value of expected future cash inflows less the present value of expected cash outflows, commonly used to assess investment attractiveness.

IRR — Internal Rate of Return: The discount rate at which an investment’s calculated net present value equals zero, often used as one measure of financial attractiveness.

ROI — Return on Investment: A general measure comparing the financial benefit of an investment with its cost. Calculation conventions should be defined before projects are compared.

CAPEX — Capital Expenditure: Spending on long-lived assets such as facilities, equipment, tooling, infrastructure, or other capitalized investments that may require specific governance approval.

OPEX — Operating Expenditure: Costs generally recognized as operating expenses rather than capital assets, including many forms of labor, services, maintenance, and routine project spending.

FTE — Full-Time Equivalent: A normalized measure of labor capacity representing the workload of one full-time employee, commonly used in resource and portfolio planning.

VOC — Voice of the Customer: Structured evidence concerning customer needs, preferences, problems, priorities, and reactions that can inform requirements and commercial gate criteria.

MVP — Minimum Viable Product: The smallest viable product or feature set designed to test important customer or business assumptions while limiting unnecessary development investment.

PoC — Proof of Concept: An early demonstration intended to establish whether a critical technical, scientific, commercial, or operational idea is feasible enough to justify further work.

TRL — Technology Readiness Level: A maturity scale used in some industries to describe how far a technology has progressed from basic principles toward demonstrated application and deployment.

MRL — Manufacturing Readiness Level: A maturity framework used in some sectors to assess whether manufacturing capabilities, processes, and supply arrangements are sufficiently developed for the intended stage.

V&V — Verification and Validation: Activities used to demonstrate that specified requirements have been met and that the resulting solution satisfies its intended use.

QA — Quality Assurance: The systems and preventive activities used to provide confidence that processes, products, and development practices will meet applicable quality requirements.

QC — Quality Control: Inspection, testing, measurement, and other operational activities used to determine whether outputs conform to defined quality standards.

QMS — Quality Management System: The formal set of policies, processes, responsibilities, records, and controls used to manage quality within an organization.

CAPA — Corrective and Preventive Action: A structured process used in regulated and quality-intensive environments to investigate problems, correct causes, and prevent recurrence.

FMEA — Failure Modes and Effects Analysis: A structured method for identifying potential failure modes, assessing their consequences and causes, and prioritizing risk-reduction actions.

DFMEA — Design Failure Modes and Effects Analysis: An FMEA focused specifically on risks arising from product or system design and its ability to meet intended requirements.

PFMEA — Process Failure Modes and Effects Analysis: An FMEA focused on risks associated with manufacturing, assembly, service, deployment, or other operational processes.

DFM — Design for Manufacturability: The practice of designing products so they can be manufactured reliably, efficiently, and economically using intended production processes.

DFA — Design for Assembly: The practice of simplifying product design and interfaces to improve assembly efficiency, quality, repeatability, and cost.

BOM — Bill of Materials: The structured list of components, materials, subassemblies, quantities, and related information required to build a product or system.

COGS — Cost of Goods Sold: The direct costs associated with producing goods sold by the business. COGS assumptions can materially affect development-program economics.

SKU — Stock Keeping Unit: A distinct product or inventory identifier. Line extensions and product proliferation can increase SKU count and create supply, operational, and portfolio complexity.

SOP — Start of Production or Standard Operating Procedure: An abbreviation with multiple common meanings. In automotive and manufacturing programs it may mean Start of Production; in quality systems it often means Standard Operating Procedure.

APQP — Advanced Product Quality Planning: A structured product and process quality-planning approach widely used in automotive and related manufacturing environments to support development and production readiness.

PPAP — Production Part Approval Process: A formal automotive-industry process used to demonstrate that production processes and suppliers can consistently produce parts meeting defined engineering and quality requirements.

EVT — Engineering Validation Test: A development phase used in some hardware environments to determine whether engineering prototypes satisfy important design and functional requirements.

DVT — Design Validation Test: A phase used in some product-development environments to demonstrate that a more mature design satisfies intended performance and design requirements.

PVT — Production Validation Test: A phase used in some hardware environments to demonstrate that the intended production process can manufacture the product at the required quality and performance.

GMP — Good Manufacturing Practice: Regulatory and quality requirements governing manufacturing and control practices in industries such as pharmaceuticals, biotechnology, medical products, and certain food products.

GxP — Good Practice Requirements: A collective term for regulated good-practice frameworks such as GMP, GCP, and GLP that govern activities in life sciences and related sectors.

FDA — U.S. Food and Drug Administration: The United States regulatory agency responsible for oversight of products including drugs, medical devices, biologics, food, and certain other regulated categories.

EMA — European Medicines Agency: A European Union agency responsible for scientific evaluation and supervision of medicines within its regulatory mandate.

ISO — International Organization for Standardization: An independent international standards organization whose standards can influence quality, safety, management systems, product requirements, and development practices across industries.

IEC — International Electrotechnical Commission: An international standards organization focused on electrical, electronic, and related technologies, including standards relevant to product development and safety.

CE — Conformité Européenne: The marking used for certain products placed on the European Economic Area market to indicate conformity with applicable European requirements.

DHF — Design History File: In medical-device environments, documentation demonstrating that a device was developed in accordance with the approved design plan and applicable design-control requirements.

DMR — Device Master Record: In medical-device contexts, the collection of specifications and procedures needed to manufacture, package, label, test, and maintain a particular finished device.

UAT — User Acceptance Testing: Testing performed to determine whether a system, application, or solution satisfies defined user and business requirements sufficiently for acceptance or deployment.

ERP — Enterprise Resource Planning: An integrated business system used to manage information and transactions across areas such as finance, procurement, inventory, manufacturing, and supply chain.

PLM — Product Lifecycle Management: The processes and systems used to manage product information, configurations, requirements, changes, and related data throughout the product lifecycle.

S&OP — Sales and Operations Planning: A cross-functional planning process that aligns expected demand, supply capability, inventory, capacity, and financial objectives and can affect launch and portfolio timing decisions.