A team page earns its place where the customer is choosing a person or letting somebody into their home. It is a maintenance liability where the business is transactional, because a page listing people who left is worse than no page at all.

When it genuinely helps

Where somebody enters a home

The strongest case. A customer letting strangers into their property wants to know who is coming, and faces do more than any assurance about vetting.

Where the customer picks an individual

Clinics, salons, tutoring, agencies. The person is the product, and a page that obscures who they are is making the decision harder.

Where trust is the main obstacle

Professional services, anything financial, anything involving children or vulnerable people. Named people with qualifications answer the question the business cannot answer about itself.

Where you are competing against a faceless alternative

A local business against a national operator or a call centre. Showing who actually does the work is the one thing the competitor cannot match.

When it does not

What each entry should carry

Less than most team pages contain and more of the right things.

A real photograph, consistent in style across the team. Mixed selfies and formal portraits read as unfinished.

A name, first name at minimum. Where staff prefer not to publish a surname, that is entirely workable.

What they actually do, in plain terms rather than a job title nobody outside the business understands.

How long they have been doing it, which is the detail customers weigh most and which most pages omit.

Relevant qualifications, named plainly rather than as acronyms.

One human detail, optional and effective. Something that makes them a person rather than a role.

What to leave out

Extended biographies, which nobody reads past the second line. Career histories at other companies. Personal information beyond what somebody volunteered. And anything that would need updating when a circumstance changes.

Also worth avoiding: a hierarchy displayed as a hierarchy. Customers do not care about reporting lines, and a page organised by seniority reads as internal rather than for them.

Permission, which is not optional

Employment does not imply consent to appear in marketing.

Ask, get it in writing, and be prepared for somebody to decline. A team page missing one person is fine; a page including somebody who did not want to be there is a problem.

Agree in advance what happens when they leave, since removing a photograph promptly is both courteous and expected. Some people have reasons for not wanting to appear online that they are not obliged to explain.

The maintenance problem

The reason to think before creating one.

A team page is a page that goes wrong on its own. Somebody leaves, somebody joins, a role changes, and the page silently becomes inaccurate.

A page listing somebody who left six months ago is noticed by existing customers, and it is one of the clearer signals that nobody is attending to the site.

The practical mitigation is attaching the update to something that already happens: a departure checklist, alongside removing their access.

The lighter alternatives

For businesses where a full page is more than the situation warrants.

A photograph of the crew on the about page, without individual entries. Shows the people without listing them, and survives a departure.

The owner only, which for a small business is frequently the person customers want to see anyway.

Named people on relevant service pages, where different people do different work.

A count and a statement, such as a team of six, all employed and in uniform, which answers the practical question without any photographs.

That last option does most of the work for a trades business where the customer's real question is whether the person arriving is employed, identifiable, and accountable.

Where it should sit

Not usually in the main navigation.

It is a supporting page rather than a destination, and a menu slot spent on it is a slot not spent on services or contact. Linked from the about page and from service pages where relevant is sufficient.

The exception is a business where choosing a person is the transaction, in which case it is a primary page and belongs in the navigation.

The decision either way follows from what the customer is actually choosing, which is the same question that determines whether the site needs updating when the team changes at all, as covered in hiring your first employee and what changes online.

Frequently asked questions

Does every business need a team page?

No. It helps where somebody enters a home, where the customer picks an individual, or where trust is the main obstacle. It is a liability where turnover is high or the business is transactional.

What should each entry contain?

A real photograph consistent in style, a name, what they actually do in plain terms, how long they have done it, relevant qualifications, and optionally one human detail.

What should be left out?

Extended biographies, career histories elsewhere, personal information beyond what was volunteered, and any hierarchy displayed as a hierarchy.

Do I need permission from staff?

Yes. Employment does not imply consent to appear in marketing. Ask, get it in writing, and agree in advance what happens when they leave.

What is the main risk?

Maintenance. A page listing somebody who left six months ago is noticed by existing customers and is a clear signal nobody is attending to the site.

What are the lighter alternatives?

A crew photograph without individual entries, the owner only, named people on relevant service pages, or simply stating the team size and that everyone is employed and in uniform.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Team page listing two people who left?

We will tell you whether the page is earning its place at all, and set up the lighter version if it is not.

Start a Conversation