Appendices

A.1 Glossary of R&D Operating Model Terms

The following terms describe the organizational structures, governance mechanisms, development processes, resource-management practices, and performance concepts most commonly encountered in R&D operating model work. Where a term has several possible meanings, the definition emphasizes how it is used when designing or managing the R&D system.

• Accountability: Clear ownership of an outcome, decision, or continuing responsibility by a defined role. Accountability should normally rest with one identifiable owner even when many functions contribute evidence, resources, or execution support.
• Adjacent innovation: Innovation that extends the company beyond its established core into new customer segments, technologies, applications, channels, or business models while still building on meaningful existing capabilities or market positions.
• Architecture: The fundamental structure of a product, platform, technology system, or solution, including major components, interfaces, design rules, and dependencies. Architecture decisions often have consequences across several development programs.
• Business-unit R&D: Research or development resources located primarily within a particular business, product division, or commercial unit and oriented toward that unit’s customers, portfolio priorities, economics, and delivery commitments.
• Capability: A combination of expertise, people, methods, tools, facilities, data, and organizational know-how that enables R&D to perform a defined type of work, such as systems engineering, formulation, validation, or computational modeling.
• Capacity: The amount of work a resource or capability can realistically support over a period. Capacity may refer to people, specific skills, laboratories, equipment, pilot facilities, external providers, or other development constraints.
• Center of excellence: An organizational unit with a defined mandate to build, steward, and provide a specialized capability across a broader enterprise. A genuine center of excellence normally owns methods, expertise development, and relevant technical standards.
• Central R&D: Research or development resources managed at the corporate, enterprise, or divisional level rather than within individual business units. Central R&D commonly supports shared technologies, long-horizon research, standards, and scarce expertise.
• Change control: The structured process for evaluating, approving, documenting, and implementing changes to requirements, designs, configurations, processes, or other controlled development elements after an agreed baseline has been established.
• Commercialization: The cross-functional work required to convert a developed product or technology into a market-ready offering, including launch preparation, manufacturing readiness, supply availability, pricing, channel preparation, training, and customer support.
• Core innovation: R&D activity directed primarily toward strengthening existing products, platforms, technologies, markets, or customers. Core programs generally operate with lower uncertainty and shorter pathways to economic impact than adjacent or breakthrough initiatives.
• Cross-functional interface: A recurring point of interaction between R&D and another function, or between technical disciplines, where decisions, information, responsibilities, or work products must cross organizational boundaries for development to progress.
• Decision gate: A formal point in a development or investment process at which an authorized role or governance forum determines whether work should proceed, stop, pause, change direction, or receive additional resources.
• Decision owner: The individual role with final authority for a defined decision within established limits. The decision owner may require recommendations or approvals from specific technical or control functions but remains accountable for closure.
• Decision rights: Explicit rules defining which roles or forums may make particular decisions, which parties must provide input or approval, and which conditions require a decision to be escalated to higher authority.
• Development model: The end-to-end structure through which work progresses from research or concept through development, validation, transfer, and launch, including phases, decision points, functional interfaces, evidence requirements, and ownership transitions.
• Development pathway: A defined version of the development process appropriate to a particular category of program. Pathways may vary in governance intensity, documentation, evidence, or approval levels according to risk and complexity.
• Design authority: The role or body with formal authority over specified architectural or technical design decisions. Design authority is commonly used where consistency, safety, configuration integrity, or platform-wide consequences require independent technical control.
• Design freeze: A defined point at which a design or major portion of it becomes sufficiently mature that further changes require formal evaluation and control. Design freeze does not necessarily mean that no future changes are permitted.
• Design transfer: The controlled transition of a developed design, associated specifications, processes, evidence, and responsibilities into manufacturing, operations, another development organization, or another party responsible for producing or sustaining the product.
• Duplicated effort: Work performed independently in more than one program, site, or organizational unit without sufficient strategic justification. Duplication may involve technologies, testing, software, methods, product variants, facilities, or specialized capabilities.
• Embedded capability: A specialist capability positioned directly within a business, product, platform, or program team rather than provided primarily through a central pool. Embedding generally increases proximity and responsiveness but may reduce pooling efficiency.
• Entry criteria: Conditions that should be satisfied before a program begins a development phase or major activity. Entry criteria help prevent teams from starting work before essential decisions, inputs, resources, or preceding evidence are available.
• Escalation: The deliberate movement of an issue or decision to a higher or different authority because defined thresholds have been exceeded, delegated roles cannot resolve the matter, or consequences extend beyond existing authority.
• Exit criteria: Evidence or conditions that must be demonstrated before a development phase can be considered complete and the program may proceed, transfer responsibility, or seek approval for the next commitment.
• External partner: An organization outside the company that performs or supports R&D-related work. Examples include engineering firms, contract laboratories, research organizations, suppliers, universities, technology partners, and manufacturing-development providers.
• Federated model: An organization design in which businesses, sites, or regions retain meaningful autonomy while selected capabilities, platforms, standards, governance mechanisms, or technical responsibilities are coordinated or owned centrally.
• Functional model: An organization structure in which R&D personnel are grouped primarily by discipline or technical function. Functional models generally strengthen expertise development and standards but require mechanisms for integration across development programs.
• Gate criteria: The specific evidence, conditions, and decision standards used at a formal stage-gate. Criteria should become more demanding as technical evidence matures and financial or operational commitments become less reversible.
• Governance: The system of roles, forums, decision rights, criteria, escalation mechanisms, and review cadences through which leadership directs R&D, allocates resources, manages risk, and exercises appropriate organizational control.
• Handoff: A transition in which information, work products, accountability, or operational responsibility passes from one role, function, development phase, site, or legal entity to another. Effective handoffs use explicit readiness criteria.
• Innovation horizon: A category describing the strategic distance, uncertainty, or expected time to impact of an innovation investment. Common horizons distinguish core improvements, adjacent growth, and longer-term or breakthrough opportunities.
• Integration: The process of combining organizational units, capabilities, development programs, governance mechanisms, sites, or processes so they can operate coherently. In acquisitions, integration should be aligned with the transaction’s value-creation thesis.
• Joint venture: A jointly owned or controlled business arrangement through which two or more parties pursue defined objectives. R&D joint ventures often require explicit rules for funding, intellectual property, shared capabilities, and reserved decisions.
• Laboratory network: The set of laboratories and related technical facilities through which an organization performs research, testing, validation, application development, or other specialized work. Network design defines differentiated roles and interdependencies among locations.
• Leading indicator: A measure that provides early evidence of likely future performance. Examples include unresolved technical risks, resource gaps, testing queues, or requirement instability that may precede later schedule or quality outcomes.
• Matrix organization: An organization in which individuals have meaningful responsibilities to more than one management dimension, commonly a technical function and a program, product, platform, business, or region. Clear priority-setting rules are essential.
• Milestone: A defined point in a development program indicating achievement of a material outcome, completion of required evidence, or readiness for a significant decision, commitment, or transfer to another phase.
• Operating cadence: The recurring rhythm through which management reviews information and makes decisions. Cadences can include annual planning, quarterly portfolio reviews, monthly operating reviews, stage-gates, and shorter program-level routines.
• Operating model: The integrated system defining how an organization gets work done, including structure, roles, decision rights, governance, resources, processes, interfaces, metrics, and management routines required to execute strategy.
• Operating model requirement: A capability or characteristic that the future R&D operating model must provide in order to support business strategy. Requirements should describe needed outcomes rather than prematurely specifying organizational solutions.
• Platform: A shared technical foundation, architecture, technology, product system, or reusable set of components that supports multiple products or programs. Platform governance balances reuse and integrity against product-specific needs.
• Portfolio: The complete set of material R&D initiatives competing for strategic attention, funding, and technical resources. A portfolio may include development programs, research initiatives, platform work, sustaining engineering, and mandatory commitments.
• Portfolio governance: The decision mechanisms through which management starts, funds, prioritizes, accelerates, pauses, redirects, or stops R&D programs and resolves resource trade-offs across the overall portfolio.
• Portfolio segmentation: The classification of programs into meaningful categories so that initiatives with different strategic purposes, uncertainty, risk, or development characteristics can be governed and evaluated using appropriate criteria.
• Program: A coordinated body of R&D work intended to achieve a defined technical, product, platform, or business outcome. Programs typically integrate several workstreams and consume resources from multiple capabilities or functions.
• Program leader: The role accountable for integrating work across the program, managing delivery, surfacing risks, and coordinating decisions. The program leader may not directly control all functional resources required to deliver the outcome.
• R&D productivity: The relationship between resources consumed and meaningful innovation or development outcomes produced. Productivity should be assessed carefully because simple activity counts may not reflect value, technical complexity, or risk reduction.
• R&D strategy: The set of choices defining how research and development will support business strategy, including priority technologies, innovation domains, capability investments, and the role R&D is expected to play in competitive advantage.
• Resource allocation: The process of assigning people, technical skills, funding, laboratories, equipment, and external capacity to programs or activities. Effective allocation links portfolio priorities directly to changes in resource commitments.
• Research-to-development transfer: The transition through which a technology, scientific finding, or concept moves from exploratory research into a development environment requiring greater reproducibility, documentation, defined requirements, and delivery accountability.
• Reserved matter: A decision that cannot be made solely by normal operating management because governing documents reserve authority to a board, shareholder, parent organization, or other specified body. Reserved matters are common in joint ventures.
• Risk-based governance: A governance approach in which review intensity, approval authority, documentation, or evidence varies according to the consequence, uncertainty, complexity, and reversibility of the decision or program involved.
• Role charter: A concise document defining why a role exists, its principal responsibilities, decision rights, resource authority, critical interfaces, and success measures. Role charters are especially useful for cross-functional or matrix positions.
• Shared capability: Expertise, equipment, facilities, systems, or technical services intentionally used by several business units or programs rather than replicated within each one. Shared capabilities require explicit access and prioritization mechanisms.
• Site charter: A clear definition of an R&D site’s mission, capabilities, portfolio or platform responsibilities, customers, assets, decision authority, and intended role within the broader global technical network.
• Stage-gate: A structured development approach in which work progresses through defined phases separated by formal decisions based on evidence. Effective stage-gates vary requirements according to risk and avoid turning routine status reviews into approvals.
• Strategic alignment: The degree to which R&D priorities, investments, capabilities, programs, and resource allocation support the organization’s stated business and innovation priorities rather than operating independently from them.
• Technical authority: Formal authority exercised by an appropriately qualified technical role over specified standards, risks, architectures, methods, or exceptions. Technical authority should be distinguished from general management authority and informal expert influence.
• Technical risk: Uncertainty that a technology, design, process, or system will fail to achieve required performance, safety, reliability, manufacturability, regulatory, or other technical outcomes within acceptable constraints.
• Technology platform: A reusable technical foundation that can support multiple products or applications. Platform operating models define ownership of architecture, roadmaps, standards, interfaces, releases, and exceptions requested by individual product programs.
• Target operating model: The defined future-state configuration of organization, roles, governance, decision rights, resources, processes, interfaces, metrics, and management routines that leadership intends to implement.
• Throughput: The rate at which useful work or development outcomes move through a system. Throughput differs from utilization because maximizing local resource usage can increase queues and reduce end-to-end development speed.
• Transfer readiness: The condition in which a product, technology, design, or process has sufficient evidence, documentation, capability, and resolved ownership to be accepted by the organization or party responsible for the next phase.
• Value stream: The connected sequence of activities and decisions required to produce an outcome for a customer or business. A value-stream perspective emphasizes end-to-end flow rather than optimization of individual functions.
• Work in progress: The number or volume of initiatives that have started but are not complete. Excessive work in progress can fragment resources, increase queues, lengthen cycle times, and conceal portfolio overcommitment.

   

