Not all useful product work ships directly into code. Sometimes the highest-leverage thing you can do is make the current state visible, sketch better structure, and give the team a more coherent direction to build toward.
That was the role of the MetaLearner redesign work in Figma.
What the Figma work included
The Figma file was not just a collection of screens. It included:
- a current-state overview of the frontend
- redesign explorations
- mobile-responsive layout directions
- industry inspiration references
- a developing design system for components, typography, colours, primitives, and icons
- forward-looking thinking around charts and data visualization
That combination made the file more useful than a static mockup deck. It was trying to show both where the product was and where it could go.
Why this work mattered even alongside shipped frontend work
The frontend improvements I implemented during the internship were useful on their own, but the Figma work gave them more shape. It helped answer questions like:
- what should become a repeatable component instead of a one-off fix
- what typography and colour choices actually support clarity
- how should mobile responsiveness behave as a system rather than page by page
- what should charting and data visualization feel like over time
I care about that layer because ad hoc UI work can solve immediate pain while still leaving the product visually inconsistent. A design-system direction makes it easier for later frontend work to feel cumulative instead of fragmented.
The part I found most valuable
I liked that the redesign work did not pretend the product started from zero. It acknowledged the current state, studied it, and then explored better directions from there.
That is a healthier way to work on redesigns in real products. Most products are not waiting for a grand replacement. They need a usable bridge between the interface they have now and the one they could realistically grow into.
What I took away from this track
This part of the internship sharpened something I already believed: design exploration is most useful when it improves implementation judgment.
The best output from a redesign exercise is not just nicer screens. It is a clearer decision-making environment for future code, components, and product tradeoffs. That is what I wanted this Figma work to provide.