Designing My Design Portfolio

The previous portfolio no longer represented the designer I had become. It could show finished screens, but it struggled to communicate stronger storytelling, clearer information architecture, enterprise positioning, systems thinking, and the ability to take work from idea into working interfaces.

Hiring managers do not only ask what I made. They ask how I think, how I structure complexity, and whether I can collaborate across product, design, and engineering. The rebuild started from that gap — not from a desire for a more decorative site.

I framed the redesign as a product brief with a short set of goals. Everything that followed — structure, writing, navigation, and implementation — had to earn its place against this list.

These principles shaped what stayed, what was cut, and how each section was ordered. They are short on purpose — used as checks during critique rather than slogans on a slide.

Most of the design happened in the browser, not in a finished Figma file handed off later. The sequence below is the real loop: content and structure first, then layout, then critique, then revision — repeated until the story held together.

AI was part of the workflow the same way a sharp editor or a fast IDE is part of the workflow: useful for exploration and implementation speed, never the author of product decisions. I set the goals, rejected weak directions, reviewed every meaningful change, and owned the final design.

Throughout development the site changed because of self-review, peer feedback from former colleagues and experienced UX designers, and an engineering mindset that asks whether something is clear, buildable, and honest. Formal usability testing was not part of this phase — the loop was iterative critique against how hiring managers actually read portfolios.

Several shifts define the difference between the previous site and this one. They are product decisions, not visual preferences.

Writing is harder than UI — and more decisive for first impressions. Removing content improved clarity more often than adding it. Iteration beat waiting for a perfect Figma pass. AI accelerates the loop but does not replace judgment. Real feedback from people who hire and design changed the product more than solitary polish. Building my own portfolio was a reminder of what visitors experience when a site is dense, unclear, or self-indulgent.

This remains a living project. Next work includes expanding case studies, continued responsive refinement, introducing a dedicated portfolio design system for the patterns that emerged in code, more deliberate motion, and additional enterprise work as it is ready to tell honestly.

The commitment is the same as the original brief: treat the portfolio as a product that can keep evolving without losing its story.