NORTHSTAR TRAVEL GROUP · PRODUCT MANAGEMENT · 2025
Northstar
AI recommendations & content activation.
I led technical product requirements and expansion work for Northstar’s existing content-recommendation platform, connecting the reader experience with publishing rules and the teams responsible for operating it.
During a short contract, I translated cross-brand template differences, content-quality issues, and commercial serving requirements into adopted placement controls, integration requirements, and a Marketing Hub activation prototype.
Product Manager — AI, Content and Personalization · June 25–August 1, 2025
5 publishing properties reviewed
Template and placement audit across Northstar Meetings Group, Business Travel News, TravelPulse, Meetings & Conventions, and Successful Meetings.
3 adopted serving controls
Conditional placement, duplicate prevention and sponsored labeling.
4-system daily pipeline
Ektron → LeverageLabs → BigQuery → Template Builder.
The reader experience
Existing live MVP · Nine recommendations below a standard article. My mandate was to make expansion work across templates and teams.
From content ingestion to the page
The existing daily pipeline connected content and metadata with recommendation output and article rendering.
Ektron
Holds content and metadata
LeverageLabs
Processes content and supplies the recommendation table
BigQuery
Contains recommendation output
Template Builder
Renders the article recommendation module
My requirements and validation checkpoints
- Valid URLs
- Consistent content classification, including sponsored content
- Scoring completeness
- Ingestion confirmation and delays
- Eligible template and widget placement
Inconsistent article definitions and sponsored-content classification required content and data cleanup across Ektron and NetSuite.
Original working whiteboard
The product decisions behind serving
Placement requirements · Three adopted controls addressed template fit, repeated modules and commercial clarity.
- Conditional widget placement
- Place the module where it fits each eligible template rather than treating every article layout alike.
- Duplicate-module prevention
- Avoid repeated recommendation modules on the same page.
- Sponsored-content labeling
- Make the commercial nature of sponsored content clear to readers.
Container → Slot → Widget → Content
- Container
Defines width, eligible widget types and maximum slots.
- Slot
Combines horizontally or vertically, with padding between placements.
- Widget
Occupies a slot and accepts defined content types.
- Content
Supplies the eligible content for the selected widget type.
Other proposed formats included sponsored spotlights, newsletter calls to action, events, webinars and richer content stacks, with metadata, eligibility, timing and placement requirements.
Original proposed container schematic
Activation for business teams
Marketing Hub prototype · A structured path from promotion inputs to campaigns and content ingestion.
Business-user workflow
- Select brand and content type
- Add metadata and assets
- Set audience and duration
- Configure campaigns and placements
- Submit for ingestion
Proposed generation workflows retained human editing and approval before publication.
I translated the dependencies into SOPs and troubleshooting guidance covering metadata completeness, ingestion, classification, approvals and campaign timing.
Structured content input specification
Problem & objectives
Expand an existing recommendation experience across publishing templates and operating teams.
Expand an existing reader experience
Adaptive Content Serving (ACS) already supported nine recommendations below a standard article. Expansion required consistent placement across varied templates, dependable content metadata and commercial serving rules.
My product work connected those requirements with the engineering, data, editorial and business teams responsible for operating the platform during the June 25–August 1, 2025 contract.
Decisions & trade-offs
Make serving predictable through template fit, duplicate prevention and commercial clarity.
Three adopted controls
I audited templates across Northstar Meetings Group, Business Travel News, TravelPulse, Meetings & Conventions, and Successful Meetings. My recommendations for conditional widget placement, duplicate-module prevention, and clearer sponsored-content labeling were adopted.
Specify the next placements
I defined a proposed Container → Slot → Widget → Content contract: container width, eligible widget types and maximum slots; horizontal or vertical slot combinations with padding; and defined content types for each widget.
The expansion requirements also covered sponsored spotlights, newsletter calls to action, events, webinars and richer content stacks, including metadata, eligibility, timing, urgency and placement controls.
Experience & systems
Connect content inputs, recommendation data, and rendering requirements.
Define system responsibilities and handoffs
The existing daily pipeline ran from Ektron through LeverageLabs and BigQuery to Template Builder. Ektron held content and metadata; LeverageLabs processed content and supplied the recommendation table; BigQuery contained the output; internal developers connected that table to Template Builder to render the module.
I defined requirements across ingestion, scoring inputs, cohort assignment and eligible template placement, connecting Navigator audience inputs and recommendation tables with CMS rendering rules.
Validate the data that reaches the page
I coordinated checks for valid URLs, consistent content classification, scoring completeness and ingestion confirmation or delays. Inconsistent article definitions and sponsored-content classification required content and data cleanup across Ektron and NetSuite.
Structure business activation inputs
The proposed Marketing Hub input model covered headlines, descriptions, sources, tags, dates, URLs or assets, content and promotion types, intent and audience. Supporting field groups addressed campaigns, timeliness and content-specific requirements for video, webinars, events, newsletters and research.
Delivery & validation
Make the workflow operable and retain human review in the activation prototype.
Make the platform operable
I translated dependencies into SOPs, integration diagrams and troubleshooting guidance covering metadata completeness, ingestion, classification, approvals and campaign timing. Checks for missing content, incorrect types, delays and publishing failures helped teams identify the failing step and coordinate a correction.
Prototype the Marketing Hub workflow
I led requirements and prototype work for a Marketing/Activation Hub within Ektron workflows. The business-user flow moved from brand and content-type selection through metadata and assets, audience and duration, campaign placements and submission for ingestion.
The prototype showed promotion inventory and campaign configuration across web widgets, social and email. Proposed generation workflows retained human editing and approval before publication; persona guidance and related AI Planner use cases remained requirements and prototype planning.
Outcomes & learning
Deliver adopted experience controls and a defined path for expansion.
Adopted controls and an executable expansion path
Adopted recommendations for conditional placement, duplicate-module prevention, and sponsored-content labeling were the concrete product result. I also delivered technical requirements, validation criteria, expansion specifications, SOPs, integration diagrams and troubleshooting guidance, alongside the Marketing Hub activation prototype.
The existing MVP snapshot recorded 51,346 page serves and 288 clicks, providing a baseline view of reader engagement for expansion planning.
The lesson was to connect recommendation data with the rules and operating responsibilities that determine what readers actually see. Clear handoffs, placement controls and review steps made the expansion requirements actionable across teams.
