Why is a water bottle shaped like that?

Pick up the nearest water bottle. Before you read on, ask yourself the question a good interviewer would ask: why is it that shape and not some other? Most people answer "because that's what bottles look like." That answer is a dead end, and in an interview it's a failing one. The interesting version of the question is: which decisions produced this object, and what would happen if we made them differently?

This is what product people call product sense, and it's the single hardest thing to fake. You can memorize a framework. You cannot memorize the habit of tracing an object back to the forces that shaped it. So let's build that habit on the most boring object we can find — and by the end, design five bottles that don't exist yet.

1. Start with the user and the moment, never the object

The reason "that's what bottles look like" fails is that it skips the user. Every object is a frozen answer to a question about a person. So the first move is to refuse to design "a bottle" and instead ask: a bottle for whom, doing what, where?

Consider three users of the "same" product:

• A marathon runner at kilometer 30 — one hand, in motion, breathing hard, wants water fast without breaking stride, and cares about weight to the gram.
• A parent packing a lunchbox — wants leak-proof above all, easy for small hands, easy to clean, and it has to survive being dropped on a tile floor daily.
• A knowledge worker at a desk — wants it to look good on a video call, hold enough that they don't refill constantly, and not sweat a ring onto the desk.

These are three genuinely different products wearing the same word. The moment you name the user and the moment, the design stops being arbitrary. The runner's bottle should be soft and squeezable with a bite valve. The parent's should be rigid with a locking lid. The desk worker's should be double-walled and handsome. Notice we haven't drawn anything yet — the constraints are already doing the work.

The amateur asks "what features should it have?" The professional asks "what job is being hired for, and what would fire the current solution?"

2. Separate the real job from the obvious one

The obvious job of a bottle is "hold water." That's true and useless — it doesn't discriminate between designs. The real jobs are the ones that create trade-offs:

• Get liquid from container to mouth with the right flow rate for the moment (a gulp when running, a sip at a desk).
• Do not leak in a bag full of a laptop.
• Be refillable and cleanable, because water is free and the bottle is used hundreds of times.
• Signal identity — a $45 insulated bottle is partly jewelry, and pretending otherwise gets the product wrong.

These jobs conflict. A wide mouth is easy to clean and fill with ice but pours badly and gulps too fast. A narrow mouth controls flow but grows mold you can't reach. The entire design is a negotiated settlement between jobs that pull in opposite directions. Good product thinking is mostly the ability to see those tensions clearly and choose which to favor on purpose.

3. Now trace every existing feature to a constraint

Here's the move that separates strong candidates from everyone else. Take the ordinary bottle apart, feature by feature, and for each one name the constraint it answers. Nothing is allowed to be "just how it is."

Notice how much of the "design" was never a free choice at all. The cupholder, the human hand, the filling machine, and the dishwasher are fixed points in the world the bottle has to negotiate with. This is the deepest lesson in the whole exercise: most of what looks like design is actually a set of interfaces to systems you don't control. The same is true of software. Your feature isn't shaped by your taste; it's shaped by the notification tray, the app-store review, the onboarding a user already knows, and the thing they were doing right before they opened your app.

4. Break a constraint on purpose — this is where innovation lives

Once you can see the constraints, you get a superpower: you can ask "what if this one weren't true?" Each removed constraint is a doorway to a product that doesn't exist yet.

• What if it didn't have to be rigid? → the collapsible/soft flask, which packs to nothing when empty. The runner's answer.
• What if the cupholder weren't fixed? → you'd get shapes optimized for the hand and the bag instead of a legacy hole in a car — flatter, book-shaped bottles that slide into a laptop sleeve.
• What if refilling were the primary action, not drinking? → you'd design around the tap, not the mouth: a wide funnel top, a base that fits under a fridge dispenser.
• What if the bottle knew how much you drank? → the constraint you removed is "dumb container," and now hydration tracking, cap sensors, and reminders become the product.

Innovation is rarely a new idea. It's an old constraint that everyone stopped questioning, removed on purpose.

5. Five bottles that don't exist yet

Now we design forward. Each of these comes straight from relaxing one constraint we uncovered above — which is exactly how you'd close a strong interview answer:

1. The book-bottle. Flat, rectangular cross-section for the person whose bag has a laptop, not a cupholder. Loses roll-ability and even pressure distribution — so it trades a manufacturing cost for a carry benefit. Defensible if your user never uses a cupholder.
2. The two-flow cap. One cap, two channels: a fast gulp valve and a slow controlled sip, chosen by which way you tilt. Resolves the wide-vs-narrow-mouth tension instead of picking a side.
3. The self-dosing bottle. Cap counts pours and glows softly when you're behind your daily target. The container becomes a coach. The real design problem is now power and cleaning, not shape — which is the honest answer, and interviewers love honest constraint-shifting.
4. The nesting refill. A bottle whose base unscrews into a shallow cup, so one object is a bottle for the commute and a glass at the desk. Solves "I don't want to drink from the bottle in a meeting."
5. The disappearing bottle. Fully collapsible with a rigid spine, so it's a normal bottle full and a coaster-sized disc empty. Removes the "empty bottle wastes space" constraint that every rigid bottle silently imposes.

None of these is obviously "right." That's the point. Each is the correct answer for a specific user whose constraint you chose to break. A strong interview answer doesn't land on one bottle — it shows the interviewer the map, then picks a point on it and says why.

The transferable skill

We spent 2,000 words on a bottle, but you weren't really learning about bottles. You were rehearsing the loop that runs underneath every good product decision:

1. Name the specific user and moment. Refuse the generic object.
2. Separate the obvious job from the jobs that actually create trade-offs.
3. Trace every existing feature back to the constraint it answers.
4. Notice which constraints are interfaces to systems you don't control.
5. Break one constraint on purpose and follow where it leads.

Run that loop on your own product this week. Take the one screen everyone treats as finished and ask why each element is there and what it's an interface to. You'll find at least one constraint nobody has questioned since the first version. That's usually where the next good idea is hiding.