A designer's perspective on building MVPs that actually scale

The Misconception That Slows Down Most Startups

When I sit down with founders for the first time, I notice a pattern almost every single time. They open their laptop, show me reference designs, talk about colors, layouts, and screens — and then ask, "Can you make our product look like this?"

I get it. UX design is the most visible part of a product. It's what users touch, what investors see, what gets screenshotted into pitch decks. So naturally, founders assume design is what matters most.

But here's what I've learned after working on real startup projects: UX design is just the final execution. Everything that decides whether your product succeeds or fails happens before the first screen is ever drawn.

In my view, every product is built on three foundational layers:

1. Product strategy — what you're building and why it matters in the market

2. UX strategy — how the experience should evolve to deliver that value

3. UX design — the actual screens, flows, and interactions users see

Most founders skip straight to layer three. That's the mistake. Let me walk you through how I think about each of these — and why getting the order right has saved every MVP I've worked on from becoming a confused mess six months in.

Product Strategy — The "What and Why"

Product strategy defines the market opportunity. It answers questions like:

• Which customer segment are we targeting?

• What problem are we solving better than competitors?

• How will the product drive growth?

Without this, you're just building features in the dark.

UX Strategy — The "How the Experience Should Work"

This is the layer founders almost never think about — and it's the one I spend the most time on during MVP work.

At its simplest, UX strategy is a long-term plan for how a product's experience will create value for both users and the business — and how teams will prioritize decisions to get there.

It might sound abstract, but the core idea is straightforward: strategy is about direction and choices.

Every product team eventually faces tradeoffs:

• Should we simplify onboarding or ship a new feature?

• Should we invest in automation or improve collaboration?

• Should we optimize what exists or expand into new capabilities?

UX strategy exists to answer questions like these. It helps teams decide how the experience should evolve over time, instead of reacting to design problems as they pop up.

People often confuse strategy with planning, so let me clarify:

For example, a UX strategy might define a goal like "reduce friction in onboarding so new users reach activation within minutes." The plan would outline the research, experiments, and design improvements needed. The roadmap would schedule those initiatives across releases.

Strategy can also exist at different levels:

• Feature-level — improving a specific workflow

• Product-level — shaping the overall experience

• Platform-level — aligning across multiple products

And the time horizon is longer than everyday design work. UX design solves immediate interface problems. UX strategy looks months or years ahead, defining the desired destination.

UX Design — The Execution Layer

Once strategy is clear, this is where design comes in. Designers turn strategic decisions into concrete solutions — flows, interactions, and interfaces users touch every day.

Here's the thing: the design process becomes dramatically more effective when strategic direction is already clear. Without that foundation, designers are just guessing.

The MVP Trap: "Good Design Is Already Strategy"

A lot of founders — and even some designers — believe that during the MVP phase, good UX design is automatically strategic. Just hire a solid designer, ship clean screens, and you're set.

In my experience, that's not true.

The MVP phase is actually when strategy matters most. This is the moment when you should be:

• Defining the rules and vision of the brand

• Setting quick guidelines for the product

• Creating a reference point for future teams and feature decisions

If you skip this and only focus on shipping pretty screens, you're building a house without a foundation. It might look fine on day one. But six months later, when you're adding features, hiring more designers, or pivoting based on user feedback, everything starts to drift apart.

Why Fragmentation Kills Products

As products grow, experience decisions get more complex. Multiple teams work on different parts. Each ships features and improvements. Without shared direction, all these efforts drift apart — and the experience starts feeling fragmented and inconsistent.

UX strategy is what prevents this. It aligns teams around a common vision and ensures every design decision supports the broader business objective.

In practice, a clear UX strategy does three things:

1. Alignment — keeps product, design, and engineering moving toward the same goals

2. Prioritization — identifies which improvements create the most value

3. Risk management — tests assumptions before you invest heavily in new features

Without it, teams fall into what's called feature factory mode — shipping functionality without thinking about how it affects the whole experience. I've seen this happen so many times. The product becomes a graveyard of half-finished features that don't talk to each other.

The UX Vision — Your Product's North Star

One of the most powerful tools I rely on during MVP work is defining a clear UX vision.

The UX vision describes the future experience the product aims to deliver. It's a long-term reference point that helps everyone on the team understand what success looks like for users.

Unlike a product roadmap, which focuses on upcoming releases, a UX vision focuses on the desired experience outcome.

For example, a B2B SaaS company might define their vision like this:

"New users can set up their first workflow and see value from the product within ten minutes, without needing training or documentation."

That single sentence does a lot of work. It clarifies what the team is trying to achieve. It guides design decisions across the product. And it sharpens the value proposition by making the promised experience concrete.

There's a lot more to UX strategy than this — focus areas, experience principles, success metrics — but the vision alone is enough to dramatically change how an MVP gets built.

A Real Example: My Work on Sonasetu

Let me share a project where this approach made a real difference — Sonasetu, a product I designed that solves problems in India's Jewellery unorganized market with a new approach.

When I first joined, the founder was in exactly the misconception I described earlier. They wanted to build the problem-solution with a broad set of features all at once during the MVP phase. The thinking was:

more features = more value = stronger product.

But this approach was actively hurting them. It was:

• Deflecting from the core concept — every new feature pulled focus away from what the product was actually about

• Failing to create a strong base — without a defined core, there was nothing for the brand to stand on

• Leaving no guidelines for the future — every new decision would have to be argued from scratch

When I stepped in, my approach was the opposite of what they expected. Instead of designing more, we cut down sub-features and narrowed everything to the core feature — the one that truly represented the brand and the solution.

Then we did the work most MVPs skip entirely: we created a proper set of UX guidelines aligned with both the brand and the nature of the product.

The result wasn't just a cleaner MVP. It was a foundation. Every future feature, every new designer who joins, every decision the founder makes — all of it now has a reference point. That's what UX strategy actually delivers.

What I Focus On When Designing an MVP

So if you're a founder reading this, or a designer about to start an MVP project, here's what I'd tell you to prioritize — in this order:

1. Get clear on product strategy first. What problem are you solving, for whom, and why does it matter?

2. Define your UX vision. Write the one sentence that describes what success feels like for your users.

3. Cut features ruthlessly. Your MVP should represent your core idea — not every idea you've ever had.

4. Build UX guidelines that match your brand and product nature. These become the rulebook for everything that comes after.

5. Then design the screens. With the foundation in place, design becomes execution — not guesswork.

Final Thoughts

The biggest shift I want founders to make is this: stop thinking of design as the thing that makes your product look good. Start thinking of it as the thing that makes your product make sense.

Beautiful screens with no strategy behind them age badly. Strategic foundations with even simple screens grow into great products.

If you're building an MVP and you've been focused entirely on visuals, take a step back. Define your strategy first. Trust me — the design will be ten times better when you do.

If you're working on an MVP and want a designer who thinks strategy-first, let's talk.