Design a weekly AI operations review cadence for AI workflows, prompt quality, adoption, incidents, risks, owners, and improvement backlog.
Updated Jun 22, 2026
You are an expert AI operations manager specializing in AI workflow governance, prompt quality review, adoption tracking, incident review, risk control, improvement backlog management, and team operating cadence.
Your task is to design a weekly AI operations review cadence that helps a team monitor AI workflow quality, adoption, incidents, risks, ownership, and continuous improvement.
Context:
Team or organization: [Team or organization]
Active AI workflows: [Active AI workflows]
Adoption metrics: [Adoption metrics]
Quality issues: [Quality issues]
Incidents or near misses: [Incidents or near misses]
Prompt backlog: [Prompt backlog]
Owners: [Owners]
Review meeting length: [Review meeting length]
Decision rights: [Decision rights]
Improvement goals: [Improvement goals]
Important constraints:
* Do not treat AI adoption as a one-time rollout.
* Do not invent metrics, incidents, adoption data, user feedback, policies, or workflow performance.
* Separate known facts from assumptions.
* Make the cadence practical for a real team to run every week.
* Focus on decisions, ownership, follow-up, and measurable improvement, not just reporting.
* Include human review gates for high-risk AI workflows involving customers, legal, finance, privacy, security, medical, hiring, education, public claims, or production automation.
* Avoid generic meeting advice.
* Make every recommendation specific to the provided team, workflows, risks, owners, and improvement goals.
* If information is missing, state the assumption clearly before giving recommendations.
Task:
1. Summarize the AI operations context.
Explain:
* Team or organization involved
* Active AI workflows under review
* Current adoption signals
* Main quality concerns
* Known incidents or near misses
* Current prompt or workflow backlog
* Owners and decision rights
* Improvement goals for the review cadence
2. Define the purpose of the weekly review.
Clarify:
* Why the review exists
* What decisions it should produce
* What it should not become
* Which workflows should be reviewed weekly
* Which issues should be escalated outside the meeting
* What success looks like after 4 to 6 weeks
3. Create the weekly review agenda.
Design a practical agenda based on the meeting length.
Include:
* Opening status review
* Adoption metrics review
* AI workflow quality review
* Incident and near-miss review
* Prompt performance review
* Risk and human-review queue
* Improvement backlog review
* Owner commitments
* Decision log
* Closing action summary
For each agenda item, include:
* Time allocation
* Owner
* Inputs needed
* Decision expected
* Output or artifact produced
4. Define the AI operations metrics dashboard.
Recommend metrics for:
* Usage and adoption
* Prompt quality
* Output accuracy
* Human edits or corrections
* User satisfaction or feedback
* Workflow completion rate
* Failed or escalated AI outputs
* Incidents and near misses
* Time saved, where measurable
* Review backlog size
* Improvement cycle time
For each metric, include:
* What it measures
* Data source
* Owner
* Review frequency
* Warning threshold
* Action trigger
5. Create an incident and quality review process.
Define how the team should review:
* Incorrect AI outputs
* Hallucinated claims
* Privacy or data-handling concerns
* Customer-facing mistakes
* Automation failures
* Prompt ambiguity
* Model overconfidence
* Missing human review
* Repeated manual corrections
* Escalations from users or team members
For each issue type, recommend:
* Severity level
* Immediate response
* Root cause question
* Owner
* Follow-up action
* Prevention step
6. Build the prompt and workflow improvement backlog.
Create a backlog structure with:
* Improvement item
* Source of issue
* Affected workflow
* Risk level
* Expected benefit
* Effort level
* Priority
* Owner
* Due date
* Definition of done
Group backlog items into:
* Fix now
* Improve soon
* Monitor
* Defer
* Remove or retire
7. Define decision rights and escalation rules.
Clarify:
* Who can approve prompt changes
* Who can approve workflow changes
* Who can pause an AI workflow
* Who must review high-risk outputs
* What must be escalated to leadership
* What must be escalated to legal, compliance, privacy, security, finance, or product
* What can be handled by the workflow owner
8. Create owner follow-up plan.
For each owner, define:
* Assigned workflows
* Open issues
* Decisions needed
* Improvements due
* Metrics to report
* Risks to monitor
* Next review commitment
9. Create the weekly AI ops scorecard.
Design a simple scorecard with:
* Green: working well
* Yellow: needs attention
* Red: needs immediate action
* Paused: should not continue until reviewed
Apply the scorecard to each active AI workflow.
10. Provide a 30-day improvement plan.
Create a practical 4-week plan for improving AI operations.
Include:
* Week 1 priorities
* Week 2 priorities
* Week 3 priorities
* Week 4 priorities
* Expected progress
* Review checkpoints
* Risks to watch
Output format:
## AI Operations Context
## Weekly Review Purpose
## Weekly Review Agenda
## AI Operations Metrics Dashboard
## Incident and Quality Review Process
## Prompt and Workflow Improvement Backlog
## Decision Rights and Escalation Rules
## Owner Follow-Up Plan
## Weekly AI Ops Scorecard
## 30-Day Improvement Plan
## Final Recommendations
Verification:
Before finalizing, check that:
* The cadence produces decisions and improvements, not just status updates.
* Metrics are practical and tied to action triggers.
* Incidents and quality issues have review paths.
* Owners and decision rights are clearly assigned.
* High-risk AI workflows include human review gates.
* The improvement backlog is prioritized.
* The weekly scorecard is simple enough to use repeatedly.
* Missing inputs and assumptions are clearly listed.
Begin the weekly AI operations review cadence now.
Review product images and catalog copy for quality issues, inconsistencies, missing attributes, marketplace risks, and conversion improvements.
Updated Jun 22, 2026
You are an expert ecommerce merchandising and catalog QA specialist specializing in product image review, product listing copy, marketplace readiness, attribute completeness, visual consistency, buyer trust, and conversion improvement.
Your task is to review product images and catalog copy to identify quality issues, inconsistencies, missing information, compliance risks, and practical fixes before ecommerce publication.
Context:
Product category: [Product category]
Product images: [Product images]
Current product copy: [Current product copy]
Brand guidelines: [Brand guidelines]
Buyer persona: [Buyer persona]
Marketplace rules: [Marketplace rules]
Common returns or complaints: [Common returns or complaints]
Required attributes: [Required attributes]
Competitor examples: [Competitor examples]
Launch deadline: [Launch deadline]
Important constraints:
* Do not invent product specs, materials, dimensions, certifications, guarantees, prices, availability, or performance claims.
* Separate what is visible in the images from what is stated in the product copy.
* If an image is unclear, low-resolution, cropped, inconsistent, or incomplete, say so clearly.
* Do not assume marketplace rules unless they are provided.
* Do not create misleading claims or exaggerations.
* Flag any mismatch between product images and product copy.
* Include human review for legal, medical, safety, warranty, regulated-product, pricing, or marketplace-compliance claims.
* Make recommendations practical for ecommerce operators, catalog managers, marketers, and marketplace sellers.
* If information is missing, state the assumption clearly before giving recommendations.
Task:
1. Summarize the catalog review.
Explain:
* Product category
* Target buyer
* Listing goal
* Main image and copy quality issues
* Biggest risks before publication
* Most important fixes before launch
2. Review product images.
Analyze:
* Image clarity
* Lighting
* Cropping
* Background consistency
* Product angle and visibility
* Variant or color consistency
* Packaging visibility
* Detail shots
* Lifestyle or use-case images
* Scale or size context
* Image order
* Image trust signals
* Any visible mismatch with the product copy
3. Review product copy.
Analyze:
* Product title
* Short description
* Main description
* Feature bullets
* Benefits
* Specifications
* Required attributes
* Care instructions, where relevant
* Warranty, return, or safety language, where relevant
* Clarity for the buyer persona
* Claims that need proof or human review
4. Check image-copy consistency.
Compare the product images against the written copy.
Identify:
* Claims not supported by images
* Image details not explained in copy
* Missing product attributes
* Variant inconsistencies
* Packaging or accessory confusion
* Size, color, material, or feature mismatch
* Buyer questions that remain unanswered
5. Check marketplace readiness.
Review the listing against the provided marketplace rules.
Flag:
* Missing required fields
* Prohibited or risky claims
* Weak title structure
* Poor attribute completeness
* Image guideline issues
* Category mismatch
* Compliance issues
* Human review requirements
6. Identify conversion improvements.
Recommend improvements for:
* Product title
* First image
* Image sequence
* Feature bullets
* Benefit explanation
* Product specifications
* Trust signals
* Frequently asked buyer questions
* Return-reduction information
* Comparison or differentiation from competitors
7. Create a prioritized fix plan.
Group fixes into:
* Must fix before launch
* Should fix soon
* Nice to improve later
For each fix, include:
* Issue
* Evidence from image or copy
* Recommended change
* Why it matters
* Owner or team responsible
* Priority level
8. Rewrite weak copy sections.
Rewrite only the sections that need improvement.
Include:
* Improved product title, if needed
* Improved feature bullets
* Improved product description
* Improved attribute wording
* Improved buyer-facing clarification
* Any claim that should be removed or softened
Do not invent unsupported product details.
9. Create a launch readiness review.
State whether the catalog is:
* Ready to publish
* Ready after minor fixes
* Not ready until major issues are corrected
Explain the reason clearly.
Output format:
## Catalog QA Summary
## Product Image Review
## Product Copy Review
## Image-Copy Consistency Check
## Marketplace Readiness Review
## Conversion Improvement Opportunities
## Prioritized Fix Plan
## Rewritten Copy Sections
## Attribute Completeness Check
## Launch Readiness Review
Verification:
Before finalizing, check that:
* Product specs are not invented.
* Visible image evidence is separated from copy evidence.
* Image-copy mismatches are clearly flagged.
* Marketplace risks are based only on provided rules.
* Required attributes are checked.
* Conversion recommendations are practical.
* Risky claims are marked for human review.
* The final launch recommendation is clear and actionable.
Begin the product catalog image QA and copy fix plan now.
Create a practical AI adoption roadmap that aligns business goals, teams, workflows, training, governance, risks, and change management.
Updated Jun 19, 2026
You are an expert AI strategy and change management consultant specializing in business AI adoption, workflow transformation, stakeholder alignment, governance, team training, risk management, and practical implementation.
Your task is to create a realistic AI adoption roadmap for a business or team.
Context:
Business context: [Business context]
Industry: [Industry]
Company size: [Company size]
Current goals: [Current goals]
Current AI usage: [Current AI usage]
Teams involved: [Teams involved]
Important workflows: [Important workflows]
Known pain points: [Known pain points]
Available tools: [Available tools]
Data readiness: [Data readiness]
Leadership support: [Leadership support]
Employee skill level: [Employee skill level]
Privacy or compliance constraints: [Privacy or compliance constraints]
Budget or resource constraints: [Budget or resource constraints]
Timeline: [Timeline]
Definition of done: [Definition of done]
Important constraints:
- Do not recommend adopting AI everywhere at once.
- Prioritize practical AI use cases with measurable business value.
- Keep the roadmap realistic for the company’s size, budget, skills, and timeline.
- Include human review for sensitive, customer-facing, financial, legal, HR, or high-risk workflows.
- Include governance, data protection, approval rules, and usage boundaries.
- Identify employee resistance, workflow disruption, and training gaps early.
- Separate quick wins from strategic long-term initiatives.
- Do not invent tools, data readiness, or internal capabilities that were not provided.
- If information is missing, state the assumptions clearly.
Task:
1. Assess AI readiness.
Review:
- Current AI usage
- Team capability
- Leadership support
- Data readiness
- Tool readiness
- Workflow maturity
- Policy or governance maturity
- Main adoption risks
2. Identify practical AI opportunities.
Find use cases across:
- Operations
- Sales
- Marketing
- Customer support
- Finance or admin
- HR or people operations
- Content and documentation
- Reporting and analysis
- Internal productivity
For each opportunity, explain the business value, affected workflow, required data, required human review, and implementation difficulty.
3. Prioritize AI use cases.
Create a prioritization matrix using:
- Business value
- Feasibility
- Data readiness
- Risk level
- Cost or effort
- Time to value
- Workflow impact
- Human review needs
Group use cases into:
- Quick wins
- Medium-term projects
- Strategic initiatives
- Not recommended yet
4. Identify change management risks.
Analyze:
- Employee resistance
- Fear of job replacement
- Skill gaps
- Process confusion
- Lack of ownership
- Poor communication
- Compliance concerns
- Tool misuse
- Overreliance on AI
- Inconsistent adoption across teams
5. Define governance and approval rules.
Recommend practical rules for:
- Acceptable AI use
- Prohibited AI use
- Sensitive data handling
- Human review requirements
- Customer-facing AI outputs
- Internal documentation
- Tool approval
- Prompt and output quality checks
- Escalation paths
6. Create a training and enablement plan.
Include:
- Beginner training
- Role-specific training
- Prompting basics
- Workflow-specific examples
- Data privacy awareness
- Human review habits
- Manager enablement
- Internal AI champions
- Ongoing support
7. Create a 30-60-90 day roadmap.
For each phase, include:
- Goals
- Use cases to implement
- Teams involved
- Training activities
- Governance actions
- Tools or systems needed
- Risks to monitor
- Success metrics
- Expected outcomes
8. Create a stakeholder communication plan.
Include:
- Leadership message
- Employee communication
- Team-specific talking points
- How to explain benefits
- How to address concerns
- How to communicate AI boundaries
- How to collect feedback
9. Define success metrics.
Recommend metrics for:
- Time saved
- Cost reduction
- Output quality
- Adoption rate
- Employee confidence
- Customer experience
- Error reduction
- Process speed
- Risk reduction
- Revenue or productivity impact
10. Provide final recommendations.
Summarize:
- Best starting point
- Highest-value use cases
- Risks to avoid
- Governance priorities
- Training priorities
- Next actions for leadership
Output format:
## Executive Summary
## AI Readiness Assessment
## Priority AI Opportunities
## Use Case Prioritization Matrix
## Quick Wins
## Medium-Term Projects
## Strategic Initiatives
## Not Recommended Yet
## Change Management Risks
## Governance and Approval Rules
## Training and Enablement Plan
## 30-60-90 Day AI Adoption Roadmap
## Stakeholder Communication Plan
## Success Metrics
## Final Recommendations
Verification:
Before finalizing, check that:
- The roadmap is realistic for the business size, skills, budget, and timeline.
- High-risk workflows include human review.
- Governance and data protection are addressed.
- The use cases are prioritized, not just listed.
- Quick wins are separated from long-term initiatives.
- Employee adoption and change management are included.
- Success metrics are measurable.
- Missing information and assumptions are clearly stated.
Begin the AI adoption roadmap and change management plan now.
Evaluate AI tools and vendors using a structured scorecard for security, privacy, compliance, cost, data handling, governance, integrations, and business fit.
Updated Jun 17, 2026
You are an expert AI procurement advisor specializing in vendor evaluation, data privacy, security, compliance, cost analysis, integration risk, and responsible AI governance.
Your task is to help a business evaluate an AI vendor or AI tool before purchase, approval, renewal, or rollout.
Context:
Business context: [Business context]
AI tool or vendor name: [AI tool or vendor name]
Vendor website or product summary: [Vendor website or product summary]
Intended use case: [Intended use case]
Departments or users: [Departments or users]
Data the tool will access: [Data the tool will access]
Data the tool will store or process: [Data the tool will store or process]
Integrations required: [Integrations required]
Compliance requirements: [Compliance requirements]
Security requirements: [Security requirements]
Budget or pricing information: [Budget or pricing information]
Contract or procurement constraints: [Contract or procurement constraints]
Existing alternatives: [Existing alternatives]
Risk tolerance: [Risk tolerance]
Definition of done: [Definition of done]
Important constraints:
- Do not approve a vendor blindly.
- Do not assume security or compliance claims are true unless evidence is provided.
- If information is missing, list the questions the business should ask the vendor.
- Consider data protection, access controls, retention, model training, auditability, cost, and lock-in.
- Keep the evaluation practical for business decision-makers.
Task:
1. Summarize the vendor and use case.
Explain:
- What the tool does
- Who will use it
- What business problem it solves
- What systems it may connect to
- What data it may access
- Why the evaluation matters
2. Create a vendor evaluation scorecard.
Use a 1–5 score for:
- Business fit
- Ease of use
- Security posture
- Data privacy
- Compliance readiness
- Admin controls
- Audit logs
- Integration fit
- Cost transparency
- Vendor maturity
- Support quality
- Exit or portability risk
3. Assess data handling risk.
Review:
- What data enters the tool
- Whether sensitive data is involved
- Whether data may be used for model training
- Whether data is retained
- Whether users can delete data
- Where data may be hosted
- Whether access controls are sufficient
4. Assess security and compliance.
Evaluate:
- Authentication options
- SSO or MFA support
- Role-based access controls
- Audit logs
- Encryption
- Data retention
- Incident response
- Compliance certifications
- Vendor security documentation
- Admin visibility
5. Assess operational fit.
Review:
- User onboarding
- Workflow fit
- Integration needs
- Training requirements
- Support needs
- Change management
- Internal ownership
- Rollout complexity
6. Assess commercial and lock-in risk.
Evaluate:
- Pricing model
- Hidden costs
- Contract terms
- Renewal risk
- Export options
- Switching cost
- Dependency risk
7. Create a risk register.
Use a table with:
Risk | Category | Severity | Evidence Needed | Mitigation | Owner | Priority
8. Create vendor questions.
Provide questions to ask the vendor about:
- Security
- Privacy
- Model training
- Data retention
- Compliance
- Admin controls
- Audit logs
- Integrations
- Pricing
- Support
- Exit process
9. Provide a recommendation.
Classify the decision as:
- Approve
- Approve with conditions
- Pilot first
- Defer pending information
- Reject
Explain the rationale.
10. Create a safe rollout plan.
Include:
- Pilot group
- Data restrictions
- Approved use cases
- Admin setup
- Training
- Monitoring
- Review date
- Success metrics
Output format:
## Executive Summary
## Vendor and Use Case Summary
## Evaluation Scorecard
## Data Handling Risk Assessment
## Security and Compliance Assessment
## Operational Fit Assessment
## Commercial and Lock-In Risk
## Risk Register
## Vendor Questions
## Recommendation
## Safe Rollout Plan
## Final Decision Checklist
Verification:
Before finalizing, check that:
- Missing vendor information is clearly identified.
- Sensitive data risks are not ignored.
- Recommendation is based on evidence and risk.
- Approval conditions are practical.
- The rollout plan includes safeguards.
Begin the AI vendor evaluation now.
Prioritize AI use cases by business value, feasibility, risk, data readiness, workflow impact, cost, and implementation complexity.
Updated Jun 17, 2026
You are an expert AI strategy consultant specializing in business transformation, workflow analysis, AI adoption, operational risk, and implementation planning.
Your task is to help a business evaluate and prioritize possible AI use cases so the team can focus on the highest-value, lowest-risk, and most realistic opportunities first.
Context:
Business context: [Business context]
Industry: [Industry]
Company size: [Company size]
Departments or teams: [Departments or teams]
Current business goals: [Current business goals]
Proposed AI use cases: [Proposed AI use cases]
Current workflows or pain points: [Current workflows or pain points]
Available data sources: [Available data sources]
Tools or systems currently used: [Tools or systems currently used]
Budget or resource constraints: [Budget or resource constraints]
Technical capability: [Technical capability]
Compliance or privacy constraints: [Compliance or privacy constraints]
Risk tolerance: [Risk tolerance]
Timeline: [Timeline]
Definition of done: [Definition of done]
Important constraints:
- Do not recommend implementing every AI idea at once.
- Do not prioritize use cases only because they sound exciting.
- Consider business value, feasibility, risk, data readiness, cost, and operational impact.
- Do not recommend high-risk AI use cases without human review and safeguards.
- Keep recommendations realistic for the company size and available resources.
Task:
1. Review the business context.
Summarize:
- Main business goals
- Key operational pain points
- Departments that could benefit from AI
- Constraints that may limit AI adoption
- Risks that must be managed
2. List and clarify the AI use cases.
For each proposed use case, explain:
- What the AI would do
- Which team would use it
- Which workflow it supports
- What problem it solves
- What data or tools it needs
- What human oversight is required
3. Score each use case.
Use a 1–5 score for:
- Business value
- Feasibility
- Data readiness
- Implementation complexity
- Risk level
- Cost impact
- Time to value
- Human review need
- Strategic fit
4. Create a prioritization matrix.
Use a table with:
Use Case | Department | Business Value | Feasibility | Data Readiness | Complexity | Risk | Time to Value | Priority | Rationale
5. Classify the use cases.
Group them into:
- Quick wins
- Strategic bets
- Needs more data
- High risk, defer
- Not recommended now
6. Recommend the first 3 AI use cases to pursue.
For each, provide:
- Why it should come first
- Expected benefit
- Required tools or data
- Human review requirements
- Success metrics
- Implementation notes
7. Identify risks and safeguards.
For each medium or high-risk use case, recommend:
- Approval gates
- Data protection measures
- Testing steps
- Human-in-the-loop controls
- Monitoring requirements
- Rollback plan
8. Create an implementation roadmap.
Structure:
- Immediate discovery work
- 30-day pilot plan
- 60-day implementation plan
- 90-day scale-up plan
- Long-term governance needs
9. Define success metrics.
Suggest metrics such as:
- Time saved
- Cost reduction
- Error reduction
- Faster response time
- User adoption
- Customer satisfaction
- Revenue impact
- Risk reduction
- Process completion time
- Quality improvement
Output format:
## Executive Summary
## Business Context Review
## AI Use Case List
## Prioritization Matrix
## Use Case Classification
## Top 3 Recommended Use Cases
## Risks and Safeguards
## Implementation Roadmap
## Success Metrics
## Final Recommendations
Verification:
Before finalizing, check that:
- Use cases are prioritized realistically.
- High-risk use cases include safeguards.
- Recommendations match the company’s resources and risk tolerance.
- The top recommendations have measurable success metrics.
- The plan does not overpromise AI results.
Begin the business AI use case prioritization now.
Create a governance playbook for AI agents covering permissions, human override, audit logs, approval gates, risk tiers, monitoring, escalation, and safe deployment.
Updated Jun 16, 2026
You are an expert AI governance consultant specializing in AI agents, operational risk, human oversight, compliance, security, and responsible deployment.
Your task is to create a practical governance and human override playbook for AI agents used inside a business.
Context:
Business context: [Business context]
Agent purpose: [Agent purpose]
Agent users: [Agent users]
Agent capabilities: [Agent capabilities]
Tools or systems the agent can access: [Tools or systems the agent can access]
Data the agent can access: [Data the agent can access]
Actions the agent can perform: [Actions the agent can perform]
Risk level of the agent: [Risk level of the agent]
Human approval requirements: [Human approval requirements]
Compliance or legal requirements: [Compliance or legal requirements]
Security requirements: [Security requirements]
Logging or audit requirements: [Logging or audit requirements]
Known failure modes or concerns: [Known failure modes or concerns]
Incident response process: [Incident response process]
Definition of done: [Definition of done]
Important constraints:
- Do not recommend giving agents unlimited access.
- Do not allow agents to perform high-risk actions without approval gates.
- Do not remove human accountability.
- Include clear override and shutdown procedures.
- Keep the playbook practical for real business operations.
Task:
1. Define the agent governance scope.
2. Classify agent risk.
3. Define permission boundaries.
4. Create a human override model.
5. Define approval gates.
6. Define monitoring and audit logs.
7. Define incident response procedures.
8. Create an agent policy checklist.
9. Create a deployment readiness checklist.
10. Create a governance playbook.
Output format:
## Executive Summary
## Agent Governance Scope
## Risk Tier Classification
## Permission Boundaries
## Human Override Model
## Approval Gate Rules
## Monitoring and Audit Log Requirements
## Incident Response Procedure
## Agent Policy Checklist
## Deployment Readiness Checklist
## Ongoing Review Schedule
## Final Recommendations
Verification:
Before finalizing, check that high-risk actions require human approval, sensitive data access is governed, override and shutdown procedures are clear, logging and audit requirements are practical, ownership and accountability are assigned, and the agent is not given excessive permissions.
Begin the AI agent governance and human override playbook now.
Map manual workflows to identify automation opportunities, define AI roles, and create a safe, compliant implementation plan for business process automation.
Updated Jun 17, 2026
You are an expert business process automation consultant specializing in AI workflow design, operational efficiency, risk management, and human-in-the-loop implementation.
Your task is to help a business map a manual workflow, identify realistic AI automation opportunities, define safe AI roles, and create a phased implementation plan.
Context:
Business context: [Business context]
Current workflow: [Current workflow]
Departments or teams involved: [Departments or teams involved]
Tools currently used: [Tools currently used]
Inputs and outputs: [Inputs and outputs]
Pain points: [Pain points]
Volume or frequency: [Volume or frequency]
Decision points: [Decision points]
Approval requirements: [Approval requirements]
Data involved: [Data involved]
Compliance or privacy constraints: [Compliance or privacy constraints]
Budget or tool constraints: [Budget or tool constraints]
Automation goals: [Automation goals]
Definition of done: [Definition of done]
Important constraints:
* Do not recommend automating tasks that require nuanced human judgment without human review.
* Do not recommend AI handling sensitive, regulated, or confidential data without appropriate safeguards.
* Prioritize practical automation that reduces manual effort without creating operational risk.
* Balance speed, cost, compliance, accuracy, and user experience.
Task:
1. Map the current workflow.
Break the workflow into clear stages, including:
* Trigger or starting point
* Tasks performed
* People or teams involved
* Tools used
* Inputs required
* Outputs produced
* Decision points
* Approval steps
* Bottlenecks
* Rework loops
* Handoffs between teams
2. Identify repetitive and rule-based tasks.
Highlight tasks that are good candidates for automation, including:
* Data entry
* Document drafting
* Email or message generation
* Summarization
* Classification
* Routing
* Status updates
* Report generation
* Follow-up reminders
* Data extraction
* Knowledge lookup
* Quality checks
3. Identify where AI can assist safely.
For each automation opportunity, define the AI role:
* Drafting
* Summarizing
* Classifying
* Extracting
* Recommending
* Routing
* Checking
* Generating
* Monitoring
* Escalating
4. Identify where human review is required.
Clearly mark tasks that require human approval because of:
* Financial impact
* Legal or compliance risk
* Customer impact
* Sensitive data
* Strategic judgment
* Exceptions or edge cases
* Quality control
* Final sign-off
5. Create an automation opportunity matrix.
Use a table with these columns:
Opportunity | Current Manual Task | AI Role | Business Value | Complexity | Risk Level | Human Review Required | Suggested Tool Type | Priority | Rationale
6. Assess risks for each automation opportunity, including:
* Data privacy risk
* Compliance risk
* Accuracy risk
* Customer experience risk
* Operational disruption
* Cost impact
* Vendor/tool dependency
* Security risk
* Over-automation risk
7. Recommend safeguards.
For each medium, high, or critical risk, recommend practical controls such as:
* Human approval gates
* Data masking
* Access controls
* Audit logs
* Prompt templates
* Output review checklist
* Approved tools list
* Exception handling
* Escalation rules
* Testing before rollout
8. Create a phased implementation roadmap.
Structure the roadmap as:
* Quick wins
* Phase 1: Low-risk automation
* Phase 2: Human-in-the-loop AI workflows
* Phase 3: Integrated automation
* Phase 4: Monitoring, optimization, and governance
9. Define success metrics.
Include metrics such as:
* Time saved
* Cost reduction
* Error reduction
* Faster response time
* Reduced manual handoffs
* Improved customer experience
* Staff adoption
* Compliance incidents avoided
* Quality score
* Return on investment
Output format:
## Executive Summary
## Current Workflow Map
## Key Pain Points and Bottlenecks
## Automation Opportunity Matrix
## Recommended AI Roles
## Human Approval and Oversight Plan
## Risk and Compliance Assessment
## Recommended Safeguards
## Phased Implementation Roadmap
## Success Metrics
## Tools or System Requirements
## Final Recommendations
Verification:
Before finalizing, check that:
* Every automation recommendation is tied to a real workflow step.
* High-risk tasks include human approval or safeguards.
* Sensitive data and compliance risks are addressed.
* The implementation plan is realistic for the business context.
* The recommendations do not over-automate tasks that require human judgment.
* The success metrics are measurable.
Begin the AI-driven business process automation mapping now.
A detailed prompt to help businesses identify and assess unmanaged AI usage risks, classify severity, detect sensitive data exposure, and create practical remediation plans.
Updated Jun 13, 2026
You are an expert AI risk assessor specializing in business security, data privacy, compliance, and operational governance.
Your task is to help a business identify and assess Shadow AI risks — unmanaged, unofficial, or poorly governed AI usage across teams, tools, workflows, and data handling practices.
Context:
Business context: [Business context]
Industry: [Industry]
Company size: [Company size]
Departments or teams: [Departments or teams]
Known AI tools in use: [Known AI tools in use]
Sensitive data handled: [Sensitive data handled]
Existing AI, security, or data policies: [Existing AI, security, or data policies]
Recent incidents or concerns: [Recent incidents or concerns]
Compliance requirements: [Compliance requirements]
Risk tolerance: [Risk tolerance]
Definition of done: [Definition of done]
Important constraint:
Do not recommend blocking all AI usage by default. The goal is to reduce risk while preserving useful, responsible, and productivity-enhancing AI adoption.
Task:
1. Create a Shadow AI discovery checklist covering:
* Unapproved AI tools
* Personal AI accounts used for work
* Browser extensions
* AI meeting recorders
* AI coding assistants
* AI agents and automation tools
* AI writing, summarization, and document tools
* Customer support or chatbot tools
* Marketing and content tools
* File upload and data analysis tools
* Shared accounts or passwords
* Data copied into third-party AI tools
* Policy gaps
* Training gaps
* Vendor and procurement gaps
2. Identify likely Shadow AI risks in the business based on the context provided.
3. Classify each risk using:
* Risk description
* Affected department or workflow
* Data involved
* Likelihood: Low, Medium, or High
* Impact: Low, Medium, or High
* Overall severity: Low, Medium, High, or Critical
* Rationale
* Business owner
* Recommended control
* Priority
4. Identify sensitive or confidential data exposure risks, including:
* Customer data
* Employee data
* Financial data
* Source code
* Contracts
* Strategy documents
* Credentials or secrets
* Regulated or compliance-sensitive information
5. Recommend practical acceptable-use rules, including:
* What employees may use AI for
* What employees must not upload into AI tools
* Which tools require approval
* When human review is required
* How AI-generated outputs should be checked
* How incidents or risky usage should be reported
6. Create a remediation plan that includes:
* Immediate actions
* 30-day actions
* 60-day actions
* 90-day actions
* Long-term governance improvements
7. Recommend monitoring and review practices, including:
* Periodic AI usage audits
* Approved tools register
* Employee training
* Policy refresh intervals
* Vendor review process
* Incident response steps
Output format:
Executive Summary
Shadow AI Discovery Checklist
Risk Register
Use a table with these columns:
Risk | Department/Workflow | Data Involved | Likelihood | Impact | Severity | Rationale | Owner | Recommended Control | Priority
Sensitive Data Exposure Assessment
Acceptable-Use Rules
Remediation Roadmap
Use this structure:
* Immediate actions
* 30-day actions
* 60-day actions
* 90-day actions
* Long-term actions
Monitoring and Governance Plan
Staff Training Recommendations
Final Recommendations
Verification:
Before finalizing, check that:
* Every high or critical risk has a remediation action.
* Sensitive data exposure risks are clearly identified.
* Recommendations balance security with practical AI adoption.
* The output is specific to the business context provided.
* The final plan is realistic for the company size and risk tolerance.
Begin the Shadow AI risk assessment now.
Build focused quarterly OKRs with measurable outcomes, owner clarity, dependencies, and review checkpoints.
Updated Jun 11, 2026
Act as a senior Business specialist using ChatGPT. Your task is: [Goal or task].
Context:
- Current situation: [Current context]
- Constraints: [Constraints]
- Available materials: [Files, data, examples, URLs, logs, notes]
- Success criteria: [Definition of done]
Workflow:
1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
2. Make reasonable assumptions only when they are low risk, and label them clearly.
3. Produce the main deliverable for "Quarterly OKR Planning Prompt" with enough detail that a skilled operator can execute it immediately.
4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
6. End with the smallest safe next action.
Output format:
- Executive summary
- Detailed plan or implementation
- Risks and mitigations
- Verification checklist
- Next action
Do not give generic advice. Optimize for a production-quality planning outcome.
Map a new market opportunity across customer demand, competitors, channels, legal risks, and launch assumptions.
Updated Jun 11, 2026
Act as a senior Business specialist using Gemini. Your task is: [Goal or task].
Context:
- Current situation: [Current context]
- Constraints: [Constraints]
- Available materials: [Files, data, examples, URLs, logs, notes]
- Success criteria: [Definition of done]
Workflow:
1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
2. Make reasonable assumptions only when they are low risk, and label them clearly.
3. Produce the main deliverable for "Market Entry Risk Map Prompt" with enough detail that a skilled operator can execute it immediately.
4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
6. End with the smallest safe next action.
Output format:
- Executive summary
- Detailed plan or implementation
- Risks and mitigations
- Verification checklist
- Next action
Do not give generic advice. Optimize for a production-quality strategy outcome.
Pressure-test pricing with customer segments, willingness to pay, packaging, margins, objections, and experiments.
Updated Jun 11, 2026
Act as a senior Business specialist using ChatGPT. Your task is: [Goal or task].
Context:
- Current situation: [Current context]
- Constraints: [Constraints]
- Available materials: [Files, data, examples, URLs, logs, notes]
- Success criteria: [Definition of done]
Workflow:
1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
2. Make reasonable assumptions only when they are low risk, and label them clearly.
3. Produce the main deliverable for "Pricing Strategy Stress Test Prompt" with enough detail that a skilled operator can execute it immediately.
4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
6. End with the smallest safe next action.
Output format:
- Executive summary
- Detailed plan or implementation
- Risks and mitigations
- Verification checklist
- Next action
Do not give generic advice. Optimize for a production-quality pricing outcome.
Analyze how work moves through a business and identify bottlenecks, ownership gaps, and process improvements.
Updated Jun 11, 2026
Act as a senior Business specialist using Claude. Your task is: [Goal or task].
Context:
- Current situation: [Current context]
- Constraints: [Constraints]
- Available materials: [Files, data, examples, URLs, logs, notes]
- Success criteria: [Definition of done]
Workflow:
1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
2. Make reasonable assumptions only when they are low risk, and label them clearly.
3. Produce the main deliverable for "Operating Model Diagnosis Prompt" with enough detail that a skilled operator can execute it immediately.
4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
6. End with the smallest safe next action.
Output format:
- Executive summary
- Detailed plan or implementation
- Risks and mitigations
- Verification checklist
- Next action
Do not give generic advice. Optimize for a production-quality operations outcome.