01. Discover
This phase is all about asking the right questions. Why do we want to implement/change something? There is a collaboration between the project manager, product owners, stakeholders, and UX designers to get all the answers. In Talend, we have different teams for different products. Once we frame the problem to be solved, we define them and put them on the product roadmap.
My role : I spend a significant amount of time conducting user research, defining priorities and cross-functional product impacts to understand the needs and behavior of our target customers. This research can involve surveys, interviews, and usability testing. I collaborate mostly with PM, PO, customers and engineering team.
02. Define
This phase goes through multiple tasks and process definitions. It enables designers to focus on the high level to the detail orientated design. These tasks include:
- Define product scope & structure : A design document in a powerpoint which is uploaded on Box and accessible to teams.
- Define flows and processes: We use figjams to build user flows and processes.
- Define scenarios and edge cases: Figjams has a section for the edge cases.
- Define details: Creating low fidelity designs on Figma.
My role: Based on the user research and persona creation, I filled all the information in the project document which contains the wireframes, user flows, use cases and journeys. It also contains the technical feasibility and API documentations for the features. Once the low-fi prototypes are discussed and approved, I work on the visual design, which is reviewed later by other peer designers.
03. Test & Iterate
Once we have the low-fidelity wireframes, we test the ideas with users, and then we iterate on the design based on the results from those tests. The tests are either performed with customers or internally.
We also hold sessions such as design critics and peer designing.
My role : With the help of a research team and other designers, I test the prototype with the internal and onsite users. We analyze the results and discuss it with the PM,PO and the team to take decisions on the changes and iterate the design if needed. I am responsible for finalizing the design and get it ready for the refinement session, where the developers can accept the tickets and start working on implementation.
04. Implementation & Evaluation
Every Wednesday, the engineering team has a refinement session. Designers demonstrate their designs to all the devs, QAs, and engineering heads. There can be discussions on the outcome that can be approved or disapproved. Once it is approved, implementation starts.
My role: Once the design is approved and in implementation, I tag them in Pendo, so we can measure the clicks and adoption later. Overall, a UX evaluation involves gathering data and feedback from users, and usage metrics to identify areas of the product that need improvement and to make informed design decisions. I also use NPS, CSAT and sometimes surveys, user testing and questioners to get more inputs on the newly added features.
UX evaluation
Surveys, interviews, and customer guides are ways we do UX evaluation. To measure the success of a feature, we compare the numbers with the old data. We tag all the new and old features on the Pendo. Heatmaps and the feature clicks are some of the ways we report the adoption of the feature.
Working on the Feedbacks
Based on the adoption and the customer support tickets, we evaluate if we have built the right product. Every 3 months, we run questionnaires to customers for the newly added or improved features. If the NPS is down, or we find critical comments about the feature, we reiterate and try to update the major usability issues via UX improvement tickets.
