Before / After

An old and new interface may look very different.

Visual difference alone does not prove usability, comprehension, or conversion improved.

Before should not only mean “before the project.”

Describe the initial state with metrics, behavior, constraints, or observable conditions.

Baseline — how is the starting state defined?

Intervention — what work was actually done?

After State — how is the new state observed?

Delta — what specifically changed?

Meaning — why does that change matter?

When many things change at once, do not assume the full delta came from a single deliverable.

If baseline uses completion time while after relies only on subjective impressions, the comparison is weak.

Not every change needs to be shown.

Choose deltas tied directly to the objective: faster, clearer, fewer errors, easier use, or easier decisions.

“Up 18%” is weak without explaining what that increase changes for users or the business.

Seasonality, traffic source, audience mix, time window, or external events can distort comparison.

Forwork can include a Before / After Block: Baseline, Baseline Evidence, Intervention, After Evidence, Delta, Meaning, Attribution Note, Timeframe.

It can connect directly to the Result Chain and Project proof.

Do not only ask, “Does before look different from after?”

Ask: “Can we prove what state changed, by how much, and why it matters?”

Baseline → Intervention → After State → Delta → Meaning.