Team pages that signal craft

A founder deciding between two studios will open five tabs of portfolio work — and then do something most teams forget: she will open the team pages, side by side, and ask a single question. Whose hands do I want on my product?

The team page is where a studio stops being a logo wall and becomes forty-five people with judgment. Buyers know the studio that did last year's famous case study may not be the studio that does their project — they're buying the current roster. Which means the team page is one of the most commercially loaded pages on the site, and it is usually treated like a yearbook.

Here is how to build one that sells craft instead of listing bodies.

The portrait is a policy, not a photo shoot

Every studio faces the portrait question, and most answer it with whatever the camera produced: a dozen mismatched headshots from three different offsites, inconsistent crops, one person against a brick wall from 2019. Mismatched photography quietly argues that the studio can't even maintain consistency on one page about itself.

There are three coherent answers:

A real photography programme — same photographer, same light, same background treatment, reshot as people join. The best possible result and a genuine operational commitment. Half-hearted versions (one good shoot, three years of drift) age worse than no photography at all.
Illustrated portraits — a commissioned style applied to everyone: geometric, hand-drawn, risograph, whatever fits the brand. Immune to drift, scalable to new hires, and a craft sample in its own right. This is our choice at Brassfern — and the same logic underlies photography art direction everywhere on the site.
No portraits — typographic cards with name, discipline and a line of character. Honest, fast, and better than bad photography.

What is not an answer: AI-generated photoreal faces. A real person's face stands behind their words; a synthetic face hides behind them. If the roster is stylised or fictional, say so — illustrated portraits signal stylisation immediately, which is precisely why they work. Photoreal fakes demand the reader's trust and repay it with a lie.

Bios: judgment over job titles

"Senior Product Designer, 8 years experience" is a LinkedIn row. It tells a buyer nothing about how a person thinks. A craft-signalling bio shows judgment through specifics:

What they believe: "A type scale is a moral position."
What they do in practice: "Runs the Thursday critique with an iron rule: be specific or be quiet."
What they've shipped: links to the case studies and articles their hands touched.

Three lines, each doing a job. The belief line gives the reader a taste of the studio's taste. The practice line makes the place feel inhabited — rituals, habits, running jokes with stakes. The shipped-work links turn the bio from a claim into evidence.

We keep bios to roughly forty words. Longer bios drift into CV; shorter ones drift into name-tag. Forty words is enough room to say one true, specific thing per person — and if you can't find one true, specific thing, that is a hiring signal, not a copywriting problem.

One discipline worth adopting: rotate which facts you publish per person rather than filling every field for everyone. One person gets their side project, another gets the talk they gave, another gets the tool they maintain. Uniformity reads as a form; variety reads as people.

Structure: a roster, not a ladder

Most team pages are organised by seniority, which is a sitemap of internal politics rendered as a web page. The reader doesn't care who's partner-track; the reader wants to know who'd be in their stand-up.

Structures that signal craft better:

By discipline cluster — design, engineering, strategy, growth — because it mirrors how a squad would assemble for the buyer's project.
Alphabetical with egalitarian order — founders in among everyone else, which quietly declares something about the culture (and is easy to maintain honestly).
By location when the studio is genuinely distributed — timezone and place are practical buying information, not trivia.

Whatever the primary order, give every person equal visual weight on the index. The headshot grid where the founders get big squares and everyone else gets thumbnails is an org chart that thinks we can't see it.

The person page: the underrated half

Most team pages are indexes that link nowhere, or worse, link to LinkedIn — exporting your credibility to a platform with ads on it. Every person deserves a page at a stable URL, and that page is a small, repeatable piece of editorial design:

Portrait, name, role, one-line belief.
The bio in full (the index shows the teaser; the page can stretch to 120 words).
Their authored work — journal articles, case studies they worked on, talks, open source.
A photo-free contact path if appropriate (via the studio, not personal inboxes).

