Skip to main content Skip to navigation
Careers
Brand USA
Agents of Change

AI as Your Chief of Staff – Building a Personal Operating System with Claude Code

Part of the Series: Agents of Change

June 26, 2026

About This Event

What if AI remembered every call you took, every commitment you made, and every insight worth saving—and surfaced exactly what you needed before you asked? Janette Roush, Senior Vice President, Innovation & Chief AI Officer for Brand USA, built a personal operating system that runs her entire work life: daily agendas assembled automatically, call prep pulled from past conversations, meeting notes that distribute key insights to the right project files, and conference debriefs that feed back into her speaking prep. This session walks through the actual system—how it’s structured, what it took to build, and how any professional can start with something simple and let it grow. Bring your curiosity and your messiest workflow.

Key Takeaways

  1. A personal operating system is just a folder of plain files. You set up one empty folder, point Claude Cowork at it, and Claude reads and writes the Markdown files inside — no coding, and you never hand-build the structure yourself. Cowork (in the Claude desktop app) is the piece that can actually read and write files on your computer.
  2. CLAUDE.md is the memory. A CLAUDE.md file at the root tells Claude who you are, how you work, and the schema for tasks; nested CLAUDE.md files inside each project or area give Claude the context it needs only when it is working there. You can ask Claude to update these files for you, so the system improves recursively over time.
  3. The PARA structure keeps it organized: Projects (time-bound, with end dates), Areas (ongoing), Resources, and Archives, plus an Inbox and a System folder. Claude files things into the right place and builds an interconnected wiki of people and companies that gets smarter as you use it.
  4. Connectors are what make it useful. Wiring in Outlook, Slack, Google Drive, Granola, Salesforce, and Wrike lets Claude pull from your real sources of truth and drop tasks onto your daily agenda. Read-only connectors (like Salesforce) and read/write connectors (like Wrike) carry different levels of risk worth understanding.
  5. Security is a real, team-by-team conversation: paid plans let you turn off model training on your data and add SOC 2 safeguards; read-only access and prompt-injection awareness protect you; and the browser/Chrome extension crosses a higher risk threshold. And prompt engineering is over for this work — just talk to Claude, use voice when you can, and let it interview you.

What You’ll Learn

After watching this video, you will be able to:

  • Create a Personal OS folder and point Claude Cowork at it as a sandboxed workspace Claude can read and write.
  • Write a root CLAUDE.md that tells Claude who you are, how you work, and the schema it should use for tasks.
  • Organize your files with the PARA structure (Projects, Areas, Resources, Archives) plus an Inbox and System folder.
  • Add nested CLAUDE.md files so Claude carries the right context into each project or area only when it is working there.
  • Connect tools (Granola, Salesforce, Wrike, Google Drive, Slack) and tell read-only from read/write access and the risk each carries.
  • Recognize prompt injection and evaluate the security safeguards — training opt-out, SOC 2, limiting the browser extension — for your own organization.
  • Test the system with a daily agenda and voice-created tasks, and capture tasks automatically from meeting transcripts.

Presenters

Janette Roush Senior Vice President, Innovation & Chief AI Officer

Documents & Resources

Available after the event concludes.

AI As Your Chief of Staff Download

Event Transcript