McLean & Company
Events Page
ROLE
Product Designer
TEAMS
FE devs, BE team, Marketing team
TIMELINE
3 months, 2025
TOOLS
Figma, Adobe
16+
events running through out a year
30%
increase in scroll depth
TASK
This project is to build a webpage in order to gather all types of events, webinars and programs in on place.
MY ROLE
collaborating closely with engineering (frontend and backend), as well as cross-functional stakeholders.
Defining UX direction through research synthesis and design exploration.
Aligning design decisions with engineering feasibility and stakeholder goals.
Driving end-to-end delivery from concept to QA and launch
Context and Constraints
The stakeholders requested a one stop for all types of events, webinars and conferences.
The users have hard time to find the events on the website.
Looking for informational exposure to reach potential clients.
Design Process
Stakeholder Wireframing: Stakeholders shared a wireframe with the features and content they wanted to add.
UX Review: Based on the request, I mapped out the iterations including the user flow, scenario mapping, copy elements and etc.
Design Phase: After approval, I designed high-fidelity pages for every scenario using SoftwareReviews brand guidelines, then carried design intent through handoff, QA and launch.
Key Decisions
DECISION 1
Realigned the UI components to the page
What I chose: Instead of custom UI styles to achieve stakeholders' preference, I reused the existing components across the site as much as possible.
Tradeoff: The referencing saved 20% of the development time on the front-end side.
DECISION 2
Introduced the viewcomponents file structure
What I chose: Introduced the viewcomponents file structure to build the reusable UI components.
Tradeoff: Established the development foundation and eased the process in this and future projects.
Outcome
ENGAGEMENT & EXPOSION
30%
more time spent on page with richer content.
16+
events running through out a year.
SEO-optimized
with targeted keywords and content
Reflection
What I'd do differently: I would request validation on the development in the UX review to catch the missing elements as early as possible.