Shane Ian Murphy: A UK Business FAQ Should Answer Before It Explains

A frequently asked question can be easy to find and surprisingly difficult to answer. The heading matches what the reader wants to know, but the paragraph beneath it begins with the organisation's history, values or internal process. By the time the answer arrives, the person may have lost confidence that it is there. I prefer an FAQ that answers the question first and then supplies the explanation needed to use that answer.

I am Shane Ian Murphy, also known as Shane Murphy, formerly of Cambridge and formerly of Limitless Mobile, where I was co-founder and Chief Business Development Officer. This UK business commentary uses a hypothetical collection service. It does not describe an existing service's terms or announce a policy on behalf of a company associated with me.

Imagine a small workshop offering an agreed collection arrangement for prepared display materials. A customer asks whether another colleague can collect the items. The FAQ entry begins by explaining how carefully the team prepares each order. That may be relevant elsewhere, but it does not tell the customer what to do about the proposed collector.

I would first establish the actual answer with the people responsible for the process. If another collector is permitted under specified conditions, those conditions belong beside the answer. The writer should not infer a convenient policy from what seems reasonable. Clear language cannot compensate for an operational question nobody has resolved.

The opening sentence should then address the question in a form the reader can use. A qualified answer may be necessary, but its qualification should be concrete. “It depends” is a beginning only if the next words explain what it depends on. The reader needs a way to identify which case applies to them.

The next part should describe the required action. In our fictional example, the service might have an agreed method for notifying the workshop of a changed collector. The FAQ would need to explain that method accurately, including which information the team requires. It should not ask the customer to follow a route that staff do not recognise or cannot support.

Background can follow when it helps the reader understand the instruction. A short explanation of why a particular confirmation is needed may make the process easier to follow. However, the explanation should remain connected to the customer's task. A long account of internal arrangements can obscure the practical answer without making it more reliable.

I would keep exceptions close to the relevant statement. If a different arrangement applies to a particular type of collection, the reader should discover that before acting on the general answer. Sending every exception to a separate page may require the customer to solve a navigation problem before they can understand the original response.

The question itself should resemble something a customer would ask. An internal category such as delegated fulfilment might be familiar to the team and unfamiliar to the reader. A plain question about somebody else collecting an item gives the answer a more recognisable entry point. The organisation can retain its internal terminology without making the customer learn it.

An FAQ also needs boundaries. Some questions require details that cannot be resolved by a general answer. In those cases, the page should explain what the reader can establish themselves and where to seek a case-specific response. A contact route should identify the information that will help the receiving team continue the discussion.

I would review repeated support questions alongside the FAQ. If people continue asking the same thing, the answer may be hard to find, difficult to interpret or inconsistent with the actual process. The correct response is not automatically to add more text. The team should identify the particular gap before deciding how to revise the page.

Finally, somebody should own the answer and review it when the process changes. An accurate FAQ can become misleading if it survives an operational change without attention. The responsibility for maintaining it should be as clear as the responsibility for writing the first version.

For a UK business, a useful FAQ is part of the service conversation. It helps the reader decide what applies, understand the necessary action and recognise when further help is required. I would judge it by those outcomes, rather than by the number of questions the page manages to contain.

Author background: https://shanemurphy.co.uk/career

This author-origin business commentary was prepared with AI assistance.