Potential Diver · Start Diving
PADI Digital Overhaul · User Flow Diagram

Start Diving · Potential Diver (Non-Logged-In)the Nov '26 flow runs live — later work is parked beneath

Each sub-segment shows two lanes. The top lane is the live Release 1 (Nov '26) flow — connected left-to-right to a booked course. The bottom lane parks the later touchpoints beneath the stage they'll plug into. Every stage bullet is backed by GA4 funnel data or Border UX research.

SegmentPotential Diver
Auth stateNon-Logged-In
Sub-segmentsUnaware Adventurer · Reluctant Explorer · Fear-Driven First-Timer · Family
ConversionBook a course (DSD → PADI Scuba Diver → Open Water Diver)

How to read the two lanes

Live flow · Nov '26 Release 1. Connected, sequential touchpoints that ship at go-live and form the booked-course path.
Parked · later phase. Sits beneath the stage it will attach to — deferred or dependent on deeper integration / CDP / mobile.

Release 1 is web-only: padi.com, the design system, the MyPADI shell, and SEO/AEO + CRO groundwork.

Two lenses beneath every flow — evidence-backed

Business & CoverageWhy each step matters for conversion + coverage before launch, tied to GA4 funnel data.
Rationale · Q · ARationale, open questions, assumptions — grounded in Border UX research signals.
Sub-segment 1

The Unaware Adventurer

A travel-minded explorer who doesn't yet know scuba is within reach — including experience-seekers chasing a specific moment ("dive the Maldives", "see a manta ray", "see a shipwreck"). Discovers diving through lifestyle, travel, and experience content rather than searching for it. Needs inspiration, not reassurance.

⊳ Conversion: book a first experience — DSD try-out or Open Water, by the diver’s choice
Flow · scroll right →
Live · Nov '26
01Awareness
AEO / SEO structured-data foundation makes PADI surfaceable to AI & search
PADI blog + social (Instagram / YouTube / TikTok) as discovery entry points
Experience-led search — "dive the Maldives", "see a manta ray", "see a shipwreck"
Lands on padi.com from an AI-referred or organic link
02First Contact
Travel / Experience-led landing page, not a course list
DSD framed as "try it on holiday — no experience needed"
03Consideration
Browses experiences by type via the new experience taxonomy
Sees the DSD → Open Water Diver ladder — a try-out that counts
04Evaluation
Opens DSD or Open Water detail — inclusions, duration, all-inclusive price (alternate tracks, by choice)
Finds a PADI Dive Resort / Center at the destination via the locator
05Identity
Saves a destination, or creates an account via AWS Cognito SSOMyPADI shell
06Conversion
Books DSD or Open Water — guided booking request routed to the Dive Resort (lead captured)
Confirmation (SFMC) → MyPADI with a next step toward Open Water
Parked · Later
parks @ Awareness
Lifestyle-influencer & partner-brand campaigns (Viator / Expedia) surfacing dive experiences
Full AI-answer presence across assistants
parks @ Consideration
Destination recommendations tuned to browsing (CDP)
parks @ Evaluation
Live availability around trip dates via Dive Shop 360
parks @ Identity
CDP identity resolution + nurture for non-converters
parks @ Conversion
End-to-end checkout on padi.com (cart → pay → confirmed booking) via CommerceTools — no "contact the shop" step
BizBusiness & Coverage
Reach
~20M+ top-of-funnel visitors today convert poorly from awareness to bookingGA4; travel-led discovery reaches an audience PADI doesn't currently compete for.
Channel
Web carries course-heavy conversions at a 25–27 day lead time; mobile is only 10–11% of volumeGA4 — Release 1 is web-first by design.
Conversion
60% of Dive Centers lack eCommerceGA4, so guided DSD booking + handoff (not universal direct checkout) is the realistic go-live.
RatRationale · Questions · Assumptions
Rationale
This sub-segment needs inspiration over reassurance — lead with place and experience, defer product detail.
Open question
Is partner-platform surfacing (Viator/Expedia) in our scope, or owned by the PADI Travel team outside Release 1?
Assumption
Experience taxonomy + DSD pages ship in R1; destination personalisation waits on the CDP.
Sub-segment 2

The Reluctant Explorer

Curious but hesitant — worried about safety and unclear on cost. Researches before committing. The job is to remove doubt with transparent pricing, real diver stories, and a confident low-commitment first step.

⊳ Conversion: book Open Water — or a DSD try-out as an alternate entry track; PADI Scuba Diver a half-step option
Flow · scroll right →
Live · Nov '26
01Awareness
AEO / SEO structured data surfaces PADI for "how do I learn to dive / is it safe?"
PADI blog + social (Instagram / YouTube / TikTok) as discovery entry points
Arrives on padi.com via organic / AI-referred link
02First Contact
Experience discovery page (new design system); geo-IP shows local context
PADI Scuba Diver visible as a low-barrier, half-commitment entry
03Reassurance
"What happens underwater" confidence / safety content layer
Transparent all-inclusive pricing (eLearning + certification)
04Evaluation
Open Water Diver course detail — eLearning + confined + open-water
Weighs DSD (try-out) vs Open Water as alternate tracks — PADI Scuba Diver a half-step option
Finds a nearby Dive Center via the locator (+ Google Maps)
05Identity
Saves a course shortlist (light-touch, no wall)
Creates account via AWS Cognito SSOMyPADI shell
06Conversion
Books Open Water (or PADI Scuba Diver half-step); guided booking request routed to the shop (lead captured)
Confirmation (SFMC) + eLearning access → MyPADI
Parked · Later
parks @ Awareness
Community presence (r/scuba) + full AI-answer optimisation
parks @ Reassurance
Real-time guided-discovery agent for specific worries
parks @ Evaluation
Instructor profiles (face + bio) — from the Pro system, via Salesforce CRM
Real-time class availability via Dive Shop 360
parks @ Identity
CDP nurture for non-converters (dynamic triggers)
parks @ Conversion
End-to-end checkout on padi.com (cart → pay → confirmed booking) via CommerceTools — no "contact the shop" step
BizBusiness & Coverage
Reassurance
73% cite unclear pricing as a barrierBorder UX — transparent all-inclusive pricing directly unblocks the biggest stall.
Evaluation
35% want to see the instructor before bookingBorder UX; the DSD → PADI Scuba Diver → OWD ladder lets them buy at their confidence level.
Conversion
Lead leakage between padi.com and shops is a known funnel lossGA4; guided booking keeps the lead in-system while attributing to the shop.
RatRationale · Questions · Assumptions
Rationale
Static content resolves cost doubt now; the parked conversational agent handles fear in real time later.
Open question
Where does identity capture happen — pre-booking save, enquiry, or booking? Today it's captured after booking — too late to nurture abandonersBorder UX.
Assumption
Course pages, pricing, locator, MyPADI shell in R1; instructor profiles, live availability, CDP nurture parked.
Sub-segment 3

The Fear-Driven First-Timer · High-Barrier Market

A potential diver in markets (e.g. parts of Asia) where safety — not cost or access — is the primary barrier, reached through conversational, in-language channels. A real-time, localised response at the moment of anxiety unlocks the first step.

⊳ Conversion: book a low-commitment DSD or PADI Scuba Diver, in-language
Flow · scroll right →
Live · Nov '26
01Awareness
AEO foundation surfaces PADI for "is scuba safe?" queries
PADI blog + social (Instagram / YouTube / TikTok) as discovery entry points
Reaches a localised padi.com (translation via Crowdin Enterprise, hreflang)
02First Contact
Local-language safety-reassurance content surfaced first
03Reassurance
Fear-reduction content: what happens underwater, how close the boat stays
04Evaluation
Reviews a low-commitment DSD / PADI Scuba Diver first step
Localised pricing & currency; finds a local Dive Center via locator
05Identity
Creates an account via AWS Cognito SSOMyPADI shell
06Conversion
Books the DSD / half-step; guided booking request routed to the local Dive Center (lead captured)
Localised confirmation (SFMC) with pre-dive reassurance → MyPADI
Parked · Later
parks @ Awareness
Full in-language AI presence on WeChat / Line / TikTok
parks @ Reassurance
Guided agent in Mandarin / Japanese / Thai / Korean
Instructor face + bio before committing
parks @ Evaluation
Booking conversation over WhatsApp / Line cart deep-link
parks @ Identity
Localised CDP nurture in local language
BizBusiness & Coverage
Awareness → First contact
In several Asian markets safety is the #1 barrier to consideration — ahead of cost and accessBorder UX; a localised, reassurance-first entry is the unlock for a large untapped pool.
Reassurance
Static content can't fully address fearBorder UX; real-time, in-language answers are the highest-leverage future investment for this market.
Conversion
A low-commitment first step (DSD / PADI Scuba Diver) maximises the chance of a confident "yes," then ladders to OWD.
RatRationale · Questions · Assumptions
Rationale
Fear needs conversation; front-load reassurance and keep commitment low until trust is built.
Open question
Does the guided agent auto-surface in high-barrier markets, or stay user-initiated? Is the WhatsApp/Line link shop- or diver-facing?
Assumption
Localised content + pricing + locator ship in R1 (subject to Crowdin readiness); agent + localised CDP nurture parked.
Sub-segment 4

The Family Dive Discovery

A parent planning a first dive experience for themselves and a child. High-value, with age-eligibility questions and an on-the-spot, linked-booking dynamic. Research found this journey is currently broken at both the discovery and data-model level — so much of the family-specific path is parked.

⊳ Conversion: book linked parent + child experience (Bubblemaker · Seal Team · Junior Open Water · family DSD)
Flow · scroll right →
Live · Nov '26
01Awareness
AEO / SEO foundation (general) makes PADI surfaceable
PADI blog + social (Instagram / YouTube / TikTok) as discovery entry points
"Can my 10-year-old dive with me?" → lands on padi.com
02First Contact
General experience-led landing page
03Consideration
Browses the general experience taxonomy
04Evaluation
Opens a DSD / course detail page; finds a Dive Center via locator
05Identity
Parent creates account via AWS Cognito SSOMyPADI shell (parent profile)
06Conversion
Books a single (parent) DSD; guided booking + handoff; confirmation (SFMC)
Parked · Later
parks @ Awareness
AEO for Seal Team · Bubblemaker · Junior Open Water family queries
parks @ First Contact
Dedicated Family Discovery Path (T9) — forks from the individual flow
parks @ Consideration
Age-filtered family experience discovery (eligibility by programme)
parks @ Evaluation
Family-programme filter in shop directory + linked availability
parks @ Identity
Family profile model: child linked to parent (not overwriting)
Minor-consent flows — HIPAA (US) / GDPR (EU)
parks @ Conversion
Linked parent + child booking in one transaction
Post-dive: parent sees child's first achievement → next step
BizBusiness & Coverage
Opportunity
High-value segment, but currently broken at discovery and the data modelBorder UX — parents piece eligibility together across multiple pages with no family path.
Programmes
Family spans Bubblemaker, Seal Team, Junior Open Water — age-gated eligibility that must be filterable, not scattered.
Conversion
Linked parent + child booking isn't possible todayBorder UX; until the data model is fixed, R1 can only convert the parent as an individual.
RatRationale · Questions · Assumptions
Rationale
The family path forks from the individual flow at experience selection via age filters — so most family-specific work is parked behind the core flow.
Open question
Critical blocker: child email currently overwrites the parent recordBorder UX. The family profile architecture + minor consent must be resolved before family build. (Owner: Product, Legal, CRM.)
Assumption
Only the general flow (landing, locator, parent account, guided booking) is in R1; the Family Discovery Path (T9, P1), linked bookings, and family data model park to a later phase.
PADI Digital Overhaul · User Flow Diagram

Start Diving · Potential Diver (Logged-In · MYPADI)identity is the start line, not the finish — the Nov '26 flow runs live, the rest is parked

The companion to the non-logged-in flow. Here the diver already has a MyPADI account, so we segment by where they stalled after signing in, not by how they arrived. Same two lanes: the top lane is the live Release 1 (Nov '26) flow; the bottom lane parks the later touchpoints. Because MyPADI is a Secondary (saved/wishlist) surface for Potential Divers in R1, the live lane is deliberately lean — the personalisation and win-back that make a logged-in view powerful are CDP-dependent and sit in the parked lane.

SegmentPotential Diver
Auth stateLogged-In · MYPADI shell
Sub-segmentsEnrolled Student · Account-Created Non-Converter · DSD Graduate · Dormant Saver · Family Parent
ConversionTurn known, latent intent into a booked course (DSD → PADI Scuba Diver → Open Water Diver)

How to read the two lanes

Live flow · Nov '26 Release 1. Connected, sequential touchpoints that ship at go-live and form the booked-course path.
Parked · later phase. Sits beneath the stage it will attach to — deferred or dependent on the CDP, mobile/app, or the data model.

Stages are re-read for a returning, recognised diver: entry is Re-entry (an SFMC email or direct link, not cold acquisition) and identity becomes Recognition — what being known unlocks. This maps to PADI's own dashboard evolution: R1 ships the Core Dashboard (lightweight baseline) while the CDP-Activated Dashboard (AI/ML, predictive) is the parked end-state.

Two lenses beneath every flow — evidence-backed

Business & CoverageWhy each step matters for conversion + coverage before launch, tied to GA4 funnel data.
Rationale · Q · ARationale, open questions, assumptions — grounded in Border UX research signals.

The recurring blocker across all four: today identity is captured after booking, so abandoners can't be nurturedBorder UX. The MyPADI shell starts to fix this by holding intent — the trigger engine that acts on it is parked.

Sub-segment 1 · lifecycle state · PADI-canonical

The Enrolled Student · eLearning active, pre-cert

Has purchased and is working through eLearning (e.g. Open Water eLearning) but isn't certified yet — one of PADI's seven canonical authenticated types, and the highest-commitment, highest-intent pre-cert state of all. They've already paid in. The job is to carry momentum from eLearning into the in-water training that completes certification, before drop-off sets in.

⊳ Conversion: convert active eLearning → booked in-water training (complete the certification)
Flow · scroll right →
Live · Nov '26
01Re-entry
Returns via SFMC eLearning reminders or a direct MyPADI link to resume
02First Contact
Core Dashboard surfaces eLearning progress front-and-centre ("X% complete")
03Consideration
Static NRA: "book your in-water training" with the same Dive Center
04Evaluation
Opens the in-water training step detail; transparent all-inclusive pricing; locator on hand
05Recognition
MyPADI knows eLearning progress + enrolment
06Conversion
Books in-water training via guided booking + handoff; SFMC confirmation → dashboard updates
Parked · Later
parks @ Re-entry
CDP-timed progress nudges tuned to module drop-off points
parks @ First Contact
CDP-Activated Dashboard predicting the right next step
parks @ Consideration
Personalised "you're nearly there" prompts by completion %
parks @ Evaluation
Instructor profile + live in-water availability (Dive Shop 360)
parks @ Recognition
Full progression model — eLearning as a milestone on a visible pathway
parks @ Conversion
Instant credit / handoff to the in-water portion; direct checkout (CommerceTools)
BizBusiness & Coverage
Opportunity
An Enrolled Student has already paid and committed — the warmest pre-cert state of all. The risk is eLearning-to-water drop-off; surfacing progress + a clear "book your water training" NRA addresses it head-on.
Reassurance
73% cite unclear pricing as a barrierBorder UX — transparent in-water pricing on the NRA removes the final stall.
Channel
eLearning is the committed surface; R1's Core Dashboard makes progress visible, while the predictive, drop-off-aware nudge parks to the CDP.
RatRationale · Questions · Assumptions
Rationale
A paid eLearning enrolment is PADI's strongest pre-cert signal; R1 surfaces progress + a static NRA, while drop-off-aware nudging is CDP-dependent and parked.
Open question
Does eLearning progress reliably surface on the web dashboard in R1 (LMS API), or is it app-only? The "resume + book water training" loop depends on it. (Owner: Product, LMS.)
Assumption
eLearning progress + static NRA + guided booking ship in R1; progress-aware nudges, instructor match, and instant credit park.
Sub-segment 2 · lifecycle state · PADI-canonical

The Account-Created Non-Converter

Created a MyPADI account — saved a destination, started a booking — but never completed it. The warmest pool PADI owns: a known, opted-in intent sitting idle. The job is to turn that latent intent into a first booking.

⊳ Conversion: convert saved/latent intent → first booked DSD or course
Flow · scroll right →
Live · Nov '26
01Re-entry
Returns via an SFMC welcome / confirmation email or a direct MyPADI link
Remembers PADI because they have an account — no cold re-acquisition needed
02First Contact
Lands on the MyPADI shell (AWS Cognito SSO session) — their saved destination / course shortlist persists
03Consideration
Reviews saved items; a static Next Recommended Action (NRA) surfaces the DSD → Open Water ladder
04Evaluation
Re-opens the saved course / DSD detail; re-checks all-inclusive pricing; locator still on hand
05Recognition
No re-auth wall — MyPADI recognises the returning diver; shows the saved list
06Conversion
Books via guided booking + handoff; SFMC confirmation updates MyPADI with the booked next step
Parked · Later
parks @ Awareness
CDP-triggered re-engagement — cart / wishlist abandonment nurture, behaviour-timed
parks @ First Contact
Personalised dashboard — recommended experiences tuned to saved + browsing (CDP)
parks @ Consideration
Personalised, behaviour-driven NRA replacing the static rule
parks @ Evaluation
Live price + availability on saved items via Dive Shop 360
parks @ Identity
CDP identity resolution — unify web + app + email behaviour into one profile
parks @ Conversion
Digital Passport / pre-configured checkout removes re-entry friction
End-to-end checkout on padi.com (cart → pay → confirmed booking) via CommerceTools — no "contact the shop" step
BizBusiness & Coverage
Opportunity
A known, opted-in intent is the warmest pool PADI has — yet today identity is captured after booking, too late to nurture abandonersBorder UX. The MyPADI shell at least holds saved intent across sessions in R1.
Channel
Web-first by design; mobile is only 10–11% of volumeGA4 and the app layer is parked, so R1 re-entry is web + a single email.
Conversion
60% of Dive Centers lack eCommerceGA4 — guided booking + handoff (not direct checkout) is the realistic logged-in conversion at go-live.
RatRationale · Questions · Assumptions
Rationale
In R1 the win is persistence (saved state survives the session) plus a static next-step nudge; dynamic win-back is CDP-dependent and parked.
Open question
Where does the re-engagement trigger live in R1 — a single SFMC welcome / abandon email, or nothing until the CDP lands? (Owner: CRM, Product.)
Assumption
MyPADI shell, saved list and SFMC confirmations ship in R1; CDP nurture, personalised dashboard, and Digital Passport park.
Sub-segment 3 · lifecycle state · crossover

The DSD Graduate

Has a logged Discover Scuba Diving experience in MyPADI and is deciding whether to commit to certification. The highest-intent Potential Diver of all — they've been underwater and liked it. (A DSD isn't a certification, so they're still pre-cert — the bridge between Potential and New Diver.) The job is to ladder the try-out into an Open Water booking while motivation is high.

⊳ Conversion: ladder DSD → Open Water Diver (or PADI Scuba Diver half-step) ⤳ Crossover flag: per team direction this state moves into the New Diver lifecycle once a DSD is logged — retained here for your manual validation, and to be surfaced in the Active Divers UFD
Flow · scroll right →
Live · Nov '26
01Re-entry
Post-DSD follow-up (SFMC) brings them back to MyPADI — the "what's next" moment
02First Contact
MyPADI shows the DSD as a completed experience + a static "Continue to Open Water" step
03Consideration
Sees the DSD → OWD ladder framed as "your try-out counts toward certification"
04Evaluation
Opens OWD detail (eLearning + confined + open water); transparent all-inclusive pricing
Same Dive Center via the locator — the one that ran the DSD
05Recognition
MyPADI knows the DSD history; pre-fills what it can
06Conversion
Books OWD via guided booking + handoff; SFMC confirmation + eLearning access → MyPADI updates the pathway
Parked · Later
parks @ Awareness
CDP-timed "strike while warm" nudge sequence (optimal-timing re-engagement)
parks @ First Contact
Personalised "because you dived at [site]" recommendation
parks @ Consideration
DSD auto-credited toward OWD — data-model dependent
parks @ Evaluation
Instructor profile (ideally the DSD instructor) + live class availability via Dive Shop 360
parks @ Identity
Full progression model in MyPADI — DSD logged as a milestone on a visible pathway
parks @ Conversion
Instant unlock of the next adventure on certification; direct checkout (CommerceTools)
BizBusiness & Coverage
Opportunity
The highest-intent Potential Diver — already in the water. The "now what?" wall right after a first experience is a known drop pointBorder UX; a visible next step in MyPADI directly addresses it.
Reassurance
73% cite unclear pricing as a barrierBorder UX — transparent OWD pricing on the next-step card removes the stall before it forms.
Conversion
Keeping the same Dive Center / instructor in the loop protects the shop relationship and the lead, countering known padi.com↔shop leakageGA4.
RatRationale · Questions · Assumptions
Rationale
Momentum is the asset; a static next-step card captures it in R1, but auto-crediting the DSD toward OWD needs the progression data model — parked.
Open question
Does a DSD record reliably flow into MyPADI in R1, or is it manual? If manual, the "your try-out counts" promise can't go live. (Owner: Product, CRM, Dive Shop 360.)
Assumption
DSD-as-completed-experience + a static OWD next step ship in R1; auto-credit, instructor match, and personalised timing park.
Sub-segment 4 · lifecycle state · Axelerant-added

The Dormant Saver · where the broken nurture model bites

Created an account and saved or wishlisted experiences, then went quiet — no recent activity. Intent has cooled, but the relationship and the data still exist. The job is to re-engage before the account goes dark. This is the segment most exposed by the fact that PADI can't yet act on behaviour — so it's the most heavily parked of the three individual states.

⊳ Conversion: re-activate a cold saver → return + book ✛ Axelerant-added state — not one of PADI's seven canonical authenticated types; included for funnel completeness
Flow · scroll right →
Live · Nov '26
01Re-entry
Limited: a generic SFMC re-engagement email at best — otherwise relies on the diver self-returning
02First Contact
If they return, MyPADI still holds the saved list — persistence is the R1 win
03Consideration
Static dashboard nudge re-surfaces saved items + the standard next-step ladder
04Evaluation
Re-opens saved course / DSD detail; pricing + locator current
05Recognition
Recognised on return (AWS Cognito SSO)
06Conversion
Guided booking + handoff; SFMC confirmation → MyPADI
Parked · Later
parks @ Awareness
Behavioural win-back triggers — dormancy detection → timed, channel-optimised nudges (CDP). The core missing capability.
parks @ First Contact
Personalised "still interested in [saved destination]?" re-entry
parks @ Consideration
Dynamic recommendations refreshed since they last visited (CDP)
parks @ Evaluation
Price-drop / availability alerts on saved items (Dive Shop 360)
parks @ Identity
Unified CDP profile spots the dormancy pattern across web / app / email
parks @ Conversion
Win-back offer / incentive logic; direct checkout (CommerceTools)
BizBusiness & Coverage
Opportunity
The biggest structural gap: identity is captured after booking today, so abandoners and dormant savers can't be nurtured at allBorder UX. MyPADI's shell begins to fix this by holding state — the trigger engine is parked.
Channel
Re-engagement is inherently multi-channel (email / push / app), but mobile is only 10–11% of volumeGA4 and the app + CDP layer is parked — so R1 re-engagement is email-only and shallow.
Risk
Without behavioural triggers, R1 re-activation depends on the diver remembering to return — a weak lever for a cold segment.
RatRationale · Questions · Assumptions
Rationale
Honesty matters here — R1 can retain saved state and send a generic nudge, but true win-back is CDP-dependent and out of R1 scope.
Open question
Is any automated dormancy nudge in R1 (a simple time-based SFMC journey), or does all re-engagement wait for the CDP? (Owner: CRM, Product, Data.)
Assumption
Saved-state persistence + a basic SFMC re-engagement email are the R1 ceiling; behavioural win-back, personalised re-entry, and alerts park.
Sub-segment 5 · lifecycle state · Axelerant-added

The Family Parent (Logged-In)

A parent with a MyPADI account planning a first dive experience for themselves and a child. High value — but research found the family journey is broken at both the discovery and the data-model level, and being logged in makes the data-model break worse: today a child's record overwrites the parent's. So this is the most heavily parked path of all four; R1 can only convert the parent as an individual.

⊳ Conversion: linked parent + child booking (mostly parked) — R1 books the parent as an individual only ✛ Axelerant-added state — not one of PADI's seven canonical authenticated types; included for funnel completeness
Flow · scroll right →
Live · Nov '26
01Re-entry
Parent returns via SFMC to their own MyPADI (parent profile only)
02First Contact
MyPADI shell shows the parent's own saved items — no family view
03Consideration
Browses general experiences; family eligibility still pieced together manually
04Evaluation
Opens a DSD / course detail for themselves; finds a Dive Center via locator
05Recognition
Parent profile only — child cannot be safely linked in R1 (record-overwrite blocker)
06Conversion
Books a single (parent) DSD; guided booking + handoff; confirmation (SFMC)
Parked · Later
parks @ Awareness
CDP family re-engagement for Seal Team · Bubblemaker · Junior OW
parks @ First Contact
A dedicated Family view inside MyPADI (the Family Discovery Path, T9)
parks @ Consideration
Age-filtered family experience discovery (eligibility by programme)
parks @ Evaluation
Family-programme filter + linked availability via Dive Shop 360
parks @ Identity
Family profile model: child linked to parent, not overwriting
Minor-consent flows — HIPAA (US) / GDPR (EU)
parks @ Conversion
Linked parent + child booking in one transaction
Post-dive: parent sees child's first achievement in MyPADI → next step
BizBusiness & Coverage
Opportunity
High-value segment, but broken at discovery and the data modelBorder UX — and logged-in makes it worse, because the child record overwrites the parent's today.
Programmes
Family spans Bubblemaker, Seal Team, Junior Open Water — age-gated eligibility that must be filterable, not scattered.
Conversion
Linked parent + child booking isn't possible todayBorder UX; until the data model is fixed, R1 converts only the parent as an individual.
RatRationale · Questions · Assumptions
Rationale
In the logged-in view almost everything family-specific depends on the family data model — so it's nearly all parked behind the parent-as-individual flow.
Open question
Critical blocker: child email overwrites the parent recordBorder UX. The family profile architecture + minor consent must be resolved before any logged-in family build. (Owner: Product, Legal, CRM.)
Assumption
Only the parent-as-individual flow is in R1; the Family view in MyPADI, linked bookings, the family data model, and minor consent all park.