AI TRAINING
Claude Projects for Team Knowledge Management
Structure Claude Projects to turn scattered team knowledge into reliable, reusable AI workflows.
What it covers
This hands-on workshop teaches team leads and knowledge managers how to configure Claude Projects for specific teams, clients, or topics — including custom instructions, reference document uploads, and conversation handoff patterns. Participants will leave with at least one fully configured Project ready for immediate team use. The format combines short concept demos with guided build sessions, ensuring every attendee produces a working output rather than just notes.
What you'll be able to do
- Create and fully configure a Claude Project with custom instructions tailored to a specific team or client context
- Upload and organise reference documents so Claude draws on them consistently across conversations
- Design a handoff pattern that allows multiple team members to resume a Project conversation without losing context
- Define naming conventions and governance rules for managing multiple Projects across an organisation
- Audit an existing Project configuration and identify gaps in instructions or reference material
Topics covered
- Anatomy of a Claude Project: instructions, knowledge base, conversation memory
- Writing effective custom system instructions per team or use case
- Uploading and structuring reference documents (SOPs, FAQs, style guides)
- Designing one Project per team, client, or topic — naming conventions and governance
- Conversation handoff patterns: how to resume context across team members
- Access control and sharing Projects safely within an organisation
- Prompt templates and starter messages for consistent team outputs
- Measuring adoption and iterating on Project configurations
Delivery
Delivered in-person or live-online (Zoom / Teams) with a recommended 70% hands-on build time and 30% facilitated discussion. Each participant needs laptop access to their Claude account during the session. Pre-work includes a 15-minute setup checklist. Materials provided: a Project Configuration Canvas, a custom-instructions template library, and a post-workshop adoption tracker. A 60-minute follow-up Q&A session two weeks later is recommended.
What makes it work
- Assign a named owner per Project who is responsible for keeping instructions and reference docs current
- Run a short 'Project review' once per quarter to prune outdated documents and tighten instructions
- Start with one high-frequency team workflow (e.g. weekly report drafting) to demonstrate value before scaling
- Document your instruction-writing conventions in a shared style guide so new Project owners stay consistent
Common mistakes
- Writing generic system instructions that could apply to any team, defeating the purpose of per-team Projects
- Uploading large, unstructured documents instead of curated, chunked reference files — leading to Claude ignoring key content
- Creating one Project for the entire company rather than scoped, purpose-specific Projects per function or client
- Treating Projects as a one-time setup and never revisiting instructions as team workflows evolve
When NOT to take this
If the team does not yet have a Claude for Work (or equivalent) subscription and has no plan to acquire one within 30 days, this workshop delivers no immediate value — defer until licences are in place.
Providers to consider
Sources
This training is part of a Data & AI catalog built for leaders serious about execution. Take the free diagnostic to see which trainings your team needs.