Rachel Kobe

What they show

A minimal homepage under the headline 'Designing What's Next' with a one-sentence positioning ('I architect the systems, standards, and cultural foundations behind intelligent products') and three doors: Writing, Speaking, Advisory. No case studies, no logos in the hero. The nav adds About, Courses and Contact. Recent posts carry titles like '10 Truths From Building Design Organizations at Scale', 'Mastering Orchestration: 8 Ways to Drive Business Outcomes as a Design Leader' and 'Design Leadership In An AI-Native World'.

Why it works at this level

Once you've held CDO-level roles, the audience for your site changes: it's boards, CEOs and executive recruiters, and they aren't going to read a case study. They want to know what you believe and whether you can articulate it. Rachel's site is built entirely for that reader. The positioning sentence is about systems and operating models rather than products, which is the correct altitude for the title. The writing titles are specific and numbered, so even a skim communicates that there's a body of thinking behind the offer. It's a portfolio of judgment with the work removed.

What to steal

If you're at VP or above, write the one sentence that describes what you build when you're not building products (systems, standards, culture, operating models) and put it under your name. Give your writing titles that promise a specific number of specific things. Decide who the site is for, and if it's executives, take out anything they won't read.

What I'd change

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

There's no work anywhere, not even a role history, so a reader who doesn't already know the name has nothing to anchor the claims to. A short career line under the positioning would fix it without adding a portfolio section.