Running a remote website discovery workshop that produces decisions

A remote discovery workshop should produce more than a recording of people talking about a website. Its purpose is to identify the audience, clarify the business problem, and resolve enough uncertainty to guide the next phase. The widespread move to remote collaboration in 2020 made this especially important. Without a shared room, an unstructured meeting could easily become a long discussion with no clear owner for the decisions.

Begin by defining the questions the session must answer. For a website project, these might include the primary audience, the most important visitor action, the services that need explanation, and the constraints that cannot change. A workshop with four meaningful decisions is often more useful than one that attempts to cover every detail of design, technology, and content at once.

Prepare people before the meeting

Send a short preparation request. Ask participants to bring examples of customer questions, common sales objections, and current website problems. Invite evidence rather than polished presentations. A support email showing recurring confusion can be more valuable than a slide claiming that the company needs a modern digital presence.

Explain who is attending and who can approve decisions. Include people who work directly with customers, not only the most senior stakeholders. Limit the group enough that everyone can contribute. If someone is there only to receive the outcome, a written summary may be a better use of their time than attendance at the full workshop.

Separate individual thinking from discussion

Give people a few minutes to write their answers privately before opening a discussion. This reduces the chance that the first confident speaker determines the entire conversation. Collect the responses, group similar concerns, and then discuss disagreements. The exercise should make differences visible without turning the session into a competition for airtime.

For example, ask each participant to finish the sentence: a visitor should leave this page knowing what. Sales may focus on service scope, operations may focus on availability, and leadership may focus on company positioning. Those answers are not necessarily incompatible. The facilitator's job is to organize them into a useful hierarchy and identify the tradeoffs that require a decision.

Work with concrete customer tasks

Choose a realistic task, such as finding evidence that the company can handle a particular project. Walk through the information the visitor would need and where it should appear. Avoid spending the whole session rating favorite websites. Visual references are useful later, but they cannot substitute for understanding the task the new site must support.

Keep a visible distinction between decisions, assumptions, and unanswered questions. An assumption such as customers prefer to call should not quietly become a design requirement. Assign someone to verify it through existing records or customer conversations. Where evidence is unavailable, document the uncertainty and choose a reversible approach that can be reviewed after launch.

End with responsibilities and an artifact

Reserve the final part of the session for a recap. State what was decided, what remains open, and who will supply missing information. Each action needs an owner and a realistic due date. A list of ideas without responsibility attached tends to disappear into the same shared folder as the meeting recording.

Turn the outcome into a concise discovery document: audience priorities, project objectives, content needs, constraints, and a decision log. Ask the decision maker to confirm it before design begins. The workshop succeeds when the team can use that document to explain why a page or feature exists. Remote collaboration becomes much more effective when the output is a usable agreement rather than simply proof that everyone attended.