Continuous Improvement

Overview

This skill defines a systematic approach to identifying, implementing, and measuring small incremental improvements. Big improvements come from many small continuous changes, not occasional major overhauls.

When to Use

• After completing any task (retrospective improvement identification)
• When reviewing processes or systems regularly
• When feedback suggests improvements needed
• When metrics show declining or suboptimal performance
• Don't use when: System is fundamentally broken and needs redesign (use incident-response instead)

Core Procedures

Step 1: Identify Improvement Opportunities

Ask these questions:

• What took longer than expected?
• What caused frustration or rework?
• What could be automated that's currently manual?
• What documentation would have helped?
• What patterns repeat frequently?
• What mistakes happen regularly?

Step 2: Assess and Prioritize

Rate each improvement by:

• Impact: How much does it improve the situation? (1-5)
• Effort: How hard is it to implement? (1-5)
• Reach: How many people/processes benefit? (1-5)

Priority = Impact × Reach / Effort - Focus on high-impact, low-effort changes first.

Step 3: Implement Small Changes

• Make ONE change at a time (isolate the effect)
• Document the change and what it aims to improve
• Implement the minimum viable improvement
• Don't over-engineer improvements

Step 4: Measure and Validate

After implementing:

• Is the improvement working? (yes/no)
• What metric shows improvement?
• Is it sustainable or requiring extra effort?
• Should it be made permanent, adjusted, or reverted?

Step 5: Share Knowledge

• Document successful improvements using knowledge-capture
• Share with relevant teams who might benefit
• Add proven improvements to standard procedures where applicable
• Archive rejected improvements with reasoning

Quality Checklist

• Improvement identified with clear problem statement
• Impact and effort assessed objectively
• Change implemented and tested
• Improvement validated with measurable data
• Knowledge shared with relevant teams
• Successful changes incorporated into procedures

Error Handling

• Error: Improvement causes unexpected issues Response: Revert immediately, document what went wrong, reassess approach
• Error: Improvement requires more effort than it saves Response: Abandon the improvement, note cost/benefit for future reference
• Error: Resistance to improvement from other agents Response: Listen to concerns, address valid objections, escalate only if beneficial improvement is being rejected without reason

Cross-Team Integration

Related Skills: knowledge-capture, feedback-integration, testing-strategy, risk-assessment Used By: ALL agents as ongoing practice, especially Refiners, Optimizers, Maintainers, Project Managers