Advocating for validating solutions before development

Context

The project began with a well-defined scope focused on executing user stories for Bradesco Global Solutions, primarily centered on UX/UI delivery. There was no formal discovery phase or validation process planned, and the initial goal was limited to designing interfaces based on predefined requirements. However, as the project progressed, an opportunity emerged to enrich the design by incorporating global corporate user needs and advocating for validation practices before development.

The main challenge was influencing the team to adopt validation methods and structure hypotheses while working within the constraints of a predefined scope.

Scope

My role evolved beyond interface execution to include:

1. Identifying gaps in the process, particularly the absence of validation.
2. Researching global references to address corporate user routines and needs.
3. Prototyping solutions to test assumptions and prepare hypotheses for the research team.
4. Influencing stakeholders to prioritize validation as a key step before development.

Approach

1. Adapting to the predefined scope

• Worked within the existing framework to deliver on the initial UX/UI requirements while seeking opportunities to introduce strategic improvements.
• Focused on small, incremental changes to demonstrate the value of validation practices without disrupting the workflow.

2. Researching global needs

• Conducted a benchmarking exercise to gather global references and best practices for corporate users.
• Used these insights to enrich the design and ensure solutions were aligned with real-world corporate user behaviors and expectations.

3. Prototyping as a validation tool

• Created interactive prototypes to go beyond static designs, enabling early validation of key functionalities.
• Structured hypotheses around the usability and effectiveness of proposed solutions and prepared them for handoff to the research team.

4. Influencing stakeholders

• Advocated for validating solutions before development, emphasizing the risks of rework and misalignment with user needs.
• Collaborated with the research team to ensure the prototypes and hypotheses aligned with their validation framework.

Expected Results and Impact

Although this phase of the project was focused on prototyping and hypothesis structuring, the anticipated impacts included:

• Improved Solution Alignment: Ensured that proposed solutions addressed the global needs of corporate users.
• Reduction in Development Risks: Early validation aimed to minimize rework and improve efficiency.
• Strategic Insights: Prototypes served as a foundation for the research team, accelerating their ability to validate and refine solutions.
• Enhanced Collaboration: Integrating design and research fostered better alignment across teams.

Reflection and Learnings

This project demonstrated that even within a predefined scope, there are opportunities to introduce strategic practices that elevate the quality of the final output. Key learnings include:

• Proactivity matters: Identifying gaps and advocating for improvements can transform a purely operational role into a strategic one.
• Prototyping as strategy: prototypes are not just visual tools but powerful instruments for testing and aligning teams.
• Influence through value: showing stakeholders the benefits of validation builds trust and drives change.

Looking forward, integrating validation earlier in the process and further aligning research and design teams could enhance future outcomes.

Check out other study cases