A website team profile brief helps a business present the people behind its services accurately. For a Kenyan firm commissioning a new site, staff names and portraits should do more than fill an About page. Visitors may want to understand who handles a service, what experience is relevant and how to contact the business without guessing which individual is responsible.
Prepare that information with your website development team in Kenya. Start with verified people and current responsibilities, not invented team members or impressive titles copied from another organisation. A short accurate profile is more useful than a long biography that nobody has checked.
The examples in this guide are illustrative content-planning exercises. They are not claims about Mocky's staff, customer results or professional credentials. This brief concerns employee and contributor profiles, rather than customer testimonials or a complete corporate history.
Decide why a visitor needs each profile
List the decision a profile should support. A prospective client might need to identify the person responsible for a technical consultation. A partner might want to understand a project leader's role. A reader of a specialist article might need context about its named contributor. Those purposes call for different levels of detail.
Avoid publishing everyone simply to make the organisation appear larger. Decide which roles need public visibility and discuss that choice with the people involved. Some staff may contribute to the service without needing a public portrait, direct email address or personal biography. The content plan should reflect the actual service model.
Choose between a compact team section and individual pages based on the available material. If a person has only a name and role, a separate page may add little. Someone with substantial approved work, relevant publications or a specific customer-facing responsibility may have enough useful information for a fuller page.
Create a profile register with factual ownership
Use one row per person. Record the approved display name, current role, public summary, relevant experience, portrait source, intended pages and approval owner. Keep private contact details and internal personnel records outside this public-content worksheet. The developer needs the approved material, not an employee's complete employment file.
Ask the subject or responsible manager to check the facts. Confirm spellings, qualifications, current responsibilities and any organisation names mentioned. Where a credential is relevant, use its correct title and avoid implying a current professional status that has not been verified. Do not turn an unfinished course into a completed qualification.
Keep the distinction between individual experience and company experience clear. A person may have worked on a project before joining the business. If that work is mentioned with permission, describe the context truthfully rather than presenting it as an assignment delivered by the current company.
Write biographies around relevant work
Start with what the person does for the intended reader. Explain their responsibility in ordinary language before listing background details. An illustrative service lead might be described as the person who coordinates discovery, checks the agreed scope and routes technical questions. Only use that description if it matches the actual process.
Select experience that supports the page's purpose. A long chronology can hide the information a customer needs. Where a project is named, specify the person's contribution accurately and confirm that it may be public. Do not imply sole ownership of collaborative work or invent performance figures to make a biography sound convincing.
Maintain a consistent voice across profiles without making every person sound identical. Agree whether the website uses first or third person, how job titles are styled and what length suits the layout. Allow factual differences to remain visible instead of forcing every biography into the same exaggerated claim.
Prepare portraits without changing identity
Collect approved images with enough space for the proposed crop. Check that the person remains recognisable on mobile and that the image does not misrepresent their role or working environment. A consistent crop can bring visual order without requiring every portrait to have the same background.
Keep image editing and factual approval separate. Adjusting exposure or cropping should not silently alter a person's identity or introduce a workplace scene that never existed. If an illustration or generated avatar is used instead of a photograph, agree how that choice will be presented rather than implying it is a documentary portrait.
Use an image register to keep track of the approved source, crop and replacement owner. Our website image content brief covers that broader preparation task. The profile register should link to the chosen image so the developer does not select an outdated file from an email chain.
Connect profiles to services and articles carefully
A profile can link to the services the person actually supports and to approved work that demonstrates their contribution. This helps the reader continue a relevant journey. Do not attach an unrelated service list merely to place more links on the page or imply competence in every area the business offers.
For authored content, decide what the byline means. Writing, technical review and business approval are different responsibilities. If a person reviewed an article rather than wrote it, describe that accurately. Maintain the connection between the article and the current profile so readers can understand the person's involvement.
Google's profile-page structured data guidance includes employee pages on company websites among its valid examples and requires the page to focus primarily on one affiliated person or organisation. Ask the developer whether the proposed page genuinely fits the relevant guidance. Markup is not a reason to invent a biography, and eligibility does not promise a particular search appearance or ranking.
Define the contact route and privacy boundary
Choose how a visitor should make contact. A shared service enquiry route may be more dependable than publishing an individual mailbox that nobody covers during leave. If direct contact is appropriate, confirm who maintains the address and what happens when responsibilities change.
Do not expose private numbers or personal accounts because they happen to appear on an old document. Provide only the public details the business and person have approved. If a social profile is linked, verify that it belongs to the intended individual and is suitable for the purpose of the page.
Check that the website does not create misleading expectations about availability. A public profile does not necessarily mean the person answers enquiries at all hours or personally handles every assignment. Explain the business process on the relevant service or contact page rather than making the biography carry an unsupported promise.
Test the profile journey before launch
Review the actual mobile layout with realistic names, titles and biography lengths. Check portraits, heading order, link labels and the route back to the relevant service. A design that works with a short placeholder name may wrap awkwardly when the final approved content is inserted.
Give a reviewer a practical task: identify who coordinates the service, understand their responsibility and find the correct enquiry route. Observe whether the page answers those questions without requiring help. Record confusing wording as well as broken links, because factual accuracy alone does not guarantee a usable page.
Check repeated profile cards against the main record. A homepage summary, article byline and full biography should not describe three different roles after an edit. Ask whether those locations share one content record or require separate updates, and include the answer in the editing handover.
Plan role changes and departures
Assign a content owner who is told when public responsibilities change. Decide how the website handles an updated title, a new portrait, withdrawn approval or a person leaving the organisation. Those are maintenance events, not reasons to leave an inaccurate profile online indefinitely.
Consider historical article attribution separately from a current team listing. Removing someone from the active team should not automatically replace their name on work they genuinely contributed. Agree a truthful archive approach with the responsible editor and ask the developer how the content model supports it.
For a proposal, send the profile register, approved portraits, intended page locations and maintenance responsibilities. Request a website quotation that includes content setup, mobile review and editing instructions. This gives the team a concrete deliverable rather than an open-ended request to make the business look more established.
Frequently asked questions
Do we need individual pages for every employee?
No. Publish profiles that serve a clear reader need and have enough accurate material. A compact team section may be sufficient for some organisations or roles.
Can we use a stock portrait while waiting for a photograph?
Avoid presenting another person's photograph as an employee. Use a clearly appropriate alternative layout until the intended person approves a real portrait or another honest visual treatment.
Should biographies include exact years of experience?
Only when verified and maintained. Relevant responsibilities and approved examples can explain experience without relying on a number that becomes inaccurate or combines unrelated work misleadingly.
Will team pages improve rankings?
There is no guaranteed result. Their immediate purpose is to explain real people and responsibilities accurately. Measure relevant journeys and enquiries separately from merely counting newly published pages.
