Define
Align the product opportunity, users, stakeholders, use cases, requirements, interfaces, constraints, assumptions, and success criteria.
Product-development process
A Development Process Built Around Learning and Risk.
I tailor the work to product maturity, uncertainty, and consequence of failure. A focused review may use only a few stages; a full program can carry the sequence from definition through production improvement.
Shared product brief and requirements baseline
Diagnose
Identify the physics, failure modes, sensitivities, risks, and unknowns that can change the development path.
Generate
Develop credible architectures, run first-order calculations, compare tradeoffs, and preserve the basis for concept selection.
Develop
Resolve CAD, calculations, tolerances, materials, processes, purchased components, assembly, service, and documentation.
Prototype
Build around the questions most capable of invalidating the product, then use the result to improve the next iteration.
Validate
Connect requirements to tests, review failures, implement corrective action, and repeat critical verification.
Release
Prepare drawings, BOM structure, supplier handoff, inspection requirements, pilot-build support, and change control.
Improve
Use production, service, supplier, cost, and field feedback to prioritize the next product improvements.
The process exists to create clarity, accelerate useful learning, and keep avoidable cost from moving downstream. I use the smallest set of reviews and deliverables that the product risk justifies.
Entry point
A useful first review starts with evidence.
A non-confidential summary, the decision blocking progress, current constraints, and available requirements, CAD, prototypes, tests, or supplier feedback are enough to frame the next step.
Does every engagement use all eight stages?
No. I tailor the sequence to maturity, risk, evidence, and the decision required.
Can the work fit an existing development process?
Yes. Outputs and reviews can map into established gates and configuration control.
How is scope controlled?
The engagement starts with defined decisions, outputs, assumptions, responsibilities, and review points.
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