# Step 1: Analyze Feedback & Create PRD

**Paste this into Claude Code along with the 8 screenshots of the current platform.**

---

First, please set your working directory to `~/Desktop/"HRS x USEBERRY DEMO X"` - that's where all the assets and screenshots are.

**IMPORTANT: Do NOT create or modify any files for this step. Output everything (audit, PRD, design approaches) directly in the chat. These prompt files are reference docs for me - don't overwrite them. Only create files when I explicitly ask you to build prototypes in Step 2.**

I'm a Senior Product Designer working on a B2B Supplier Portal for a travel management company. This portal is used by hotel and ground transportation suppliers to manage their bookings, operations, and communication settings.

I need your help redesigning one of our most problematic pages: **Communication Emails**. This is where suppliers manage which email contacts receive booking notification emails from the platform.

## Here's what I'm attaching

8 screenshots of the current Communication Emails page showing the full flow:

1. **Read-only table view** - The default state with one contact, an "Edit" button in the top right, and no way to add or modify anything
2. **Edit mode (empty form)** - After clicking Edit, a form appears above the table with fields for Daily Booking Line, Email, Active, Day of Week, Time Period, Operation, Planning, Not Work. Delete and Save are disabled, only "Add New" is active
3. **Contact selected - Save disabled** - When you check the checkbox next to a contact, the form populates with that contact's data. Delete becomes active, but Save stays disabled. This is the core bug.
4. **Daily Booking Line dropdown** - A time picker dropdown for a global "Daily Booking Line" setting. Unclear what this means to a supplier.
5. **Not Work date picker** - A calendar date picker for exception dates. The label "Not Work" is confusing.
6. **Delete confirmation modal** - "Do you want to delete the selected item(s)?" with No/Yes buttons
7. **New contact added - Save now active** - After clicking "Add New" and filling in a new contact, the Save button turns GREEN. This proves Save only works when creating a new contact, never when editing an existing one.
8. **Success state** - Back to read-only view with 2 contacts now showing. The new contact was saved successfully.

## User feedback we've collected

**From support tickets (3-5 per week about this page):**

- Hotel Operations Manager (Paris location): "When I try to edit an existing contact's schedule, the Save button stays greyed out. I have to delete the contact and re-add it with the correct settings every time. This happens multiple times a week when we need to adjust notification schedules for seasonal changes."

- Ground Transportation Provider: "We cannot add any new email contacts at all. The Save button does not respond when we click it. We've tried on Chrome and Edge. Our transport coordinators have been unable to receive Operations notifications for 3 weeks."

- Hotel Chain Regional Admin: "The page is hard to use. I don't understand what 'Daily Booking Line' means. The 'Not Work' label makes no sense. When I select a contact to edit, I can't tell which one I'm editing because the form is far away from the row."

**From stakeholder interviews:**

- Airline Client Operations Lead: "Our hotel partners regularly complain about this page. We get 3-5 support tickets per week. Some transportation suppliers have just stopped trying and call us instead."

- Internal Product Owner: "This page was built 2 years ago and hasn't been touched since. The form-above-table pattern was a quick implementation choice, not a design decision. We need a proper solution before Q2 when we onboard 40 new hotel suppliers. Whatever we redesign has to be easy enough that hotel front desk staff can use it without training."

**Quantitative data:**
- Save button bug affects 100% of edit attempts
- Transportation supplier blocking bug affects ~15% of supplier base
- Users resort to delete+recreate workaround in ~60% of edit cases

## What I need from you

1. **Analyze the screenshots and feedback** - Do a UX audit of what you see. What's broken, confusing, or non-standard?

2. **Create a PRD** that includes:
   - Problem statement
   - Who uses this page and their technical comfort level
   - Success criteria (how do we know the redesign worked?)
   - Core functional requirements
   - Design constraints (dark nav header, cyan/teal accent, white content area, desktop 1440px)

3. **Propose 3 different design approaches** to solve these problems - each taking a fundamentally different UX direction. Explain the tradeoffs of each so we can test them with real users.