A website discovery workshop should produce a useful basis for decisions. It is easy to leave a lively meeting with a wall of notes and several design preferences, yet no agreed problem, clear scope or next action. The value of the workshop comes from turning discussion into a brief that the business and project team can review.
The workshop does not need to settle every detail. It should establish what is known, what is assumed and what needs further investigation. Useful outputs include customer tasks, project constraints, content responsibilities and testable requirements. This guide explains what to expect and how to make the resulting information usable after the meeting.
An agreed problem and intended outcome
Begin by describing why the website work is needed. Avoid a statement such as “the site looks dated” standing alone. Ask what that affects. Customers may struggle to find the right service, staff may receive incomplete enquiries or important information may be difficult to maintain.
Write the problem in terms the team can recognise. Include examples and the evidence currently available. A handful of staff observations can identify a question worth investigating, but they should not be presented as a complete account of every visitor's behaviour. Keep the strength and limits of the evidence visible.
Agree the intended outcome alongside the problem. For example, prospective customers should be able to identify the relevant service and submit enough information for a prepared response. This outcome can guide structure, content and forms more effectively than a broad instruction to make the website modern.
A clear account of users and their tasks
Identify the people the website needs to help and the tasks they want to complete. Consider new visitors, returning customers and anyone using the site to find practical information. Include the questions they need answered before choosing the next step.
Distinguish evidence from assumptions about those people. A team member's belief that customers prefer one layout is a hypothesis, not a confirmed requirement. Shared research planning can turn assumptions and uncertainty into prioritised questions. Use the workshop to identify what should be checked next and how the team will obtain useful evidence. Our user research planning guide provides the related checks.
Produce a short task list with the relevant context. Someone finding a location may be travelling on a phone. Someone comparing services may need detailed explanations before contacting the business. Those contexts help the project team decide what information belongs on each part of the site.
A draft journey with important handovers
Map one or two priority journeys from arrival to a useful outcome. Include how people reach the site, what they need to understand and what happens after they act. For an enquiry journey, continue beyond submission to the staff response. The website's form and the business's working process should be considered together.
Record the current difficulties and proposed changes at each step. Be specific. “The service choice is unclear” leads to different work from “the enquiry reaches a mailbox nobody monitors”. Both can affect the journey, but they require different owners and evidence of improvement.
Keep the map provisional where it depends on assumptions. Use it to plan investigation and to explain the intended service, then update it when the team learns more. A workshop sketch should not become an unquestionable design simply because it was drawn early in the project.
A scope statement with boundaries
List the work currently proposed, together with what is outside the agreed project. Include content, design, development, integrations and any migration work where relevant. State the assumptions behind the scope so suppliers can understand what their proposal depends on.
Describe uncertain items separately. The business might want an account area but not yet know what customers should be able to manage. Record that as a requirement to investigate, with an owner and next step. Avoid presenting a broad wish as a fully defined feature ready for implementation.
Explain how scope changes will be assessed. A new feature may affect content, operating responsibilities, testing and delivery time. The output should establish who can approve a change and what information they need. This helps the team make later decisions without relying on informal agreement during a busy meeting.
A content inventory and responsibility plan
Identify the content the proposed site needs. Include service descriptions, contact details, team information, photographs, case studies and practical instructions. Note what exists, what needs checking and what must be created. An existing folder of material should be reviewed for suitability rather than assumed to be ready.
Assign factual owners and editorial responsibilities. A service manager may confirm what is offered, while a writer prepares the page and a project lead coordinates approval. Record the approved source for important facts and the route for resolving missing information.
Include photography and supporting assets in the plan. If a page needs a particular view of the premises or a real project example, give that requirement an owner. Ask the designer how the material will be used so content preparation supports the actual page structure. This is more useful than leaving images as a final decoration task.
Operational and technical constraints
List the systems and processes the website must connect with. These could include booking tools, customer records, staff inboxes or payment services, depending on the project. Identify the relevant owners and ask which connections are already understood and which need technical investigation.
Record hosting, domain and access coordination where they matter to delivery. Do not place credentials in workshop notes. The output should identify who can arrange authorised access and what the development team needs to verify. Include relevant supplier dependencies rather than assuming every connected system can be changed immediately.
For an existing website, identify important pages and addresses that the project must account for. Ask the team to investigate current content, links and migration requirements before finalising the implementation plan. The workshop should flag the work and its owner, rather than promising that a redesign will produce a particular search result.
Requirements that can be tested
Convert broad preferences into observable behaviour where possible. “Easy to use” is a useful ambition, but it does not explain what the team needs to demonstrate. A more specific requirement might say that a visitor can choose the relevant service, submit an enquiry and receive a clear explanation of the next step.
Write example scenarios with expected results. Include the normal journey and important exceptions, such as missing information, an unavailable booking slot or a customer who needs to contact the team another way. The scenarios help designers, developers and staff share an understanding of what completion means.
Do not attempt to specify every screen during discovery. Identify which requirements are sufficiently understood and which need a prototype or further discussion. The next stage should resolve the most important uncertainties before the team makes expensive implementation choices.
A decision record and research questions
Summarise decisions in a concise record. Include the decision, supporting evidence, person responsible and any conditions. Mark provisional decisions clearly. This stops a casual suggestion being remembered later as a firm commitment that nobody actually approved.
Create a separate list of unanswered questions. Prioritise them according to their effect on scope, customer tasks and delivery. Assign an owner, a method for obtaining evidence and a date for reviewing the answer. A useful research question asks something specific enough to influence the project.
For example, “what information does the team need to prepare the first response?” can lead to a review of recent enquiries and staff work. “Do people like our website?” is much less precise. The workshop should leave the team with investigations that can reduce meaningful uncertainty.
Frequently asked questions
What should we know about an agreed problem and intended outcome?
Begin by describing why the website work is needed. Avoid a statement such as "the site looks dated" standing alone. Ask what that affects. Customers may struggle to find the right service, staff may receive incomplete enquiries or important information may be difficult to maintain. Write the problem in terms the team can recognise. Include examples and the evidence currently available. A handful of staff observations can identify a question worth investigating, but they should not be presented as a complete account of every visitor's behaviour. Keep the strength and limits of the evidence visible. Agree the intended outcome alongside the problem. For example, prospective customers should be able to identify the relevant service and submit enough information for a prepared response.
What should we know about a draft journey with important handovers?
Map one or two priority journeys from arrival to a useful outcome. Include how people reach the site, what they need to understand and what happens after they act. For an enquiry journey, continue beyond submission to the staff response. The website's form and the business's working process should be considered together. Record the current difficulties and proposed changes at each step. Be specific. "The service choice is unclear" leads to different work from "the enquiry reaches a mailbox nobody monitors". Both can affect the journey, but they require different owners and evidence of improvement. Keep the map provisional where it depends on assumptions. Use it to plan investigation and to explain the intended service, then update it when the team learns more.
What should we know about a content inventory and responsibility plan?
Identify the content the proposed site needs. Include service descriptions, contact details, team information, photographs, case studies and practical instructions. Note what exists, what needs checking and what must be created. An existing folder of material should be reviewed for suitability rather than assumed to be ready. Assign factual owners and editorial responsibilities. A service manager may confirm what is offered, while a writer prepares the page and a project lead coordinates approval. Record the approved source for important facts and the route for resolving missing information. Include photography and supporting assets in the plan. If a page needs a particular view of the premises or a real project example, give that requirement an owner.
What should we know about operational and technical constraints?
List the systems and processes the website must connect with. These could include booking tools, customer records, staff inboxes or payment services, depending on the project. Identify the relevant owners and ask which connections are already understood and which need technical investigation. Record hosting, domain and access coordination where they matter to delivery. Do not place credentials in workshop notes. The output should identify who can arrange authorised access and what the development team needs to verify. Include relevant supplier dependencies rather than assuming every connected system can be changed immediately. For an existing website, identify important pages and addresses that the project must account for. Ask the team to investigate current content, links and migration requirements before finalising the implementation plan.
What should we know about a decision record and research questions?
Summarise decisions in a concise record. Include the decision, supporting evidence, person responsible and any conditions. Mark provisional decisions clearly. This stops a casual suggestion being remembered later as a firm commitment that nobody actually approved. Create a separate list of unanswered questions. Prioritise them according to their effect on scope, customer tasks and delivery. Assign an owner, a method for obtaining evidence and a date for reviewing the answer. A useful research question asks something specific enough to influence the project. For example, "what information does the team need to prepare the first response?" can lead to a review of recent enquiries and staff work. "Do people like our website?" is much less precise.
A reviewed brief and clear next steps
After the workshop, bring the outputs into one coherent brief. Check that the problem, tasks, scope and proposed next work agree with one another. Circulate it to the relevant owners for factual correction and confirmation of responsibilities. Keep the open questions visible instead of smoothing them into apparent certainty.
Giraffe Digital's website design services provide a starting point for connecting structure, content and customer journeys. A strong discovery brief makes that work easier by explaining what the business needs, what evidence supports it and what still requires investigation.
The useful result is a reviewable project foundation: an agreed purpose, a realistic scope, accountable content owners and a plan for resolving uncertainty. With those outputs, the workshop becomes a practical step towards a better website rather than a collection of ideas waiting for someone else to interpret them.


