The first step in solving a problem in the engineering world is to define the requirements.

Simply put, the goal is to systematically determine what the solution will do.

Take a Roomba for example.

When someone had the idea of deploying an autonomous vacuum cleaner indoors, the engineers likely first defined exactly what they expected the device to do.

What size area will it accommodate? Which types of surfaces will it work on (carpet, hardwood, tile, etc)? How quickly will it clean an area? What will be defined as “clean?” What happens if the device runs into a family dog or cat? How loud will it be?

And on and on.

Before any significant effort is put into designing the system, a significant amount of time is taken to understand exactly what type of system they’re trying to build.

It makes sense if you think about it.

It would’ve been a waste of time for the Roomba developers to design an internal combustion engine powertrain system for their vacuum. It would have been far too loud and dirty for interior use.

Admittedly, anyone with common sense probably would’ve known that an electric system would’ve likely been the right option in this situation.

But there are dozens, or even hundreds, of choices that go into something as simple as a vacuum cleaner that are nowhere near as obvious.

-Brandon