The authored-work list is the highest-leverage element. When an engineer's article on design tokens surfaces in search, it should land next to the engineer — and it does, on their page, where the reader can see the same person appears in the case study for a design-system client. Expertise becomes traceable through the site rather than asserted in a headline. It also does quiet SEO work: author pages consolidate a person's topical authority, and byline design points readers there from every article.

A practical note: person pages must survive departures with grace. Our policy is that pages persist while the work is live, with role changed to "formerly" — because the case studies they touched remain true. Vanishing people retroactively from project pages is a small dishonesty that compounds.

Signals buyers actually read

Session recordings and client debriefs keep showing the same behaviours on team pages:

Scanning for someone like them. A founder looks for other founders' energy; a head of product looks for the product designer. Discipline labels matter more than ranks.
Hunting for the seniority mix. Buyers have been burned by the classic bait-and-switch: partners in the pitch, juniors on the project. If your model is genuinely senior squads, the team page is where you prove it — show actual headcount and tenure distribution rather than claiming "senior-led" in a badge.
Reading the jokes. Humour in bios is a high-risk, high-yield trust signal. A genuinely funny line ("Has never once said 'it works on my machine' without irony") conveys more cultural information than a values section. Forced fun conveys the opposite. The test is whether the person wrote it or approved it happily — bios written about people always sound like obituaries; bios co-written with them sound like introductions.

Maintain it like the product it is

Team pages rot faster than any other page on a studio site. Someone joins, someone leaves, someone's role changes, and the page silently becomes a museum. Treat it as production software:

Owned. One person (we use our producer) owns the roster, with a quarterly review in the calendar.
Generated where possible. Build the person index from a data file, not a CMS page someone hand-edits — joins and leavers become data changes, not layout surgery.
Linked into hiring. The team page and the careers page should reference each other honestly: candidates look at the team to imagine joining, and the team's craft signals set the bar for who applies. A careers page that filters people in starts with a team page worth joining.

The concept-site honesty problem

A special case worth naming: if your site is a concept, a demo, or a portfolio exercise, the team page is where honesty matters most, because fake photoreal people are the easiest lie on the web. Illustrated portraits, names that clearly belong to a fiction (check the colophon), and a visible note that the studio is a concept — these make the page more impressive, not less. Craft includes the craft of being straight with the reader. Our studio page carries that note in the open, and the team page inherits the honesty by styling.

Key takeaways

The team page answers the buyer's real question — whose hands will be on my product — so design it as commercial evidence, not a yearbook.
Pick a portrait policy (real programme, illustration, or none) and hold it. Photoreal synthetic faces are a lie with good cheekbones.
Bios sell judgment: a belief, a practice, a link to shipped work — forty words, one true specific thing.
Structure the roster the way a squad assembles, not the way the org chart climbs.
Every person gets a page at a stable URL, with authored work attached — expertise should be traceable, not asserted.
Own the roster operationally; a team page that lies about who works there is worse than no team page.

FAQ

How many people should be on the team page?

Everyone who'd plausibly touch a client project, shown at equal weight. Hiding most of the team to look boutique backfires in diligence calls; showing all forty-five with lazy uniformity overwhelms. Equal-weight cards with a filter by discipline solve both.

Should we show photos of the office and offsites?

Yes, but not as substitutes for the people index — as texture further down, clearly captioned with where and when. A team page made entirely of party photos says "we socialise" and answers nothing about craft.

What do we do about contractors and long-term collaborators?

Label them honestly ("working with us since 2021, usually on motion"). Buyers appreciate knowing the bench; hiding that you use specialists reads, on discovery, as concealment rather than tidiness.

Do person pages help recruiting or just sales?

Both, and the same mechanism: traceable expertise. A candidate reading three good articles by your engineers on their person pages gets a stronger signal about the calibre of colleagues than any employer-brand copy could deliver.

How often should portraits be refreshed?

For a photography programme, annually with a reshoot budget for joiners. For illustration, on joining plus whenever the system itself is redesigned — the consistency is the point, so refresh the system, not individuals.