The leadership portfolio

A leadership portfolio is a different problem from a designer's portfolio, and most advice on the internet doesn't know it. A designer shows what they made. A leader has to show what they led: the team, the decisions, the outcomes. Most of it is under NDA and none of it is a screenshot. Almost every portfolio gallery is a wall of IC work, so when a Director goes looking for how a peer presents themselves, they end up on LinkedIn with a couple of Medium posts.

This page is the map. It covers what's true at every level, then walks the ladder from Manager to Executive: what changes at each step, which sites in the collection show it best, and what most people get wrong. The depth lives in the entries. This is where to start.

What's true at every level

State your scope as numbersHow many people, which disciplines, how many managers report to you, what business you're accountable for. Put it in the first screen. A reader should know what you run before they read a word about how. Ramy Adel does this to the person (two units, 16 people). Ashwarya Subhluxmi does it to the dollar ($3B marketplace, five verticals).

Lead every case study with what you ledThe first sentence decides whether the reader sees a leader or a designer. "I led a group of designers, researchers and data analysts to…" is a leadership case study. "I designed…" is not, no matter how big the project. Chelsea Watson has the cleanest version of the grammar.

End with a business outcomeOriginations up 300%. Team from 5 to 15. A platform on 80% of searches. Process numbers (82 interviews, 40 screens) say you worked. Outcome numbers say it mattered. A small, specific number beats a big vague one.

Show that you still make thingsBehind every leadership hire is the question of whether you've lost the craft. Answer it before it's asked: a side project, a lab, a hundred-day challenge, something you built yourself. Chelsea's generative art, Tanner Christensen's apps and Buzz Usborne's founded-and-sold product all do this job.

Write the sentence that says how you lead"I build the picture, the team, and the product, in that order" (Ashwarya Subhluxmi). "I build platforms for the vision, not the ask" (Ben Roach). "I design the organization, not just the interface" (Harrison Wheeler). A thesis is what people remember and repeat. If you can't write yours yet, the portfolio isn't ready. The sentence is the portfolio.

Manager

What the reader is askingCan you run a team and still do the work? First-line management is a leader-doer job, and the hiring manager wants evidence of both at once.

What changes at this levelThis is where the portfolio is most likely to still look like a designer's, and it shouldn't. The mix is about half craft and half leadership, but the order matters: the organizational problem first, the artifact as evidence. The structural move that separates a Manager portfolio from a Senior Designer's is labeling. Every case study should say what role you played (manager, lead, IC) so the reader can see the hands-on work and the management work without mixing them up. Then add the things only a manager produces: a leadership page with your beliefs and the rituals that prove them (the 1:1 format, the pairing session, the team ethos doc), the team size before and after, and the recommendations former reports have written about you. Those are your case studies for the part of the job that doesn't produce screenshots.

Study theseOriol Bedia splits his site into Designer, Manager and Mentor columns and writes each role as a team outcome (Typeform from 5 to 15). Ben Roach leads with the org he built from zero and keeps a lab of working code to answer the craft question. Harrison Wheeler is filed under Director, but his Base CRM case study, "Building the Design Organization," is the best account of a first-time manager's job in the collection.

The common mistakeNot having a portfolio at all. Public Manager portfolios barely exist; this collection found two. The usual reasoning is "my work is the team," which is true, and is exactly why it needs writing down. If you're a Manager without a site, the three things you do for your reports (help them see themselves, grow them, teach them to have influence) are your content. Write them as if you were offering them to a stranger.

Director

What the reader is askingCan you run a business area, not just a team? Can you set direction for managers, hold a quality bar you don't personally enforce, and partner with product and engineering leads as a peer?

What changes at this levelThe case studies stop being about products and start being about the organization that made them. The best Director sites title their work as org changes ("Pods Over Silos: Restructuring to Build Faster") and show the product underneath as the result. Team infrastructure becomes a legitimate case study: a design hub, an onboarding path, a critique ritual, a research-ops system. These are shippable things with before-and-after states, they're rarely confidential, and they're exactly what a Director actually produces. Scope should be explicit (which verticals, how many pods, which managers) and the case studies should be dated so the reader can see you taking on more each time. The craft question is still live at Director, so keep one project that's yours, but it's no longer the argument.

Study theseHarrison Wheeler names the organizational problem in the first line of every case study and shows himself with his team in a community section no one else has. Andrés Clavijo makes the team's Figma design hub a full case study and opens every project with three questions: the business problem, the leadership decision, the measurable impact. Rakesh Patwari tags each case study with the kind of leadership it took (shaping direction, elevating execution, enabling success) so the reader sees range without being told about it.

The common mistakeListing leadership activities instead of showing them. "Hiring, strategy, exec partnership" in a bio is a claim. One story about restructuring the pod model, with the team before and after, is evidence. Most Director sites have the first and not the second.

VP

What the reader is askingHave you run a function, and what changed under you? Nobody is evaluating your design work. They're evaluating your judgment, your record with organizations, and whether you can be trusted with a budget and a seat at the table.

