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 fine-tuning the experience when you don't even know if anyone truly needs the product, or if there are no real users to measure and improve. At that stage, the priority is to validate demand and find the right customers. However, not needing to fine-tune deeply doesn't mean you can be careless to the point where customers don't reach out or make purchases.
- 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 unsure if anyone truly needs the product, then that is not the right action to take at this time. Refining the experience is valuable when there is data to inform what to adjust. Without real users, there is no real data, so all design decisions are merely guesses.
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 neither question has a clear answer, the bottleneck does not lie in the experience. The bottleneck is that you do not yet know if the product truly meets anyone's real needs. Spending money to finalize the interface at this point 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.
- The budget is limited: according to IDEO's framework of the three lenses of Desirability (user desire), Feasibility (technical feasibility), and Viability (business effectiveness), investing deeply in the experience lens is only warranted 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 deep refinement doesn't mean you can be careless. There is a minimum threshold you must maintain once publicly launched: the experience should not obstruct the main actions of customers.
The main actions here are: customers can contact, register, and purchase. If customers enter the page without knowing what the next step is, or get lost before completing a task, that is an error that needs to be fixed immediately, regardless of aesthetics or advanced features.
No need to worry about adjustments: You are still verifying if anyone needs the product. Focus on customer interviews, quick testing, and a simple page for 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 do not have customers or are unsure if the product meets needs, Sinh Vũ advises focusing resources on proving there is demand first. A concise page that directs customers to contact is sufficient for this stage.
Sinh Vũ chooses to advise you on the right areas rather than sell 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 attracting customers.
Decision checklist
Topic: When you don't need to worry about digital experience yet. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, 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 is no hard number, but the threshold to maintain is: the experience should not obstruct the primary actions of customers, meaning customers should still be able to contact, register, or purchase even if the interface is not yet appealing. If customers enter the page and do not know what to do next or get lost, that is an error that needs immediate correction, even if deep optimization is not yet required.
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 hinder the main actions, launched early to gather genuine feedback, is far more valuable than a polished product that no one has touched.