Financial Times /

In 2016 I joined the FT as a Lead UX Designer during the relaunch of With almost 850k paying subscribers, the site is an essential daily resource for high-profile professionals working in business, finance, politics, and culture around the globe.

My work is a mix of hands-on design and the role of a project lead. Hands on, I'm part of various teams, designing across the entire product lifecycle; from the initial vision to the final assets. As a lead, I work with the product design team on our global design language, to support the major user journeys across all channels. In addition, I mentor other team members, refine our processes, and represent the team to other parts of the business.

Check out some work examples below, or see how we work.

How we work

I’m part of various multidisciplinary teams that work autonomously on problems and solutions. Our work is user-centred and data-informed with a focus on shipping quickly to learn from actual users. Our process includes Kanban and Lean elements but we aren’t dogmatic about it. Instead, we often follow the steps below, either simultaneously or sequentially, in a way that best fits the problem.

Understanding the user journey and defining the problem
The FT has an excellent customer-research team, whose insights often form the foundation of our work. Together with the product owner, I articulate our initial questions and hypothesis, scan existing insight and refine these into a tangible journey and product vision. This helps us to understand the problem and where it’s located.

Discovering potential solutions
Together with the team and stakeholders, I will run an initial ideation session. We collect a set of ideas and decide as a team which one to explore further, with prototyping and testing. This session helps to hear everyone's perspective and get a shared understanding of the direction and scale of a possible solution.

In parallel, we discuss the best ways to understand the problems with our research teams. This could be an additional data report, qualitative user research or surveys hosted on the site or sent by email.

Design, prototyping and testing to validate our hypothesis
Depending on the complexity of the solution, I either prototype in Marvel, Keynote or Framer, or our developers build a codebase prototype to be rolled out for a small percentage of our users. The usability is tested fortnightly with a group of readers that we invite to the FT.

Defining the UI specification and adding it to our pattern library
Once a solution looks promising, and we are shipping it to a larger group of readers, we refine the UI and interaction design in Sketch or Framer, and use Principle for animations. The handover is done with Zeplin or directly in the browser.

Finally, the new components are added to our internal style guide and to Origami, our white-label component library, used internally across multiple sites and applications.

Revisions and further iterations
Once it has been shipped, our new feature is closely monitored. We use these insights to find out whether the solution has solved the intended problem, and what needs to be improved or changed for the next iteration.