Case supporting the view. The operations method has real economic consequences — unit cost, flexibility, quality consistency, capacity — that shape what the firm can profitably sell. Designing a product that the firm's method cannot produce efficiently builds in cost disadvantage from day one. Firms with flow production should design products that fit flow (standardised, modular, high-volume-friendly); firms with job production should design products that fit job (bespoke, high-value, low-volume). Designing a product that fights the method produces operational problems the market ultimately sees in price, quality or availability.
Case against the view. Products should be designed around what customers want, not what the factory wants to produce. A firm that designs around the method risks producing products optimised for its operations convenience but not for customer need — and losing to competitors who design around the customer and then adapt operations. The dominant modern practice is customer-centric design — understand what customers want and then figure out how to produce it; the operations method should serve the product strategy, not constrain it. Several famous innovations (Toyota Production System, Apple's product design, Dell's build-to-order) came from re-thinking operations to serve a product-strategy ambition that existing operations could not deliver.
Case for a middle view. Product and operations should be designed TOGETHER, with each informing the other. The firm cannot design products in a vacuum (ignoring operational reality produces unprofitable products); it cannot design operations in a vacuum (ignoring customer need produces products that fail commercially). The best firms iterate between product design and operations design, trying to converge on a combination that serves customers at a cost the firm can profitably produce.
Reasoned judgement. I partly disagree with the view. Operations method should be an input to product design (realistic constraints), not the dominant driver (which produces operationally-optimised products customers don't want). The right practice is iterative — design the product around what customers want, check against operational feasibility, iterate until a profitable combination emerges. The strongest statement is: product and operations should be designed together, with customer need as the primary input and operational feasibility as a real constraint. 'Design the product around the method' makes operations the primary driver, which produces products that fit the factory but not the customer; the modern practice treats customer need as primary and adapts operations (often with significant investment) to deliver it.