How can we help you?

Purpose

The purpose of Obstacle Escalation is to ensure that high-impact obstacles never get stuck. When critical blockers are not actively addressed, the system automatically escalates ownership through predefined organizational level bringing in the right people at the right time, up to executive leadership if needed.

This feature replaces the previous obstacle escalation rule, which did not function reliably.

Business Case

In fast-moving organizations, unresolved obstacles can quietly stall progress, delay outcomes, and reduce accountability. Manual follow-ups and informal escalations often happen too late or not at all.

Obstacle Escalation solves this by:

• Automatically advancing ownership when progress stalls

• Increasing visibility at higher organizational levels

• Preventing obstacles from being “updated” without real resolution

• Ensuring executive awareness of unresolved critical issues

The result: fewer stalled initiatives, clearer accountability, and faster resolution of high-impact blockers.

Overview

Obstacle Escalation is a configurable, rule-based system that monitors high-impact obstacles and escalates ownership when they are not updated or resolved within defined timeframes.

Escalation occurs progressively across organizational levels (for example: Team → Portfolio → OLT → ELT), ensuring that unresolved obstacles gain visibility and attention as time passes.

All escalation behavior is configurable and can be enabled or disabled at each level.

When Obstacle Escalation Applies

Escalation rules run only when all of the following conditions are true:

• Obstacle impact level is High or Critical

• Obstacle status is not Completed

• Obstacle status is not On Hold

If any of these conditions are not met, escalation does not occur.

What Counts as an Update?

An obstacle is considered updated when any change is saved on the obstacle, including:

• Changing the owner

• Updating dates

• Modifying status

• Editing the title, description, or any field

If no changes are saved, the obstacle is considered not updated.

Escalation Model (How Ownership Moves)

Obstacles can escalate through up to seven ownership levels, ultimately reaching executive leadership if unresolved.

A typical escalation path may include:

1. Team level

2. Team of Teams (ToT) or Portfolio level (configurable)

3. Portfolio or OLT level

4. OLT level

5. ELT level

6. Final executive escalation

Escalation paths are configurable per organization and may vary by setup.

Team-Level Escalation

Initial Owner (Owner 1)

• Set at creation

• Typically the Scrum Master or the user who created the obstacle

• Ownership at creation is user-defined

Rule: No Update Within N Business Days

• Condition: Obstacle is not updated within N business days (default = 2)

• Action: Ownership automatically moves to Owner 2

• Default Role: Product Owner of the same team

Escalation to the Next Level

Rule: Continued Inactivity

• Condition: Obstacle (now owned by Owner 2) is not updated within the configured time window (default = 2–3 business days)

• Action: Ownership escalates to the next configured level

Configuration options include:

• Next level selection (Team of Teams or Portfolio)

• Role at that level (Scrum Master, Product Owner, etc.)

Anti-Gaming Rule: No Resolution Within M Business Days

Sometimes an obstacle gets “touched” but not truly resolved. This rule prevents that.

Rule: Not Completed Within M Business Days

• Condition: Obstacle is not marked Completed within M business days from creation (default = 5)

• Action: Ownership escalates to the next level regardless of interim updates

This rule is optional and configurable per level.

Higher-Level Escalations (ToT → Portfolio → OLT → ELT)

At each escalation level, the same two rules can apply:

1. No Update Rule (default = 3 business days)

2. Not Completed Rule (default = 5 business days)

For each level, administrators can configure:

• Level type (specific team or level-based)

• Team selection (for OLT / ELT)

• Role selection (Scrum Master, Product Owner, etc.)

Ownership is reassigned automatically based on these settings.

Final Safeguard: 10-Day Executive Escalation

10-Day Escalation Rule

• Condition: Obstacle is not completed within 10 business days of creation

• Action: Ownership automatically escalates to a configured executive-level role (for example, ELT Product Owner)

This rule ensures executive visibility and can be enabled or disabled independently.

Notifications

Obstacle Escalation relies on existing notification behavior:

• When ownership changes, the new owner receives a notification

• Duplicate notifications are prevented if the same user holds multiple roles

No additional notification setup is required for v1.

Configuration & Controls

Global Toggle

• Enables or disables Obstacle Escalation entirely

Level Toggles

• Escalation rules can be enabled or disabled per level (Team, ToT, Portfolio, OLT, ELT)

Time Thresholds

• All business-day thresholds are configurable

Summary

Obstacle Escalation ensures that critical blockers never fade into the background. By automatically advancing ownership based on time and progress, the system keeps obstacles visible, accountable, and moving so teams can focus on delivery instead of chasing blockers.