Skip to content

03 / xBuild

The build is judged on what it hands over.

The model, the measures and the report, implemented as a working artefact. An implementation is only as good as the evidence that comes with it — the files that changed, the checks that ran, and what those checks showed did not move.

The evidence

What is handed over.

Four things, every time — a checklist, not a maturity ladder.

  1. 01

    The changed files

    Exactly what moved, named, so a reviewer can see the boundary of the work without guessing at it.

  2. 02

    The validation output

    What ran against the change, and what it reported — not a description of tests that exist somewhere else.

  3. 03

    The rendered evidence for every batch

    A real screenshot or export from the actual build, for each batch of work, not a description of what it should look like.

  4. 04

    The tie-out re-run against what was actually built

    The same reconciliation the redesign promised, run again against the finished artefact, not against the design that preceded it.

The rule

No silent substitution.

The rule

Anything in the approved design that could not be implemented is listed with the exact blocker.

A simpler technique is never quietly swapped in for a harder one without saying so.

The tooling

Adopted, not claimed.

Where the work comes from

Platform tooling, adopted where it already does the job.

Where Power BI and its own tooling already do a piece of this work well, they are used rather than re-implemented and re-branded as something original. Reports and models are authored as PBIR and TMDL text, so every change can be read in a diff.

The differentiator is the judgement and the proof that come with the build, not who authored the underlying tooling. The build is done by hand for each engagement; it is not an automated product.

Next

Check what the build changed.

The build's only real claim is that the tie-out survives it.

Start with the question

What should your report help you decide?

Two answers are enough to begin. The brief is written in your browser: email it from your own mail app, or save a copy. This site sends nothing on its own.

The buttons switch on when this page has finished loading. If they stay off, email mihai@playwithdata.io directly.

Goes to mihai@playwithdata.io · No account · No tracking · No network request from this site