Website strategy
Website Discovery Workshop Checklist Before Design Begins
Run a practical website discovery workshop covering goals, audiences, offers, content, proof, functionality, SEO, and launch ownership.
- Direct answer
- Full process
- Real example
- Clear checks
The short answer
By the end, the team should have a shared brief that can guide copy, structure, design, development, and launch checks. Start by documenting the present situation, then make one decision at a time. A tool should support the workflow; it should not be used to avoid deciding how the workflow works.
The fastest way to waste a website budget is to begin with colours and homepage references. Those things matter, but they cannot answer who the site is for, what visitors need to believe, or what the business wants them to do.
A discovery workshop should feel less like a creative brainstorm and more like a focused business conversation. We are trying to expose decisions early, while changing them is still cheap.
By the end, the team should have a shared brief that can guide copy, structure, design, development, and launch checks. If a step does not change what somebody knows, decides, or does, it probably does not belong in the process.
The complete process
Work through these stages in order. It is tempting to jump to the visible part, but most expensive revisions begin in an earlier decision that nobody finished.
Name the business result
Choose the main outcome: qualified enquiries, bookings, applications, product sales, trial registrations, or trust for a longer sales process. Secondary actions are fine, but the homepage needs a priority.
Ready to move on when: The team can finish the sentence “This website succeeds when…” with a measurable result.Describe real visitor groups
List the people arriving, what triggered their search, what they already know, what worries them, and who makes the final decision. Avoid empty personas made from age and hobbies when buying questions are more useful.
Ready to move on when: Each audience has a need, objection, proof requirement, and next action.Audit the offer and evidence
Collect service details, pricing approach, process, team information, results, testimonials, certifications, project images, policies, and common sales questions. Mark what exists and what must be created.
Ready to move on when: No section depends on proof that nobody owns or can provide.Plan the page map around decisions
Create a page for each distinct intent that deserves a complete answer. Group closely related information and avoid dozens of thin pages created only for keyword variations.
Ready to move on when: Every planned page has one audience question and one desired action.Define functions and integrations
Record forms, payments, bookings, portals, CRM, WhatsApp, analytics, email, multilingual needs, search, and content editing. Include privacy and consent requirements.
Ready to move on when: Each integration has an owner, data flow, and test case.Agree on launch ownership
Assign who approves copy, supplies assets, checks legal information, configures domains, receives form submissions, and maintains the site. A beautiful build can still fail at handover.
Ready to move on when: Every launch task has one named owner and deadline.A realistic example
For a clinic, the workshop might reveal that visitors are not simply “looking for healthcare”. Some need to understand a service, some want the earliest appointment, and some are checking whether they can trust a practitioner. That discovery changes the page map, proof, form fields, and CTA language before anyone chooses a card style.
Where people usually make the wrong turn
Inviting too many people without deciding who has final approval
Inviting too many people without deciding who has final approval. Stop, identify the decision that is missing, and correct the source of the problem before adding more tools or content.
Talking about competitor appearance while ignoring their page structure and customer journey
Talking about competitor appearance while ignoring their page structure and customer journey. Stop, identify the decision that is missing, and correct the source of the problem before adding more tools or content.
Leaving copy, photography, and policy content until development is nearly complete
Leaving copy, photography, and policy content until development is nearly complete. Stop, identify the decision that is missing, and correct the source of the problem before adding more tools or content.
How to know the work is improving
Do not collect numbers simply because a dashboard can show them. Pick a small set that reflects the outcome and review it on a schedule long enough to make a sensible decision.
- Brief approved without unresolved ownership gaps
- Reduction in structural changes after design begins
- Clear analytics events linked to the main website goal
We can review the current setup, clarify the workflow, design the customer-facing experience, build the required system, and support the work after launch.
Before you call it finished
- The main decision and responsible owner are written down.
- The mobile journey has been completed from beginning to end.
- Claims, prices, dates, links, and permissions have been checked by the right person.
- Tracking measures the intended outcome rather than activity alone.
- Someone owns maintenance, review, and follow-up after launch.
Questions people ask before starting
Who should attend a website discovery workshop?
Include the decision-maker, someone close to customers or sales, the project lead, and the people responsible for strategy, content, design, and technical delivery.
How long should it take?
A focused small-business workshop may take 90 minutes to half a day. Complex systems often need several sessions by topic.
Should we prepare content first?
Bring existing material and evidence. The workshop decides the content plan; finished copy usually follows the agreed structure.
References and further reading
Policies and platform features change. Use these sources to verify requirements that affect your implementation, then apply them to the real business context.