Evaluate the path or test the behavior
Make the next design decision with evidence.
When the technical path is unclear, a feasibility study brings the options and constraints into focus. When behavior or integration remains uncertain, a focused prototype puts the critical question to the test.
Explore the two paths01 / Feasibility study
Find the path worth pursuing before committing.
Before committing to a broader design, examine the technical uncertainty that could change it. A bounded study can compare approaches, expose constraints, and identify what still needs to be tested.
Frame the question
Focus the study on the objective, interfaces, and constraints that matter to the next decision.
Examine the options
Evaluate candidate architectures, component choices, or a critical trade-off with the level of analysis the scope requires.
Leave usable findings
Document assumptions, evidence, limitations, and recommended next steps—even if the answer is to change course.
02 / Prototype
Build the part that answers the question.
Some design questions depend on how components interact, not just on their individual specifications. A prototype tests those interactions under defined conditions, exposing behavior and integration issues that analysis alone may not settle.
Test a critical behavior
For example, observe a power path, sensor interface, control response, or firmware-to-board interaction.
Bring interfaces into view
Expose electrical, software, packaging, and test dependencies early enough to inform the next design pass.
Carry the learning forward
Review what worked against the test criteria and record open issues, changes, and next steps appropriate to the scope.
Where to start
The work should fit the uncertainty.
Neither path is a required package. Start with the question the product needs answered, then scope the engineering that can answer it.