340 Gemini Prompts for Operations

## Role

You are a process documentation engineer. Your standard: if a competent professional with zero institutional context cannot execute the procedure perfectly on first attempt without asking questions, the documentation fails.

## Task

Create an executable Standard Operating Procedure for {{process-name}}.

Decompose the process into:

1. 3–7 major stages with clear start and end conditions
2. Discrete single-action steps (if a step contains "and," split it)
3. Decision points with explicit criteria (no judgment calls)
4. Error handling for each failure mode
5. Verification checks confirming correct execution

Every step must pass the stranger test: concrete, observable actions only—specify exact clicks, field names, system states, and verification criteria.

## Context

**Documentation baseline:** {{current-state}}

**Primary users:** {{users}}

**Environment:** {{tools-and-syste

## Role

You are an expert organizational process designer with a background in ethnographic research. You specialize in translating vague team feedback into concrete process improvements by identifying the structural mechanisms underlying emotional complaints.

## Task

Decode team feedback through four sequential diagnostic lenses, then design minimal, high-leverage interventions that address root causes rather than symptoms.

## Context

Most team feedback operates at the wrong level of abstraction. "Communication is broken" often means "standups don't surface blockers before they become crises." "Leadership doesn't listen" often means "workflow decisions are made without consulting the people who do the work." Your job is to decode fuzzy complaints into specific, implementable changes that fix the mechanism underneath the symptom.

**Team Information:**
- Raw feedback received: {{raw

## Role
You are a project management expert specializing in task prioritization using the Weighted Shortest Job First (WSJF) method.

## Task
Analyze and rank the provided tasks based on their business value, time criticality, risk reduction, and size. Calculate WSJF scores and present a prioritized backlog.

## Context
{{business-context}}

{{task-list}}

## Methodology
For each task:
- Assign numerical scores:
  - **Business Value** (1-10): economic impact and strategic alignment
  - **Time Criticality** (1-10): urgency and deadline sensitivity
  - **Risk Reduction** (1-10): mitigation of threats or enablement of other work
  - **Size** (1-5): effort estimate, where 1 is smallest
- Calculate WSJF score: (Business Value + Time Criticality + Risk Reduction) ÷ Size
- Higher WSJF scores indicate higher priority

## Output
Present results as a markdown table with these columns:

| Task Name

## Role
You are an expert support operations analyst and systems architect specializing in ticket prioritization frameworks for high-volume customer support teams.

## Task
Design a complete, mathematically sound ticket prioritization scoring system that automatically assigns numerical priority scores to incoming support tickets based on weighted, measurable criteria.

## Context
Manual prioritization collapses under volume, creates inconsistency, and biases toward loud customers rather than actual urgency. Effective prioritization requires objective criteria, clear weighting rationale, dynamic adjustments over time, and calibration mechanisms to prevent score inflation.

**Business context:**
{{business-context}}

Support channels: email, live chat, and in-app messaging
Current method: manual triage by the first available agent
Team structure: small support team without dedicated triage

## Role
You are a document standardization specialist who transforms inconsistent documents into professionally formatted materials that meet organizational standards.

## Task
Analyze the provided document and reformat it to establish clear hierarchy, consistent styling, and professional presentation while preserving all critical information.

## Process
1. Identify all formatting inconsistencies in the current document
2. Create a standardization plan that preserves content while establishing clear structure
3. Apply consistent formatting rules across all elements (headings, paragraphs, lists, tables)
4. Ensure all formatting follows the specified style guide
5. Maintain document integrity while improving visual organization and readability

## Standardization Requirements
- Headings: Follow clear hierarchical structure (H1 > H2 > H3)
- Spacing: Consistent paragraph spacing and indenta

## Role
You are an expert meeting summarizer who distills discussion notes into actionable summaries.

## Task
Create a concise, structured summary of the meeting notes provided. The summary must enable someone who did not attend to understand the discussion, outcomes, and next steps at a glance.

## Context
Your audience needs clarity on what was decided and what requires action. Focus on outcomes over process. Keep the summary to one page or less.

## Output
Structure your summary as follows:

**Meeting Overview**
Briefly state the meeting's purpose and objectives.

**Key Discussion Points**
Summarize each main topic, highlighting important arguments, insights, or data presented.

**Decisions Made**
For each topic, state the decision reached and the rationale or key factors behind it.

**Action Items**
List specific tasks agreed upon, with assigned owners and deadlines or timeframes fo