How I work
Hardware prototyping & engineering
I like seeing an idea take physical form.
I’ve taken ideas into physical prototypes, and I enjoy that part of the work. Once something is in front of you, you can handle it, see how the parts fit, and find out whether it behaves as expected. I use what I learn to decide what to change next.
Know what you’re testing
I start by deciding what I need to learn from the prototype. It might be whether a component fits, whether someone can reach a connection, or whether an assembly does what it needs to do. That question determines what I build first.
I decide what to look for before the test. I want to know what would confirm the design works and what would tell me it needs to change. It keeps the test focused and makes the result easier to act on.
Think about assembly
I look at the space each component needs and how the parts will come together. Connections need to be accessible. Someone may also need to take the assembly apart later to inspect a component or replace it.
The enclosure illustration shows those relationships between the parts. I think through how a person would assemble and handle something as well as how it looks. A physical model helps expose details that deserve another look.
Let the test guide the next version
Define
I choose the question this version needs to answer and what I’ll look for in the test.
Make
I build a version that lets me test that question, with the relevant parts and constraints represented.
Observe
I compare what happens with what I expected and pay attention to anything I hadn’t accounted for.
Refine
I use what I learned to decide what needs to change before building the next version.
Tell me what the idea needs to do
Show me the idea and explain who would use it. I’ll want to understand where it needs to fit and any components it has to work with. Sketches or early models help, along with the question you’re trying to answer next.