A.2 Common Acronyms and Abbreviations

Acronyms vary substantially by industry and company. The list below includes abbreviations that commonly appear in R&D organization design, product development, governance, resource planning, engineering, quality, and transformation work. Teams should define any organization-specific terms at the beginning of an engagement rather than assume that all participants use an acronym identically.

• AI — Artificial Intelligence: Technologies enabling computer systems to perform tasks involving prediction, reasoning, generation, classification, optimization, or other capabilities traditionally associated with human intelligence.
• BU — Business Unit: A defined organizational segment with responsibility for a market, product portfolio, customer group, geography, or combination of these, often with its own financial accountability.
• CAPA — Corrective and Preventive Action: A structured quality process for investigating identified problems, correcting their causes, and taking action intended to prevent recurrence or comparable future failures.
• CAPEX — Capital Expenditure: Spending on assets expected to provide benefits over multiple periods, including major laboratory equipment, test facilities, pilot plants, buildings, or other R&D infrastructure.
• CCB — Change Control Board: A governance body that evaluates and approves defined changes to controlled products, systems, architectures, configurations, or program baselines.
• CD — Corporate Development: The function commonly responsible for mergers, acquisitions, divestitures, joint ventures, strategic investments, and other transactions that can materially affect the R&D organization or portfolio.
• CoE — Center of Excellence: A designated organizational unit responsible for developing and stewarding specialized expertise, practices, standards, or technical capabilities for broader use across the enterprise.
• COGS — Cost of Goods Sold: Direct costs associated with producing goods or delivering products. R&D decisions can influence COGS through design, materials, architecture, manufacturing processes, and supplier choices.
• CMO — Contract Manufacturing Organization: An external organization that manufactures products or components under contract and may participate in development transfer, process validation, scale-up, or related technical activities.
• CRO — Contract Research Organization: An external organization providing research or development services, especially common in life sciences for laboratory, preclinical, clinical, data, or regulatory-support activities.
• CTO — Chief Technology Officer: A senior executive responsible for technology strategy, technical capabilities, architecture, innovation, or related responsibilities, with the exact mandate varying substantially across companies.
• CTQ — Critical to Quality: A product, process, or service characteristic that must meet defined requirements because it materially affects quality, customer needs, safety, performance, or compliance.
• DFM — Design for Manufacturability: The practice of incorporating manufacturing considerations into product design so that the resulting product can be produced reliably, economically, and at the required scale.
• DFMEA — Design Failure Mode and Effects Analysis: A structured method for identifying potential design failure modes, evaluating their consequences and causes, and prioritizing mitigation actions during development.
• DFX — Design for X: A family of methods for designing products with explicit consideration of attributes such as manufacturing, assembly, reliability, serviceability, cost, sustainability, or testability.
• DOE — Design of Experiments: A structured statistical approach for planning experiments so that teams can understand relationships among variables, test hypotheses efficiently, and identify drivers of performance.
• E2E — End to End: A perspective covering the complete flow of work across functions or development phases rather than optimizing one isolated activity, team, or organizational boundary.
• EBITDA — Earnings Before Interest, Taxes, Depreciation, and Amortization: A widely used financial performance measure that may influence R&D investment constraints and near-term portfolio trade-offs.
• ECO — Engineering Change Order: A formal authorization documenting an approved engineering change, typically identifying affected configurations, documentation, implementation requirements, and effective timing.
• ECR — Engineering Change Request: A formal proposal to evaluate a potential engineering change before it is approved for implementation, often preceding an engineering change order.
• ERP — Enterprise Resource Planning: Enterprise software used to manage financial, procurement, supply, inventory, workforce, and other operational data that may support R&D planning or resource management.
• FMEA — Failure Mode and Effects Analysis: A structured method for identifying potential failures, analyzing causes and consequences, and prioritizing actions to reduce technical or process risk.
• FTE — Full-Time Equivalent: A standardized measure of labor capacity representing the workload of one full-time person over a defined period, commonly used in R&D resource planning.
• IP — Intellectual Property: Legally protected or proprietary knowledge and rights, including patents, trade secrets, copyrights, designs, data, and know-how relevant to R&D and technology development.
• JV — Joint Venture: A business arrangement jointly owned or controlled by two or more parties, often governed through agreed funding, decision, intellectual-property, and operating provisions.
• KPI — Key Performance Indicator: A measure selected because it provides management with important evidence about performance, risk, capacity, portfolio health, development flow, or another decision-relevant outcome.
• NPI — New Product Introduction: The coordinated process of developing and introducing a new product into production and the market, often spanning engineering, operations, quality, supply chain, and commercial functions.
• NPV — Net Present Value: The present value of expected future cash flows after accounting for investment and the time value of money, sometimes used to compare R&D investment alternatives.
• OEE — Overall Equipment Effectiveness: A measure combining equipment availability, performance, and quality to assess productive effectiveness, particularly relevant to manufacturing and selected pilot or technical facilities.
• OKR — Objectives and Key Results: A goal-setting framework that combines defined objectives with measurable results used to assess progress, sometimes applied to R&D teams, programs, or transformation initiatives.
• OPEX — Operating Expenditure: Costs incurred through ongoing operations, including many categories of labor, external services, supplies, and recurring R&D expenses.
• P&L — Profit and Loss: A statement or management accountability covering revenues, expenses, and profit. Business-unit R&D priorities are frequently influenced by the P&L responsibilities of business leadership.
• PLM — Product Lifecycle Management: Processes and systems used to manage product information, configuration, documentation, changes, and lifecycle data from development through production and support.
• PMO — Program Management Office: A team that coordinates planning, governance, reporting, dependencies, risks, and implementation activities for a major program, transformation, or portfolio of related work.
• PPAP — Production Part Approval Process: A structured process, common in automotive and related industries, for demonstrating that suppliers and production processes can consistently meet specified requirements.
• QA — Quality Assurance: Activities and systems intended to provide confidence that development and operational processes are capable of consistently meeting defined quality and compliance requirements.
• QC — Quality Control: Inspection, testing, measurement, or other activities used to determine whether products, materials, processes, or outputs conform to specified requirements.
• QMS — Quality Management System: The formal system of policies, processes, procedures, responsibilities, and controls through which an organization manages quality and relevant compliance obligations.
• RA — Regulatory Affairs: The function responsible for regulatory strategy, submissions, interactions with authorities, interpretation of requirements, and other activities necessary to obtain and maintain market authorization.
• RACI — Responsible, Accountable, Consulted, Informed: A responsibility-mapping framework used to clarify participation in activities or decisions. It should be applied selectively because overly detailed RACI charts can create complexity.
• R&D — Research and Development: The organizational activities through which companies create scientific knowledge, technologies, products, platforms, software, processes, or other innovations and develop them toward practical use.
• RFP — Request for Proposal: A formal document inviting potential external providers to propose an approach, staffing model, commercial terms, or solution for a defined project or service requirement.
• ROI — Return on Investment: A measure comparing economic benefit with the investment required to generate it. ROI may inform portfolio decisions but can be difficult to estimate for highly uncertain research.
• RPN — Risk Priority Number: A numerical risk-ranking measure often associated with FMEA methods, typically derived from ratings such as severity, occurrence, and detection.
• SKU — Stock Keeping Unit: A distinct product or variant tracked separately for inventory and commercial purposes. Excessive SKU proliferation can create significant engineering, testing, supply-chain, and sustaining-development complexity.
• SME — Subject-Matter Expert: An individual with deep knowledge in a particular technical, industry, functional, or regulatory domain who provides specialized judgment to programs, governance bodies, or project teams.
• SOP — Standard Operating Procedure: A controlled instruction describing how a recurring activity should be performed to achieve consistency, quality, safety, compliance, or other operating requirements.
• SOW — Statement of Work: A document defining services or project work to be performed by an external or internal party, typically including scope, deliverables, responsibilities, timing, and commercial provisions.
• TOM — Target Operating Model: The defined future-state design for how an organization should operate, including structure, roles, governance, decision rights, processes, resources, metrics, and management routines.
• TRL — Technology Readiness Level: A maturity scale used in several industries to describe how far a technology has progressed from early concept toward demonstrated and deployable application.
• TTM — Time to Market: The elapsed time required to move an opportunity, concept, or development program to commercial availability, with the precise starting point varying by organization.
• UX — User Experience: The overall experience a person has when interacting with a product, system, or service, including usability, accessibility, usefulness, and other dimensions relevant to product development.
• V&V — Verification and Validation: Related but distinct activities used to demonstrate that outputs meet specified requirements and that the resulting product or system fulfills its intended use or need.
• VOC — Voice of the Customer: Structured information about customer needs, expectations, preferences, and problems used to inform product requirements, prioritization, design choices, and innovation decisions.
• WIP — Work in Progress: Development work that has been started but is not complete. High WIP can increase queues, context switching, resource fragmentation, and cycle time across the R&D system.