AI-Native ORB Workflow (Beginner-Friendly)

Principle

Use AI for drafting, summarizing, and organizing, not for making decisions with sensitive data.

“Never paste” list (do not put into AI)

  • Passwords, API keys, secrets
  • Full configuration exports containing PII
  • Full user lists with emails
  • Incident logs with sensitive details
  • Anything regulated (HIPAA/PCI) unless scrubbed

1) Meetings → transcript → summary

  • Record calls (with consent).
  • Export transcript.
  • Prompt AI: “Summarize decisions, risks mentioned, action items (owner + due date).”
  • Save summary as a dated note in /working/meeting-notes/.

2) Evidence capture → human notes → AI drafting

  • You collect screenshots + short Loom videos.
  • You write raw bullets: “What we saw” + “Why it matters”.
  • AI turns bullets into:
    • Clean risk statements
    • Executive summary paragraphs
    • Action plan items

3) Standard templates

Use the deliverable templates:

  • Exec Summary
  • Risk Register
  • 30/60/90 Plan
  • Maturity Scorecard

4) Automations (Zapier/Make)

Beginner automations worth doing:

  • Intake form submitted → create:
    • Google Drive folder structure
    • Project board template
    • Calendar invite templates
    • Slack/Email notification to internal team

Suggested tools (choose what you already have)

  • Google Workspace OR Microsoft 365
  • Notion OR ClickUp OR Trello
  • Loom (or Teams/Meet recording)
  • Zapier/Make
  • Password manager for access coordination (1Password/Bitwarden)

AI prompt snippets (copy/paste)

Meeting summary

“Summarize this transcript into: Decisions, Risks, Open Questions, Action Items (Owner Type, Due Date). Keep it concise.”

Risk drafting

“Turn these bullets into a risk register entry with: Title, Description, Impact, Likelihood, Evidence, Recommendation, Effort (S/M/L).”

30/60/90 plan drafting

“Create a 30/60/90 plan from these risks. Prioritize high impact + low effort first. Include Owner Type and Dependencies.”

Exec summary

“Write a 1–2 page executive summary for non-technical leadership. Focus on top risks, restore readiness, and top 5 actions for next 30 days.”


Beginner tip

If you do nothing else: use the templates and keep your language plain.