A document on Google Drive, FigJam, Miro, or any similar tool, that would share all the insights from Desk Research and Benchmarking (research being done from the competitors to get a full picture of the market)

A document on Google Drive that explains all the necessary aspects for planning user research, describing the user research methods chosen, the goals for this research, the timelines, the criteria for selecting the users for the research, and the methodology for documenting the execution of it.

After the execution of the user research, a document will be shared on Google Drive, FigJam, Miro, or any similar tool, that outlines the results of the user research method used

A deliverable to show what are the main frustrations of the users, and insights that are based on the user research. These frustrations will guide the UX/UI Process for designing a solution to all of those pain points.

This consists of creating archetypes for putting a face into the typical or typical type of user that this website is targeting. This is done with the goal of taking their needs, tasks, motivations, frustrations, and personal characteristics when creating the design solution

This deliverable goes deeper for understanding the user because it shows what the user sees, hears, thinks and feels, and what they do and say.

This deliverable goes one step further into understanding the user because it outlines the whole journey they currently go through for achieving their goals without this digital product

Now, this is the first step in defining the Information Architecture of the digital product. This deliverable establishes what if the sequence of steps and processes the user will be able to take on the digital product

Being the second step in defining the Information Architecture, this sitemap outlines the sections or pages of the digital product, based on the userflow previously created.

This is the creation of all the screens of the digital product, in a simple way, that focuses on creating the structure of each section and page, without entering into details of the copywriting, images, or colors, only focusing on the structure and the information on each page.

After having a meeting together, where we review the wireframes and gather some feedback on each screen, I will iterate on the wireframes to apply all the feedback discussed during the meeting.

After having a meeting together, where we review the wireframes modified and gather some feedback on each screen, I will iterate a second time on the wireframes to apply all the feedback discussed during the meeting.

Now, it's time to create the Design System, each will be documentation for maintaining consistency throughout all screens, for optimizing time in design, and for future modification or scalation of the digital product. This will be using the brand's identity or creating the branding if the business doesn't have one yet.

This is the result of applying the Design System to the wireframes, adding also all the copywriting, images, and the rest of the elements to create designs that look like something the user will find on the final design

After having a meeting together, where we review the mockups and gather some feedback on each screen, I will iterate on the mockups to apply all the feedback discussed during the meeting.

After having a meeting together, where we review the mockups modified and gather some feedback on each screen, I will iterate a second time on the mockups to apply all the feedback discussed during the meeting.

This consists of adding interaction to the mockups, for understanding what will be the flow of the screens and buttons on each one. The goal for this is to have a very close design and user experience to what the user will find when launched