Engineering & Inventions · Design & invention

How engineers design things

Engineering starts with a vague want and a list of limits. See how engineers turn it into testable requirements, weigh trade-offs, test and revise, and decide when a design is good enough.

4 short lessons · about 16 minutes · 9 sources · updated November 2026

What you will learn

  • Explain how engineers turn a vague need into measurable requirements
  • Describe what constraints are and why engineers list them early
  • Explain why improving one requirement often makes another worse
  • Describe how engineers compare design options against weighted criteria

Lesson 1 of 4 · 4 min

Turning a vague want into a design you can test

Before you readA client asks an engineer for "a better water bottle." What does the engineer usually do first?

Correct.Not quite. The answer is Define what "better" must mean.

The first job is to define the problem, because nobody can test a design against "better." The lesson shows how that's done.

Say a company asks you for "a better water bottle." You can't build that yet, because nobody could tell whether your design meets it. Better for whom, and better at what?

Engineers start by defining the problem. The US National Research Council's framework for science teaching says a design begins with clear goals, called criteria, that the finished product must meet. It adds that criteria should be measurable whenever possible, so anyone can tell if a design passes.

So "better" becomes a list. The bottle keeps a drink cold for 12 hours. It holds 750 ml. It survives a drop onto concrete. It doesn't leak upside down in a bag. Each line is a requirement, and each one can be tested.

A good requirement is verifiable. You can check it by a test, an inspection or a calculation. "Feels premium" fails that check until someone turns it into something measurable, such as a weight or a type of finish.

Check yourselfWhich of these could serve as a requirement for a new water bottle, one a design can be tested against?

Correct.Not quite. The answer is Holds 750 ml of water.

A volume can be measured, so anyone can check whether a design meets it. "Sleek" and "beats every rival" need turning into numbers first.

Requirements say what the design must do. Constraints are the limits on how you get there. The framework lists limits on cost, size, weight and performance, as well as legal, social, ethical and aesthetic ones.

For the bottle, say it must sell for under $20, weigh under 300 grams, use only food-safe materials and reach shops in nine months. Each limit rules out whole families of designs before you draw a line. Thick steel walls might keep drinks cold longest, but they break the weight limit.

That's why engineers write constraints down early. They turn an open question into a smaller search. The US science standards call this defining and delimiting a problem, stating it "as clearly as possible in terms of criteria for success and constraints or limits."

Constraints aren't always fixed, the framework notes. A client may accept $25 for a bottle that keeps ice all day. Finding out which limits are firm is part of the job.

Try to recallWhat's the difference between a design requirement and a design constraint, and why do engineers list constraints early?

A requirement says what the design must do, such as hold 750 ml. A constraint is a limit on how you can do it, such as a price, a weight or a deadline. Listing constraints early rules out designs that could never be used, so the search gets smaller.

You can now turn a vague want into testable requirements and a list of limits. That pair defines the problem, and every later design choice gets checked against it.

Lessons in this topic

  1. Turning a vague want into a design you can test

    See how engineers turn a request like "a better water bottle" into requirements they can measure, and why they list the limits before they draw anything.

    Essentials · 4 min

  2. Why every design gives something up

    See why making a design better at one thing usually makes it worse at another, and how engineers compare options to pick the best compromise.

    Essentials · 4 min

  3. Why the first design is always wrong somewhere

    See how the Wright brothers found the flaw in the numbers everyone trusted, and why cheap, quick tests let engineers revise a design hundreds or thousands of times.

    Deeper · 4 min

  4. How engineers decide a design is good enough

    See how a safety factor sets the margin a design carries, why the humble drink can is still being refined, and how engineers decide to stop.

    Deeper · 4 min

Three quick stories from this topic

The shrinking drink can

Early drink cans weighed over 80 grams. A 330 ml aluminum can now weighs about 13

Engineers have shaved metal off the can for decades, and its walls can now be 0.097 mm thick. So many cans are made that one gram saved per can saves over 200,000 tonnes of aluminum a year.

Lighter every decade

The Aluminum Association says the average can is 38% lighter than in the 1970s.

Fixes that bite back

The 1975 stay-on tab ended the litter of loose pull tabs, but part of it now sinks into the drink.

Too strong to fly

An aircraft built five times stronger than needed would probably be too heavy to fly

Aircraft parts are usually built to take about 1.5 times the largest load they should face, while buildings commonly get twice the load. Every bit of extra strength adds weight, and weight is what a plane can least afford.

Paying another way

Because the margin is thin, aerospace parts get very strict quality control and maintenance schedules.

Not one number

A pressurized fuselage is usually designed to a factor of 2, while main landing gear often gets about 1.25.

The Wrights' missing lift

The Wright brothers' 1901 glider gave only a third of the lift their math predicted

Their sums used a number for air pressure that had sat in the standard lift equation for over 100 years. The math was fine. The old number overstated lift, and only testing showed it.

A bicycle test

They mounted a model wing on a bicycle wheel and rode through Dayton. By the published figures the wheel should have stayed still, and it turned.

The tunnel's verdict

A homemade wind tunnel showed the old air-pressure number was the culprit. The German glider pioneer Otto Lilienthal's wing data held up fairly well.

Sources

  • The Tacoma Narrows collapse and what it taught

    In 1940 the Tacoma Narrows Bridge twisted itself apart in a 42 mph wind. See what the famous film can't show, how a steady wind fed the twist, and how engineers tested the fix.

    4 lessons · 15 min

  • Why a system with backups still fails

    Every defense has holes, and the holes move. See why an accident needs several of them to line up, how spare parts make failure look almost impossible on paper, and how a backup can leave a system less safe.

    4 lessons · 21 min

  • Thomas Edison

    Edison didn't invent the light bulb alone, and his bigger invention was a lab that turned out inventions to order. See what his team built, how the bulb became a system, and where his fame overshoots.

    4 lessons · 16 min

  • Why automatic controllers overshoot and oscillate

    A controller that corrects too hard, or on an out-of-date reading, swings past its target and back. Meet the three-term PID controller, the way engineers tune it and the failures no tuning can fix.

    4 lessons · 25 min

  • How robots work

    A robot senses, decides and acts in a loop. See what its sensors, computer and motors each do, why walking is harder for it than chess, and how much of today's robots is still a person at the controls.

    4 lessons · 16 min

  • How a heat pump moves heat

    See how a machine warms a house with heat taken from freezing outdoor air, follow its refrigerant around the loop, and learn to read the performance number on its spec sheet.

    4 lessons · 16 min

All engineering & inventions topics · Take the quiz