This website, building my portfolio as a working product

The short version

The problem

A template portfolio would not show how I think, and would not sound like me.

What I did

Built this site from scratch with AI as the building partner, keeping tone, structure and judgement mine.

What it was worth

A live product I keep refining while using it for my own job search.

The call

Treated it as a working product, not a brochure. It changes because I use it.

I did not want a portfolio that read like a tidied up CV, or a template with my name dropped into it.

I wanted a working product that shows how I think, what I have built, and how I handle the awkward space between an idea, the logic behind it, the wording and the delivery.

Two reasons. The site had to sound like me and not like portfolio copy. And I wanted somewhere to keep my product sense in use by building, testing, fixing and refining something real.

Claude and Codex wrote essentially all the code. I kept tone, scope, hierarchy and what deserved to stay.

The loop was short. Write or rewrite a section, see it in context, click through the page, notice what feels off, fix the wording or the spacing or the logic, and go again.

That made the work faster without making the judgement automatic. AI got rough ideas into the browser early. The useful part was reacting to something real instead of discussing an outline for too long.

The site became a small system rather than a page.

• a homepage that leads with the builds, then the career work as expandable rows, each opening on what changed and what it was worth
• an examples index with all fourteen, grouped by whether they shipped in a role, were built on my own time or were exercises
• a write-up for each, with a short version at the top for whoever will not read the whole thing
• a decision log on Archive Lens, with what I got wrong left in
• a method page, an about page and an experience page carrying the longer story
• a content structure that takes a new example without touching the rest of the site

The pages have to hold each other up. The examples have to support the claims on the homepage, and the about page has to add to the story without turning into a corporate profile.

Most of the useful work was in the refinement, not the first draft.

I kept adjusting the pace of the pages, the wording of headings, the order of examples and how much each section should carry before it became too much. Some changes were visual, some structural. A surprising amount was getting the tone to sound less rehearsed.

The site also became the place I smooth rough edges. Bugs, copy, navigation, mobile layouts, and the small frictions that quietly make a page worse.

That is one reason I think building matters in a product role. Once you click through something yourself, you notice the unclear transitions, the missing states, and the parts that technically work and still feel wrong.

1. April 2026
   Reshaped the homepage so the prototyping approach and the proof came through earlier.
2. April 2026
   Reworked the examples copy and order so the page read as work rather than a gallery.
3. April 2026
   Rewrote copy across the site to sound like me and drop the portfolio clichés.
4. April 2026
   Smoothed navigation, spacing and mobile behaviour so the site felt calmer to read.
5. April 2026
   Added this example, so the site documents itself the same way as the other builds.
6. August 2026
   Rebuilt the whole site on a new dark design, with the work list restructured around what each change was worth.
7. August 2026
   Swapped the palette to light and restructured again. Own-time builds now lead the page, and the career work is a compact list of expandable rows.
8. September 2026
   Went over every page for verbal tics and stiff sentences, using the writing rules from Resume Builder as the checklist.

AI is fast. Judgement is slower.

Generating sections, layouts and variations is easy. Deciding what sounds true, what belongs on the page, what is trying too hard and what needs another pass is the work, and it feels exactly like product work. The same lesson, with evidence, is in the Archive Lens decision log.

It also confirmed something I already believed. Building real things keeps me sharper as a Product Owner. It keeps my eye on detail, makes trade-offs visible, and gives me a grounded sense of what is awkward, what is clear, and what still needs simplifying before someone else has to carry it.