Skill: expectations-reset

Skill: expectations-reset

Purpose

Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.

When to Use

• Release date has moved by more than 2 weeks
• Significant scope has been cut
• A committed feature will not be delivered as promised

Framework: Expectations Reset

Step 1 — Acknowledge Before Explaining

Never lead with reasons. Lead with acknowledgment.

"I want to be transparent with you about a change to our delivery plan."

Step 2 — State What Changed

Be precise:

• What was committed → what is now the reality
• Use specific numbers and dates, not vague language

Step 3 — Explain Root Cause (Brief)

One or two sentences. No blame, no excuses.

"This was caused by [X]. We identified it on [date]."

Step 4 — New Commitment

State the new date or scope with confidence.

"We are now committing to [new date / new scope]. This is a reliable estimate, not a best case."

Step 5 — What We're Doing Differently

Show that the same problem won't happen again:

• Process change
• Risk mitigation
• Monitoring improvement

Step 6 — Invite Questions

Close by inviting dialogue, not just passive acceptance.

Output Format

1. Conversation script (verbal or written)
2. FAQ: anticipated questions with prepared answers
3. Suggested next command: /status-update or /steering-deck