User story map · Diagram Design

Reporting, first release

Narrative order runs left to right — find the data, build the report, share it, trust it — while priority runs top to bottom. The release-cut line under MVP is the editorial point: everything above it ships first, and the riskiest bet, row-level permissions, lands in Release 2.

Reporting, first release · User story map User story map for a reporting tool's first release: four narrative activities from finding data to trusting it, walking-skeleton steps beneath each, and three release slices sliced by an MVP release-cut line, with the row-level-permissions story flagged as the riskiest bet in Release 2. MVP RELEASE 2 LATER Find the data ACTIVITY 1 Build the report ACTIVITY 2 Share it ACTIVITY 3 Trust it ACTIVITY 4 Search datasets Preview rows Pick columns Add a chart Send a link Check freshness Keyword search RPT-101 · 3pt Table + one chart RPT-102 · 5pt Public link RPT-103 · 2pt Last-updated stamp RPT-104 · 1pt RELEASE CUT Saved filters RPT-110 · 3pt Scheduled email RPT-112 · 5pt Row-level permissions RPT-114 · 3pt RISK Natural-language query RPT-120 · 8pt Alerting on anomalies RPT-121 · 5pt LEGEND Story card Highest risk Release cut

RELEASE CUT

MVP · 4 stories

Keyword search, a table with one chart, a public link, and a last-updated stamp — enough to answer "what is the whole story" without shipping every activity's full depth. Everything below the cut line waits.

Release 2 · 3 stories

Saved filters and scheduled email round out the workflow, but row-level permissions is the riskiest bet in the map — untested access-control logic sitting right after the cut, not buried in "Later".

Later · 2 stories

Natural-language query and anomaly alerting are named and ordered, not promised — three slices is the ceiling before nobody believes the sequencing anymore.