What changes at this levelThe unit of the portfolio changes from the project to the role. Company, titles held, years, then a narrative of what you inherited, what you changed and what you could measure afterward. Project case studies from a decade ago stop earning their place. Nobody hiring a VP wants a checkout flow from 2018, though they do want to know you'd recognize a good one. Craft shows up differently: in older work that carries the visuals while recent roles carry the scope, in the taste of the site itself, and in a founded product or side project that proves you still build. Writing matters more than artifacts. A VP who has published how they think about running a design org has shown the reader more than any redacted screenshot could. References become load-bearing: a product director describing you rebuilding a team from one FTE does more for a VP candidacy than anything you can say about yourself.

Study theseJoel Califa tells the career as a timeline and gives building the DigitalOcean team its own case study, with the same weight as a product. Aarron Walter organizes the whole portfolio by role and tenure, with the titles he grew into inside one company as the headline. Sandeep Datar shows the version where the work is entirely gated, and the career arc, the writing and six long references carry the site instead.

The common mistakeThe most recent, most senior work having no story. A rich case study from the IC years, then two VP roles with nothing but a title. The reader is left to take the years that matter most on faith. Even a short "what changed under me" paragraph for each role closes the gap.

Principal

What the reader is askingCan you raise the bar for people who don't report to you? Principal is leadership without the org chart: influence through the work, the systems and the standards, not through headcount.

What changes at this levelThis is the hardest level to portfolio, because the reader wants proof of craft and proof of influence at the same time, and most sites pick one. The answer is to keep the work visual and make every sentence of copy about leverage. Project captions that state the outcome in a line. Copy about the conditions you created, the practices you established, the teams you made better without running them. A product you built and shipped yourself, if you have one, settles the business-judgment question before anyone asks it. If you coach or advise other leaders, say so; it's evidence that your influence travels.

Study theseBuzz Usborne keeps a craft-heavy project grid while the copy around it is entirely about scale, conditions and teams, and his one-line project captions are the best micro-writing in the collection. Tanner Christensen puts books, talks and side projects in the same grid as his product work, so the mix says "this person shapes how others think" without a line of self-description.

The common mistakeHiding the craft to look senior. A Principal site with no visible work reads as a Director who couldn't get the title. Show the work. Just don't let it be the argument.

Founder

What the reader is askingWhat did you build, and would I want to build the next thing with you? The reader might be an investor, a co-founder, a client or a company that wants a founder's judgment in-house.

What changes at this levelThe problem flips. Founders have too much to show, not too little, and the portfolio has to choose. The strongest founder sites pick one idea and make everything an expression of it: a thesis on the homepage, a list of companies as evidence, writing as proof you're still thinking. The companies you founded become the credentials, listed by name. Ventures belong in the same grid as client work, each with a credit line that says what you owned. If you've started advising or investing, list the companies; it's a portfolio of judgment. Writing is the connective tissue between the executive years and the founder years.

Study theseScott Belsky puts one sentence on the homepage and makes the books, newsletter and investments all evidence for it. Tobias van Schneider attaches a founder credit to every venture and files them next to Spotify and NASA. Andy Budd lists the institutions he built (an agency, two conferences, a leadership community) as the headline and organizes the site around what a visitor can get from him now.

The common mistakeBarely mentioning the company you're known for. Founders move on and their sites follow them, which leaves the reader without the evidence. Belsky's site scarcely mentions Behance; Budd's doesn't show Clearleft's work. One paragraph on the thing that made the rest possible is enough.

Executive

What the reader is askingWhat do you believe about how design should work inside a company, and can you say it in a way a board would understand? At this level the audience is CEOs, boards and executive search, and they are not going to read a case study.

What changes at this levelMost sitting executives don't have a portfolio at all, and the ones who do have mostly stopped showing work. What replaces it is a published operating philosophy, written while in the seat: how the org is structured, what counts as done, what a prototype is for, what the team believes. Speaking and press pages work better as an index of positions ("what I argued at each venue") than as a list of logos. The one positioning sentence under your name should be about systems, standards and operating models rather than products. Scope is stated as a fact (headcount, disciplines, geographies, number of directors), once, without a screenshot.

Study theseMike Davidson runs a twenty-year blog that now reads as a public record of how he runs design for Microsoft AI. Jehad Affoneh writes about what he's learning as a CDO while doing the job, and his speaking page summarizes what he argued in each appearance. Aastha Gaur has almost no product work on her site and instead publishes a management curriculum tagged by level.

The common mistakeNo anchor. A site with a thesis, writing and an offer but no role history or scope gives a cold reader nothing to hang the claims on. One line of where you've been and what you ran fixes it without adding a portfolio section.

If you're a Manager

The gap in this collection is at the bottom of the ladder, which is where the need is greatest. If you manage a design team and have a site that shows it, submit it. If you have a site that doesn't yet, the Manager section above is the brief. Write the leadership page, label your case studies, state your team size before and after, and send it in.