Release Readiness

Brief keeps the customer’s need tied to the definition of done, so “is it ready?” has evidence behind it.

0:43

The ticket says
what done means

Brief keeps the approved requirements in the ticket. Each one names the decision or customer evidence behind it, and says so when there isn’t one.

JiraMeridian / MER-2 · Updated 6 minutes ago

Add industry filter to benchmark table

To Do

STATUS: D-43 is now an approved, active decision with a confirmed supersedes edge over D-041. The eight-peer default and single-select industry filter below are authorized to build.

D-43 D-041

ACCEPTANCE CRITERIA · TESTABLE

STATUS FOLLOWS THE DECISION

When a decision is approved, the ticket says so and names the decision it replaces, so the build follows the current call.

  1. Eight-peer default

    Given a QBR export with no industry filter applied, when peer benchmarks are selected, then the export defaults to exactly eight (8) peer benchmarks, replacing the prior twelve-peer default.

    D-43 D-041 Q1 reporting review: benchmark default

    SUPERSEDES, NOT ERASES

    Each criterion cites the decision behind it. The decision it replaced stays linked, with its original reasoning.

  2. Filter-before-limit ordering

    Given a single-select industry filter is applied, when the peer set is computed, then the account-scoped peer pool must be filtered to the selected industry FIRST and the eight-peer limit applied SECOND. Never limit to eight and then filter, which could silently exclude peers that should have qualified.

    D-43 meridian-qbr-demo #2

  3. Sparse/empty result handling

    Given an industry filter that matches fewer than eight peers, when the benchmark table renders, then it must show only the matched peers without padding to eight with unrelated accounts. Given an industry filter that matches zero peers, then an explicit empty-state message must be shown rather than a blank or broken table.

    No recorded decision Extends D-43

    NO RECORDED DECISION

    When nothing on record covers a requirement, the ticket says so instead of citing a source that doesn’t exist.

  4. CDP-only data access

    D-039 Customer data governance review

  5. Compass v2 only

    D-040

  6. PDF rendering

    QBR formatting feedback 4

    FROM THE CUSTOMER

    Some criteria trace back to customer feedback rather than a decision.

Evidence for
every requirement

Ask Brief to compare the ticket with the implementation. It answers requirement by requirement and points to where the evidence is.

BriefYour AI product assistant

You: Compare MER-2 with the implementation and identify the evidence for each requirement.

Brief: Each of the six criteria in MER-2 has evidence in the running app, the exported PDF, or PR #2.

  1. AC 1

    Eight-peer default

    The report shows eight peers with and without the industry filter, and the PR moves the default from twelve to eight.

    Evidence: Running app, Exported PDF, PR #2 checks

  2. AC 2

    Filter before limit

    Filtering to Manufacturing leaves only Manufacturing peers, and the PR filters before it slices to the count.

    Evidence: Running app, PR #2 checks

  3. AC 3

    Sparse and empty results

    An account with two matching peers shows two, with no padding.

    Evidence: Running app

  4. AC 4

    CDP-only data access

    The report and the PDF name Meridian CDP as the source, and the PR reads peers from the CDP service.

    Evidence: Running app, Exported PDF, PR #2 checks

  5. AC 5

    Compass v2 only

    The PR builds the table from the Compass v2 component.

    Evidence: PR #2 checks

  6. AC 6

    PDF rendering

    The exported PDF renders the benchmark table with its column headers.

    Evidence: Exported PDF

Sources

  • MER-2
  • PR #2
  • D-43
  • D-039
  • D-040
Example readiness check in Brief.
RUNNING APP
The running QBR app with the Manufacturing industry filter applied: Northstar Manufacturing, eight peers, data source Meridian CDP, and the peer benchmarks table.
EXPORTED PDF
The exported PDF of the Northstar Manufacturing quarterly business review, with the peer benchmarks table and its column headers.
PR #2 CHECKS
Pull request #2 on GitHub: all three checks have passed and there are no conflicts with the base branch.

Ship with the
evidence attached

See Brief compare one of your own tickets with the implementation, requirement by requirement.