Skip to main content
Skip to content
Menu

Future of Work Intermediate 3 parts

Document your team's AI tool usage policies to mitigate security risk

You'll have a written policy covering which AI tools are approved for which data sensitivity levels, what information employees should never paste into free tools, and clear escalation paths for gray-

What you'll make

Team AI Usage Policy

  1. Tool Approval Matrix: sensitivity level vs approved tools
  2. Data Boundary Guidelines: what never goes into free tools
  3. Escalation Protocols: who decides gray-area cases

The 3 parts

Each part ends with a check you can see.

  1. Map Current AI Usage

    Survey your team's actual AI tool usage to identify security risks and productivity patterns

    Done when

    You have a documented inventory of which team members use which AI tools for what types of work, with specific security risks identified for each usage pattern

  2. Set Data Boundaries

    Create clear guidelines for what information should never be shared with free AI tools

    Done when

    You have specific data boundary rules that team members can apply to real situations, with examples from your actual work context

  3. Design Escalation Paths

    Create clear procedures for handling gray-area AI usage decisions that don't fit standard guidelines

    Done when

    You have escalation procedures that specify who makes decisions for different types of unclear AI usage cases, with response time commitments your team can actually meet

    Capstone: you put together your Team AI Usage Policy.

Where this helps

An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.

About this lesson

What you'll be able to do

  • Inventory actual AI tool usage across your team with specific security risks identified
  • Define clear data boundaries for AI tools based on sensitivity levels you can observe
  • Create escalation protocols that work for real gray-area decisions your team faces

Who it's for

  • Team leads responsible for operational security
  • Managers who need to balance productivity gains with risk management
  • Operations folks dealing with shadow AI usage

What it won't cover

  • Enterprise AI procurement strategies
  • Legal compliance frameworks
  • Technical implementation of AI security controls

Skills you'll practise

  • Shadow AI risk assessment
  • Data sensitivity classification
  • Policy workflow design
  • Stakeholder consultation