How to objectively prioritize design and UX (and ship quickly)
Sometimes good UX/UI is crucial. Other times, it's a distraction. Here's how to know the difference.
I always believed high-end UX was a necessity from day one, but my perspective changed during my last three years building Bildr.
In the early days, we prioritized removing design friction. This meant that not everything would get a "design pass" before shipping into production. Extra process here would only slow down product development — this is particularly true for startups, where design and UX often bottleneck into a single person’s workload. Instead, by following a few loose guidelines and using common sense, we shipped much faster without worrying about finalizing design and UX.
The rate of change for our product was faster than I’d ever worked, and the benefits of the iteration speed were immediately clear. Any negative effects of a bad UX decision or an inconsistent design element were outweighed by feature improvements.
As Bildr grew, though, we noticed this approach started to cause problems. We had gotten into the habit of releasing updates with complex interfaces and new UI paradigms, but with no documentation, and occasionally even errors. This left users confused and frustrated. We were making the product feel inconsistent and untrustworthy to our growing base of new users.
This forced us to reassess the role of design and UX in the product, but ultimately, the shift in focus helped unlock our next phase of growth (including the ability to charge more).
Threading the needle
Focusing on design and UX too early means neglecting other things that could move the product forward.
In theory, it would be great to implement a perfect design and UX system from day one, but that's not realistic. Your product will grow and change a lot before it's stable enough to know what design and UX it even needs.
A minimum or base level of design and UX is essential, of course, but remain flexible and remember that time spent improving UX has opportunity cost. Weigh the importance of design and UX work (especially work that’s just “polish”) against new features, bug fixes, and even marketing.
Ultimately, the amount of design and UX needed is a spectrum, so at any given point, you have to choose where you want to sit on that curve. With a designer on staff, you may be able to get more done early, but don't let design and UX slow the product development pace... until the appropriate time.
When design is worth it: True believers vs everyday users
While design and UX are essential for any product with users, they are less important in the early stages of a SaaS startup.
At this point in a product’s life, functionality is typically not good enough to attract a large number of “everyday” users. Instead, the focus should be on attracting “true believers” who see your vision and are willing to overlook imperfections in your product. These early adopters will become invested in your product and will tolerate a lot, including imperfect design and UX. In fact, they’re the ones who will ultimately show you what the perfect design and UX is.
As your product grows and attracts more “everyday” users, however, the role of design and UX flips and becomes crucial. Everyday users have no investment in you or loyalty to your product, and they’ll leave at the slightest challenge or roadblock. Every interaction is an opportunity to win over or lose a customer. Design and UX play a crucial role in building trust and retention, essentially "speaking on your behalf" in the product as you grow too large to literally speak to all of your customers.
When design is worth it: Feature completeness
One way to think of when to shift focus is that design should go hand in hand with product feature completeness. When your product's features are ready, and it's starting to feel complete and powerful, design should be in place and doing its job. Before your product is ready, design and UX alone cannot carry it.
By the time your product is at this stage, your ratio of true believers to everyday users should be very heavy on the everyday users side. Before your everyday users outweigh your true believers, design and UX beyond the basics will have limited return.
Another way to think about it: products are never “complete.” There’s always more to work on. But at some point, a product is no longer missing features that most users need. It doesn’t have bugs or edge cases that require support regularly. The tasks are self explanatory and everything is able to be 100% self-service. This is the time where UX increases in importance exponentially. UX is what will replace the hands-on roles of founders and customer success advocates who help users and shape the product in the early days.
In practice
Implementing design and UX improvements later in a product's growth has its challenges, but it's not prohibitively difficult. At Bildr, we're currently implementing a design and UX overhaul of our whole Studio. We're balancing it with shipping speed and reacting to feedback, putting design and UX on the same level of priority as major product features and other technical components.
It’s been, and will continue to be, an increasingly important part of our entire product (and brand). Currently, it still feels a bit like we’re cleaning up after an early growth phase (because we are), but the upgrades are exciting for our team and our users, and the future is bright!
Timeline
Implementing a design system on a growing product will realistically take six months to a year. We’re around five months in, and you can see a lot of huge improvements in our Studio (and in our brand and website), but we still have a ways to go until our whole product is brought up to the design and UX level of our new system. By implementing slowly, we’re making sure that the design system grows organically and that we don’t lose focus on the thousands of other important priorities at a startup in our stage. Everything’s a balance.
The slower implementation is a necessity for us, but it’s also likely a key component of doing this right. The benefit of de-prioritizing UX early is that you can move really quickly. But when it’s time to implement a more permanent system, there’s a lot to consider. You’ll know your existing processes and pain points, so it’s important to solve any inefficiencies while setting up a versatile system that can accommodate current and future design and interface needs. Important tasks take time and can be slow, but they pay off in the long run.
Change is hard
A big challenge with implementing any new process is getting a full team of fast moving, independent people to update their processes at the same time. We actually over-processed at first and ended up dialing back the amount of design friction we were willing to introduce. We were all used to working on our own, sometimes up until the last minute, but we introduced a “design pass” step for everything, which meant coordinating several things with several people before anything could ship. Our deadlines and time estimates were thrown off completely.
So we scaled it back, but we figured it out. One rallying cry that helped immensely was our mutual agreement that design and UX bugs are officially causing issues with trust. With that problem in mind, the only solution was implementing new processes and overcoming any challenges with them. To solve our process challenge, we created detailed (and ongoing) guidelines for anyone on the team to follow, so they can get 90%-100% design-ready without anyone else’s help. It was a little more work and process, but not so much that it felt inefficient.
If you face challenges in your organization introducing changes and new priorities, frame everything in terms of value captured, and don’t oversell the “woo woo” side of UX! As long as the updates and changes are objectively beneficial to the company, your work will speak for itself. In the gap between implementation and results, it’s best to be extremely understanding and accommodating of colleagues’ concerns and really listen to them. You don’t have to implement what they say, but listening and trying to accommodate will make a huge difference. Not everyone intrinsically understands the value UX can provide, but if they feel like they’re a part of the changes, they’re more likely to be supportive.
Earning its worth
When poor or under-thought design and UX decisions cause users to lose trust, there’s a crucial side-effect... people don’t want to give you money.
They can’t trust something with interface errors, and they won’t pay for something they can’t trust. Often it’s subconscious. The flip side of that, though, is that by adding design and UX polish, people will more willingly pay more... and sooner!
It’s not always easy to see where you’re losing customers or prospects due to UX decisions. There are some things to look out for, though. The biggest one is low conversion to paid accounts or upgrades. People will put up with a lot when something is free, but when it’s time to pay, their whole mental calculation changes. If users are happily using for free but reluctant to upgrade, it’s critical to ask them why and find out what to fix. When there’s no consistent answer or missing feature, you’ve got UX and/or trust issues. Even if only subconsciously, your users don’t think your product is worth the price.
But it’s all perception.
The flip side of that perception is that when you clean things up and add UX polish, people happily pay more and are ready to pay sooner.
At Bildr, when we moved out of beta pricing and our long-term pricing took effect, we timed the increase with visual and trust updates in our Studio. We wanted to show people that even though our prices went up, the product took a jump to a new level of professionalism and polish as well. It became clear we were taking the presentation and experience seriously, and our product was high-end, reliable, and for serious users.
Since then, our overall revenue has increased much more than our prices did.
All about trade-off
In the early days, managing your resources effectively is the key to moving your product forward. This means identifying the most important areas of your product that need to be developed and prioritizing resources towards those areas. It also means being willing to make trade-offs and decisions about what can be temporarily deprioritized in order to make progress on the most critical areas.
How do you know what and when to trade off? That’s product- and audience-specific, but the truth is always somewhere in the numbers. If you’re seeing user dropoff or confusion in any area of your product, addressing that confusion and allowing users to get to the next step is the highest priority. Unless you have a clear missing feature or functionality, the fix is almost always UX related, and process-blocking issues are the most important to fix!
Once your users are effortlessly doing everything they need to in your product, that’s when you can get into more detailed UX improvements that may save people time and headspace, but otherwise wouldn’t block anyone’s success.
Ultimately, the role of design and UX in a SaaS startup is not a one-size-fits-all approach. It depends on the stage of growth of your product, the needs of your users, and the resources you have available. By being flexible and strategic in your approach to design and UX, you can ensure that it serves its intended purpose of building trust, retention, and usability without slowing down your product development.
The trickiest part of that equation for me was de-emphasizing design and UX early on. It pains me to even write that, but practically speaking, it’s the only way in the early days. As a SaaS startup, it's important to understand and be objective about the role of design and UX for your growth stage. While they are always important, they may not be a top priority. Instead, focus on attracting true believers who are invested in your product and are willing to overlook imperfect design and UX. Just remember that as your product grows and attracts more everyday users, the role of design and UX becomes increasingly important, especially for building trust and retention... so you can’t ignore it forever!
40 open-source gems to replace your SaaS subscriptions 🔥 🚀
After 19,314 lines of code, i'm shutting down my project
Need feedback for my product.
We are live on Product Hunt
Don't be a Jerk. Use this Tip Calculator.
Loved this section from the post
----
These early adopters will become invested in your product and will tolerate a lot, including imperfect design and UX. In fact, they’re the ones who will ultimately show you what the perfect design and UX is.
As your product grows and attracts more “everyday” users, however, the role of design and UX flips and becomes crucial. Everyday users have no investment in you or loyalty to your product, and they’ll leave at the slightest challenge or roadblock. Every interaction is an opportunity to win over or lose a customer.
---
This is so true and have been facing similar issues as we keep changing our product so rapidly that UX takes a back seat. I also found that the more time I spent on my own product I start building biases which result in bad UX. The only way to validate is by presenting the product to a user to try it out and that when we realise our biases or blind spots while self evaluating the effectiveness of the UX.
Yep, exactly! And it's easier said than done.
LOVE this line----"When poor or under-thought design and UX decisions cause users to lose trust, there’s a crucial side-effect... people don’t want to give you money."
very true in my opinion.
Lot of wisdom here. Thanks Drew!
🙏
I can completely relate to your journey with Bildr. In the early stages, prioritizing rapid development over meticulous design was crucial for our startup too. It allowed us to navigate the challenges of limited resources and accelerate our product's evolution.
However, as Bildr expanded, we encountered issues stemming from this approach. Complex interfaces lacking documentation led to user confusion and frustration, jeopardizing trust. This prompted a reevaluation of our design and UX strategy, a pivotal shift that propelled us into a new phase of growth.
Much like navigating the ever-shifting sands of a Dubai desert adventure, our agile development initially brought speed and excitement. Yet, the lack of a structured approach eventually created a maze of inconsistencies for our users. Adapting and refining our strategy, akin to a well-guided Hatta city tour from Dubai, ultimately paved the way for sustained success.
I wonder how this approach would be different for a small solo dev vs. Bldr, which is a multi-man op.
Even more important for a solo dev to focus on the core things!
Many times we don't faced the mainest goal. You can named as whaever you want. And it's diferent and special in every single case. But if don't money arrives someting it's wrong. Meanwhile don't see green our ego choose play with decorations and over stuff shities...
A designer's word
It's a trap for sure!
Thank you, this is a huge help. I've been stuck in development hell for 3 years trying to hone the interface to perfection, but don't have a whole lot to show for it because I've spent way too much time making things look pretty without thinking about UX, and working on UX when I should have been working on a working product. The result is that I'm on V10 without ever having shipped it for real. This was a good reminder that I need to do the important thing right now which is get into the hands of real people, who will give me real feedback.
For anyone else in development hell.. don't be like me, someone too scared to ship :')
It's super hard to actually do! I constantly fight the urge to build/fix/tweak "that one last thing" before going live. I've never regretted just shipping something, though!
I like how pragmatic you are with how you look at prioritizing design vs shipping. I think it's a really healthy approach.
This is also my first introduction to Bildr - looks really cool and keen to try it out!
Great to hear!
You can just build a good UI using good practices in early stage and once you have a product, refine it and focus on a better and more detailed experience.
great post!
🤝
I think also having Product Designer / UI Engineer knowing how to code helps a lot to iterate and actually quickly ship. I know it's a rare breed but happened for me to be working within design and code in last couple products and speed&quality is unmatchable
I agree, I do the same in my team, I take care of the ux and I am part of the development team
Definitely a huge help.
It's tempting to obsess over perfecting every detail before launching.
I'm learning the hard way that overengineering leads to delays, missed opportunities, and unnecessary complexity. Starting with an MVP and gradually improving the design and UX based on user insights is the way to go I think.
Ultimately, finding the right balance between functionality and design is key to delivering a valuable product while staying agile and calming your inner perfectionist.
Great post!
Thanks! Yes, exactly, and it's definitely hard to not overengineer!
I use to work in a basic way (that in my opinion is the faster and in my case is perfect)
I use to select a theme such as Tailwind or Shadcn.
I create a simple wireframe of the application, including and most focussing on the User Experience (instead of UI as this is basically just a "plug & play" of components provided by library I choose).
Actually it worked and I think the result is good.
Nice, exactly
As a UX designer, objectively prioritizing design and UX while aiming to ship quickly is indeed a challenging task. However, it's essential to strike a balance between providing a great user experience and meeting business objectives. Here's an honest response and some practical suggestions:
Understand User Needs: Conduct thorough user research to understand the target audience's needs, pain points, and goals. This will help you identify the most critical design aspects that will have the most significant impact on users.
Focus on Core Functionality: Prioritize the essential features and core functionality that align with the product's primary purpose. Avoid adding unnecessary bells and whistles that might delay the shipping process.
Iterate and Validate: Adopt an iterative design approach and continually validate design decisions through user testing and feedback. This will help you catch and address usability issues early on, reducing the need for extensive redesigns later.
Collaborate with Stakeholders: Engage with stakeholders, including product managers, developers, and business leaders, to ensure a shared understanding of priorities. Collaborative decision-making can help align design efforts with business goals.
Set Realistic Time-frames: Set realistic time-frames for design tasks, considering the project's scope and complexity. Avoid the temptation to rush through the design process, as hasty decisions can lead to subpar user experiences.
Utilize Design Systems: Leverage design systems and component libraries to streamline the design process. Reusing design elements can save time and maintain consistency throughout the product.
Rapid Prototyping: Use rapid prototyping tools to quickly visualize and test design concepts. Prototyping early and often can help identify potential issues and facilitate faster design iterations.
Prioritize Usability: Focus on creating a user-friendly and intuitive interface. Usability should always take precedence over fancy visuals or extravagant animations.
Perform A/B Testing: When possible, conduct A/B testing to compare different design solutions and identify which one performs better. Data-driven decisions can lead to more effective and efficient designs.
Learn from Feedback: Embrace constructive criticism and feedback from users and team members. Use this input to improve the design continuously.
Remember that shipping quickly doesn't mean sacrificing quality. Instead, it's about being efficient and making informed decisions throughout the design process. By staying user-focused and collaborating effectively with stakeholders, you can strike the right balance between design excellence and timely delivery.
Interesting read Drew. Personally I think it's a harder trade off to make when you try to bookend the development process with up-front design and design sign-off. Up front design can naturally lead to over-scoping plus intent is lost in the transfer from design to delivery which then leads to push back at sign-off.
I think one way to thread the needle is to have the designer collaborate directly as part of the delivery team, so every design decision is made collectively with the various skills, perspectives and business priorities all being considered at all times.
Really liked your distinction between true believers and everyday users, see a lot of that in my day job currently and it's an interesting way of thinking about it.
Good luck with Bildr!
Hey Drew, insightful read! Your journey with Bildr and the shift in perspective on design and UX is a valuable lesson for SaaS startups. Balancing speed with the need for a polished product is a challenge.
Wondering, in your experience, how did you navigate the transition from attracting true believers to everyday users? Also, any tips on efficiently implementing a design system without compromising product development speed?
Excited to learn more from your experiences!
When did you find the balance between focusing on UX and pushing for rapid product development was just right for Bildr?
I like your point that the most important thing about a product is to solve the needs of the user
This is the post I needed while working on my first SaaS product. I consider myself a full-stack developer, but my frontend development skills are not as strong. As a result, I find myself spending a lot of time, perhaps too much, trying to create the perfect UI, even though I know it's already good enough for the MVP. This post provides me with some relief, reassuring me that I don't need to exert extra effort to make the UI feel perfect.
I am currently building an startup, and it is my first time leading the development of a software (I am still a student). I am definitely learning this lesson. Although my product focus in accessibility, once I realized we did not need to control to perfection every single little detail in our product, we had time to innovate more, to test more, and I could say we doubled our productivity while having an equality solid result. Obviously we still have very high standards for us since we focus in accessibility, but experience and a constant team has helped being consistent with our work.
This post beautifully captures the evolution of design priorities in a growing SaaS startup. How did you navigate the challenges between rapid development and prioritizing design for trust and retention?
It's a realtime challenge, and we don't always get it right. They key is probably a flexible mindset. We shifted too much focus into ux for a minute, then cut it back a little, for example. It was something we thought we needed to do, and once we saw some results, we decided we might have overshot just a little, and adjusted it to where we all felt comfortable.
Fascinating insights on the evolution of prioritizing UX in product development! Similar to the challenges faced in balancing design enhancements at Bildr, the journey of refining desert safari dubai offers involves a strategic blend of prioritizing user experience and addressing evolving needs. The parallel of adapting to growth stages resonates, emphasizing the critical shift when attracting "everyday" users in the realm of adventure tourism. The delicate balance between functionality, trust-building, and design evolution mirrors the dynamic nature of crafting enticing desert safari experiences.
“Everything’s a balance.” I deeply sympathize with this statement.
But now, for my project, I should move fast to make true believers. I have to follow a few loose guidelines and use common sense.
I think that's smart 🤝
Thanks for sharing. A lot of founders don't understand the necessity of UX. I know not everyone has the budget or is willing to spend for UX.
That is why your article explains very well.
For sure, it's a tough sell sometimes
As a UX Designer, this is like chicken soup for the soul. Thank you for sharing this, Drew.
🤝
Thanks Drew, your journey with Bildr has been a gold mine of insight! Finding the delicate balance between speed and design is a common challenge for new startups. It's like cooking - add UX spices too early and the dish may lack flavor, add it too late and the flavor may be off. As Bildr grows, your approach to adaptation resonates. This reminds us that new ventures are a dance of priorities.
Good post, I like this point more "Just remember that as your product grows and attracts more everyday users, the role of design and UX becomes increasingly important, especially for building trust and retention... so you can’t ignore it forever!"
This was truly an eye-opener, something beginners like me might have learned after many years. Grateful for sharing this in-depth experience with us. Thank You.
Good point ship quickly is the key for success
What metrics or user feedback primarily signaled the need for enhanced design and UX?
In general, some specific metrics would be the around conversion rates between different steps of acquiring users and onboarding them, and then a churn rate or dropoff metric.
But it's hard to actually see those numbers before you focus on UX, since it might not be a change per se... like your free-to-paid conversion would actually start low and stay low, but you might feel like it should be increasing. At Bildr we noticed a big and consistent uptick in sign ups and new projects, but no increase in later-stage metrics like published projects, additional projects, etc. From there, we dug in and talked with users and ultimately learned almost everyone was confused at one point or another to the point where they dropped. We hypothesized UX could fix these dropoffs, so we implemented improvements, and then tracked those conversion and drop off metrics to make sure they increased.
I really enjoyed reading your post on how to objectively prioritize design and UX, Drew. I especially appreciate your emphasis on the importance of finding a balance between speed and quality.
One thing that I'm particularly interested in is how you measure the success of your design and UX changes. Do you rely on qualitative feedback from users, or do you also use quantitative metrics like conversion rates and time on site?
Another question I have is how you deal with team members who are resistant to change. It can be difficult to get everyone on board with new processes and priorities, especially in a fast-growing startup. What are some tips you have for overcoming this challenge?
The answers to those questions really depends on the product/company culture. At Bildr, we have some quantitative goals and things we always measure, so if a UX change affects them, we'd notice. But at the same time, we mix that with anecdotal and qualitative stuff... we're not running A/B tests or anything like that, but we here from customers in our Discord, etc. There's even a lot of gut feeling involved. Not every company would be that laid back, I'd imagine.
Getting people on board is super, super hard sometimes. I don't know if there's a great trick besides being genuinely open to feedback and respecting everyone's opinion at the table. A lot of people have opposition to UX changes or want input when they frankly have no business having input, haha. But that's part of running a product, and I think the only thing that makes it easier is to lean into that rather than fight against it.
Really appreciate this, thanks for sharing!
Thanks for reading!
Fantastic article. As a Product Designer I (nearly) completely agree.
The only caveat I would put on this advice is that it depends on the intended user. If you have large institutional customers then the level of polish will need to be higher because the stakes are much higher.
Great post.
Thanks, "Before your product is ready, design and UX alone cannot carry it", I completely agree. Deep into ui details too early will surely slow the progress.
🔑
Just like it's mentioned in the post, every interaction could either make or break your customer. Therefore, I believe that your design should always be up to the mark even in the early stages and that's what we strive to deliver at usedesignpro.
that's motivating !
Release early and often! If theres a way to get consistent feedback from users you're golden
Really helpful, thanks for sharing
Great Content! As a developer, I always recall Rich Hickey's words: Programming is not about typing, it's about thinking. And I believe this can apply universally to any role, it's all about thinking!!
Love it.
Here are some points which can objectively help you to prioritize UX:
Use a prioritization method that helps you evaluate the impact, effort, feasibility, desirability, and viability of each design decision.
Start with research to understand your https://thecapcut.app/capcut-pro-apk-download/ users, their needs, pain points, goals, and behaviors.
Incorporate business needs into your design process. Align your design decisions with the product vision, strategy, and objectives.
Test early and often with real users. Use prototypes, mockups, or wireframes to get feedback on your design concepts and iterations.
Thanks,
Helpful content.
Glad to hear!
As Bildr advanced, you encountered a shift in dynamics. Complex interfaces and novel UI paradigms without proper documentation led to user confusion. This prompted a strategic pivot towards prioritizing design and UX, which in turn unlocked the next growth phase. Your insights regarding striking the right balance, embracing change, and understanding the timing for integrating design are exceptionally valuable for startups navigating the intricacies of UX. Thanks!
🤝
This is great, i've been dealing with design vs function for a while while working on my first project.
I'm definitely attempting to give excessive value in both design and function and it definitely taken much longer then expected.
Thanks for the article, very thorough.
There is definitely still a lot of value in design... it's just necessary a little later than most of us expect!
Thanks for that tip @truedrew
Here are some points which can objectively help you to prioritize UX:
Use a prioritization method that helps you evaluate the impact, effort, feasibility, desirability, and viability of each design decision.
Start with research to understand your users, their needs, pain points, goals, and behaviors.
Incorporate business needs into your design process. Align your design decisions with the product vision, strategy, and objectives.
Test early and often with real users. Use prototypes, mockups, or wireframes to get feedback on your design concepts and iterations.
Thanks for sharing! I'm currently in the pre-launch phase of my startup, and I have to say this article really resonated with me. I've been grappling with the dilemma of how much emphasis to place on design and UX right from the beginning. The insights shared here about focusing on functionality and attracting "true believers" initially make a lot of sense. It's reassuring to know that it's okay to prioritize other aspects of product development at this stage.
Definitely. It took me a lot of years to understand this. In the past, I always placed a huge emphasis on design, thinking it would attract people. In realty, people are much more interested in their problem getting solved than a nice looking site that doesn't solve their problem!
Congratulations on starting your UI/UX career, and thank you for sharing valuable information. I truly appreciate it, and it has been immensely helpful for me as I begin this new journey in my professional life!
Glad to hear!
In the United Kingdom, all limited companies file their accounts publicly on the company's house. As someone fascinated by start-ups, I spend many hours investigating companies, and Twinkle .co .uk has to be one of the most fascinating.
They provide printable worksheets for schools, ordered by age, level, etc. According to my partner, these worksheets used to be time-consuming to create.
What's fascinating: they made nearly £29 million in 2022, and the website looks dated by modern Indy hackers standards. Further, no trendy tech stacks here; probably Jquery.
This leads me to think, design and UX - in certain verticals - does not nearly matter as much as we think. What matters, is solving the problem. In reality, we know this; however, it's so darn tempting to ponder over UX choices and tech stacks.
Very true for sure... a site that comes to mind in US in Craigslist. But at the same time, design and UX doesn't have to mean "beautiful design"... Amazon is a great example that. Some of the worst aesthetics, but some of the best UX at the same time.
In design, functionality should always come first. While feel are significant, they are auxiliary to making plans that are helpful, effective, and easy to use. By understanding the necessities and assumptions for clients, architects can make plans that genuinely address their issues and upgrade the client experience.
🤜🤛
I completely agree with your point. Different stages of a product require different focus. I've seen many perfectionist indie developers who never feel like it's "ready." In the beginning, it's crucial to quickly show the product idea to users and gather feedback to validate its value. Don't isolate yourself thinking you've created a world-changing product.
Another important point is that if there are already many competitors, success lies in attention to detail and providing an exceptional user experience. Sometimes we lose sight of the user's perspective and add things we think are important but may not be what users need. Even small UX changes can have a big impact on user behavior. Users' love for a product is limited, and minor user experience issues can lead to failure.
In the early stages, be open to criticism to grow quickly. During growth, be careful and focus on users' experiences to retain them.
Great points! If you have competitors with good UX, and there's no obvious product differentiation, I'd argue that you can't skip UX in that situation.
In that case, the role of UX becomes important much earlier... in fact, UX might be the only way to beat out that competitor!
I just started my UI/UX career and thx for sharing with a good info. That really help me a lot!
Great to hear!!
TBH I’m stick at this stage and ur article helped me resolve this issue. , i’m starting a new product and it’s my 1st time,
Thaaanks
Awesome to hear! And good luck! 👏
Nice post!
tldr: Think about UX after product market fit
😂 basically, but I might say "don't over-emphasize UX before PMF"... I was a little worried it didn't come across in the article, but I'm assuming a baseline UX quality that's at least acceptable/usable haha
This comment was deleted 10 months ago.