workflow-optimization

---
name: workflow-optimization
description: Analyze, optimize, and automate workflows using Lean, Six Sigma, and intelligent automation for maximum productivity and efficiency. Adapted from msitarzewski/agency-agents.
---

## Triggers

- workflow optimization
- process improvement
- automation opportunity
- workflow analysis
- bottleneck resolution
- process mapping
- SOP creation
- workflow automation
- efficiency improvement
- Lean Six Sigma
- process redesign
- task automation
- workflow streamlining
- operational efficiency
- process documentation

## Instructions

### Current State Analysis and Documentation
- Map existing workflows with detailed process documentation using `shell_execute`
- Identify bottlenecks, pain points, and inefficiencies through data analysis
- Measure baseline performance metrics: time, cost, quality, satisfaction
- Analyze root causes of process problems using systematic investigation

### Optimization Design and Future State Planning
- Apply Lean, Six Sigma, and automation principles to redesign processes
- Design optimized workflows with clear value stream mapping
- Identify automation opportunities and technology integration points
- Create standard operating procedures with clear roles and responsibilities
- Use `knowledge_write` to store process maps and optimization patterns

### Implementation Planning and Change Management
- Develop phased implementation roadmap with quick wins and strategic initiatives
- Create change management strategy with training and communication plans
- Plan pilot programs with feedback collection and iterative improvement
- Establish success metrics and monitoring systems

### Automation Implementation and Monitoring
- Implement workflow automation using appropriate tools and platforms
- Monitor performance against established KPIs with automated reporting
- Collect user feedback and optimize processes based on real-world usage
- Scale successful optimizations across similar processes and departments
- Use `web_search` for automation tool research and best practices

### Optimization Standards
- Always measure current state performance before implementing changes
- Use statistical analysis to validate improvement effectiveness
- Consider user feedback and satisfaction in all optimization decisions
- Document process changes with clear before/after comparisons
- Prioritize user experience and reduce cognitive load
- Balance automation efficiency with human judgment and creativity

### Opportunity Identification Framework
- Error rate > 5%: Quality improvement needed
- Bottleneck severity >= 4/5: Process redesign required
- Automation potential > 70%: Implement workflow automation
- User satisfaction < 5/10: Redesign user interface and experience

## Deliverables

### Workflow Optimization Report Template

```markdown
# [Process Name] Workflow Optimization Report

## Optimization Impact Summary
**Cycle Time Improvement**: [X% reduction with quantified time savings]
**Cost Savings**: [Annual cost reduction with ROI calculation]
**Quality Enhancement**: [Error rate reduction and quality metrics improvement]
**Employee Satisfaction**: [User satisfaction improvement and adoption metrics]

## Current State Analysis
**Process Mapping**: [Detailed workflow with bottleneck identification]
**Performance Metrics**: [Baseline measurements for time, cost, quality, satisfaction]
**Pain Point Analysis**: [Root cause analysis of inefficiencies]
**Automation Assessment**: [Tasks suitable for automation with potential impact]

## Optimized Future State
**Redesigned Workflow**: [Streamlined process with automation integration]
**Performance Projections**: [Expected improvements with confidence intervals]
**Technology Integration**: [Automation tools and system integration requirements]
**Resource Requirements**: [Staffing, training, and technology needs]

## Implementation Roadmap
**Phase 1 - Quick Wins (4 weeks)**: [Minimal effort improvements]
**Phase 2 - Process Optimization (12 weeks)**: [Systematic improvements]
**Phase 3 - Strategic Automation (26 weeks)**: [Technology implementation]
**Success Metrics**: [KPIs and monitoring systems for each phase]

## Business Case and ROI
**Investment Required**: [Implementation costs with breakdown]
**Expected Returns**: [Quantified benefits with 3-year projection]
**Payback Period**: [Break-even analysis with sensitivity scenarios]
**Risk Assessment**: [Implementation risks with mitigation strategies]

---
**Implementation Priority**: [High/Medium/Low with business justification]
**Success Probability**: [High/Medium/Low based on complexity and readiness]
```

## Success Metrics

- 40% average improvement in process completion time across optimized workflows
- 60% of routine tasks automated with reliable performance and error handling
- 75% reduction in process-related errors through systematic improvement
- 90% successful adoption rate for optimized processes within 6 months
- 30% improvement in employee satisfaction scores for optimized workflows

## Verify

- The deliverable for this phase exists as a concrete artifact (doc, ticket, board, repo) and its location is shared, not described
- Each commitment has an owner name, a due date, and a definition-of-done that someone other than the author could check
- Risks are listed with likelihood/impact and a named mitigation, not as a generic 'risks: TBD' bullet
- Dependencies on other teams/vendors/agents are explicit; an ack from each dependency is recorded or marked 'pending'
- Success criteria for the next phase are numeric or otherwise objectively testable
- A rollback / kill-switch / 'we will stop if X' criterion is written down before work starts