Ixana · Delivery reporting

Team performance reporting

Window — Not yet run 0 counts from a model

Viewing as

Team

Window

What this demo is

A working recreation of the team performance reporting engine described in the case study. Two parameters — which team, which window — produce every report on this page. The run is simulated and the content is invented; the structure, the rules and the gate are the real ones.

The four decisions it makes visible

1. Counting is deterministic; only synthesis goes to a model — every panel carries a rule or model badge.

2. The window decides what the model is for: a threshold weekly, the worst decile monthly, and at quarter it reads the three monthly reports and writes no task analysis at all.

more

3. The signature gate exists from monthly upwards. A weekly report is a working document and is never signed, because signing it would cost four times as much for a document nobody quotes.

4. Five teams share a report shape and six cause categories, and are never ranked against each other. The one sheet that puts them on a page reports whether the process ran, not how they performed.

All teams, tasks, names, comment threads, causes and figures on this page are invented for the demo. No task, customer or individual’s performance data appears here. The five team names are real internal groupings at Ixana; everything inside them is not. March and April are held as the monthly reports they produced, not as task records, because that is what the quarterly report actually reads.