The about-us page is where visitors can assess whom they will work with. A complete company history is not always the best opening for that. Start with what matters to the relationship: which problems the organisation handles, which people are involved and how they work. Background becomes meaningful when it helps explain those choices.
Explain who is responsible
Show which expertise the organisation has and whom a customer will get to know during a project. Job titles alone offer little guidance. A short explanation of someone’s role may say more: responsible for substantive analysis, design, technical implementation or support during adoption. Stick to roles that are actually fulfilled.
Not every team member needs to be presented in the same way. Choose a form that fits the organisation and the people involved. Do keep names, photos and roles current. A page showing people who have not been involved for a long time raises questions about the attention given to the rest of the website.
Connect history to current choices
An origin story can be valuable when it explains why the organisation works in a particular way. The founding date itself is usually less interesting than the experience from which the offering emerged. Choose a few relevant moments and explain their significance. Avoid a chronology where every office move or internal milestone receives equal weight.
In a fictional example, an agency was started by employees who often had to retype information between different systems. That may explain why their current work starts by investigating data flows. The story then supports the approach. It does not prove that every new project automatically saves time or needs the same solution.
Make values visible in working agreements
A list of values becomes stronger when visitors understand how those values lead to behaviour. ‘Clarity’ may mean recording decisions and open questions after a work session. ‘Collaboration’ may mean users working with a prototype along the way. Publish such examples only when they reflect actual practice.
Refer to services where relevant. A description of how a team develops websites and online stores can be expanded on the services page. The about-us page does not need to repeat that content in full. It mainly adds the human and organisational context that helps visitors assess the working relationship.
Check whether the page helps the visitor
After reading, ask an outsider who the contact might be, what knowledge is available and what characterises the approach. If the answer mainly consists of general adjectives, the content can be more specific. Also check whether the page unintentionally excludes important groups through too many internal abbreviations or assumed prior knowledge.
Connect with the intended next step. A potential client needs to be able to get in touch easily; a job applicant needs a recognisable route if there is a careers section. Check these routes whenever the content is updated. The about-us page does not need to be impressively long. It needs enough specific information to turn an anonymous organisation into an understandable potential partner, using facts the team can explain themselves.