Module 2
Create one Claude Project around a real problem in your work. It does not need to be perfect. It needs to be real. The only way to understand what a Project changes is to experience the difference it makes on something you actually care about.
Choose something you return to regularly - a strategic initiative, a persistent challenge, an ongoing relationship you manage. It should be something where Claude having context about your role, your organization, or your goals would change the quality of what you get back.
A paragraph or two. Who you are, what this project is for, and how you want Claude to approach it with you. Do not overthink this - it is a brief, not a contract. You can refine it after your first few conversations reveal what Claude needs to know.
A document that captures something Claude should always know - a strategy memo, a set of guidelines, a previous analysis, a brief. Start with whatever single document would give Claude the most useful foundation for this problem.
Use the project for actual work this week - not a test prompt, not a demo. Bring a real question from your real work and see what changes when Claude already knows the context. Then compare it to what you would have gotten starting from scratch.
The first project you build will not be perfect. The instructions will be too vague or too specific. That is fine - you will know exactly what to fix after one real conversation. The goal is to start, not to get it right the first time.
No formal submission required. Come to Module 3 ready to discuss what you built - wins and failures are both worth the conversation.