← Back to work
AI Governance · OneTrust

AI Policy Orchestration — Moving from Passive Flagging to Automated Enforcement

Enterprise AI teams were struggling to govern models and agents at scale. I led the design of an orchestration engine that turns static compliance rules into active, cross-platform enforcements.

Role
Principal Product Designer
Timeline
Sep 2025 – Present
Team
AI Governance PM, Eng, Cloud Leads
Status
Live
AI Guardrails Laptop Mockup0.1 IMAGE
Highlights
An automated governance engine that detects model violations, triggers native cloud guardrails, and automates remediation at scale.
Central Policy Registry0.2 IMAGE
0.2 Central policy registry across standards (NIST, EU AI Act).
Guardrail-to-agent conditional architecture0.3 IMAGE
0.3 Guardrail-to-agent conditional architecture.
Automated Risk Flagging0.4 IMAGE
0.4 Automatic risk score creation upon violation detection.
AI Policy Daily Digest0.5 IMAGE
0.5 Stakeholder daily compliance digest to combat alert fatigue.

Enterprises deploy hundreds of AI agents and models across fragmented ecosystems like AWS, Azure, and Foundry. Compliance and risk teams had no single place to enforce guardrails, leaving them blind to which models violated documentation or safety policies until after an audit broke down.

  • AI policies were disconnected from actual infrastructure — flagging issues without remediation paths.
  • Remediation was fully manual: teams were handed text instructions and forced to fix models across disparate cloud consoles.
  • No automated mechanism to trigger enterprise risk reviews, assessments, or alerts when non-compliant models went live.
2.8 min
Average policy creation time
82%
Cross-platform coverage
1-Click
Automated multi-cloud enforcements replaced manual steps
Unresolved violations monitor0.1b IMAGE

Detailed process breakdown and technical tradeoffs below ↓

Prework
Mapping policy attributes, equators, and baseline condition builders.
Research
Testing early prototypes with enterprise pilot accounts (TELUS, Dell).
Concept
Pivoting from manual instructions to native platform enforcement cards.
Detail
Multi-action orchestration: risks, assessments, and daily digest alerting.
Deployment
Private preview rollout and scaling directly into enterprise GA.
PREWORK

Defining "If This, Then That" for AI Governance.

The baseline logic engine.

We started with a foundational goal: allow compliance teams to select attributes and write conditional rules to identify which agents or models failed critical documentation or guardrail thresholds.

What's Happening
  • Established condition operators (equals, not blank, contains) for model attributes
  • Mapped out seeded guardrails across domains (Health, Loans, Employment)
  • Created the primary mechanism to flag models in violation state
Governance ecosystem architecture diagram1.1 DIAGRAM
Show early logic planning
Outcome
What this led to
A functional rule-building engine for AI assets
Initial prototype ready for enterprise validation
RESEARCH

Validating with TELUS, Dell, and Early Adopters.

The limits of manual checklists.

Testing our initial solution with large customers revealed a major flaw: our system gave them a checklist of remediation steps, but made engineers jump out to third-party tools to manually fix them.

What's Happening
  • Tested text-based manual remediation guides with risk teams
  • Discovered users found cross-system context switching tedious and error-prone
  • Customer feedback proved that teams wanted the platform to push fixes directly into their cloud environments
Manual Remediation Steps2.1 IMAGE
Outcome
What this led to
Pivot from manual checklists to automated platform enforcement
Buy-in to architect native integrations into AWS and Azure
CONCEPT

Architecting System-Aware Enforcement Cards.

Enforcement at the infrastructure layer.

Instead of treating all models identically, we made policies environment-aware. We designed preset enforcement cards tailored to AWS, Azure Foundry, and internal actions.

What's Happening
  • Built preset enforcement cards targeting specific cloud environments (AWS Bedrock, Azure)
  • Enabled targeted rules: "If a model is in AWS East, apply this Bedrock Guardrail card"
  • Designed automated triggers for instant risk creation and assessment launches
Concept Wireframe3.1 WIREFRAME
Compare enforcement strategies
Outcome
What this led to
Native multi-cloud enforcement architecture
Automated multi-action orchestration engine
DETAIL

Orchestrating Actions and Mitigating Alert Fatigue.

From detection to executive digest.

We detailed the side drawers for complex rule triggers, configured automated risk evaluations, and designed daily digest reports to give stakeholders quick action items instead of endless notifications.

What's Happening
  • Streamlined unresolved violation lists with quick-resolution actions
  • Configured automated risk scoring with impact and probability criteria
  • Designed automated email digests categorizing critical violations for policy owners
Violations List4.1 IMAGE
Risk Drawer4.2 IMAGE
Email Alert Drawer4.3 IMAGE
Outcome
What this led to
Deep multi-action workflow without screen clutter
Daily digest framework preventing alert fatigue
DEPLOYMENT

Live across the platforms that matter.

Already running for real customers.

Now live in production, with coverage expanding across the platforms our earliest customers actually run on.

What's Happening
  • Rolled out to GA with active enterprise adoption
  • Shipped and in active use by Dell, TELUS, and Lumen
  • Iterative roadmap expanded based on real-world multi-cloud orchestrations
Concept Wireframe5.1 IMAGE
Enforcement Strategies5.2 IMAGE
Outcome
What this led to
Proven enterprise governance scalability
Customer-led demand for deeper orchestration actions
Key Discovery
Compliance teams didn't need another place to document rules — they needed their rules to talk directly to their cloud infrastructure. Moving from passive checklists to system-aware automatic enforcement turned governance from a friction point into an automated guardrail.
Before view6.1 BEFORE
  • Manual, text-only remediation checklists
  • Disconnected from underlying cloud infrastructure (Bedrock, Azure)
  • Risk teams forced to context-switch across external consoles to resolve issues
Toggle to see the automated enforcement engine
✓ WORKED WELL

Preset Enforcement Cards (AWS Bedrock, Azure Foundry) allowed users to deploy deep technical cloud remediations without dealing with overwhelming API configuration settings.

△ STILL HARD

Balancing notification frequency with actionable urgency. It required multiple rounds of design to separate instant high-severity triggers from consolidated daily and weekly digests.

Ask me about: How we designed the action-triggering architecture to bridge governance compliance teams with technical AI engineers operating across multi-cloud environments.

AI Policy Orchestration evolved from a static rule-flagging concept into an automated enforcement engine. Since launch, it has cut average policy creation time to 2.8 minutes and reached 82% coverage across the platforms our customers actually run on — Dell, TELUS, and Lumen among them.

2.8 min
Policy creation time
3+ Tier-1
Major Enterprise Adopters
100%
Automated Enforcement