Turn capability into direction
- Set shared AI priorities and standards.
- Shape the 30/60/90-day leadership path.
- Decide what the monthly team conversation should keep learning.
The advance conversations found practical work, not abstract enthusiasm. These are the highest-value starting points for turning individual capability into repeatable team patterns—while keeping sensitive work inside the right enterprise boundary.
Find the work that consumes time across people, houses, or reporting cycles.
Start from an export, template, or known-good example before building a system.
Leave with a reusable workflow, a named owner, and a boundary for what still needs review.
Each card holds the strongest practical use cases from the deep dives. “Best place” means where the work should be developed first—not a final platform decision. Sensitive lanes remain export-first, human-reviewed, and subject to Our House IT, privacy, compliance, and BAA confirmation.
Claude Code is not the default answer for these leaders. It becomes relevant only if Our House later designates a technical owner for backend integration, permissions, or a durable internal service around a proven workflow.
If you are thinking, drafting, or learning, go to chat or a project where the context can stay with you and your team.
If you are already in Excel, stay there. The workbook, formulas, tabs, and templates are in the room with you.
When the steps work, go here for enterprise files, bounded multi-step workflows, repeatability, and scheduled work.
Keep this place with IT or the builders for integrations, validation scripts, backend services, and governed automation.
Public information, generic training, de-identified examples, templates, and administrative work without sensitive data.
Employee data, internal reports, finance exports, SharePoint, mailboxes, connectors, and shared assistants.
PHI, resident identifiers, clinical records, medication data, autonomous action, or automatic external communication.
The point is not to make twelve unrelated assistants. It is to identify a few patterns that can travel safely: export → inspect → reconcile; context → draft → review; and repeatable method → shared skill.
Bring the real template, export, checklist, or example that defines “good.”
Which other role has the same shape of work, even if the content is different?
Who maintains the instruction, checks the output, and decides when it changes?
Choose one safe team experiment for Friday’s governance and pilot conversation.
“Which useful pattern can travel across Our House—and what must stay role-specific, reviewed, or protected?”