The designs we never ship still matter

As UX designers, we often spend hours exploring different ways to solve the same problem. We create multiple versions of a design, experiment with different flows, rethink interactions, and try different approaches to make an experience better.

Yet, most of these ideas never make it into the final product. Some remain buried in our Figma files, while others eventually find their way into the trash.

But does that mean the effort behind them was wasted?

I don't think so.

Sometimes, the designs we never ship teach us more about the problem than the design we eventually deliver. They help us challenge assumptions, uncover overlooked requirements, understand trade-offs, and get closer to a solution that genuinely works for users.

And that's what makes design exploration valuable.

Why do we create multiple design options?

When working on a new feature or improving an existing experience, we don't always have all the answers upfront.

Requirements might be unclear, user expectations might vary, or there could be several ways to approach the same problem. As designers, we're expected to make sense of this uncertainty and translate it into an experience that works for users while meeting business and technical needs.

That's where exploring alternatives becomes useful.

You might create different variations, each exploring a different flow, level of detail, interaction, or approach to completing a task.

One version might prioritise simplicity, another might offer more flexibility, while a third might introduce a completely different way of approaching the problem.

These alternatives aren't necessarily competing solutions. They're different ways of understanding what the experience could be and what trade-offs each approach introduces.

However, despite putting considerable thought and effort into these explorations, we often hesitate to share them.

Why do we hesitate to share unfinished ideas?

Sometimes, it's the fear of judgement. You might feel that your designs aren't polished enough or that others will criticise an idea before you've had the chance to explain the thinking behind it.

Other times, you may still be figuring out how a feature should behave. You're working through interactions, validating assumptions, or considering edge cases. Sharing something that feels incomplete can be uncomfortable.

And then there are the practical constraints.

You might hear things like:

• We don't need so many options. Let's move forward with one solution.

• We don't have time to evaluate multiple directions.

• We're already behind schedule. We need to start building.

These concerns are understandable. Teams have deadlines, resources are limited, and not every design decision needs extensive exploration.

But there's a difference between being efficient and settling on the first acceptable solution without considering whether it's actually the right one.

Moving forward without exploring important alternatives can leave user needs unaddressed. What initially seems like a quicker decision might eventually result in rework, additional development effort, and a frustrating product experience.

Exploration isn't about having more options

Here's something I've learnt over the years: creating more design options doesn't automatically lead to better design.

What matters is whether those alternatives explore meaningful differences.

For example, imagine you're designing a cluster creation workflow for an enterprise storage product.

You could explore three different approaches:

• A simple form: Keeps the experience straightforward by asking users for only the essential configuration details.

• A guided workflow: Breaks the process into smaller steps, helping users understand what they need to configure and why.

• An advanced configuration experience: Gives experienced users more flexibility and control over the setup.

Each approach introduces different trade-offs.

A simple form might reduce complexity but leave users wanting more guidance. A guided workflow might make the process easier to understand but introduce additional steps. An advanced configuration experience might offer greater control but overwhelm someone who is unfamiliar with the system.

Simply looking at these alternatives helps us ask better questions.

What does the user actually need at this point? How much guidance is necessary? Which configurations should be available upfront? Are we making the experience easier, or simply moving complexity somewhere else?

These are important design decisions, and comparing different approaches gives the team something concrete to evaluate rather than relying entirely on assumptions or personal preferences.

Sometimes the best solution is a combination

One of the most interesting outcomes of exploring multiple directions is that the final solution doesn't always have to come from a single concept.

You might discover that one approach has a better overall flow, another handles configuration more effectively, and a third communicates important information more clearly.

With feedback from teammates, stakeholders, subject matter experts, and users, you can bring together the strongest elements of these alternatives.

This is also why sharing unfinished ideas can be valuable.

Someone else might notice a missing requirement, challenge an assumption, or suggest an improvement you hadn't considered. Feedback can help you identify weaknesses in an approach before they become problems in the product.

As designers, we also need to be comfortable receiving criticism. Not every piece of feedback will be easy to hear, but it can reveal genuine frustrations, overlooked requirements, or opportunities to improve the experience.

Sometimes, the best idea comes from a conversation around a design that was never intended to become the final solution.

When is exploring multiple options actually worthwhile?

Not every design decision requires multiple concepts. Exploring alternatives is most valuable when the decision has meaningful implications for how users interact with a product.

Consider exploring different approaches when:

• Requirements are ambiguous: You need to understand different interpretations of the problem before committing to a solution.

• There are multiple ways to complete a task: Different flows or interactions could significantly change the user experience.

• User needs compete with business or technical constraints: You need to understand the trade-offs before deciding what to prioritise.

• A design decision has significant usability implications: The wrong approach could introduce complexity, confusion, or unnecessary effort for users.

On the other hand, minor visual adjustments or decisions already governed by established design patterns don't always need multiple concepts.

The goal isn't to explore everything. It's to spend time exploring the decisions that matter.

Not every design needs to make it to production

It's perfectly fine for most of your design explorations to remain unused. Their value isn't determined by whether they eventually become part of the product.

A discarded concept might help you identify a confusing interaction. An alternative flow might reveal a missing requirement. Comparing two approaches might help your team recognise why one is more intuitive than the other.

These are all valuable outcomes of design exploration.

So, the next time you find yourself creating multiple design options, don't think of them as versions competing to become the final design. Think of them as different ways of understanding the problem and getting closer to the right solution.

Good design isn't always about getting to the answer quickly. Sometimes, it's about exploring enough possibilities to understand why that answer is the right one.