Harrison Wheeler

What they show

A one-page site that opens with a role timeline (Manager at Base CRM, Director of Product Design at LinkedIn, podcast host, advisor, now founder of LeadCraft) and a 'Select work' section explicitly labeled as case studies in design leadership. The titles do the work: 'Pods Over Silos: Restructuring to Build Faster' (99+ quarterly requests, morale at a low, restructured to ship the AI roadmap), 'Building the Design Organization' at Base CRM, and a B2B events bet reframed and funded off a $100M+ pilot. Then the podcast with its numbers, a community section with photos from meetups and talks, a writing list, and a footer with follower counts across six platforms.

Why it works at this level

This is the most complete answer in the collection to 'what does a Director actually show.' Every case study summary names the organizational problem before the product problem, so the reader is reading about leadership decisions from the first line. The timeline at the top establishes the arc without a resume. And the community section does something the others don't: it shows him with people, which is the job. The podcast and follower counts read as reach, not vanity, because they sit next to the work rather than in front of it.

What to steal

Write case study titles as the organizational shift, not the product: 'Pods Over Silos' says more about a Director than any feature name. Lead each summary with the state you inherited in one clause, then what you changed. If you speak or run a community, put photos of it on the site; it's evidence of the part of leadership that doesn't produce screenshots.

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 CV is a PDF link in the nav rather than a page, and the case studies open in modals, which makes them hard to share individually. Each one deserves its own URL.