The Brief Was Bigger Than It Looked
When the project came in, it sounded straightforward on paper. A San Francisco-based startup needed their digital product redesigned and then presented — wireframes, mockups, visual branding, and a PowerPoint deck that explained every design decision to the internal team. Simple enough, I thought.
But once I sat down with the actual product, I realized the scope was much wider. The existing interface had been built quickly and functionally, with no consistent design language. Color usage was inconsistent, icons felt borrowed from different eras, and there was no clear visual hierarchy guiding users through key flows. Before I could even think about a UI presentation graphics design, I needed to rebuild the visual foundation from scratch.
Starting in Figma: Wireframes and Visual Identity
I opened Figma and started where every proper redesign should — with low-fidelity wireframes. The goal was to map the user journey before applying any visual treatment. I sketched out the main screens, identified where users were likely losing context, and restructured the navigation to feel more intuitive.
From there, I moved into visual identity. The startup had a rough color palette and a logo, but nothing formalized. I developed a refined color scheme, selected a type pairing that felt both modern and readable, and created a small icon set that matched the product's tone. These elements fed directly into the high-fidelity mockups I built next.
The mockups covered the core use cases — onboarding, dashboard, and key interaction states. By the time I had three or four screens polished in Figma, the product was starting to look like something users would actually want to engage with.
The Presentation Was Where Things Got Complicated
Here is where I hit a real wall. Translating detailed Figma work into a coherent PowerPoint presentation is a different skill set entirely. I needed the deck to do more than show screenshots — it had to walk the development team through the rationale behind each design decision, explain the brand choices, and set up clear handoff instructions.
I built a draft in PowerPoint. It had the screenshots, a few annotations, and some slide titles. But when I reviewed it honestly, it did not do justice to the work. The slides felt flat, the layout was inconsistent, and the narrative flow was missing. A product redesign deck needs to tell a story — from problem to solution — and mine was not doing that.
After spending a full day trying to fix it and still feeling like the presentation was working against me, I reached out to Helion360. I shared the Figma files, the draft deck, and a brief on what the presentation needed to communicate. Their team took it from there.
What the Helion360 Team Delivered
The turnaround was faster than I expected. Helion360 restructured the entire presentation with a clear narrative arc — starting with the problem the redesign was solving, walking through the wireframe-to-mockup process, and presenting the visual identity decisions with proper context and design rationale.
Every slide had a consistent layout, a visual hierarchy that matched the Figma work, and enough whitespace to let the design breathe. They incorporated the UI mockups as full-bleed visuals where it made sense, and used annotated breakdowns for screens that needed explanation. The deck finished with a section laying out developer handoff notes in a format the engineering team could actually use.
It was the same content I had been struggling with, but organized and presented in a way that made the product redesign feel intentional and polished.
What This Project Taught Me
Designing in Figma and presenting in PowerPoint are two genuinely different disciplines. I was comfortable with the former and underestimated the latter. A strong product redesign presentation does not just show what changed — it explains why, and it does so in a visual language that matches the quality of the design work itself.
The collaboration also changed how I think about handoffs. The final deck became a reference document the product team kept returning to during development. That kind of usefulness does not happen by accident — it requires deliberate structure and visual clarity from the start.
If you are working through a similar project and find that your presentation is not matching the quality of your design work, Helion360 is worth reaching out to — they handled exactly that gap for me and delivered something the team genuinely used.