Designing a portfolio that survives career evolution

This site rebuild was not primarily visual work. It was an information architecture problem.

The challenge: show depth in learning innovation without hiding the broader product, UX, service, AI, and tooling work that makes that depth useful.

The structure that held up was simple:

• Projects for proof.
• Insights for thinking.
• Resources for transfer.

Once those buckets were stable, most copy decisions became easier. Every line either clarified positioning, demonstrated work, or helped someone act.

The practical lesson: career narratives break when they rely on chronology alone. They stay coherent when they are organised around a durable practice question.