Selected work

Case studies

Every project here started with one hard decision. Here’s what each client decided, and what changed.

Headline finding

Users spent 3× longer in the 2D version. The 3D metaverse was pulling effort away from the core product.

Case study 1 · Product testing

Testing a new app with the people it was built for

Client
ZIYX – an app that helps people start a business
Project
Two rounds of testing over several months

The challenge

ZIYX had built a new version of their app. They needed to know if it worked for their target users. These were young people not in work, education or training, who hadn’t gone to university.

The app was built on guesses about how people would use it. That included a 3D metaverse, which was a big investment.

ZIYX needed three answers. Did the onboarding work? Did the core experience hold this audience? And was the metaverse worth building further?

What I did

I ran a survey with 1,200 people, all from the target group. They came through four email campaigns with partners. I found and secured two of those partners as part of the project.

I also interviewed 10 people about how they moved through the app.

The first round led to a full redesign of the onboarding. The 3D experience became a 2D questionnaire, laid out as a journey along a road. This gave users a sense of progress.

A second round then tested the new version.

The results

Users spent three times longer in the 2D version than the 3D version. Time spent and positive reviews both showed the simpler version was far more engaging.

The research led to a clear recommendation: drop the metaverse and focus on the core 2D experience. The metaverse was costly, and the basic experience hadn’t been tested yet.

The data made that case clearly. The work led to two new versions of the app.

“You showed us we were building far too much – users couldn’t engage with any of it until we had a really strong core to build on.”
– CTO, ZIYX
Headline finding

The product wasn’t the problem. The emails just weren’t talking to people the way the brand talks to people.

Case study 2 · Email marketing

Finding out why the emails weren’t working

Client
Nordic Life – an outdoor weather brand for elite adventurers and athletes
Project
Three weeks

The challenge

Nordic Life had a strong customer base, but their emails weren’t working. Existing customers weren’t buying again. New subscribers weren’t buying at all.

Open rates and click-through rates were below the industry norm. They knew something was wrong. They just couldn’t see what.

What I did

I started with their past email data from Mailchimp. I looked for the point where people were losing interest. Then I designed A/B tests based on research into how people read and act.

There were two main changes. First, I changed the layout so the key content and buttons sat where the eye goes first.

Second, the founder started telling more stories and showing more human faces. Research shows that people remember stories and faces better. They’re also more likely to act on them than on product-only content.

The results

The new emails lifted click-through rate by 12%. Open rates and overall engagement went up too.

These customers were already loyal. The work made that bond more active again.

“Annabel looked at our email data and showed us exactly why people weren’t buying. Three weeks later our click-through rate was up 12%.”
– Founder, Nordic Life
Headline finding

Some search terms had 0% overlap. Researchers were missing whole areas of work. The work existed, but it was filed under a different name.

Case study 3 · Research search tools

Mapping search terms across research databases

Client
ANSResearch – a foundation that supports researchers in trauma and adversity
Project
Mapping search terms and building a product feature

The challenge

Researchers in trauma and adversity struggled to find work related to their own. Some were even repeating studies that already existed, because they hadn’t found them.

The same ideas were listed under different terms across the main academic databases. Someone searching “Adverse Childhood Experiences” on PubMed might miss thousands of papers. Those papers could be listed as “Early Life Stress” or “Childhood Maltreatment” on Google Scholar.

About 20 different terms were in use across the field. Nobody had mapped how they linked together.

What I did

I mapped 19 key terms across four major databases: Google Scholar, PubMed, PsycINFO and ERIC. For each term, I recorded the number of results.

Then I worked out the overlap between each pair of terms. This showed how much research someone would miss by searching with only one term.

The result was a grid showing where terms differed across databases, and how much unique research sat behind each one. ANSResearch then built this into their own database as a “related terms” feature.

The results

Some pairs of terms had zero overlap. So a researcher using one term would miss all the work filed under the other, even when both meant much the same thing.

This showed how big the field was, and how split up it had become.

The related terms feature helped a team of about 30 researchers, including partners at Harvard. They could search more fully without knowing every version of a term. This cut the risk of people repeating each other’s work.

“Annabel flagged the terminology problem and mapped the scale of it.”
– ANSResearch
Headline finding

2,860 reviews pointed to the same thing. Two suppliers were behind most of the bad feedback. The fix was a better printer.

Case study 4 · Customer feedback

Finding what was behind the bad reviews

Client
Moteefe – a print-on-demand online shop platform
Context
Worked inside the company as Junior Chief of Staff

The challenge

Moteefe was getting bad customer feedback, but no one had looked at it in a structured way. There were so many reviews and support emails that patterns were hard to spot.

They needed to know what customers were unhappy about, and whether it could be fixed.

What I did

I went through about 2,860 customer reviews and support emails. I used keyword analysis to find the common complaints and group them.

I treated the feedback as data rather than reading it one story at a time. I sorted each issue by how often it came up, how serious it was, and which supplier it traced back to.

The results

A large share of the bad reviews came from print quality problems. These traced back to two suppliers. The work became part of the case for dropping them. Orders moved to a new supplier with better print quality and faster delivery.

After the switch, customer feedback improved and delivery got faster. The brand’s image problem was a supply chain issue, hidden in the review data.

The CEO later tried to rehire Annabel twice. – Moteefe

Got a big call to make?

Tell me what you’re trying to decide. The first call is free, and you’ll leave with a clearer view either way.

Pattern & Proof is based in London.