Throwing spaghetti at the wall to see what sticks is a common English idiom that refers to haphazardly testing multiple random ideas, strategies, or creative solutions to see which one yields results.

In UX design, it is often used to brainstorm ideas where teams lack a specific strategy and tries out many different approaches through pure trial and error.

ORIGIN

The origin of the phrase comes from a simple cooking test: Throw a single spaghetti at the wall and if it sticks, it’s done, but if it fell, it needed more time. The earliest known publication of this method is in the 1946 cookbook “You can cook if you can read”.

Culinary experts consider this a myth, as boiled pasta will stick to a wall regardless of whether it’s undercooked, perfectly cooked, or overcooked. The recommended approach to avoid guesswork is to follow exact boiling times for various cuts of pasta paired with traditional taste test to achieve perfect al dente bite. This method results in reliable outcomes and avoid unnecessary kitchen clean-ups.

Applied to work, it became a metaphor for trial-and-error problem solving – trying many approaches without a clear hypothesis or process, and waiting to see what works.

WHEN

You’ve encountered Spaghetti at the Wall when:

• Features are shipped without a clear problem to solve
• Experiments lack a hypothesis or success criteria
• Teams rely on volume instead of direction
• Roadmaps feel like collections of ideas, not decisions
• You hear: “Let’s just try it and see what happens”

If effort is high but intention is low, the spaghetti is flying.

WHY

Throwing spaghetti feels productive.

• Action over thinking: Doing something feels better than deciding what to do.
• Low cost of shipping: Modern tools make it easy to launch quickly.
• Fear of missing out: “What if this is the thing that works?”
• Misunderstood experimentation: Testing becomes random instead of intentional.

The result includes a lot of motion with very little learning.

HOW

Throwing spaghetti against the wall by itself isn’t the problem. Doing it without learning is.

In UX and product design, avoid a messy approach by following these steps::

• Start with a hypothesis: What do you expect to happen – and why?
• Define success before launching: If you don’t know what success looks like, everything looks like progress.
• Limit parallel experiments: Too many tests create noise instead of insight.
• Measure outcomes, not activity: Shipping is not learning.
• Close the loop: Every test should lead to a decision.

Good experimentation is structured curiosity. Bad experimentation is well-documented randomness.

PRO TIP

Use research insights to define a UX strategy. Without strategy, everything is becomes an unguided and hard to measure experiment.

EXAMPLES

Examples of throwing spaghetti against the wall pattern include the following:

• Launching multiple features without understanding the problem
• Running A/B tests without clear hypotheses
• Adding options to “see what users prefer”
• Shipping ideas based on trends instead of insight
• Iterating endlessly without deciding what worked

CONCLUSION

Throwing Spaghetti at the Wall isn’t always wrong. Sometimes you need exploration. But without intentional direction, it becomes noise. As a result, activities won’t produce insights and change happens without real progress.

In the end, something sticking isn’t enough. You need to know why it did.