EOL Stakeholder Communication Sequence (eol-stakeholder-sequence)

Skill Overview

Plan the order of stakeholder communications and the content of each conversation for a product end-of-life (EOL) decision—legal first, then finance, followed by revenue and customer teams—so you uncover landmines before the announcement goes out, not afterward.

Applicable Scenarios

1. The EOL decision has been made, but you are unsure whom to speak with first or what to bring to each conversation—the skill generates a complete, ordered itinerary based on the principle of “speak first with the people who can kill the plan”: legal → finance → sales → marketing → customer success → engineering → support.
2. The last product shutdown blew up because the sales team made unauthorized promises at customer sites—this time, proactively investigate commitments that were never documented in contracts or tickets before announcing, so customers do not come back demanding answers after the announcement.
3. Time is tight, but dependencies cannot be compromised—the skill clearly identifies which communications must be strictly sequential (for example, legal conclusions must come before everything else) and which can safely run in parallel, compressing a ten-stop itinerary into three weeks.

Core Functions

1. Tiered communication sequences: Recommends a lightweight (3–4 stops), standard (7–8 stops), or heavyweight (10+ stops, including executives, channel partners, and regulators) itinerary based on the blast radius. The standard tier is the default—do not spend the team’s credibility on a ten-stop roadshow for a single feature retirement.
2. Five-field conversation design for every stop: For each stop, specify the timing, why it matters (4–8 words), what you need to obtain from the other party (specific questions, not “get their feedback”), what you owe them (context, lead time, commitments), and red-flag signals to watch for. Also require a decision or deliverable from each stop—without an output, a stop is merely a briefing.
3. Pitfall warnings and operating principles: Includes five common mistakes—announcing first and asking questions later, putting legal last, treating sales as an information recipient, skipping the most difficult customers, and only asking without giving—and provides symptoms, consequences, and corrective actions for each.

Frequently Asked Questions

Who should we communicate with first before retiring a product?

Speak first with the people who can “kill the plan,” then with those who must execute it. The standard order is: legal (contractual and regulatory exposure) → finance (revenue and forecasting impact) → sales → marketing → customer success → the most difficult customers → engineering → support → affected users. Reverse the order, and you may already have announced the plan to forty people only to have it overturned by a single contract clause.

Why include the most difficult customers in the communication sequence?

Customers with the most tickets and who apply the most pressure in business reviews are precisely the customers using the product most deeply and critically. They will find integrations you forgot, contract clauses no one read closely, and workflows that alternatives cannot cover. You can learn about these landmines during a call scheduled now, or wait six months for them to announce them for you on a public forum.

How is this skill different from a Stakeholder Map?

A Stakeholder Map classifies groups by power and interest. It is a static snapshot suited to answering “Who matters?” This skill is an ordered itinerary answering “Whom do we see first, what do we discuss, what should we watch for, and what must we produce?” It is not a broadcast plan—customer announcements are a separate deliverable—and it is not equivalent to a RACI: decision authority and conversation order are two different questions. It is also specifically for product retirement; use a standard stakeholder-mapping method for stakeholder analysis in general projects.