JUSTIN GRANT SWANSONContact
All projects

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

Scope · Engineering, Data and Analytics, Editorial, Marketing, CRM, Sales, and external providers.

Publishing scope

5 publishing properties reviewed

Template and placement audit across Northstar Meetings Group, Business Travel News, TravelPulse, Meetings & Conventions, and Successful Meetings.

Product outcome

3 adopted serving controls

Conditional placement, duplicate prevention and sponsored labeling.

Technical scope

4-system daily pipeline

Ektron → LeverageLabs → BigQuery → Template Builder.

01 / 04

The reader experience

Existing live MVP · Nine recommendations below a standard article. My mandate was to make expansion work across templates and teams.

Northstar recommendation module, 2025.
Fit to screen
Northstar Meetings Group article recommendation module with a three-column grid of related stories.

Northstar recommendation module, 2025.

Existing MVP snapshot · 51,346 recorded page serves · 288 clicks.

Templates audited · Northstar Meetings Group, Business Travel News, TravelPulse, Meetings & Conventions, Successful Meetings.

02 / 04

From content ingestion to the page

The existing daily pipeline connected content and metadata with recommendation output and article rendering.

  1. 01

    Ektron

    Holds content and metadata

    Content for processing

  2. 02

    LeverageLabs

    Processes content and supplies the recommendation table

    Recommendation output

  3. 03

    BigQuery

    Contains recommendation output

    Internal developers connect the table to templates

  4. 04

    Template Builder

    Renders the article recommendation module

    Reader experience

Existing daily pipeline · Reconstructed responsibility and handoff map.

My requirements and validation checkpoints

  • Valid URLs
  • Consistent content classification, including sponsored content
  • Scoring completeness
  • Ingestion confirmation and delays
  • Eligible template and widget placement

Navigator audience inputs, cohort/scoring dependencies and rendering rules informed the requirements.

Inconsistent article definitions and sponsored-content classification required content and data cleanup across Ektron and NetSuite.

Original working whiteboard
Working-session map of activation inputs, content and user scores, and recommendation placements. Photograph edited for presentation.
Fit to screen
Whiteboard photograph in several marker colors mapping activation inputs, content and user scores, an Activation Hub, and recommendation placements on a page layout.

Working-session map of activation inputs, content and user scores, and recommendation placements. Photograph edited for presentation.

03 / 04

The product decisions behind serving

Placement requirements · Three adopted controls addressed template fit, repeated modules and commercial clarity.

Conditional widget placement · Adopted
Place the module where it fits each eligible template rather than treating every article layout alike.
Duplicate-module prevention · Adopted
Avoid repeated recommendation modules on the same page.
Sponsored-content labeling · Adopted
Make the commercial nature of sponsored content clear to readers.

Container → Slot → Widget → Content

Proposed expansion specification

  1. Container

    Defines width, eligible widget types and maximum slots.

  2. Slot

    Combines horizontally or vertically, with padding between placements.

  3. Widget

    Occupies a slot and accepts defined content types.

  4. 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
Proposed container and placement model, 2025.
Fit to screen
Planning diagram showing article content with a three-slot side container and a six-slot container below the article.

Proposed container and placement model, 2025.

04 / 04

Activation for business teams

Marketing Hub prototype · A structured path from promotion inputs to campaigns and content ingestion.

Marketing Hub prototype · Promotion inventory, brands, markets, dates, status and campaign actions.
Fit to screen
Marketing Hub prototype promotions dashboard with content types, titles, brands, markets, dates, status and View Campaigns actions.

Marketing Hub prototype · Promotion inventory, brands, markets, dates, status and campaign actions.

Marketing Hub prototype · Web widget, social and email campaign configuration and status.
Fit to screen
Marketing Hub prototype campaign configuration showing Web Widget, Social and Email placements with campaign status and dates.

Marketing Hub prototype · Web widget, social and email campaign configuration and status.

Business-user workflow

  1. Select brand and content type
  2. Add metadata and assets
  3. Set audience and duration
  4. Configure campaigns and placements
  5. 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
Reconstructed table from MarketingHub_LLM_Input_Fields.xlsx, July 1, 2025. Field names retained and purposes condensed from the proposed input specification.
Fit to screen
Reconstructed Northstar input-specification table with eleven fields and their intended purposes, labeled as a proposed requirements model.

Reconstructed table from MarketingHub_LLM_Input_Fields.xlsx, July 1, 2025. Field names retained and purposes condensed from the proposed input specification.

1 / 4