We want our operations team to use AI to analyze our historical delivery data and find inefficiencies, but our compliance and legal stakeholders are blocking all progress due to IP leakage concerns. How do we use the Issues Solving Track (IDS) to break this deadlock and set safe, actionable boundaries?

Question

Tyler Smith · Accepted Answer

This is a classic conflict between the entrepreneurial drive for efficiency and the necessary guardrails of risk management. To break this deadlock, you must take the issue to your leadership team Level 10 Meeting™ and run it through the Issues Solving Track (IDS®).

Start by identifying the root cause of the fear. Usually, legal pushback occurs because the operations team has not defined a clear purpose and scope for the AI application. They are trying to use public consumer tools for enterprise data, which is a legitimate security threat.

Resolve this by establishing a clear compromise that satisfies both security and operational speed:

- Create a strict policy that completely bans the upload of customer or proprietary data into public, consumer-facing AI models.

- Agree to use enterprise-grade APIs with strict data-retention policies that guarantee your data is never used to train public models.

Once these technical guardrails are set, write them directly into your company processes. Update your operational seats on the Accountability Chart to make adherence to these security protocols a non-negotiable expectation. By establishing clear, written rules and utilizing enterprise-grade tools, you eliminate the legal risk while still giving your operations team the leverage they need to optimize delivery.