Your AI Action Plan

Analyze this data for trends, outliers, and practical next steps. Return: 1. top 5 findings, 2. possible explanations, 3. questions to verify, 4. recommended next actions. Do not assume causes without evidence.

Data:
[PASTE]

In this workbook, analyze [TABLE/RANGE] and answer: What changed most, what looks unusual, which rows need attention, and what chart or pivot would best explain the result?

Use these spreadsheet findings to write a decision memo. Include: headline insight, supporting numbers, likely drivers, caveats, recommended action, and what data should be checked next.

Findings:
[PASTE]

Create a recurring analysis checklist for [DATA TYPE]. Include: required inputs, cleaning checks, metrics to calculate, outlier rules, interpretation questions, caveats, and the final memo format.

Write a weekly [TEAM / CLIENT / PROJECT] report.
Period: [DATE RANGE]
Metrics: [PASTE METRICS]
Highlights: [WHAT WENT WELL]
Risks or blockers: [WHAT NEEDS ATTENTION]
Next actions: [3-5 BULLETS]
Audience: [MANAGER / CLIENT / TEAM]. Keep it factual, concise, and easy to scan.

Analyze this report data before drafting the summary.
Data: [PASTE TABLE OR METRICS]
Return: 1. Top 5 changes, 2. likely explanations, 3. questions to verify, 4. what should be highlighted, 5. what should not be overclaimed.

Turn this exported data into a decision memo.
Audience: [WHO WILL READ IT]
Data: [PASTE CSV OR TABLE]
Return: executive summary, key changes, likely causes, recommended action, risks, and a short appendix explaining assumptions.

Create a reusable monthly review template for [ROLE / TEAM]. It should include: required inputs, KPI table, variance analysis, stakeholder narrative, recommended actions, risks, and a quality checklist before sending.

Create a research brief on [TOPIC] for [AUDIENCE]. Include: current landscape, 5 key facts, 3 risks, 3 open questions, and source links for every claim that affects a decision.

Review this research draft. Split it into: source-backed facts, reasonable inferences, unsupported claims, and questions to verify. Then rewrite the summary so unsupported claims are removed or clearly caveated.
Draft: [PASTE DRAFT]

Research [OPTIONS / VENDORS / TOPIC], compare them against [CRITERIA], and produce a recommendation memo. Include a table, tradeoffs, risks, source links, and the decision I should make if the priority is [COST / SPEED / QUALITY / RISK].

Create a research intake template for [ROLE / TEAM]. It should capture: decision to support, scope, time period, must-use sources, sources to avoid, comparison criteria, output format, approval owner, and caveats required before sharing.

Turn these rough process notes into a simple SOP. Include: purpose, when to use it, required inputs, step-by-step workflow, owner, tools, quality checks, and common mistakes.

Notes:
[PASTE]

Create a reusable checklist for [PROCESS]. Include sections for intake, execution, quality check, handoff, escalation, and completion evidence. Format it so I can paste it into Notion.

Convert this process explanation into: 1. SOP, 2. quick checklist, 3. training note for a new person, 4. edge cases, 5. questions to confirm with the process owner.

Transcript or notes:
[PASTE]

Design a procedure-library template for [TEAM]. Include fields for owner, last reviewed, inputs, steps, tools, examples, risks, escalation path, related templates, and update log. Add rules for when a procedure must be reviewed.

Summarize this meeting.
Notes or transcript: [PASTE]
Return: 1. short summary, 2. decisions made, 3. action items with owner and due date, 4. risks, 5. follow-up message draft.

Review this meeting transcript and create a follow-up note. Separate exact decisions from discussion points. Flag anything unclear. Transcript: [PASTE TRANSCRIPT].

Convert this meeting transcript into project tasks. For each task include owner, due date, dependency, priority, and a follow-up email paragraph. Transcript: [PASTE].

Create a meeting memory template for [TEAM / CLIENT]. For each meeting, capture decisions, action items, repeated themes, unresolved questions, stakeholder commitments, and items to revisit next time.

Extract business requirements from these stakeholder notes.
Notes: [PASTE]
Return: functional requirements, non-functional requirements, pain points, assumptions, open questions, conflicts, and source stakeholder for each item. Mark anything that needs confirmation.

Create a requirements matrix from these notes.
Notes: [PASTE]
Columns: requirement, stakeholder source, business goal, priority, acceptance criteria, dependency, conflict, open question, and validation owner.

Convert this stakeholder transcript into backlog-ready work.
Transcript: [PASTE]
Return: requirements, user stories, acceptance criteria, dependencies, risks, and Jira-ready ticket text. Flag any requirement that lacks enough evidence.

Create a requirements intake and validation playbook. Include: interview prompts, evidence rules, requirement categories, priority scoring, conflict resolution, validation checklist, traceability fields, and final sign-off template.

Turn these process notes into a current-state workflow.
Notes: [PASTE]
Return: steps, actor, system, input, output, handoff, wait time if mentioned, bottleneck, and question to verify.

Create a process map for this workflow. Include swimlanes for [TEAMS], decision points, system handoffs, bottlenecks, and open questions. Workflow notes: [PASTE]

Create a process improvement packet from this workshop transcript.
Transcript: [PASTE]
Return: current-state workflow, future-state recommendation, bottleneck list, data needed, decision points, and improvement backlog.

Design a process mapping standard for business analysis. Include: intake questions, workshop agenda, notation rules, swimlane rules, bottleneck categories, required evidence, future-state design checklist, and stakeholder review format.

Create an options matrix for this business problem.
Problem: [PASTE]
Options: [PASTE]
Return: option, benefit, downside, cost/effort, dependency, risk, evidence, and recommendation questions.

Build a weighted scoring model for these solution options.
Options: [PASTE]
Criteria: [PASTE OR SUGGEST]
Return: criteria definitions, suggested weights, score table, sensitivity risks, and where human judgment is required.

Create a decision memo from this research and options table.
Research: [PASTE]
Options table: [PASTE]
Return: recommendation, rationale, score summary, risks, implementation assumptions, and decision needed from leadership.

Create a reusable decision framework for business analysis. Include: problem framing, option intake, evidence standards, scoring criteria, weighting rules, stakeholder review, risk handling, and final recommendation memo template.

Analyze these KPI changes.
Data: [PASTE]
Return: top changes, possible drivers, anomalies, segments to inspect, questions for data owners, and what not to conclude yet.

In this dashboard, identify the biggest KPI changes, likely driver dimensions, outlier segments, and which visuals or measures should be checked before we present the finding.

Create a root-cause memo from these dashboard findings.
Findings: [PASTE]
Return: headline insight, evidence, likely drivers, alternative explanations, checks needed, business impact, and recommendation.

Create a KPI anomaly review system. Include: dashboard inputs, threshold rules, segment checks, seasonality checks, data-quality checks, owner questions, root-cause memo format, and escalation rules.

Turn this recommendation into a rollout checklist.
Recommendation: [PASTE]
Return: stakeholders, impacted systems, training needed, communications, risks, dependencies, decision owner, and success measures.

Create stakeholder-specific rollout messages for this change.
Change: [PASTE]
Stakeholders: [PASTE]
Return: leadership summary, manager message, frontline team message, support-team note, FAQ, and questions to verify before sending.

Create a change rollout pack from this recommendation memo.
Memo: [PASTE]
Return: rollout plan, timeline, RACI, stakeholder messages, training outline, readiness risks, and success measures.

Create a change-readiness assessment template for business analysis. Include: impacted groups, process changes, system changes, training need, communication need, adoption blockers, risk rating, mitigation, and readiness score.