UX is a perfect example why it is crutial to have people with different experience and point of view in team. If team understand that nowadays users make decidion extremely fast, they would never underrate meaning of UX in product development. Bad UX at saturated market can push away users and they will never explore amazing functions of your product.

- Usability Value: Usability testing is essential in product development, revealing how real users interact with your product. - User Insights: Observing users helps identify where they encounter problems or confusion, providing critical feedback. - User-Centered Decisions: This feedback guides user-centered design choices, enhancing the overall user experience. - Avoiding Pitfalls: Skipping usability testing can lead to a product that's hard to use or doesn't meet user needs, risking poor adoption rates and negative feedback.

Even if your time is squeezed, you always have option to show feature to someone who not use your product (office manages, collegues from other project) and avoid most critical UX issues. Also UX designer with good skill can help with development with all nuances from the beginning

Good project should starts with CustDev. UX is something that helps to meet user needs, but investigation user needs is the first step, even before team recruting

In Agile process, UX testing starts from the UI prototype. Designer shows desigion, team discuss it, designer improve it. After developing, designer check that functions implemented as it planned. Then QA team test feature's function.

In my practice, UX was often skipped as not as nessesary as speed and volume of implemented features. I disagree with this approach. Only product without competitors can effort this. Open market will exclude projects which makeUX discomfort from race. Better to support good UX (and perfomance) in case if your product will be presented to wide amount of users.