Overview
Reconhecimento de Paternidade is a service where mothers can start the paternity acknowledgment request electronically. The service has intention to positively contribute to improving the scenario of absent paternal recognition in the country.
Role
User Experience, product optimization, strategic redesign, information archicheture, flow study and flow optimization, stakeholder alignment
The problem
The project had been fully designed by a previous team member who left the company. After this transition, business rules and operational requirements changed, making the existing user flow outdated and misaligned with the new process. Several screens and fields were no longer relevant, and the flow contained steps that caused friction and did not reflect the updated service model.
To fully understand the current challenges, I met with the client and the Product Manager to clarify the project’s context, identify pain points in the existing process, and gather the updated business requirements.
Goals
Realign the product with the updated requirements by reviewing the entire journey, removing unnecessary steps, and restructuring the flow. This included designing new screens to support the revised process and creating the document layout to ensure consistency, clarity, and compliance across the system.
Project Adjustments
I eliminated a small set of fields that no longer aligned with the revised operational rules, ensuring the flow accurately reflected the new process. Then, I aligned the updates with the Product Manager and the developer to validate requirements and feasibility. Once confirmed, I created the document templates and started designing the new signing flow to complete the updated experience.
The new signing flow
First, I designed a preliminary version of the flow to validate the direction with the Product Manager. During this validation, additional requirements surfaced: specifically the need for the father to edit his own information in the document, which consequently required the mother to sign the updated version. Based on this, I redesigned the flow to accurately represent the new steps and dependencies.
After these adjustments, the Product Manager and the client approved the updated flow, allowing me to move forward with prototyping.
Prototyping
The prototype was created using components from our new UI Kit. For confidentiality reasons, the document was hidden in the image.
After the prototypes were completed, the client approved the solution, and the project is now awaiting implementation.
What I learned from this project?
I learned how to effectively take over an existing project, assess what should be kept or removed, and adapt the flow to new operational needs while maintaining coherence and usability. This project also reinforced the importance of iterating quickly, validating early versions, and staying flexible as new requirements emerged.