Skip to content
Prompt to Prototype
Shadow AI policy for worker-built apps
Initializing search
Home
Start here
Strategy
Lifecycle
Operating model
Builder handbook
Platform & ops
Security
Governance
Evidence
Templates
Prompt to Prototype
Home
Start here
Start here
Start here by role
What is vibe coding?
Principles
Glossary
FAQ
Strategy
Strategy
Risks for business
Rollout roadmap
Rollout roadmap
Find existing apps
Pilot
Scale
Measurement
Measurement
ROI
Baselining
Vanity metrics
Lifecycle
Lifecycle
Intake and approval
Verify before release
Production ready
Change
Graduate to IT
Retire
Field guides
Field guides
Finance invoice matching
HR onboarding tracker
AI ticket triage
Sales-ops data sync
When the builder left
Operating model
Operating model
Roles and decision rights
Risk tiers
App registry
App ownership
When the builder leaves
Support model
Enablement and training
Builder handbook
Builder handbook
Write a build spec
Test your app
Document your app
Evals for AI features
Platform & ops
Platform & ops
Paved road
Paved road
Guardrails
Hosting
Low-code vs AI app builders
Approve tools
Operations
Operations
Incident response
AI spend
Security
Security
Exposed data and secrets
Coding agents
MCP and agents
AI features
Incident response
Governance
Governance
Acceptable use policy
Shadow AI policy
Data handling
IP and licensing
Regulation
Regulation
Compliance
US and Canadian laws
EU AI Act
Decisions about people
Standards crosswalk
Evidence
Evidence
Incidents
Failure patterns
Success patterns
Productivity studies
AI code security
Sources
Templates
Templates
App record template
Decision record
Risk tier workshop
Leadership charter
Incident tabletop
it-manager
governance
Shadow AI policy for worker-built apps
¶
This page is being written.
Back to top