TecnoStack
Start a projectالعربية

Silent video with on-screen text. The transcript below repeats every screen and describes what it shows.

  1. 0:00–0:06

    Name the recurring decision • The user needs a route from the number to action. • Weekly overdue review • D · confirmed undelivered • Assign follow-up owner • Hypothetical order · inspect permitted records

    A route grows from the weekly overdue review to hypothetical order D, whose source confirms it is undelivered, then to a follow-up owner. The film does not claim delivery or a completed follow-up.

  2. 0:06–0:12

    Define one counted item • Orders, lines and shipments are different units. • One order • Line 1 · Line 2 • Shipment 1 · Shipment 2 • Illustrative details · count orders once

    One counted order branches independently into two illustrative line details and two shipment details. The groups remain separate, and attention returns to the one order; detail rows must not silently become new orders.

  3. 0:12–0:18

    State the denominator • The example 60% and 75% answer different questions. • Due: 3/5 = 60% • Delivered: 3/4 = 75% • Overdue included • Cancelled excluded • Due • 3/5 = 60% • Delivered • 3/4 = 75% • Fri 18:00 · Riyadh • Example: D due · F excluded

    The approved nested sets show three on-time orders, one late-delivered order and one confirmed overdue-undelivered order. The due population contains five eligible orders, giving 3/5 = 60%; the delivered subset contains four, giving 3/4 = 75%. These are hypothetical Friday 18:00 Riyadh-time figures, not client results. D remains due and undelivered. F is excluded only by the example cancellation rule.

  4. 0:18–0:24

    Expose update conditions • Unknown delivery is different from confirmed undelivered. • Source stored • Delivery unknown • D · confirmed undelivered • Retrieval succeeded ≠ source complete • Qualify or withhold incomplete results.

    An unchanged source clock sits beside separate unknown-delivery and confirmed-undelivered states. Each state is highlighted independently. A retrieval-success panel is highlighted without changing either source state: successful retrieval does not make source data complete. Qualify or withhold incomplete results.

  5. 0:24–0:30

    Accept through tasks • Recalculate, inspect exceptions and test access. • 3/5 = 60% • Inspect D · verify F exclusion • Test permitted detail access • Failed refresh: show a state, not zero.

    The reviewer traces 3/5 = 60% to order D and the exclusion of F, then to a separate permitted-detail access check. A failed-refresh state must be shown explicitly rather than as an unexplained zero. No acceptance result is claimed.

A silent 30-second explanation in five six-second beats. A dashboard brief connects a decision and metric definition to source records and a usable next action.

Read the article: Business Dashboard Requirements: Write the Decision Before the Chart