Purpose

The Obstacle Escalation feature automatically reassigns ownership of unresolved High and Critical obstacles when they are not updated or resolved within configurable timeframes.

Rather than relying on manual follow-up, Obstacle Escalation ensures that important issues continue moving through the organization until they receive attention and are resolved.

Ownership progresses through predefined organizational levels such as Team, Team of Teams (ToT), Portfolio, OLT, and ELT providing increasing visibility and accountability as time passes.

Business Value

Unresolved obstacles can delay strategic initiatives, reduce team accountability, and prevent organizations from meeting critical business objectives.

Obstacle Escalation helps organizations:

• Prevent High and Critical obstacles from becoming stagnant.
• Increase visibility as unresolved issues move through leadership levels.
• Automatically assign ownership without manual intervention.
• Reduce the risk of missed deadlines caused by unresolved blockers.
• Ensure executive awareness of long-running critical issues.

By automatically escalating ownership based on configurable business rules, organizations maintain momentum while ensuring accountability at every level.

Overview

Obstacle Escalation continuously monitors qualifying obstacles and evaluates them against administrator-defined escalation rules.

When an obstacle remains inactive or unresolved beyond the configured business-day thresholds, ownership is automatically reassigned to the next configured organizational level.

Administrators can configure:

• Escalation Levels
• Business-Day Thresholds
• Organizational Roles
• Organizational Teams
• Global Enable/Disable
• Individual Level Enable/Disable

When Obstacle Escalation Occurs

Obstacle Escalation is evaluated only when all of the following conditions are met:

✔ Impact = High

OR

✔ Impact = Critical

AND

✔ Status is not Completed

AND

✔ Status is not On Hold

If any condition is not met, the obstacle is excluded from escalation processing.

⚠️ Important: Low and Medium impact obstacles are never escalated.

What Counts as an Update?

An obstacle is considered updated whenever changes are saved to the record.

Examples include:

• Changing the Owner
• Updating the Status
• Modifying the Title
• Editing the Description
• Changing Dates
• Updating any editable field

If no changes are saved during the configured timeframe, the obstacle is considered inactive.

📝 Note: Saving any modification resets the "No Update" timer but does not reset the overall "Not Completed" timer.

(This distinction is one I'd add because it's not obvious from the current draft and will prevent confusion.)

Escalation Rules

Obstacle Escalation uses two independent timing rules.

Rule 1 – No Update

This rule monitors obstacle activity.

If an obstacle has not been updated within the configured number of business days, ownership automatically moves to the next escalation level.

Typical default:

2 Business Days

Purpose:

Prevent inactive obstacles from remaining with the same owner indefinitely.

Rule 2 – Not Completed

This rule monitors overall obstacle resolution.

Even if an obstacle is updated frequently, ownership continues to escalate until the obstacle is marked Completed.

Typical default:

5 Business Days

Purpose:

Prevent users from repeatedly updating an obstacle without resolving it.

💡 Tip: Think of the No Update Rule as checking for activity, while the Not Completed Rule checks for progress toward resolution.

Escalation Path

Obstacle ownership can progress through multiple organizational levels.

A typical path includes:

1. Team
2. Team of Teams (ToT)
3. Portfolio
4. OLT
5. ELT
6. Executive Owner

Each organization may configure its own escalation hierarchy.

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

The obstacle owner assigned during creation.

Typically:

• Scrum Master
• Card Creator
• Assigned User

First Escalation

If no updates occur within the configured timeframe:

Ownership moves to:

Product Owner

(or another configured role)

Additional Escalations

Ownership continues progressing through each configured level until:

• The obstacle is completed
• Escalation reaches the final configured level

Executive Escalation

Organizations may optionally configure a final executive safeguard.

Default Rule

If an obstacle remains unresolved after 10 Business Days, ownership automatically moves to the configured executive role.

Examples include:

• Executive Leadership Team
• Executive Product Owner
• CIO
• VP

This rule can be enabled or disabled independently.

Notifications

Whenever ownership changes:

• The newly assigned owner receives a notification.
• Duplicate notifications are automatically prevented when the same user occupies multiple escalation roles.
• Existing notification settings are used.
• No additional notification configuration is required.

Configuration

Administrators can configure:

Global Toggle

Enable or disable Obstacle Escalation for the organization.

Level Toggles

Enable or disable individual escalation levels.

Examples:

• Team
• ToT
• Portfolio
• OLT
• ELT

Business-Day Thresholds

Configure:

• No Update Days
• Not Completed Days

for each escalation level.

Role Assignment

Choose which role receives ownership at each escalation level.

Examples:

• Scrum Master
• Product Owner
• Team Lead
• Executive Owner

Team Assignment

Select which organizational team participates in each escalation level.

Expected Result

After Obstacle Escalation is enabled:

• High and Critical obstacles are monitored automatically.
• Ownership advances based on inactivity or lack of completion.
• Notifications are sent to newly assigned owners.
• Escalation continues until the obstacle is completed or reaches the final configured level.

Frequently Asked Questions

Does editing an obstacle stop escalation?

Editing an obstacle resets the No Update timer but does not prevent escalation triggered by the Not Completed rule.

Can organizations skip escalation levels?

Yes. Administrators can enable, disable, or configure each escalation level independently.

Can Executive Escalation be disabled?

Yes. The final executive escalation rule is configurable and may be enabled or disabled independently.

Summary

Obstacle Escalation helps organizations ensure that High and Critical blockers remain visible, accountable, and actively managed. By automatically advancing ownership through configurable organizational levels based on inactivity and completion thresholds, the feature reduces stalled work, strengthens accountability, and ensures that critical issues receive the appropriate level of attention before they impact strategic objectives.