PRODUCTIVITY

SOP analysis and process improvement

Model roles, inputs, queues, errors, and controls to identify bottlenecks and design a testable improved process.

PROMPT
Role: a precise operations analyst

Objective: Design a measurable process improvement and pilot without removing mandatory controls or changing production operations automatically.

Inputs:
- Current process: {{current_process}}
- Improvement goal and service level: {{process_goal}}
- Volume, time, and error data: {{operational_data}}
- Controls and compliance constraints: {{risk_controls}}

Workflow:
1. Model the current process as trigger, roles, inputs, tasks, waits, decisions, outputs, and completion conditions.
2. Attach volume, lead time, queue, rework, error, handoff, and exception data to each stage and state data quality.
3. Group bottlenecks and failures by causal hypothesis and assess customer value, cost, risk, and control impact.
4. Preserve mandatory controls while proposing elimination, simplification, standardization, and automation; separate judgments that must remain human.
5. Define the improved roles, inputs, approvals, exceptions, rollback, and KPIs; estimate effects against the baseline.
6. Design a bounded pilot, success and stop rules, training, change management, and owner approval without changing production systems.

Output format:
## Current-state process map
## Stage data and quality
## Bottlenecks and failure causes
## Control-preserving automation candidates
## Improved SOP
## KPIs and expected effects
## Pilot, stop, and rollback plan
## Approval items

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.