When the final product design fails...

Although companies follow extensive Design thinking  and UX Process,  we often wonder why the end delivery failed to meet the customer expectations.   Despite the data collected  during the  discovery phase has been quite impactful in deriving user insights and identifying the key problem statement, the end deliverables fail to bring a great experience.  Need to know why?      Here are some of the  checkpoints.  

1. UX team understands the new requirements and initiates a user study (ethnography)
2. Product Owners approves the Clickable user flow through an early  paper prototype for all given user journeys
3. Product Owners confirm with stakeholders and random users via a quick 5 minute test...
4. Product Owner and UX head  to discuss future feature scalabilities and the stability of the existing framework 
5. UX team to confirm with Product Owners (based on their studies) the below
   1. Supported platforms, Browsers,  Versions
   2. Accessibility Support (required / not)  if yes to which level (A, AA, AAA)
   3. Multi Device support (Responsiveness)
   4. Brand adherences
6. UX team builds high fidelity Prototypes in accordance based on the approved Paper design and flow
7. UX head to present all visual and interactive components included in the final prototype to  the PO and Engineering head to ensure the proposed design is "doable" using the current tech stack. 
8. PO to approve the Final version of the prototypes for the defined user flow for the current release. 
9. UX team handovers the design kit to the engineering team
   1. Clickable final Prototype
   2. User journeys and flows  (for the current release)  
   3. Design Dimensions
      1. gutters,  Styles,  Red-lining kit
      2. Block diagrams to show the tile spacing   
   4. Documentation covering Visual Accessibility aspects that needs to be considered 
   5. Every image in the usable format  as a file with the given dimensions 
   6. All instances /behavior of buttons to be explicitly documented with style guide
   7. Deliver a Style guide document  with the screen shot of  the component 
10. PO to ensure the UX team and the engineering team has a clear  vision of the scalability of the existing program and scope
11. UX team to ensure a proper UX QA is in place for every Sprint/Pi 
12. UX to ensure Engineering team understand every aspect of the shared design and the use of style and tiles prior to the start of the  development phase

There are three "process" that needs to align well for any product to successfully launched 

1. UX Process
2. Thought process of the team (UX, Front End and the Application development team) 
3. Development process -  How the engineering team evaluates, respects the design and maintains the overall aesthetics and interactions of the UI

PO= Product Owner

_{Image source :https://www.google.com/url?sa=i&url=https%3A%2F%2Ftwitter.com%2Fsmashingmag%2Fstatus%2F1059811167588225024&psig=AOvVaw0QQN_gNt3p8elhI4OutvrO&ust=1679670166384000&source=images&cd=vfe&ved=0CA8QjRxqFwoTCNigyo6p8v0CFQAAAAAdAAAAABAE}