When is there no need to worry about experience
Investing in experience at the right time adds value; doing it too early wastes money on unnecessary expenses.
You don’t need to worry about refining the experience when you still don’t know if anyone truly needs the product, or if you don’t have real users to measure and improve. At this stage, the priority is to validate demand and find the right customers. However, not needing to refine deeply does not mean you can be careless to the point where customers cannot contact or purchase.
- no market demand validated yet, so focus on experimentation
- there is no real traffic to know what to fix
- has publicly launched and has real users
- the experience is so poor that it hinders the customer's main action
Sinh Vũ will be straightforward: if you are considering investing in digital experience while you are not sure if anyone truly needs the product, then this is not the right time to do so. Refining the experience is valuable when you have data to know what to fix. Without real users, there is no real data. Without real data, every design decision is just a guess.
Questions to answer first
Before deciding whether to invest in the experience, you need to answer these two questions:
- Is there evidence that someone needs the product, or is it still just speculation?
- Are there real users to measure behavior yet?
If both questions still do not have clear answers, then the bottleneck is not in the experience. The bottleneck lies in your uncertainty about whether the product meets the real needs of anyone. Spending money to perfect the interface at this time is optimizing in the wrong area.
When to postpone adjustments
- Unverified demand: resources should be focused on interviewing customers and testing hypotheses, not on the interface.
- Without real traffic: without data, it’s unclear what to correct, and adjustments at this stage are merely subjective.
- With a limited budget: according to IDEO's framework, there are three lenses: Desirability (the level of user desire), Feasibility (technical feasibility), and Viability (business effectiveness). Investing deeply in the experience lens is only worthwhile when there are clear signs that the problem is real and the users are real.
At a low maturity level and with a small budget, improving the experience should go hand in hand with demonstrating value. Without users and data, there is not enough foundation to refine with direction.
Nielsen Norman Group, The 6 Levels of UX Maturity
The minimum baseline must still be maintained.
Not needing to refine deeply does not mean you can be careless. There is a minimum threshold you must maintain once you have launched publicly: the experience must not obstruct the main actions of the customers.
The main actions here are: customers should be able to contact, register, and purchase. If customers enter the page and do not know what the next step is, or get lost before they can do anything, then that is an error that needs to be fixed immediately. This error must be corrected even if aesthetics or advanced features are not yet a concern.
No need to worry about refining: You are still validating whether anyone needs the product. Focus on interviewing customers, conducting quick tests, and having a simple page that allows customers to contact is sufficient.
Need to address immediately: Launched publicly but customers don’t know what to do, cannot contact, or cannot make purchases. Even if it doesn’t need to look good, you must fix the main action blockers first.
Common mistakes
- Polishing the interface when the original problem is that no one knows or needs the product: beautifying does not create customers.
- Building a feature-rich page before knowing if customers want it: the more complex it is, the more resources are wasted on unproven value.
- Using the excuse of not needing to worry about the experience to the extent that customers cannot contact or make purchases: this is a misunderstanding of the minimum threshold.
- Wait for perfection before launching: every day you wait is a day lost in receiving real feedback from real customers.
The viewpoint of Sinh Vũ
Sinh Vũ will be honest with you if the time is not right to invest deeply in the experience. If you don’t have customers or are not sure if the product meets the needs, Sinh Vũ advises focusing resources on proving that there are people who need it first. A simple page that directs customers to contact is sufficient for this stage.
Sinh Vũ chooses to advise you on spending wisely rather than selling a large project when you do not need it yet. A beautiful experience on a product that no one needs still does not solve the problem of having customers.
Decision checklist
Topic: When you don't need to worry about digital experience yet. Sinh Vũ guide, sinhvu.com
Tick each item that applies or that you can already answer, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
IDEO, Design Thinking, the Desirability-Feasibility-Viability framework. Nielsen Norman Group, The 6 Levels of UX Maturity. Practical consulting experience from Sinh Vũ Studio.
Frequently asked questions
Products that have launched but do not have many customers, should you invest in enhancing the interface?
The more relevant question is: what is the current bottleneck? If customers are unaware of the product or do not see a reason to try it, then spending money on the interface will not solve that problem. You should prioritize understanding why there are no customers first, then decide whether to improve the experience.
What is the minimum experience level required when not optimized?
There are no hard numbers. But the threshold to maintain is that the experience must not obstruct the main actions of the customers, meaning customers should still be able to contact, register, or purchase even if the interface is not beautiful. If customers enter the page and do not know what to do next or get lost, that is an error that needs to be fixed immediately even if deep optimization is not yet necessary.
Is it okay to wait for a perfect product before launching?
Not okay. Waiting for perfection before launching wastes time learning from real customers. A usable version that does not obstruct main actions should be launched early to gather real feedback. Real feedback is much more valuable than a polished product that no one has touched.
This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.