# UX Review — Sprint 5

## Why Analytics was too complicated before

The Analytics page previously behaved like a reporting console. It exposed seven tabs — overview, import, videos, trends, topics, insights and import history — before answering the creator's core question: which video got how many views?

That made normal daily use slower because the creator had to understand where the important answer lived. The page also mixed raw import management, charts, topic analysis and insight cards at the same visual priority. Technically useful, yes. Immediately understandable, no.

## Tabs removed or merged

Sprint 5 reduced Analytics to three areas:

1. **Results** — the default view. Shows video performance immediately.
2. **Improvements** — shows whether a creative change appears to have helped.
3. **Import data** — keeps CSV upload, import history and raw management out of the daily path.

Merged/removed from primary navigation:

- Overview → merged into Results KPI cards.
- Videos → became the default Results table.
- Trends → removed from primary view; key trend labels are shown in rows.
- Topics → not primary in Analytics; topic link appears per video.
- Insights → replaced by next-action/recommendation wording.
- Import history → moved under Import data.

## New simple workflow

The user now lands on `/analytics` and immediately sees:

1. Total views.
2. Best video.
3. Biggest improvement.
4. Subscriber gain/loss.
5. A Video Results table with views, view change, CTR, retention, subscribers, linked package/topic, what changed and next action.

Clicking a video opens a detail drawer with summary, metrics, imports-over-time, change history, add-change-note form and recommendation.

## How the user finds a video and its values

The Video Results table is visible by default. No tab hunting is required.

Visible columns:

- Thumbnail / video title.
- Views.
- Delta views with a human label such as `+40 since last import` or `new`.
- CTR.
- Retention.
- Subscribers.
- Linked package/topic.
- What changed.
- Next action.

The row click opens Video Performance details for secondary values and history.

## How changes and experiments connect to performance

Sprint 5 introduced `CreativeChange` as the simple source of truth for title/caption/hook/schedule/topic/etc changes.

Change notes can be created in two ways:

- Automatically when Review metadata save changes important fields.
- Manually from the Analytics video detail drawer.

The Improvements page compares changes against available analytics snapshots:

- If before/after data exists, it shows the delta.
- If not enough imports exist yet, it shows `Needs more imports` rather than pretending certainty.

This keeps the learning loop honest: the dashboard can now say what changed and whether the next import suggests improvement, without pretending to run serious statistics from thin air.

## What remains open

- Topic-only and ignore actions in the unlinked drawer need UI polish.
- Improvements need richer fixture/import flows to reliably demonstrate measured before/after changes.
- Change History can later show grouped diffs and restore actions.
- Calendar reschedule needs full save/retry workflow hardening.