A privacy-conscious, offline-first mental health and resilience app for airline flight crew: signed in with your existing company credentials, with nothing you do inside the app ever logged.
Portfolio case study built for Delta Air Lines Product Owner roles. Demonstrates the full product-ownership loop: translating an operational pain point into product vision, scoping an MVP under real constraints, writing build-ready user stories and acceptance criteria, and defining the metrics that prove it worked.
🔗 Try the interactive prototype → (If the link isn’t live yet, see “Getting Started” below to preview it another way.)
The prototype is a single static HTML file; there’s no build step, no npm install, no server required.
Option 1: Live link (once GitHub Pages is on):
Visit https://serrayon.github.io/delta-wellness-app/prototype/. To turn this on: repo Settings → Pages → Source → Deploy from a branch → main / / (root) → Save. Takes a minute or two to go live after saving.
Option 2: Preview locally, no setup:
prototype/index.html directly in any browser (double-click it, or drag it into a browser tab)That’s it; it’s plain HTML/CSS/JS with no dependencies, so it works the same whether it’s opened as a local file or served from Pages.
Flight crew operate inside a uniquely high-stress environment most consumer mental health apps aren’t built for: irregular operations (IRROPS), unpredictable reassignments, layover isolation, and anxiety tied to FAA/company reporting. The tools that exist are either hard to reach mid-shift, require connectivity crew don’t have on the tarmac or in-flight, or create a record crew don’t want tied to their name.
CrewAnchor meets a crew member in the exact 2–4 minute window they actually have between boarding calls, works with zero network dependency, and never logs what they do inside it. Access is gated by the company’s existing SSO, that’s realistic for an internal tool, but your in-app activity is never recorded, tracked, or reviewable. Three MVP capabilities, each chosen because it survives the worst case (no signal, no time, no willingness to create a paper trail):
A flight attendant (Sarah) hits an IRROPS trigger, opens the app in a quiet galley corner, selects “IRROPS Grounding,” completes an offline breathing exercise, sees a peer message posted under a display label, and returns to the cabin grounded, in under 3 minutes. Walk through it yourself in the interactive prototype.
| Doc | What’s in it |
|---|---|
docs/product-vision.md |
Problem statement, vision, target personas, explicit non-goals |
docs/mvp-scope.md |
Prioritization framework and why each MVP cut line was drawn |
docs/backlog.md |
Full Agile backlog, 12 user stories across 4 epics, each with build-ready acceptance criteria |
docs/okrs.md |
Objectives & key results, and the metrics deliberately excluded and why |
docs/definition-of-done.md |
The blanket “done means done” standard applied to every story, beyond its own acceptance criteria |
docs/stakeholder-map.md |
RACI across PO, Engineering, Design, Security, and a Crew Advisory Group, including where the PO is deliberately not the final word |
docs/roadmap.md |
Now/Next/Later sequencing; the reasoning behind the order, including what’s cut permanently, not just deferred |
wireframes/index.html |
Low-fidelity layout pass for the core flow, predating the visual design |
⚠️ See
KNOWN_ISSUES.mdfor the live prototype link’s current status and other open items.
All three personas defined in the product vision now have a full 6-panel storyboard in the interactive prototype, switchable via the tabs at the top:
I spent eight years as a Southwest flight attendant, and the hardest parts of the job were rarely on the aircraft. They were the unplanned layover nights, the long reserve stretches, and the weeks after an incident when you were quietly wondering how a report would read. The tools available for that assumed you had signal, time, and a willingness to leave a record.
Since then I have worked in quality assurance at Meta and Apple, auditing work, tracking defect trends, and turning what reviewers kept getting stuck on into clearer standards. CrewAnchor combines the two: a crew problem I know firsthand, approached the way I now approach any product, with a backlog, acceptance criteria, measurable goals, and a prototype people can actually click.
It is a portfolio piece, so I tried to show the work, not just describe it.
The demo page (prototype/index.html) uses Microsoft Clarity to collect anonymous usage analytics (session replays and heatmaps), so I can observe how real visitors move through the walkthrough. This is separate from the CrewAnchor app concept, which requires company sign-in to access but is designed to never log in-app usage activity. Measuring a product without breaking that promise is itself one of the open product questions; see KNOWN_ISSUES.md.
Built as a portfolio project. Not an official Delta Air Lines product.