In Summer 2025, I joined EdisonOS as a Lead Product Designer on a 3-month consulting engagement.
The goal: help lay the foundation for their new B2B2C SaaS product — built for test prep academies, tutors, and students.
My responsibilities included:
Designing the application modal and mapping key user flows
Creating the first version of the design system — including components, grids, and typography
Providing design strategy, UX consultation, and UI guidance across the product
Working closely with PMs, engineers, and stakeholders to ensure alignment at every step
The focus was not just to design screens, but to create a system the entire team could build on.
Lead Product Designer
Duration
Apr 2025 - Jun 2025
Web
B2B2C SaaS
EdisonOS is a test-prep platform for academies helping students crack exams like SAT, ACT, AP, and PSAT. When I joined, the team was preparing to rebuild the product from scratch.
I started by speaking with stakeholders, listening to customer calls, and exploring how the platform was used. This gave me a clear picture of the users, their needs, and where the experience was falling short.
The existing product had grown organically, without a clear system or strategy. As a result:
Key user flows were fragmented.
The visual language was inconsistent.
Collaboration between design and development was unstructured.
The goal was clear:
→ Align the team on a shared vision.
→ Create scalable systems and flows.
→ Set a strong design foundation for the new product.
Laying the foundation
To avoid repeating past mistakes, I defined a clear design strategy:
This gave the team a shared mental model — and kept our work focused.
I also synced early with the engineering team to:
Plan the developer handoff process
Set expectations around design specs
Align on how the new design system would be integrated
We agreed that as we designed, we'd build a library of reusable components - not just screens.
With early context in place, I brought the team into the process.
I created an open FigJam space where everyone — from product to customer success — could drop insights, ideas, and user needs.
This wasn’t about design opinions — it was about surfacing what really mattered to users.
From those inputs, I defined the core objects of the product — the building blocks that power everyday actions across roles.
This helped everyone see the product the same way.
Then, I mapped key user flows — especially for Admins, Tutors, and Students — and shared them for alignment.
Once the team aligned on core flows, I created an application modal — a simplified structure showing how everything connects in the product.
This helped clarify navigation, relationships between objects, and what each role could do where.
It became a shared reference for the whole team — design, dev, and product — before moving into screens.
Visual design is how users feel and navigate the product — it's the layer they interact with every day.
To bring clarity and consistency, I created a style guide covering Color palette, Typography scales, Grid and spacing system, Core components etc.,
This guide became a shared reference for both designers and developers — reducing guesswork and helping maintain consistency across the team, especially as more contributors joined the project.
Clarity early on saves time later. Getting alignment before screens made every next step smoother.
Good systems outlive features. The design system is now a reference point — not just a UI kit.
Design is a team sport. The best ideas came from conversations, not just Figma.
This project is protected by a Confidentiality Agreement, please contact me for additional information related to it.
