Decide what the meeting needs to resolve
I judge a discovery workshop by the decisions people can make when they leave. For a Claude pilot, I want the group to choose one workflow, identify the sources it needs and agree how someone will review the answers. If the meeting ends with a longer list of possibilities and no owner, it has created more work for the next meeting rather than preparing a pilot.
Define the outputs before you send the invitation: a prioritized question set, a source and permissions map, a review method and a pilot recommendation. Concluding that more preparation is needed is a perfectly good outcome when the missing prerequisite is named and assigned. What the workshop cannot do is declare production readiness for every integration someone mentions.
Invite the owners and settle security first
Bring a business process owner, a representative user, an analyst or data owner, a source system administrator and someone accountable for security or governance. One person may cover several roles, but every responsibility needs a voice in the discussion. Invite the people who will approve the proposed pilot early enough to identify a missing prerequisite while the scope can still change.
My consistent field lesson is security first. Identity, permissions and data boundaries should be agreed before the first user logs in, not retrofitted after a pilot succeeds. Send data-handling expectations with the agenda. Participants should never upload credentials, customer records or protected health information into an unapproved workshop tool. In healthcare, HIPAA obligations do not pause for a brainstorming session.
Map the workflow before the connector
Use a short pre-work questionnaire: which recurring task consumes effort, what an acceptable answer looks like, which systems hold the evidence, and who is allowed to see it. An abstracted example is enough to show whether a question is well formed.
In the room, walk the task from trigger to final action, separating retrieval, interpretation, review and approval. Only then discuss where Claude might assist and how an approved connection would supply information. An MCP connector provides access to a service; it does not establish business meaning or authorization. If an application lacks a suitable MCP server, record the need for a supported API or a custom integration assessment. An unavailable connector is never permission to bypass the application's access controls.
Test three contrasting questions
Choose a straightforward question, an ambiguous one, and one that should hit an access or evidence boundary. In a finance workflow that might be a defined period, an unspecified meaning of revenue, and data outside the test user's scope. In a wealth management or private banking context, the boundary case might be a household the user is not entitled to see.
Ask the group what a good answer, or a good refusal, would look like for each. That produces a far more useful demonstration brief than a collection of impressive prompts that assume perfect data and unlimited access.
Write the pilot agreement in the room
Record users, sources, duration, support owner, review responsibilities and stop conditions. Decide how a completed unit of work will be measured against the current process, including time spent checking answers. List the approvals needed before production data is used. A pilot with no stopping rule becomes a permanent experiment with no owner.
Reserve the final part of the session for the decision itself: proceed with the bounded pilot, resolve a named prerequisite, or pick a different workflow. Capture unresolved disagreements explicitly. If two teams define the same metric differently, that belongs in the plan, not hidden behind a fluent answer. Share a short decision record, not a transcript.
Follow through with the same evidence
At the pilot review, return to the question set and acceptance criteria agreed in the workshop. Explain what changed during implementation and why. Compare the completed workflow, including review and exceptions, with the baseline. I prefer to measure in weeks, so the workshop should end with a pilot whose first results arrive within a quarter.
As a Claude Partner Network services partner, dotSolved runs enterprise Claude assessments that organize this discussion around a real business process. Where the workflow involves governed analytics, a Nexatron demonstration can explore that portion with the relevant integrations.