For teams · Product & UX

Unfair trading reform for product and UX teams

Product and UX teams can begin with the customer’s decision environment rather than a legal checklist pasted onto individual screens. Map how price, recurrence, options, notifications, support and exit are presented over time, compare the current interface with a neutral alternative, and make the approved outcome testable across responsive states and experiments.

Who this is for
Product managers, designers, researchers, content designers and design-system teams responsible for Australian consumer journeys.
Practical outcome
A coherent journey in which material choices and consequences are understandable, usable and reviewable from the first offer through confirmation and exit.
Boundary
Fair-design implementation for Australian customer journeys. A research or taxonomy label is not, by itself, a finding under the Australian Consumer Law.

Evidence workflow

Product & UX: from question to reviewable decision

Each stage produces evidence for the next team. Keep the sequence together so a later reviewer can see what was enacted, observed, assumed and decided.

  1. Map

    Mark every consequential choice

    Identify where the customer pays, starts recurrence, accepts an option, changes a service or leaves the relationship.

    Evidence to retain
    Journey map, commercial rules, audience, variants and intended user outcome.

  2. Compare

    Prototype the neutral path

    Place the current and fairer versions side by side and explain how each affects comprehension, effort and control.

    Evidence to retain
    Annotated interfaces, alternative prototype and legitimate-purpose statement.

  3. Test

    Check consequence and control

    Observe whether users can predict the result, find the alternative, recover from error and complete exit across devices and assistive technology.

    Evidence to retain
    Research observations, accessibility results, error states and counterexamples.

  4. Release

    Make the decision durable

    Turn the approved experience into component rules and acceptance tests that include price logic, state persistence and confirmation.

    Evidence to retain
    Decision record, acceptance criteria, experiment boundary, owner and release evidence.
This workflow is a practical review model, not a statement of legal duty.Provenance: Original Flowlane workflow diagram authored for the Product & UX pathway from the portal’s current legislative and journey methodology; source context checked 2026-09-14.

Role ownership

What this team should make explicit

Design the whole price path

Show how the first displayed amount becomes the final total, including mandatory components, transaction charges, optional extras and conditions.

Connect the subscription lifecycle

Treat offer, recurring payment, notification, account controls, change, cancellation and confirmation as one experience rather than separate tickets.

Protect meaningful choice

Compare labels, prominence, defaults, timing and effort. Ensure the customer can understand and take the less profitable option without avoidable obstruction.

Document fair-design rationale

Record the user need, business purpose, alternative considered, research result and accessibility boundary behind each consequential design decision.

Evidence checklist

The records needed for a defensible handoff

Connected journey
Screens and states from entry through purchase or subscription, account management, cancellation and effective confirmation.
Commercial information
Prices, charge types, recurrence, dates, contract conditions, claim basis and where each item first becomes visible.
Choice comparison
Prominence, wording, default, steps, delay and channel requirements for accepting, refusing, changing and cancelling.
User evidence
Comprehension, accessibility, error recovery and interrupted-session research for the current and neutral designs.

Use in review

Questions that expose missing context

  1. Can a customer reproduce the final total from the amounts and conditions visible before commitment?
  2. Is a recurring payment, notification or cancellation consequence disclosed at the moment it can still inform the choice?
  3. Can customers decline, change or cancel without unnecessary steps, delay, lost progress or a forced channel change?
  4. Do the preferred and alternative options have comparable clarity, even where their visual emphasis is not identical?
  5. Does the design preserve refusal, removal or cancellation across refresh, device, recalculation and the next lifecycle event?
  6. Can the same outcome be completed with keyboard navigation, screen readers, zoom and small-screen layouts?

Cross-functional handoffs

What the next team needs from you

From legal

Ask for the statutory element, material consequence, commencement boundary and any prescribed detail still unresolved.

To engineering

Specify price calculation, persistence, notification state, cancellation effectiveness and error recovery alongside the visible design.

To compliance

Provide the journey map, alternatives, research record and release criteria so the review can be repeated after material change.