What is on your mind?
What are you working on? Where are you losing time? What is pushing work into evenings or weekends?
A two-hour conversation to imagine the 12-month path ahead: less late-night work, more time back for the people doing the work, and a safer shared understanding of how AI may help Our House.
One discussion, not two sessions. We are gathering the questions and shape of the year.
Microsoft Copilot and Anthropic Claude are the chosen tools to learn, compare, and govern.
One monthly meeting for the next year, shaped by what the team is seeing and trying.
Do not arrive with a finished roadmap. Use the room to hear what matters to the people doing the work, identify the boundaries that need clarity, and decide what questions the monthly relationship should keep open.
What are you working on? Where are you losing time? What is pushing work into evenings or weekends?
Where could better tools support clinical staff, house teams, regional leaders, and the people they serve?
Which data, decisions, systems, and communications need policy, permission, review, or a human owner?
What should the monthly 90-minute rhythm help the team test, understand, measure, and bring back?
“What would make the next year of work feel more supported, less burdensome, and safer to navigate?”
These are the outcomes to keep testing against. They are not promises or metrics yet; they are the reason to have the conversation.
Help clinical and frontline staff get time back, reduce avoidable rework, and spend less work at night or on weekends.
Make recurring work, training, communication, reporting, and follow-up more consistent without erasing local judgment.
Help staff understand where AI may help, where it must be checked, and where it should not be used.
Use these prompts to bring the policy work Our House may need into view. Today’s job is to discover what requires an answer—not to invent the answer in the room.
What can enter Copilot or Claude? What is PHI, resident, employee, finance, internal, or public?
Which account, plan, tenant, connector, SharePoint site, or mailbox is actually approved?
May AI draft, summarize, retrieve, recommend, or execute? Where is human review required?
Who maintains a shared skill, checks a result, handles an exception, and retires a workflow?
Generic training, public information, de-identified examples, and low-risk administrative experiments.
Internal documents, employee information, finance exports, shared assistants, and connected Microsoft 365 work.
PHI, resident identifiers, clinical decisions, autonomous changes, or automatic external communication.
Each 90-minute session can be shaped by the team’s current work, the challenges that came up, and the tools and techniques that changed since the last meeting.
What is on your mind? What are you working on? What challenge or experiment should we understand before we meet?
Bring one workflow, tool update, technique, or governance question. Brainstorm together. Keep the boundary visible.
Record what was learned, what remains open, who owns the next step, and what should shape the next month.
“Before each monthly meeting, tell us what you are trying, where you are stuck, and what you want the room to help you think through.”
By 12:30, aim to have a shared picture of the questions, outcomes, guardrails, and monthly rhythm worth carrying forward.
The work and people outcomes the year should serve.
The policy, access, data, and ownership questions still open.
The pre-meeting prompts that let the team shape each 90-minute session.
Evidence of time returned, work improved, and safer understanding.