Interviews with multiple stakeholders.
Audit has been conducted over UI explorations delivered by client.
Session of exploration and analysis with client's experts (Business Analysts).
Delivered for UX and technical validations
Delivered for UX and technical validations
A set of 5 user testing sessions were conducted for concept and UX proposal validation.
Methodology used to prioritize and identify UX iterations over proposal.
Document delivered to development team.
Figma file with documentation, prototypes and user stories delivery.
Initial UI explorations were delivered by client. A UI audit and exploration discovery was held. Several inconsistences were discovered and UX expectations were clarified.
Objective: Understand from general to specific the way the client envisions the functionality in his product user flow and alignement with other features across the platform.
Task analysis session was conducted with the client's BAs team with support of the Endava's BA.
The diagram was mainly divided in main tasks, subtasks and each one of the user's possible actions and inputs.
Different user flows were identified and per each of of them a different flow diagram was created and shared with stakeholders. As for current project the flows identified were:
- First crop / Assign boundary
- Assign boundarie
- Remove boundaries
- Edit crop record
- Delete crop record
- New crop record (from drawer)
- Delete boundary
Wireflows allow stakeholders to understand and visualize the user journey as a whole. Specifically for the development team it helps in accuracy and user story estimation.
Five moderated user testing sessions were carried out with different stakeholders within the clients internal users. Stakeholders roles in the company were: BAs, Director of Agronomy Solutions, Product Owner and UX Researcher.
Mission 1:
User selects boundary to split
Mission 2:
- User selects boundary to split it
- User split without selecting
- User uses Dropdown to Create Cropping Record
- User uses New Cropping with selecting area.
Mission 3:
Assign to existing crop record
Mission 4:
Edit Crops Records
Mision 5:
Delete boudaries and Crop Records
Notes were taken with support of the clients product design team
Used this clustering technique in order to identify painpoints and insights that constantly hustles the users tested
Delivered along with the prototypes. Helps the developers understand in detail the touchpoints physical components and backend actions triggered by users.
Each squad Front End and Back End tickets is fed by a Figma prototoype link, static images, video clips (micro interactions) and behavior notes for developers reference.
Doing boxes and helping people since 2015
