I have had this conversation more times than I can count.
A founder calls us three months after launch. The product is live. The team worked hard. But signups are low, users are dropping off after the first session, and nobody can explain why. They want us to fix the UX.
When I ask what research was done before the build started, the answer is usually the same: we talked to a few people, we knew the market, we had a clear vision. No formal design discovery process. No user research. Just assumptions and momentum.
This is not rare. It happens constantly in SaaS. And the cost is always higher than people expect.
So I want to walk through what actually happens when teams skip the discovery phase. Not theory. Real examples from real products. And what a proper design discovery process would have caught before a single screen was built.
First, What Is the Discovery Phase?
The design discovery phase is the work you do before design and development begin. It answers one question: what should we build, and for whom?
This includes user research, stakeholder interviews, competitive analysis, information architecture, user flows, and wireframes. Together they give you a clear picture of user needs, business goals, and product direction.
It is not a long process. A focused discovery phase can run two to four weeks. But most teams skip it because they feel they already know enough. That feeling is usually wrong.
Skipping discovery does not save time. It moves the cost further down the road, where fixing mistakes is much more expensive.
Real SaaS Examples of What Goes Wrong
1. Quibi: $1.75 Billion and No Discovery
Quibi launched in April 2020 with one of the biggest budgets in tech history. The idea was short-form video for mobile, designed to be watched in quick moments throughout the day.
It shut down six months later.
The product was built on assumptions about how people use their phones. A proper user research discovery phase would have shown that users already watched short video on TikTok and YouTube Shorts, on platforms they trusted, inside scroll-based feeds. Not in a separate paid app.
Quibi also locked content to mobile only. No casting. No tablet support. No flexibility. A real design discovery process asks: how does our target audience currently solve this problem? It maps actual behavior, not imagined behavior. Quibi mapped what the team wanted users to do, not what users actually did.
2. Snapchat's 2018 Redesign: Skipping the Feedback Loop
Snapchat redesigned its app in 2018 to separate social content from publisher content. The intention was to make the product cleaner and more structured.
The result was a petition signed by 1.2 million users demanding the old design back. The stock dropped 6% in a single day after launch.
The redesign was rolled out without adequate user testing. The team made structural changes to navigation and content layout without running the changes through real users first.
A proper discovery phase in UX involves heuristic evaluation and user testing before shipping changes at scale. It runs A/B testing to validate assumptions. It includes a feedback loop so designers catch problems before they reach millions of users.
Snapchat skipped this. The discovery work that should have happened before the redesign happened after it, in the form of a very public and expensive lesson.
3. Google Wave: Built Without a Clear Problem
Google Wave launched in 2009 combining email, instant messaging, and collaborative documents into one tool. It was shut down in 2010.
The core problem was that nobody could explain what Google Wave was for. It did not solve a specific user need clearly. It was a solution in search of a problem.
This is exactly what a design discovery phase prevents. Goal setting and problem definition are the first steps in any proper UX design discovery process. The question is simple: what specific problem does this solve for a specific type of user?
Google Wave could not answer that question because the team never did foundational design research. They built something technically impressive that users did not know how to fit into their lives.
4. Rdio: The Product Was Right, the Market Was Wrong
Rdio was a music streaming service that many UX people considered beautifully designed. It launched before Spotify entered the US market and had a loyal user base. It filed for bankruptcy in 2015.
The product itself was well built. But Rdio did not do the market research needed to understand the competitive landscape and pricing expectations. When Spotify arrived with a freemium model, Rdio could not compete.
Design discovery is not just about UX. It includes competitor analysis and brand positioning. It asks: what is happening in the market, and where does our product fit? Rdio found out the answer too late.
The Signs You Skipped Discovery (And Did Not Know It)
Sometimes teams run a light version of discovery and think they covered the bases. Here are the signs that the design discovery process was not thorough enough:
• Users complete onboarding but do not return after day one
• Your support team gets the same questions repeatedly
• Different team members describe the product differently to newusers
• The navigation made sense to the team but confuses real users
• Features were built that nobody uses
• Conversion rate is low despite good traffic
• The product solves a problem, but not the most painful one the user has
Each of these points back to a gap in the design discovery process. Either user research was not done, user flows were not validated, or stakeholder alignment did not happen before the build.
What Good Discovery Looks Like in SaaS
A proper design discovery phase for a SaaS product covers several things. Not all of them are glamorous. But all of them matter.
Stakeholder Interviews
You start by talking to everyone inside the company who has context. Founders, sales, support, product. Each person sees the product from a different angle. Discovery workshops surface those angles before they become conflicts during development.
User Research
You talk to real users or potential users. You ask about their current workflow, their frustrations, and how they solve the problem today. This is foundational design research, and it shapes every decision that follows.
Competitive Analysis
You look at what already exists. Not to copy it, but to understand what users are used to, where gaps exist, and where your brand positioning can stand apart.
Information Architecture and User Flows
Once you know the users and the goals, you map how the product should be structured. This is where information architecture and user journey mapping come in. What pages exist, how users move through them, and what actions lead to conversion.
Wireframes and Clickable Prototype
You build low-fidelity versions of the product and test them with users before a single line of code is written. Prototyping at this stage is cheap. Fixing problems after launch is not.
Design Discovery Report
Everything gets documented. Research findings, validated features, user flows, and a clear design direction. This design discovery report becomes the foundation for the entire build.
The goal of discovery is not to delay the project. It is to make sure the project builds the right thing the first time.
Why SaaS Teams Skip Discovery Anyway
I understand why it happens. There is pressure to ship. Investors want to see product. The team has conviction. Running a discovery phase feels like slowing down.
But here is what I tell every team I work with: discovery does not slow you down. Rebuilding after a failed launch is what slows you down.
When Quibi spent 1.75 billion dollars and shut down in six months, the cost was not the six months of operation. The cost was the entire build, built on unvalidated assumptions.
When Snapchat spent months responding to user backlash after their 2018 redesign, the cost was not just the fix. It was the retention and revenue lost during that period.
A two to four week design discovery phase is not a delay. It is an investment that protects everything that comes after it.
How to Run a Discovery Phase That Actually Works
If you are about to build a SaaS product, or if you are rethinking an existing one, here is what a real design discovery process looks like in practice:
• Start with a kickoff session to align all stakeholders on business goals and constraints
• Run exploratory user interviews with five to eight people who represent your target audience
• Map the competitive landscape and identify gaps your product can fill through competitor analysis
• Define user personas based on actual research, not assumptions
• Build user flows that reflect how real users will move through the product
• Create wireframes and test them before investing in visual design
• Document findings in a design discovery report that guides the full build
This process takes time. But it takes far less time than rebuilding a product that shipped without it.
Final Thought
Every product that launched without discovery and failed had a team that believed in what they were building. Belief is not the problem. Building without evidence is.
The design discovery phase is how you test your belief against reality before it costs you everything. Quibi believed. Google Wave believed. Rdio believed. Belief is not enough.
Do the discovery work. Build something that actually fits your users. That is the only path to a product that lasts.
Ready to Build the Right Thing the First Time?
Skipping the design discovery phase is one of the most common and most expensive mistakes SaaS teams make. We have seen it enough times to know exactly what it costs.
At ReloadUX, our design discovery process is built specifically for SaaS products. We run stakeholder interviews, user research, competitive analysis, wireframes, and a full discovery report so your team builds with confidence, not assumptions.
Start Your Design Discovery Today
Top comments (0)