Short case studies in taking technically sound reports and presentations — the kind with genuinely good analysis underneath — and redesigning one page so the argument is visible at a glance.
The official Test Completion Report template every DDTS project uses to sign off testing — redesigned so its exit criteria section states a verdict instead of leaving the reader to tally one.
Read the case study → UAT summaryThe same official template's UAT results section gave zero guidance beyond "insert a graph or table" — redesigned into an actual pass-rate verdict a stakeholder can act on.
Read the case study → Defect analysisA defect table with severities but no verdict makes the reader do the release-risk math themselves — redesigned so the headline states it directly.
Read the case study → Release readiness reportAn open risks and issues log that never once stated whether the release should go ahead — redesigned so the go/no-go verdict leads the page.
Read the case study →A Cabinet Office review of eleven real public-sector data breaches had already found three recurring causes — redesigned so the appendix groups incidents by cause instead of narrating each one separately.
Read the case study →A UK government Digital Service Standard assessment reduced its 18-point outcome to a bare "Not met" label — redesigned so the header states which point failed and how narrow the gap really was.
Read the case study →The UK's flagship major-projects report buried a headline delivery-confidence finding under a cross-tab table that needed its own reading key — redesigned so the answer leads.
Read the case study →One slide from a UK government actuarial deck, redesigned so a buried argument about climate exposure becomes the headline instead of a footnote three slides later.
Read the case study →