02 / xDesign
A redesign that cannot show its findings is a mood board.
Decide what the report needs to communicate before styling it. A redesign is only as trustworthy as the findings it resolves and the meaning it leaves alone.
The contract
What a redesign has to carry.
Four things travel with every redesign, whether or not the visual changes.
- 01
A finding register with a resolution claim
Every named finding from the review gets an explicit claim about how the redesign addresses it — not a general impression that things look better.
- 02
A meaning-preservation proof
The same definitions, the same filter scope, and a named-cell tie-out with zero unexplained differences between the old and new numbers.
- 03
A declared dominant element
The one thing the report is now built to answer first, stated plainly, so the reviewer's own judgement can be argued with instead of guessed at.
- 04
An explicit list of what was not changed
Anything deliberately left alone is named, so silence is never mistaken for an oversight.
The rule
The rule that is not a judgement call.
The rule
A redesign never changes a definition, sign convention, denominator, unit, grain or filter scope as a side effect.
If a definition turns out to be wrong, fixing it is a separate, named, approved change with its own proof — never bundled into a redesign.
What it is not
Not a restyle.
Limits
A redesign starts from findings, not from taste.
xDesign is not offered on its own. Without a review there is nothing named for a redesign to resolve, so it always follows xReview, inside a rescue or a transformation. It changes how a report communicates, never what its numbers mean.
Next
See what a review finds first.
xDesign only has something to resolve once a review has named it.