Keep
Still accurate, required, and ready for the integrated destination.
Radisson integration / Content operations / 2022—2023
The hardest part wasn't moving 1,500+ files.
It was knowing what still belonged.
During a corporate integration, every piece of content carried a decision: keep it, revise it, retire it, or identify what was missing. The work connected platform administration with the business conversations needed to make those decisions safely.
RoleProject DirectorPlatform administration / content distribution / client relations
Brand workstreams06
Migration inventory1,500+Files
Launch06.152023
Required contentCompleteNo known gaps at launch
01
The real migration problem
A file can move successfully and still be wrong.
Corporate integration changed the context around the material. Some content remained valid. Some needed new language, ownership, or placement. Some had become obsolete. Other required information was missing entirely.
The migration therefore operated as a content-governance program: evaluate the information, communicate uncertainty, and distribute only what the combined organization could stand behind.
Revise
Still useful, but needed new ownership, language, metadata, or placement.
Retire
Duplicated, obsolete, or no longer aligned with the combined organization.
Missing
Required by the destination model but absent from the supplied source material.
02
Six brand workstreams / one release
Preserve each brand. Standardize the operating path.
Brand differences remained visible at the destination. Behind the experience, shared content rules, validation steps, and platform structures gave the migration one accountable route to launch.
01Radisson Blu
02Radisson
03Radisson RED
04Park Plaza
05Park Inn by Radisson
06Country Inn & Suites by Radisson
Shared operating modelValidate→Map→Distribute→Verify
LaunchJune 15, 2023
Reconstructed project view based on approved public-safe facts; not an internal client artifact.
03
Project direction at the decision boundary
The role sat between the platform and the business.
Technical progress depended on business clarity. Direction meant moving both sides together: administering the platform while making missing data, conflicts, and downstream effects visible to the people responsible for resolving them.
- 01
Platform administration
Directed how content entered, moved through, and appeared within the shared platform.
- 02
Content distribution
Mapped validated material to brand pages, resources, and the appropriate operating destinations.
- 03
Client relationship
Worked directly with business teams to clarify intent, ownership, priorities, and unresolved questions.
- 04
Gap communication
Surfaced missing data and content problems early enough for stakeholders to make launch decisions.
04
From source files to launch confidence
A migration designed as a feedback loop.
The work did not move in a single direction. Questions and gaps returned to business teams, decisions came back to the platform, and validation repeated until the required content was ready.
- 01
Inventory
Collect and classify 1,500+ source files
- 02
Validate
Confirm what remained accurate and required
- 03
Map
Assign ownership, brand, content type, and destination
- 04
Distribute
Move approved material through shared platform patterns
- 05
Report
Return gaps, conflicts, and missing inputs to business teams
- 06
Launch QA
Verify the required experience before release
05
The integrated destination
Visible result
Shared navigation. Brand-specific utility.
The final hub brings Radisson resources into the larger Choice platform while retaining a recognizable brand context. Users can move among brand pages, quick links, vendors, profitability resources, and learning content within one operating environment.
Launch outcome
The measure was not files moved. It was required content accounted for.
June 15, 2023
Six brand workstreams launched with no known missing required content.
- 1,500+ files inventoried through the migration
- Business questions surfaced instead of hidden
- Content distributed through shared platform patterns
- Final gaps communicated and resolved before launch
The screenshot and brand names are shown with permission. Migration diagrams are reconstructed from approved project facts. Private source files, internal business data, and stakeholder communications are intentionally excluded. Public acquisition context.