Overview

Year: June 2022
Timeline: 3 weeks
Role: Lead UX Designer
Company: Freetrade

Background

The case study focuses on enhancing the Information Architecture (IA) for Freetrade, an app-based share dealing platform, to support the introduction of new subscription plans.

Problems to solve
  • Scalability problems with the existing Information Architecture as the platform expanded.
  • Navigation challenges within the app, making it difficult for users to find information and offerings.
  • The need to enhance overall user experience to effectively communicate the benefits and pricing of new subscription plans.
The goal

Establish a new Information Architecture for Freetrade that could scale effectively, improve navigation, and enhance user experience. This was in order to better present the benefits and pricing of new subscription plans, ensuring that users could easily find and understand the information they needed.

Freetrade is a user-friendly, app-based, share dealing platform offering a range of investment products. Recently Freetrade launched a new subscription model aimed to simplify and better communicate benefits and pricing. As part of the subscription launch, the product and marketing website had to undergo huge changes to promote and communicate the details of the new plans. This case study will be detailing the process I lead on to assess the current Information Architecture and suggest and implement an improved solution to support the launch of the new subscription plans.

With the plan subscriptions rolling out in July (Starter, Standard, and Plus), we need to understand how customers navigate through our account types and plans and the user journey they would expect to take to sign up and find relevant information.

The problem we were trying to solve for Tiltsta's clients was how to maximise their marketing budget and generate greater revenue in their social channels on mobile.

Pain points of current navigation

  • Scalability
    Soon we will be introducing plans, crypto, and then more products will be following, we will not be able to accommodate the additions in the current setup.
  • Space for login portal
    We will need to have space in the nav to log in to the web app.
  • Limited space for a ‘download now’ CTA
    The addition of a sticky ‘download now’ would help improve acquisition.
  • Long on mobile
    The download now CTA is hidden under all the navigation items.
  • An overwhelming amount of information/options
    Hicks’s Law is a great example of this: Hick’s Law is a simple idea that says that the more choices you present your users with, the longer it will take them to reach a decision. source

What do we want to achieve?

  • Promote subscriptions.
  • We want to meet business goals (OKRs SEO, traffic, conversion goals, etc).
  • We want to provide a good user experience to visitors.
  • We want to design the navigation and information architecture in a way that means it’s easily scaleable over the next year and into the future.
  • We want to design a navigation that reflects our branding and design style.
  • We want these changes to provide value.

Next steps...

  • Gather inspiration from other competitors/websites - Wealthsimple is a great example.
  • Scope out development/build/implementation time - options for ready-built components could be faster.
  • Sitemap/wireframing.
  • User testing.
  • Navigation solution - mega nav?

Examples from competitors and other websites

Desktop sticky navigations with ‘get started’ CTAs in the top right corner

Wealthsimple

Robinhood

Monzo

Wireframing

We had a few brainstorming sessions between branding and design with a focus on subscriptions. We looked at the limitations of the current navigation and produced a few ideas around categorisation. From here we established three variations that we would run user tests on (see below).


Brainstorming session

Variation one

Variation two

Variation three

User testing plan

Objective

We want to test 3 variants of a navigational structure to validate our information architecture decision. We will first use a method called tree testing. This is because we have already decided on a few variations of the navigation and we want to validate the find-ability of different topics across each variation.

Why did we choose to tree test?

There are a couple of methods when it comes to testing information architecture. tree testing and card sorting are two great ones, to begin with. We decided to start with tree testing as we had already decided on a few variations of the structure and labels and we were looking to validate each one. Card sorting is great if you want to understand how users would structure navigation content, which was slightly different from how we approached it.

Example of a tree test

The participant is asked to complete a task and they navigate through the levels and then pick a page as the correct destination. We select which pages are correct for each question before the test is sent out.

Who are we testing on?

We will test on our existing customers using internal resources like Intercom to email customers and ask them to participate in a user test.

How many participants?

13 participants per test. There will be a total of three tests conducted.

Research questions

We will have a total of ten questions. This is the recommended amount by Optimal to ensure we don’t risk participants becoming too familiar with our tree, which would bias the results for later tasks.

  • Do our labels make sense to people and what labels are most effective?
  • Are our pages/content grouped logically to people?
  • What categories are most intuitive to users?
  • Can people find the information they want easily and quickly? If not, what’s stopping them?
  • Which iteration of the IA performs best?

Research goals

  • Evaluate the findability of pages/topics/content on the site with a consideration of the new subscription rollout
  • Run 3 different unmoderated tests using the tree testing tool on Optimal
  • Confirm which variation is most successful

Results and takeaways

  1. When using ‘Products’ as a top-level navigation label, we saw a 30% decrease in directness to stocks and a 38% decrease in success to account pages. the label ‘Products’ is generally unclear and causes confusion when locating stock information, leaving users unsure of what to expect.
  2. ‘What we offer’ as a top-level navigation label was the most effective at 80% success when asking participants to choose an account or plan.
  3. 50% of participants expect to sign up from the account pages and the other 50% expect to signup from plan pages.
  4. ‘Learn’ is over 90% effective when used as a top-level label to direct users to Investment guides and market news.
  5. ‘Company’ is 80% effective when used as a top-level to direct users to ‘careers’.
  6. ‘Help’ is 90% effective when used as a top-level to direct users for support.
  7. When asking participants to select where they would expect to see Freetrade app features, 64% of first clicks were to ‘What we offer’ and 30% were to Learn.

Overall recommendation

From the research we’ve seen above, I’d recommend implementing a hybrid between variations 2 and 3. In variation 3 we have ‘Stocks’ housed within ‘What we offer’. However, as we saw a 40% decrease in variation 3, I’d recommend implementing it in the same way as variation 2 (at top level).

Example of working prototype (for desktop only)

see the fully operational navigation at freetrade.io.

See more work

More case studies