# OPS02-BP05 - Mechanisms exist to request additions, changes, and exceptions

Best practice: OPS02-BP05
Pillar: Operational Excellence
Source: https://wellarchitected.cloudvisor.eu/docs/operational-excellence/ops02-bp05.html

## Implementation Guidance

"Mechanisms exist to request additions, changes, and exceptions" should be delivered as a standard operating capability with explicit scope, controls, and validation checkpoints. Embed it into day-to-day engineering and operations workflows.

For the question "How do you structure your organization to support your business outcomes?", define measurable outcomes, assign owners, and review execution regularly. Integrate this practice into delivery and operations processes so improvements persist as workloads and requirements evolve.

### Key Steps

1. **Define implementation scope and outcomes**:
   - Set explicit success criteria for "Mechanisms exist to request additions, changes, and exceptions"
   - Identify dependencies, prerequisites, and sequencing constraints
   - Assign accountable owners for execution and maintenance

2. **Implement with standards and validation**:
   - Use reusable templates and runbooks for consistent execution
   - Validate implementation with tests, checks, or controlled rollouts
   - Capture telemetry to confirm adoption and effectiveness

3. **Operate and iterate**:
   - Review outcomes against KPIs on a recurring schedule
   - Fix recurring failure modes and process bottlenecks
   - Update implementation guidance based on operational learning

## Risk / Impact

**Level of risk if not implemented**: Medium

**Impact**: Without this best practice, workloads typically accumulate inefficiencies and execution drift that increase failure probability over time. Problems often surface during traffic spikes, major releases, or dependency failures.

**Benefits of implementation**:
- More predictable operational and engineering outcomes
- Better alignment between architecture decisions and business goals
- Continuous improvement through measurable feedback loops

## AWS Services to Consider

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Organizations</h4>
    <p>Applies governance controls across accounts so operational and architectural standards stay consistent.</p>
  </div>
</div>

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Control Tower</h4>
    <p>Automates multi-account setup with guardrails, making standardized operations easier at scale.</p>
  </div>
</div>

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Service Catalog</h4>
    <p>Publishes approved patterns so teams deploy compliant infrastructure consistently.</p>
  </div>
</div>

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Systems Manager</h4>
    <p>Provides automation, inventory, and operational runbooks for day-2 management.</p>
  </div>
</div>

## Related Resources

<div class="related-resources">
  <h2>Related Resources</h2>
  <ul>
    <li><a href="https://docs.aws.amazon.com/wellarchitected/latest/framework/ops-02.html">OPS02: How do you structure your organization to support your business outcomes?</a></li>
    <li><a href="https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html">AWS Well-Architected Framework - Operational Excellence Pillar</a></li>
    <li><a href="https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/design-principles.html">Operational Excellence Design Principles</a></li>
  </ul>
</div>