Frame the product
Align users, business goals, product requirements, interfaces, constraints, unknowns, and decision criteria before detail work begins.
From product opportunity to production reality
Product Design and Development for Physical Products
I lead the mechanical development of physical products from early definition and architecture through detailed design, prototypes, validation, and manufacturing launch.
Signals this work is needed
- The product opportunity is compelling, but user needs, requirements, and technical boundaries are not yet aligned.
- Industrial-design intent needs a feasible mechanical architecture, robust interfaces, and a credible manufacturing path.
- A promising concept needs feasibility screening before substantial CAD, tooling, or supplier commitment.
- A prototype works, but remains fragile, inconsistent, difficult to assemble, hard to service, or unsuitable for production.
- An established product needs a new platform, variant, performance improvement, or cost and reliability redesign.
- An internal team needs experienced product-development capacity without adding a permanent role.
What I evaluate
- User needs, use cases, product goals, operating states, success criteria, and non-negotiable constraints
- Product architecture, technology choices, interfaces, packaging, ergonomics, and industrial-design integration
- Loads, motion, thermal or fluid behavior, environments, misuse, safety, reliability, and failure modes
- Materials, processes, part count, assembly sequence, service access, product-family strategy, and sustainability implications
- Suppliers, inspection, purchased components, tolerance accumulation, cost drivers, and schedule risks
- The smallest prototype and validation plan that can answer the most consequential open questions
Approach
A practical path from uncertainty to a buildable result.
Create and compare architectures
Develop credible product and mechanical directions, test feasibility with first-order analysis, and make the tradeoffs visible.
Design the complete system
Resolve form, fit, function, mechanisms, packaging, materials, CAD, tolerances, assembly, service, and supplier inputs at the right level of detail.
Prototype, validate, and launch
Build around the highest risks, correct the design from test results, and prepare the engineering definition for suppliers, pilot builds, and release.
Typical deliverables
- Product brief, use cases, requirements, and interface definition
- Architecture concepts, feasibility calculations, prototypes, and trade studies
- Mechanical layouts, product surfaces, parametric CAD, and detailed assemblies
- Material, process, fastening, sealing, and purchased-component recommendations
- Tolerance analysis, DFM/DFA findings, test plans, and corrective iterations
- Drawings, BOM structure, supplier-review packages, inspection criteria, and validation plans
Engineering considerations
- User experience, industrial design, engineering, manufacturing, inspection, and service are connected design inputs.
- Functional interfaces and tolerance chains are resolved before drawing release.
- Safety-critical assumptions and unresolved risks remain visible until testing or analysis closes them.
- Cost includes tooling, labor, yield, quality, service, supply risk, and change exposure—not only piece price.
- Prototypes are built to answer specific questions, not to create false confidence.
A productive fit
- A physical product needs architecture, detailed design, prototype learning, production readiness, or senior ownership across several stages.
- The team values product judgment, documented tradeoffs, technical depth, production thinking, and direct collaboration.
- Industrial design, electrical, manufacturing, test, business, and supplier contributors can engage at the points their input matters.
Usually not a fit
- The primary need is brand or styling work without mechanical engineering scope.
- The request is for staffing placement rather than ownership of a defined product outcome.
- The program expects unsupported performance, certification, cost, or schedule promises.
Questions
Practical details before the first review.
Can you join a product already in development?
Yes. I review the product goals, requirements, CAD, prototypes, test results, supplier feedback, and open decisions, then define the smallest workstream that can materially move the product.
Can the engagement cover concept through production release?
Yes, when the scope and team support it. I tailor the sequence and documentation to product maturity and risk instead of forcing every program through the same process.
Do you replace an industrial designer?
No. I can develop mechanically driven product geometry and work directly with industrial designers, but dedicated styling, brand language, and user-research programs should remain with the appropriate specialist.
What is enough for an initial review?
A non-confidential product summary, current stage, primary challenge, timing, known constraints, and available requirements, CAD, hardware, or test results is enough to begin.
Direct senior involvement
Turn the product decision into a clear next step.
Share a non-confidential summary, the current stage, and the outcome the team needs.
Discuss Your Project