What should a website team directory include when roles change?

Build the directory around customer needs

Visitors rarely need to know every person employed by a business. They need to know who handles a question, what kind of help is available and what happens after they get in touch. Begin with those needs. A useful directory may be organised by responsibility, service or customer situation rather than by department names that only make sense internally.

For each role, write a plain-language description. “Helps existing customers change a booking” is more useful than “customer success executive”. “Prepares technical estimates for installation projects” tells a visitor what to expect. Include the main route for contact, such as a form, shared email or booking link, instead of publishing a private mobile number for every employee.

Think about the page as a routing tool. If a visitor chooses the wrong person, can they still reach the team through a shared route? Good structure reduces repeated explanations and prevents customers from searching social profiles for a current contact.

Choose roles before names

Names and photographs can build trust, but the responsibility should remain useful when a person changes role or leaves. Put the role, area of help and contact route first. Add names where they are genuinely helpful, and make clear whether the person is a direct contact or part of a shared team.

Avoid titles that require internal knowledge. Explain abbreviations and replace impressive labels with the language customers use. If two people share one responsibility, describe the team route rather than making the page depend on a single individual.

Consider accessibility and scanning. Use headings, short descriptions, consistent contact actions and meaningful image text. A directory made of photographs with no explanation does not help someone who cannot see the images or needs a quick answer on a phone.

Publish only necessary personal information

A team page can accidentally reveal private information. Do not publish home addresses, personal numbers or details about schedules unless there is a clear reason and appropriate consent. A work email may be useful, but a shared inbox is often more durable and easier to protect.

Explain the purpose of any personal detail. A photograph may help a visitor recognise a person at an appointment. A short biography may establish relevant expertise. Personal hobbies or family details are optional and should never be required for credibility. Give employees a clear way to request corrections or removal when circumstances change.

Review connected data. A staff profile may appear on the website, search results, newsletters and social accounts. Removing someone from one page is not enough if an old profile remains in another system or is still linked from a service page.

Describe handoffs and shared responsibilities

Many customer questions cross roles. A sales adviser may collect the initial request, a specialist may prepare the work and an account contact may follow up. Show this journey without making the visitor repeat information at every stage. Explain who receives the first message and when another colleague becomes involved.

Use shared routes for changes, support and urgent matters. If a named person is away, the customer should not have to guess whether the message is lost. A short note such as “For existing projects, use the project support form; the delivery team monitors it” creates confidence and sets expectations.

Do not promise personal availability that the business cannot maintain. The directory should be accurate about response times, channels and responsibilities. Clarity is more trustworthy than a page full of direct contacts that no longer work.

Make ownership and review visible internally

Assign someone to maintain the public directory. Their job is not necessarily to edit every biography, but to trigger a review when people join, leave, change roles or take ownership of a new service. Keep the internal source of truth separate from the public page so changes can be checked before publishing.

Add a review date and a checklist. Confirm names, role descriptions, links, images, contact routes and accessibility text. Ask whether each published detail still has a purpose. A quarterly review may be enough for a stable team; fast-changing teams need a simpler trigger-based process.

Record why a route exists. This helps a new colleague understand the page and prevents useful context from disappearing when the original editor leaves.

Keep the page useful as the team evolves

When roles change, update the responsibility before polishing the presentation. A correct shared contact route matters more than a new portrait. If the business temporarily has a vacancy, explain how visitors should reach the team rather than leaving an outdated name visible.

Watch the questions customers still ask after the page is published. Repeated misrouting is evidence that the directory needs clearer labels or a better first question. Analytics can show page use, but staff feedback and support conversations reveal whether the page actually helps.

A good team directory is modest, accurate and easy to maintain. It gives visitors enough context to choose the right route, protects unnecessary personal information and continues to work when the organisation changes.

Sources

• Writing for Web Accessibility · W3C
• Principles of the GDPR · European Commission

Frequently asked

Should every team member have a profile?

No. Publish roles and contact routes that help customers. Add individual profiles when a person’s expertise or appointment role genuinely improves clarity.

Is a shared inbox better than personal email?

Often it is more durable and easier to manage, especially when responsibilities change. Use a personal route when continuity and consent are clear.

How often should a team directory be reviewed?

Use a regular review plus triggers for starters, departures, role changes and new services. Fast-changing teams should not wait for an annual update.