^{Defining the problem}

^{Pins down exactly what needs solving and why it matters. This means writing clear objectives and identifying every constraint up front : budget, timeline, available materials, performance targets, safety codes, and user needs. A well-defined problem prevents wasted effort later, because a vague problem statement produces a vague solution.}

^{I define requirements that are traceable and verifiable, so every one can be tested later and nothing essential is left ambiguous at the next stage : the target is then measurable rather than vague.
‍
From our problem definition I'm able to surface constraints early :  cost, manufacturability, and compliance ( before they become expensive surprises downstream). The details  and limitations will remain accessible  for us to consult or iterate throughout the process in a format thay can be archived.}

^{Research and gather information}

^{Investigate what already exists before inventing anything. Study existing products, prior solutions, relevant standards, material properties, and the failure modes of similar designs. The goal is to learn from what has already been tried so you do not repeat known mistakes or reinvent a solved problem.}

<sup>Researching often stops at market research but I don't !

By studying failure modes of similar designs before committing to an approach, mistakes are stopped from being  repeated and can be anticipated. I pull from materials data and manufacturing standards to ground decisions in evidence rather than assumption.</sup>

^{I generate concepts with manufacturability in mind from the first sketch, applying DFM and DFA thinking so ideas are not just clever but actually buildable at scale. From there, structured trade studies and decision matrices can be used to compare options objectively across cost, manufacturability, and performance, so the chosen concept is defensible rather than a matter of preference.}

^{Brainstorm and generate solutions}

^{Produce a wide range of possible concepts (Quantity matters here). Only then can the concepts be  narrowed   down by judging each against the requirements and constraints defined in step one.}

^Prototyping

Turn the chosen concept into a physical or digital model you can actually examine. A prototype makes the idea tangible and exposes problems that are invisible on paper. It can range from a rough proof-of-concept to a near-final representation, depending on what question you are trying to answer.

^{I design and fabricate custom fixtures and prototypes that produce repeatable, reliable results, so the model actually answers the engineering question instead of introducing new variables.}

^{I build and execute test protocols that translate requirements into measurable validation, and I apply statistical analysis so conclusions are backed by data, not impressions. From there, root-cause investigations and drive corrective actions through FMEA and CAPA, show us clearly what iteration is needed to removes the actual source of failure rather than masking the symptom.}

^{Test and evaluate}
‍

^{Subject the prototype to realistic conditions and measure how it performs against the requirements. This is where assumptions get checked against reality: does it hold the load, fit the assembly, survive the cycles, meet the spec.
Use what testing revealed to refine the design, then build and test again. This loop is the heart of engineering — almost no design is right on the first attempt. Each cycle moves the solution closer to meeting all requirements reliably.}