CEO Executive AssistantNew product development is the function where manufacturing CEOs most commonly get the delegation balance wrong in both directions. Either they stay too involved in development decisions that should belong with R&D, slowing the process and frustrating the engineering team, or they step back entirely and find themselves blindsided by a product launch that misses the market or a capital commitment that has outpaced the business case.
The right model is neither. It is a stage-gate structure where your R&D director and product engineers own development execution within defined investment levels, customer validation responsibility sits with the team closest to the customer problem, and CEO involvement is triggered by investment size, strategic importance, or signals that a development is off track.
This article builds that structure.
Why NPD Delegation Is Different from Other Manufacturing Delegation
New product development involves decisions that are harder to delegate than production or quality control decisions because the stakes are asymmetric and the information is incomplete. A production decision can be evaluated against a clear quality standard. A product development decision at Stage 2 of a gate process involves projections, assumptions, and customer feedback that may or may not hold up.
This creates a temptation for manufacturing CEOs to stay too involved: because the outcomes are uncertain, it feels safer to keep decisions close. The cost is development velocity and engineering team autonomy. The teams that move fastest are the ones that have clear authority within defined guardrails, not the ones waiting for CEO sign-off on every milestone.
The stage-gate framework solves this by creating predictable decision points where CEO involvement is structured, rather than sporadic and reactive.
Defining the Stage-Gate Investment Authority
Your stage-gate process should have defined investment approval authority at each gate, with clear thresholds for when escalation to the CEO is required.
A practical authority structure for a mid-size manufacturer looks like this:
Stage 0 to Stage 1 (Concept Screening to Feasibility): R&D director authority to allocate engineering time and initial materials budget up to a defined amount (typically in the range of $25,000 to $75,000 depending on your business size). No CEO sign-off required for concept exploration and preliminary feasibility work.
Stage 1 to Stage 2 (Feasibility to Development): VP of Engineering or R&D director authority to approve development initiation up to a defined investment level (tooling, prototype materials, lab time). At this stage, a gate review document is prepared and presented to the CEO as an information item, not an approval. CEO can call a pause if there is a strategic concern, but the default is that the R&D director has approved and the project advances.
Stage 2 to Stage 3 (Development to Validation): Gate approval requires CEO sign-off when the cumulative investment exceeds your defined threshold (commonly $150,000 to $500,000 for a mid-size manufacturer) or when the product involves a new market, a new manufacturing process, or a strategic partnership. Below that threshold, your VP of Engineering or Operations approves.
Stage 3 to Stage 4 (Validation to Launch): CEO sign-off required regardless of investment level. This is the commit-to-launch decision, and it belongs at the top of the house.
Document these thresholds explicitly. Revisit them annually as your NPD portfolio and capital capacity evolve.
Customer Validation Responsibility
Customer validation is the step most manufacturing NPD processes execute poorly, and most of the failure is a delegation problem. Either the CEO is the one running customer conversations (which creates dependency and slows the process), or customer validation is done superficially by engineers who are not accountable for the commercial outcome.
The right structure assigns customer validation responsibility to the person who owns the commercial relationship: your VP of Sales or your business development director, in partnership with the R&D team.
Your R&D director owns the technical performance validation: does the product meet the design specifications, and does it perform consistently in the use environment? Your sales or business development lead owns the commercial validation: is this the product the customer actually wants to buy at the price you need to charge?
These two forms of validation should happen in parallel during Stage 2, not sequentially, and both should be complete before you reach the Stage 2 to Stage 3 gate.
The CEO’s role in customer validation is to open doors that your team cannot open themselves. If validating a new product requires a meeting with the purchasing director at your largest customer, you make that introduction. The validation itself is owned by your team.
Product Decisions That Require CEO Involvement
Beyond the investment thresholds defined in your stage-gate authority matrix, certain product decisions require CEO involvement regardless of cost.
New Market Entry. A product designed for a market where you do not currently compete is a strategic entry decision, not a product development decision. Even if the development investment is within your R&D director’s approval authority, the decision to enter a new market belongs at CEO level.
Products That Require New Capital Equipment. When a product concept requires a capital investment in new equipment or a new manufacturing line, the product approval decision and the capital approval decision are effectively linked. These stay at CEO level.
Products With Significant IP Implications. If a new product involves filing for new patents, licensing IP from a third party, or building on technology developed under a customer contract, the IP strategy belongs at CEO level, even if the development work is delegated.
Products That Change Your Customer Concentration. If a new product is being developed primarily for a single customer and would represent more than a defined percentage of your revenue if it succeeds, that concentration risk is a CEO-level strategic consideration.
Platform Products That Affect Multiple Existing Lines. If a new product involves changes to a manufacturing platform or process that affects your existing product lines, the decision to make that change cannot be delegated to the team developing the new product alone.
For a broader view of how to delegate quality and production management alongside product development, see the manufacturing CEO production and quality control framework, which covers how NPD handoffs to production should be structured.
R&D Director Accountability: What They Own and What They Report
Your R&D director should own the NPD portfolio management function completely: tracking which projects are in which stage, managing the engineering resources allocated to development work, and presenting a portfolio review to the CEO and leadership team on a defined cadence.
This includes the authority to:
- Prioritize development projects within the approved portfolio when resource constraints require trade-offs.
- Kill projects that are not meeting stage-gate criteria, without waiting for CEO sign-off to terminate a project that has failed its gate review.
- Adjust development timelines and resource allocations within the approved project scope.
- Engage with customers for technical validation without CEO involvement in routine technical discussions.
Your R&D director should not have authority to:
- Add new projects to the portfolio above their investment approval threshold without CEO approval.
- Commit to customer delivery timelines for new products before the product has cleared the validation gate.
- Authorize manufacturing scale-up spending that was not included in the approved Stage 3 to Stage 4 business case.
The reporting structure supports this accountability: your R&D director presents a monthly NPD portfolio update covering stage status for all active projects, gate decisions made since the last review, resource utilization, and any projects approaching a gate that will require CEO involvement.
Stage-Gate Reviews That Work
Many manufacturing companies have stage-gate processes on paper that do not function as real decision gates in practice. Projects advance through gates without rigorous review. Underperforming projects accumulate in the portfolio because no one has the authority to kill them. CEO gate reviews become rubber stamps because the project team has already committed resources and customer expectations.
The design principles that make stage-gate reviews actually work as decision points:
Pre-read materials go to gate reviewers at least 48 hours in advance. Gate reviews should not be presentations; they should be decision conversations. If the CEO and other gate reviewers are reading the business case for the first time during the meeting, the gate review is not functioning as a real decision point.
The gate has explicit go/kill/hold criteria. Before the project enters a gate review, everyone knows what a pass looks like, what a fail looks like, and what conditions would result in a hold for additional information. Ambiguous criteria lead to advancement of projects that should be killed.
The gate owner has authority to recommend a kill. Your R&D director should be empowered to recommend killing a project at any gate, without it being treated as a failure of their program management. A disciplined kill is a sign that the stage-gate process is working.
CEO gate reviews are time-bounded and focused on the go/no-go decision. You are not redesigning the product at a gate review. You are deciding whether the project meets the criteria to advance to the next stage with the proposed investment. Keep it focused.
Connecting NPD to Supply Chain Early
One of the most expensive mistakes in manufacturing NPD is developing a product that cannot be produced at target cost because the supply chain was not engaged early enough. Your supply chain delegation structure should include a clear expectation that the R&D team engages supply chain on component sourcing, supplier qualification, and cost validation starting at Stage 1, not at Stage 3.
This is a CEO-level expectation to set, not an engineering process detail. If your R&D and supply chain organizations are siloed during development, you will continue to discover supply chain problems at launch. Make cross-functional engagement during development a standard expectation, and hold your R&D director and supply chain director jointly accountable for cost-of-goods accuracy at each gate.
For how to structure supply chain delegation as part of your broader manufacturing leadership model, the manufacturing CEO supply chain oversight playbook covers the accountability structures that support early supply chain engagement in product development.
The Launch Readiness Decision
The decision to launch is always a CEO decision. Your R&D director can tell you the product is validated. Your VP of Sales can tell you the customer demand is real. Your operations VP can tell you the production process is ready. You make the call to launch.
This is not because the CEO is the most technically informed person in the room at this stage. It is because the launch decision commits resources, customer commitments, and organizational energy that no single functional leader can commit alone. The CEO is the accountable executive for the outcome, and the launch decision should reflect that.
Build the stage-gate structure, delegate the development work within it, and show up personally at the gates that matter. That is how manufacturing CEOs drive product innovation without becoming the bottleneck in their own development process.
Related Reading
For further context, explore How Manufacturing CEOs Delegate Capital Expenditure Decisions and How Manufacturing CEOs Delegate Continuous Improvement Programs.