Meghan Race · Product Manager

From managing service leadersto managing digital products.

I came to product from the front line, leading a service team and cultivating member relationships. In every role I've held, I've been the person who learns the technical systems and translates between the people building them, the people supporting them, and the customers using them. That's the bridge I bring to product.

4 yrsIn product: 2 as stakeholder, 2 as PM
$200M+Member Portal: booking, trips, Clubhouse
~25KMember trips supported a year
6Certifications in 18 months
The story

I forged
this path.

Portrait of Meghan Race smiling, wearing a black-and-white patterned blazer over a black top, photographed against a neutral gray studio background.
Meghan Race · Denver, CO

Twenty years in hospitality shaped how I think about product. Martha's Vineyard, Vail, then Exclusive Resorts since 2012: long enough to build a real instinct for what customers need, what they'll forgive, and what they'll never forget. I bring that to every prioritization decision I make.

At every job I've ever had, I've been the person who digs into how the systems actually work, and then becomes the one training everyone else on them. That instinct is what changed my trajectory.

In April 2022 I became the key Member Services stakeholder for our new Member Portal. The job description was "bring the member perspective." I went well past that. I trained the whole MS team on the new product. I created the feedback Slack channel still used today. Before I ever joined Engineering, I was already in Jira writing stories and troubleshooting inside our Auth0 authentication platform.

Exclusive Resorts created a Product role on the Engineering team specifically for me, because I'd already forged that path through the work and through the relationships I built with PMs, UX, developers, and the Head of Engineering. Twelve months later, I went from Junior PM to Product Manager and full owner of the Member Portal, a product I had worked on for four years. I now own the roadmap, the decisions, and the day-to-day. Along the way I earned six certifications in eighteen months, including AWS Certified Practitioner and Salesforce Platform Associate.

What I bring to product is unusual: I deeply understand our customers because I took their calls long before I wrote my first ticket, and I deeply understand our complex technical systems because I refused to treat them as a black box. That combination is what I optimize for.

What I do now

What owning it means

A members-only luxury travel club. I own the Member Portal: the $200M+ digital surface our customers use to plan and book the trips they fly across the world to take.

See the case studies →
  • 1

    I own the roadmap end-to-end.

    Discovery, prioritization, sprint planning, release. Booking, trip planning, customer engagement workflows: the whole portal. I held the mobile app too, for the first year of the role.

  • 2

    I challenge solutions until I understand the problem.

    When an architect comes with a recommendation, I dig until I'm sure we're solving the right problem, not just the first problem someone named. I'd rather slow a meeting by ten minutes than ship a fix that solves the wrong thing.

  • 3

    I do my own technical investigation.

    DevTools, GraphQL traces, API analysis, Auth0 spelunking, AI-assisted repo triage with Claude Code. I triage independently before I escalate: engineering's time is for the part that's actually theirs.

  • 4

    I ship from a place of customer evidence.

    Taking member calls is how I know exactly which moments are sacred. Pre-arrival friction. Post-trip follow-through. Booking flow under a lottery release. I prioritize there.

  • 5

    I move the cadence forward.

    When I took ownership, features were stalling across multiple sprints. We now ship bi-weekly major releases with continuous hotfixes, with a real release-notes practice tuned for both internal and exec audiences.

The differentiator

I use Claude the way most PMs wish they used Jira.

Not as an autocomplete. As a teammate that's read every reference doc, knows our architecture and team directory by name, drafts tickets in our voice, summarizes my Zoom transcripts to Confluence every afternoon at 5:36, and analyzes the weekly member survey before I'm done with my first coffee on Monday.

Resources I've made

Teaching is part of the practice.

When I work out how to do something well with tools that change month to month, I write it up. Four guides now: two that assume no technical background at all, two for PMs who want the full setup. Each one is a thing I wish someone had handed me.

  1. Claude 101A plain-English handbook for anyone: how the model actually works, what makes a prompt good, and how Projects, Skills, and Connectors fit together. No technical background required.Handbook · start hereRead Claude 101 →
  2. The Claude PlaybookThe answer to “okay, but what do I do with it?” Automate a recurring chore, pull one report from many tools, and produce a standardized deliverable every time.Recipes · companionRead the Playbook →
  3. Claude Code for PMsA complete setup-and-workflow guide for non-engineering PMs. Folder structure, CLAUDE.md, context files, MCP connectors, daily workflows, and a five-week onboarding path.Training guide · 18,700 wordsRead the guide →

All four guides →

Experience

From Member Services
to owning the platform.

Four roles at Exclusive Resorts, each one a closer step to product. I joined as a Membership Account Manager in 2012, was promoted into regional leadership, then into Member Portal stakeholder, then into Engineering as a Product Manager. Promoted again twelve months later.

  1. Product Manager, EngineeringExclusive Resorts · Denver, COFeb 2025 – Present
  2. Member Services Stakeholder, Member PortalExclusive Resorts · the trajectory shiftApr 2022 – Jan 2025
  3. Regional Manager, Member Services, NortheastExclusive ResortsOct 2015 – Jan 2025
  4. Membership Account ManagerExclusive ResortsSep 2012 – Sep 2015
  5. Vail Resorts · hospitalityVail & Beaver Creek, CO2007 – 2012
Let's connect

I’d rather have the conversation than the email thread.

The transition wasn't a side door. It was years of being the person who learned the system before anyone asked me to, and then the relationships, the credentials, and the work to back it up.

If you're hiring, collaborating, or just want to talk product, reach out.

Let's connect