Updated Login
ConstructConnect | UX / UI Design | User Journeys | Task Flows
The company login was cleaned up and completely redesigned to improve usability and security. Steps for new users to get started in their accounts were reduced, making onboarding smoother and faster.
AI was used to help speed up the identification of the initial user flows based on current data, ensuring the redesigned process met user and business needs efficiently and by deadline.
This project was driven by the urgent need to migrate off Auth0 before the subscription expired — a hard cutoff that would have disabled access for some users and disrupted business operations. From the start, I collaborated with developers to ensure the proposed login and onboarding updates were technically feasible within the tight timeline, and partnered closely with the project manager to help keep milestones on track.
A UX partner worked with me on the mapping of overall user journeys, while I concentrated on creating the detailed task flows used for the interactive prototype. I used ChatGPT as a starting point to outline an initial version of the user and account setup flows, which the team then refined and iterated on together. My focus was on simplifying the new‑user process after first login by reducing required information entry and creating a clearer, more guided experience.
Throughout the process, I coordinated with stakeholders to ensure the solution met both business needs and user expectations — and most importantly, was delivered before the non‑negotiable deadline.
We used miro boards to collaborate and capture various user and task flows
The overall layout and design remained simple due to the tight deadline. We still created the flows in Figma to make sure that the developers understood where user was coming from. This helped keep the team in alignment and facilitated questions about flow and technical feasibility.
Part of the handoff was making sure that we annotated the figmas, this was a tight deadline so we did not have a clickable prototype for every interaction. This also helped when they were writing the Jira tickets.
