Nathan Haslewood. Contact

/work/credit-cards/case study

Restructuring how a bank sells credit cards

The conversion journeys had too much friction, and the friction wasn't in the copy. It was in the architecture. Customers were doing work the structure should have done for them.

Client · ANZ Role · Senior content strategist, credit cards squad Method · Traffic and heatmap analysis, IA restructure
A tangled dark thread entering a frosted glass cube and leaving as three straight parallel threads in orange, cobalt and green

The situation

Credit cards are one of the most contested product categories in Australian banking, and one of the most heavily analysed. Everyone had opinions about the pages. What the squad didn't have was a clear picture of what customers actually did on them.

The decision

Before proposing anything, I built the evidence base: traffic flows across the category, and HotJar heatmap analysis of how people actually moved through comparison and product pages. The pattern was consistent. Customers weren't failing to understand the products. They were failing to find the right one, backtracking through a structure organised around how the bank thought about cards rather than how a person chooses one. The intervention I proposed wasn't a rewrite. It was an information architecture restructure: reorganising the category around customer decision paths, then rewriting only what the new structure demanded.

What shipped

A restructured credit card category: new hierarchy, new comparison logic, rebuilt page structures, and plain-language content where legal complexity had been hiding the value proposition. All of it through the approval reality of a big four bank, where every change touching a regulated product clears risk, legal and compliance before it ships. That constraint is the job, not an excuse. Work that only converts in a wireframe isn't finished.

Proof

10 to 15%

Uplift in conversion across the restructured journeys

$3m to $5m

Estimated cumulative revenue impact of the uplift

Evidence first

Every structural change traced to observed customer behaviour, not stakeholder preference

What it says about how I work

Information architecture is where I look first, because structure fails silently. Copy problems announce themselves; architecture problems disguise themselves as everything else, including as copy problems. The discipline is to instrument before you intervene. It's slower for the first fortnight and faster for every month after.

Next case study: two government websites, one statutory deadline →