Established Team's UX Practice, Transformed Product Development Process

Established Team's UX Practice, Transformed Product Development Process

Organization:

Organization:

Organization:

Methodify

Timeframe:

Timeframe:

Timeframe:

2 years

My role:

My role:

My role:

UX Designer, UX Research

Tools:

Tools:

Tools:

Sketch, Whimsical, Inspectlet

Industry

Market Research Tech

Headquarters

Toronto

Founded

1998

Company size

80-90

As Methodify’s first UX hire, I established their UX design and research practice, transforming development workflows and introducing a user-centered approach despite initial resistance.

My work directly shaped the roadmap, streamlined collaboration, and improved customer retention. By the time I left, they had embraced UX as a core practice, hiring three full-time designers to continue the work.

100+ hrs

Development time saved by refocusing product roadmap

4x

More efficient data manipulation (#1 user need) than previous version

Industry

Market Research Tech

Headquarters

Toronto

Founded

1998

Company size

80-90

As Methodify’s first UX hire, I established their UX design and research practice, transforming development workflows and introducing a user-centered approach despite initial resistance.

My work directly shaped the roadmap, streamlined collaboration, and improved customer retention. By the time I left, they had embraced UX as a core practice, hiring three full-time designers to continue the work.

100+ hrs

Development time saved by refocusing product roadmap

4x

More efficient data manipulation (#1 user need) than previous version

Industry

Market Research Tech

Headquarters

Toronto

Founded

1998

Company size

80-90

As Methodify’s first UX hire, I established their UX design and research practice, transforming development workflows and introducing a user-centered approach despite initial resistance.

My work directly shaped the roadmap, streamlined collaboration, and improved customer retention. By the time I left, they had embraced UX as a core practice, hiring three full-time designers to continue the work.

100+ hrs

Development time saved by refocusing product roadmap

4x

More efficient data manipulation (#1 user need) than previous version

The Challenge

When I joined Methodify, the company lacked a UX foundation and had no meaningful insights into its users. Leadership relied on assumptions and feedback from sales calls to set the roadmap, building features for individual client requests rather than addressing broader user problems.

This reactionary approach wasted resources and led to building features that clients would use only once. Furthermore, it failed to solve the company’s glaring customer retention issues. (This comic illustrates a real conversation →)

From the start, I was discouraged/restricted from conducting research, and informed that my role was mainly to design new features in order to boost the low customer retention rate. (Detailed in the comic below)

However, leadership was unable to answer two fundamental questions:

  1. Who are our users?

  2. Why is customer retention so low?


Therefore, my role ultimately entailed educating my team about user-centered design (via workshops and documentation), in addition to actually answering those questions via design.

Example of initial resistance

Establishing the UX Practice

Building Foundations Through Research

Overcoming Resistance

UX research wasn’t part of Methodify’s culture when I arrived, and leadership resisted investing in it. But I knew understanding our users was essential to addressing retention issues and shaping a more effective product roadmap. To address this gap, I conducted and synthesized research using a range of methods, while also collaborating with engineering to deliver features:

  • web analytics

  • usability tests

  • industry reports

  • surveys & interviews

  • competitive analyses

This enabled me to create valuable documents such as user personas, journey maps, etc., which helped me build a compelling case for why Methodify needed a user-centered approach.

Revealing Actionable Insights

By synthesizing all the user data I gathered, I uncovered a few key points:

  • Our team had been investing heavily in the process of creating a survey/experiment, which was a non-critical area for retention

  • The reporting UX was by far the most critical to users, but had been neglected in favor of survey creation.

User Scenario Map showing frustrations with the previous reporting UX

User Journey Map showing how users want to use our app

Example of initial resistance

Driving Collaboration and Innovation

To bring research into action, I facilitated workshops to align cross-functional teams and brainstorm solutions. By leveraging prioritization matrices, I guided the team to focus on features with the highest user impact.

I even took on product management responsibilities, writing user stories, defining acceptance criteria, and collaborating closely with the engineering team. These efforts streamlined workflows, reduced back-and-forth, and accelerated the time to ship features.

Photo at the end of a brainstorming workshop

Prioritization Matrix used to align on high-impact features

Focusing on Key Features

Although I had designed numerous features in my two years with Methodify, I wanted to highlight the work that most directly improved customer retention.

Reporting 2.0

Identifying and Solving the Real Problem

The original reporting feature was clunky, unintuitive, and failed to address user needs for data manipulation and storytelling. My research revealed that users relied heavily on exporting data to tools like PowerPoint, which created unnecessary friction in their workflows. To address this, I reimagined the Reporting UX with a focus on:

  • Data flexibility: Empowering users to filter, customize, and visualize data directly within the platform.

  • Ease of storytelling: Simplifying the creation of polished, client-ready reports.


Before diving into my process, here is a quick side-by-side comparison of the reporting page:

Designing and Validating

Before beginning my designs, I conducted a thorough UX audit and used my research findings to develop a low-fidelity prototype. This enabled me to validate the new workflowers with usability tests, and I incorporated the feedback into subsequent mockups. The redesign improved clarity, usability, and efficiency, contributing to improved customer satisfaction and retention.

Annotations of initial Reporting Page, identifying problems

Scaling Success with Story Builder

With the foundation of Reporting 2.0 in place, I expanded on its capabilities by designing Story Builder with users’ familiarity of tools like PowerPoint in mind.

By manipulating data in Reporting 2.0, Story Builder could import such data to craft their own narratives from within the app — effectively addressing the critical user need for seamless storytelling.

Key takeaways

  1. Advocacy through collaboration: By working closely with cross-functional teams, I was able to align the company around user needs. Interestingly, the engineering team was much more receptive than leadership to the workflow changes, which helped build momentum for a user-centered approach.

  2. The benefit of wearing many hats: Acting as a de facto product manager (and UX researcher), I bridged gaps between design, engineering, and leadership. This multifaceted role ensured alignment across teams and streamlined product development.

  3. Implement analytics early: Without early analytics, we lacked baseline data to measure critical user behaviors. Introducing analytics sooner would have provided valuable insights into how design iterations influenced user sentiment and engagement over time.

  1. Advocacy through collaboration: By working closely with cross-functional teams, I was able to align the company around user needs. Interestingly, the engineering team was much more receptive than leadership to the workflow changes, which helped build momentum for a user-centered approach.

  2. The benefit of wearing many hats: Acting as a de facto product manager (and UX researcher), I bridged gaps between design, engineering, and leadership. This multifaceted role ensured alignment across teams and streamlined product development.

  3. Implement analytics early: Without early analytics, we lacked baseline data to measure critical user behaviors. Introducing analytics sooner would have provided valuable insights into how design iterations influenced user sentiment and engagement over time.