D · Power-user group

Shared organizational context

A small group works in parallel during the hands-on block to sketch what shared context Therme should build for everyone. The proposal and open questions come back into the room for the discussion that follows.

This group Cipriana + 1–2 power users

The task

Design shared context the rest of the team can use. Cover what to include and how to implement it inside the team's current Claude setup. Capture decisions, gaps, and questions you can't resolve in the room.

What "shared context" can mean on Claude Team

Shared Projects

Project-level instructions and a knowledge base, shared with the team (public or invite-only). The main lever for organizational context on Team plan.

Admin-deployed skills

Skills that an admin pushes org-wide so everyone has the same repeatable processes available.

Enterprise Search ("Ask your org")

Permission-aware search across connected sources (Google Drive, Gmail, SharePoint, etc.). Pulls at query time, doesn't index externally.

Individual layers (out of scope here)

Settings → Instructions for Claude, individual Cowork global instructions, individual skills. Each person controls these. Not what this activity is about.

Worth considering

What does every Therme team member need Claude to know about the company before any conversation starts?
Which existing documents are stable enough to be reference material, and which change too often?
Which decisions or framings about Therme do you not want re-explained every time?
Where does shared context unlock work people can't do today? Where would it just add noise?
Who owns shared context once it's set up? How does it stay current?
Given the paused SharePoint integration, what's the right starting point that doesn't require it?

Bring back to the room

A proposal in plain language: what shared context to build first, what goes in it, and how the team would use it. Plus open questions the whole group should weigh in on.