Communicating the migration plan, internally.

Communicating the migration plan internally begins with reading the internal audience as four separate groups rather than as a single organisation. Each group has a different stake in the plan, a different need for information, and a different risk profile in the event that the plan reaches the external side before the buyer side intends it to. The communication strategy that works treats each group on its own terms.

A buyer side reading of the internal audience separates the executive sponsor, the steering committee, the platform team, and the broader engineering organisation. Each is communicated to on a different schedule, with a different level of detail, and with a different framing. Conflating the four into a single audience is the most common reason internal communication fails; the platform team needs operational detail the executive sponsor does not, and the executive sponsor needs commercial framing the platform team does not.

The companion notes on the credible migration plan as leverage, on migration timing relative to the renewal cycle, on the exit planning service, and on how leaving Red Hat changes the current contract sit on adjacent surfaces. This note covers the audience and the sequencing.1

The executive sponsor is the first internal audience and the audience that requires the least frequent communication. The sponsor needs to understand the commercial framing of the plan, the renewal arithmetic the plan is intended to produce, and the conditions under which the migration would actually execute. The sponsor does not need the workload classification detail; the sponsor does need to know that the workload classification exists, that the platform team has read it, and that the cost model has been drawn from it.

The communication discipline for the sponsor is to brief once at the start of the discovery window, to update once in the middle of the proposal window when the seller side response has been read, and to brief once at the close before the contract is countersigned. Three communications across the cycle is typically sufficient. The sponsor reads the plan as a commercial document; the briefing materials should read as commercial documents rather than as engineering documents.

The risk profile for the sponsor is leakage upward to the board or outward through a casual conversation with the seller side at an industry event. The mitigation is the framing. The sponsor is briefed on the plan as a contingent posture rather than as a committed direction, with the explicit understanding that the destination is held in posture and the execution is a separate decision the buyer side will reach downstream. A sponsor briefed in this framing is unlikely to commit to either side prematurely; a sponsor briefed in committed framing is at materially higher risk of premature commitment.2

The steering committee is the second internal audience and the audience that requires the most careful framing. The committee sits between the executive sponsor and the platform team, and is the audience most likely to include functional leaders whose preferences may diverge from the buyer side strategy. Procurement, finance, legal, security, compliance, and the platform team all have representatives on the committee; each has a different relationship to the plan and a different appetite for the migration.

The communication discipline for the committee is to brief monthly across the discovery window and the proposal window, with the framing that bridges the commercial and the operational. The committee should see the cost model, the workload classification at summary level, the destination shortlist, and the timeline. The committee should not see the seller side internal correspondence, the day to day platform team execution detail, or the negotiation tactics that are being held for the renewal table.

The risk profile for the committee is two sided. The first risk is that an individual committee member with a relationship on the seller side communicates the plan prematurely, either through a casual conversation or through a more deliberate signalling intended to soften the seller side response. The second risk is that the committee reaches a vote on the plan that commits the buyer side to a destination before the discovery phase has produced a defensible answer. The mitigation for both is to brief the committee on the plan as the work in progress rather than as the conclusion, and to reserve the destination commitment for a single point in the cycle after the proposal window has opened.3

The platform team is the third internal audience and the audience that lives inside the plan day to day. The platform team needs the workload classification, the destination shortlist, the timeline, the cost model, and the operational risk reading. The platform team is also the audience whose work the plan most directly depends on; the calendar that the plan announces externally is the calendar the platform team has to execute against.

The communication discipline for the platform team is continuous engagement across the discovery window, weekly status across the proposal window, and weekly to daily engagement during any actual execution phase. The team needs to understand that the plan is a real plan even if it may never execute; the team is doing real work in the discovery phase regardless of whether the migration ultimately runs. The framing is operational and detailed; the team is the audience that catches inconsistencies between the documented plan and the underlying engineering reality.

The risk profile for the platform team is the perception that the plan is theatre. Engineers asked to draft a migration calendar that may never be executed will, in the absence of clear framing, suspect that the work is a paper exercise and reduce the rigour accordingly. The mitigation is to be transparent about both possible outcomes. The plan is a real plan that may or may not execute; the discovery work is real engineering work that produces a defensible artefact in either outcome; the team is delivering the discovery whether or not the migration follows. A team briefed in this framing produces a stronger plan than a team briefed in either of the simpler framings.

The broader engineering organisation is the fourth internal audience and the audience that should be communicated to last. Application teams, security operations, network operations, and adjacent functions all have a stake in any operating system migration but do not need to know about the migration in detail until the destination is committed and the execution calendar is opened. Communicating earlier produces noise, speculation, and a meaningfully higher risk of external leakage through a routine vendor conversation.

The communication discipline for the broader engineering organisation is to communicate one time, in the proposal window if the destination is being held in posture for renewal leverage and the migration may not execute, or at signature if the destination is committed and the migration is going forward. The framing is operational at summary level; the broader organisation needs to understand what the change means for their workloads, what the timeline looks like for their participation, and who their named contact on the platform team is.

The risk profile for the broader organisation is the speculation that arises in the absence of communication. Engineers see procurement activity, sense the calendar, and form their own theories about the destination. The theories are not always correct and frequently leak to vendors through routine conversation. The mitigation is the timing. Communicate too early and the destination leaks; communicate too late and the organisation feels excluded; communicate in the right window and the organisation is prepared without the destination becoming public.4

The principal failure mode across observed engagements is leakage of the destination to the seller side before the proposal window opens. The leakage path is rarely deliberate; it is usually accidental, through a casual remark in a vendor meeting, through a job posting that names the alternative distribution, through a procurement request for proposal that reaches the seller side via a partner network, or through a steering committee member who mentions the consideration to a Red Hat representative at an industry event.

Each leakage path has a mitigation. The casual remark mitigation is the briefing framing on the sponsor and the steering committee; the framing that the plan is contingent and that the destination is not committed reduces the likelihood of premature confirmation. The job posting mitigation is the procurement liaison; postings that name the alternative distribution are routed through procurement and either reworded or held until the proposal window has opened. The request for proposal mitigation is the partner discipline; requests are issued under non disclosure where possible and through channels that minimise overlap with the seller side network.

The steering committee mitigation is the membership composition. Committee members with active seller side relationships should be briefed at a higher level of abstraction than committee members without those relationships, with the explicit understanding that the briefing reflects the commercial sensitivity rather than a judgment on the individual. The companion note on the credible plan covers the documentation discipline; the documentation reduces the risk that any individual leak can compromise the plan as a whole, because the plan has structural integrity that survives a single point of disclosure.5

The buyer side line that holds across every internal communication cycle is the line worth holding through every steering committee briefing and every platform team standup. The destination is real even when it is held in posture. The plan is the deliverable; the destination is the engineering question; the renewal is the outcome. Communicating the three to each audience in the right framing and at the right time is the discipline that produces a plan capable of doing its work at the renewal table. The contact form at the engagement section returns a desk response on the communication question typically inside the business day.6

Preparing a response? The practice keeps a one-page Red Hat audit response checklist — what to acknowledge, what to preserve, and what not to volunteer in the first fourteen days after the letter arrives.