Every product begins with a question.
What if this could work differently? What if this problem could be solved another way? What if technology could make something simpler, safer, faster, or more human?
At this stage, there are possibilities, but very few certainties. An idea can exist as a sketch, a conversation, a reference, or simply a thought about how something could be better.
But turning that possibility into a product is where the real work begins.
A sketch can suggest a direction. A render can make a concept look convincing. A presentation can communicate a vision. But none of them can tell us whether something will actually work in the hands of a real person, within a real environment, and under the realities of manufacturing.
That is the journey from “What if?” to “What works?”
It starts with understanding
Good product design doesn’t begin with drawing the product. It begins with understanding why the product needs to exist in the first place.
Before developing a form or deciding how something should look, there is a need to understand the problem behind the brief. Who is going to use it? Where will they use it? What are they trying to accomplish? What already exists? What isn’t working? What technical, environmental or commercial constraints already exist?
This is where design research becomes an important part of product development.
Research helps us understand users, environments, existing products, technologies, materials and behaviours. It also gives us an opportunity to challenge assumptions before they become expensive design decisions.
Sometimes research confirms the original direction. Sometimes it changes it completely. Both outcomes are valuable.
The objective isn’t to prove that the first idea was right. It is to make sure we are solving the right problem.
Exploring what could be
Once the problem becomes clearer, possibilities begin to take shape.
This is where ideas become tangible. Sketches help us explore form and function quickly. References establish visual and conceptual directions. Diagrams help us understand relationships and systems. CAD allows us to investigate proportions and spatial relationships, while physical mock-ups allow us to experience an idea before committing to a final direction.
At this stage, industrial design isn’t about finding one perfect answer immediately. It is about exploring the space between different answers and understanding what each one enables or compromises.
A change in form might improve ergonomics but increase manufacturing complexity. A smaller footprint might improve portability but limit internal components. A particular material might create the desired tactile experience but introduce cost or fabrication challenges.
Every design decision creates consequences.
So instead of asking only whether something looks good, we start asking a much broader set of questions: How does it feel to use? How does it move? What needs to happen inside? What materials make sense? How will it be assembled? Can it actually be manufactured?
That is where product design starts becoming product development.
When the idea meets reality
Eventually, every concept has to meet the physical world.
Real components have dimensions. Real materials have properties. Real mechanisms require space. Real manufacturing processes have limitations.
A component may be larger than expected. A mechanism may require additional clearance. A surface finish may be difficult to reproduce consistently. An elegant form may create unnecessary complexity during assembly.
These aren’t problems that appear because the design process has failed. They are part of the design process.
This is where product design and engineering begin to overlap.
The external form affects the internal architecture. Components influence proportions. Material selection affects manufacturing. Manufacturing influences geometry. User behaviour affects interaction.
The product is no longer a collection of individual design decisions. It becomes a system of interconnected decisions, where changing one element can affect several others.
This is why close collaboration between design and engineering matters. The earlier these conversations happen, the more opportunities there are to find better solutions rather than simply solving problems at the end.
Prototypes make ideas honest
A prototype is more than a physical version of a design. It is a way of asking a question.
Does this actually work?
A simple foam model might tell us whether a product feels too large or whether a grip is comfortable. A 3D-printed prototype might reveal an unexpected interference or an assembly problem. A functional prototype can help test mechanisms, electronics and interactions that cannot be understood through CAD alone.
Different prototypes answer different questions.
Not every prototype needs to be polished, either. Sometimes the most valuable prototype is the fastest and roughest one because it allows a decision to be tested before too much time is invested in it.
This is why prototyping and iteration are central to product development.
If something doesn’t fit, it changes. If something doesn’t feel right, another approach is tested. If something cannot be manufactured as intended, the design is reconsidered.
The purpose of a prototype isn’t to prove that the design is finished. It is to discover what still needs to change.
Designing for the real world
A product eventually has to leave the studio.
It has to be manufactured, assembled, transported, used and maintained. Depending on the product, it may also need to withstand different environments, comply with technical requirements, accommodate different users, or be produced at a particular scale and cost.
At this stage, design decisions become closely connected to production.
Material selection is no longer only an aesthetic decision. Tolerances become important. Assembly becomes part of the design. Manufacturing processes influence geometry. Production volumes influence tooling and fabrication decisions. Components and suppliers can influence what is technically and commercially possible.
This is where principles such as Design for Manufacturing (DFM) and Design for Assembly (DFA) become part of the conversation.
A successful product isn’t simply one that looks right.
It needs to be feasible, functional, manufacturable and appropriate for its intended context.
The closer an idea gets to production, the more these realities shape what the final product becomes.
The design changes. The idea evolves.
One of the most interesting parts of product development is that the final product rarely looks exactly like the first sketch.
That isn’t necessarily a failure of the original idea. It is evidence that the idea has been tested.
Research changed something. A prototype revealed something. An engineering constraint introduced a new direction. A manufacturing process suggested a better solution. User feedback challenged an assumption.
Each iteration adds information.
The original idea provides the direction. The development process provides the evidence. Somewhere between the two, the product takes shape.
From “What If?” to “What Works?”
At Arbitrary, we see product development as a continuous conversation between imagination and reality.
We move between research and making, design and engineering, digital models and physical prototypes, possibility and constraint. The process is rarely completely linear. A project may move forward, return to research, revisit a concept, change direction and then move forward again.
That isn’t wasted effort. It is how uncertainty is reduced.
The goal isn’t simply to create an idea that looks convincing. It is to develop an idea until it can exist in the real world — as something that can be manufactured, used, understood and experienced.
A question becomes a direction. A direction becomes a concept. A concept becomes a prototype. A prototype is tested, challenged and refined until the idea becomes something more tangible than the original thought.
Something that works.
“What if?” starts the conversation.
“What works?” is where the product begins.