Compare equivalent versions of the same task or artifact and explain the conditions around them. Use matching scale, content and context where possible, disclose reconstructions and selection limits, and separate visible change from evidence of better performance. Obtain the necessary publication permissions before sharing either version.
Choose a comparison that answers a question
Decide what the comparison is meant to show. A navigation revision might demonstrate a change in grouping; an edited paragraph might demonstrate clearer responsibility wording. Select material that lets the reader inspect that specific change. Avoid placing an intentionally poor fragment beside an unrelated polished artifact and presenting the contrast as a fair account of the project. The versions should share enough context for someone to understand what the work actually altered.
Identify the source and status of each version. Was the “before” an approved live artifact, a draft or a reconstructed example? Was the “after” implemented, proposed or still under review? State those differences explicitly. A proposed redesign can be useful evidence of reasoning, but it should not look like a delivered replacement. Keep a record of the original materials and permissions so later formatting changes do not detach the comparison from its factual basis.
Preserve comparable presentation conditions
Use similar scale, cropping and visible task context when those factors affect interpretation. A tiny blurred original beside a large sharp replacement exaggerates difference without explaining it. If the formats cannot match, describe why and show the relevant content in text. Do not remove important elements from the original to create a stronger contrast. Where redaction is necessary, make the editorial treatment clear and check that the remaining image still supports the point fairly.
Explain a small number of changes with annotations or adjacent text. Identify what moved, what was rewritten and what remained unchanged because it served the task. A fair account can acknowledge trade-offs: the revised version may add explanatory content while reducing visual simplicity. Give readers a way to understand the comparison without relying only on colour or side-by-side viewing. Alternative descriptions should convey the important differences rather than merely naming the images “before” and “after.”
Keep performance claims separate from appearance
A visible revision does not establish that people completed tasks more easily or that a business outcome improved. If evaluation occurred, describe its method, scope and limits separately. If it did not, explain the intended benefit and the evidence still needed. Avoid labels such as “high-converting” or “fully accessible” based only on an attractive screenshot. The comparison shows an artifact and a rationale, while a performance claim needs appropriate supporting evidence.
Review the comparison after it is placed on the actual page. Check that captions, sequence and image descriptions preserve the context at narrow widths, where the versions may stack. Make sure the first image is still identified correctly when viewed alone or shared. Keep essential qualifications near the visual, and update the status if a proposed version is later implemented. A comparison should remain interpretable outside the exact desktop arrangement in which you first designed it.
Fictional example: comparing two request instructions
A fictional content editor, Bea, creates an independent example comparing two versions of a repair-request instruction. Both use the same invented task and source facts. The original requires readers to infer who approves a request; the revised version names the approver and separates required information from optional context. Bea uses equivalent text size and includes both complete passages rather than cropping away the original explanation.
The caption labels both versions as synthetic and identifies the wording decisions. Bea describes the intended improvement in responsibility clarity but does not claim a reduction in errors because no user study occurred. A text explanation remains available when the visual comparison stacks on a small screen. The example illustrates fair presentation without inventing a commissioned redesign or measured result.
A checklist for your next step
- Choose one comparison question.
- Record each version’s status.
- Use comparable presentation conditions.
- Explain changes in text.
- Separate visuals from performance evidence.
Common questions
Can I reconstruct a before example?
Yes, if it is labelled as a reconstruction and does not misrepresent the source or disclose material you cannot publish.
Does a cleaner screenshot prove better usability?
No. Explain the intended benefit and use appropriate evaluation evidence before claiming improved task performance.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.