Jehad Affoneh

What they show

A blog-first site. The homepage introduces him as Chief Design Officer at Toast, formerly CDO at Splunk and Head of Design at VMware, and says he writes about what he's learning in design, product and leadership, what's worked, what hasn't, and what he's still figuring out. Below that, posts. An About page adds the career line, advisory roles, and a newsletter subscribe. A Speaking & Interviews page lists podcasts and talks, each with a one-line summary of what he argued (the CDO as corporate executive, end-to-end experiences versus org structures, becoming experience-led rather than design-led).

Why it works at this level

Jehad is in-seat, so the constraint is total: nothing current can be shown. The site accepts that and turns the job itself into the content. Writing about what he's learning while doing the role is the most credible possible evidence for a CDO, because it demonstrates the thinking in real time rather than reconstructing it afterward. The speaking page is well done: instead of a list of logos, each entry summarizes the argument, so it functions as an index of his positions. The tone ('what hasn't worked, what I'm still figuring out') signals a leader who's secure enough not to perform.

What to steal

If you can't show the work, write about the job while you're in it. On a speaking or press page, summarize what you argued in each appearance rather than just naming the venue; it turns a vanity list into a reading guide to your views. Admit what you're still figuring out; at senior levels it reads as confidence.

What I'd change

One thing I'd push on. Every site here is good; this is the note I'd send the author.

The VMware era (growing a team from 30 to 300, open-sourcing the Clarity design system) is the most concrete leadership story he has and it lives in podcast interviews rather than on the site. One page telling it would anchor everything else.