Claude Workshop Pre-Assessment

Before we dive into the workshop, let's take 5 minutes to help us understand how your team currently works with Claude. Note: When it comes to Claude implementations, there are no right or wrong answers.

What is your role, and what does your team primarily focus on?

Helps us tailor examples and use cases to your domain. Knowing whether you're in ops, sales, finance, or product shapes the entire conversation.

How would you describe your current familiarity with Claude?

Sets the baseline so we don't over-explain basics or skip past foundations. No wrong answer here.

How are you currently using Claude, if at all?

Distinguishes casual chat usage from structured prompting or API/workflow integration. Helps us know

What's the #1 thing you're hoping to walk away with from this session?

Anchors the workshop to your actual outcome. We can then make sure we address it directly before time runs out.

How clearly defined are the use cases you wantto implement?

Tells us whether to focus on ideation, scoping, or execution. Attendees at different stages need very different conversations.

What has been the biggest obstacle to adopting or expanding your use of Claude so far?

Surfaces the real constraint — whether it's technical, organizational, trust-related, or simply a lack of time. This shapes how we frame solutions.

What types of data or systems would your ideal Claude use case interact with?

Helps us flag complexity early — integrating with PDFs or internal docs is very different from connecting to live databases or APIs.

At what stage is the data you're feeding into Claude?

Understanding whether you're working with raw exports, cleaned datasets, or unstructured documents tells us how much pre-processing your pipeline may need before Claude can be effective.

How are you currently getting data into Claude?

The method of ingestion significantly affects scalability and reliability. What works for a one-off task often isn't sustainable for a repeatable business workflow.

Do you intend Claude to perform write operations - such as updating a database, or executing actions in systems like ERPs, CRMs, or planning tools?

This distinguishes read-only use cases (summarize, extract, analyze) from agentic ones where Claude is taking action. The latter requires a more careful design and trust framework.

If time & resources weren't a constraint, what's one thing you'd love Claude to do your your business?

Opens up the conversation beyond immediate constraints and often reveals the highest-value opportunity worth working toward.

You are almost there …