> ## Documentation Index
> Fetch the complete documentation index at: https://academy.pathfindr.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Do we need a policy if we're only using basic AI features?" icon="circle-question">
    Yes. Even basic AI use involves data handling, decision-making, and quality concerns. A lightweight policy takes an afternoon to create and prevents expensive problems later.
  </Accordion>

  <Accordion title="How do we balance innovation with risk management?" icon="scale-balanced">
    Create "innovation zones" where teams can experiment with AI under controlled conditions. Allow approved uses freely, require approval for moderate-risk uses, and prohibit high-risk uses. Review the boundaries quarterly as you learn.
  </Accordion>

  <Accordion title="What if our team is already using AI without policy?" icon="triangle-exclamation">
    Don't panic. Conduct a quick audit to understand current usage. Grandfather in appropriate existing uses while setting boundaries for future adoption. Focus on education rather than punishment.
  </Accordion>

  <Accordion title="How detailed should our policy be?" icon="file-lines">
    Detailed enough to guide decisions, brief enough that people read it. Aim for 3-5 pages of core policy plus specific guidelines for high-risk use cases. If it's more than 10 pages, it's too long.
  </Accordion>

  <Accordion title="Should we ban AI tools we can't control?" icon="ban">
    Banning tools without providing alternatives drives use underground. Instead, approve enterprise tools with proper controls and explain why personal AI accounts aren't suitable for work use.
  </Accordion>

  <Accordion title="How do we keep policy current when AI changes so fast?" icon="clock">
    Focus on principles rather than specific tools. Review quarterly but don't chase every new feature. Major updates once or twice a year are sufficient for most organisations.
  </Accordion>
</AccordionGroup>