top of page

Reseach samples

Sample 1

Company: Microsoft.

Role: Lead UX researcher.

Problem: Previous UXR studies have concluded that the current speech pricing page is confusing for users.

Goal: Make it easier for users to navigate the pricing page and understand the pricing options.

Study Design

I did content analysis for the current page and worked with the design team to come up with 3 prototypes where we addressed the challenges that were found in the content analysis. The study was a moderated one with a pilot session and 6 users from UserTesting.com. The users were given a link to the 3 prototypes and asked to complete 3 tasks (easy, medium, difficult), to understand their comprehension of navigating the price options. There were 3 parameters in the study design:

  • 3 prototypes (A, B, C)

  • 3 tasks to complete

  • 6 participants

Counterbalancing was used in the experiment to avoid the introduction of confounding variables. There were no participants that follow the same order of tasks, nor follow the same order of prototypes.

Success metrics

  • Tasks success

  • Ease of use (Single Ease Question SEQ)

  • Time spent solving the tasks (we also relied here on our observation of the session as some users might be slower than others in navigating)

Impact

I analyzed the findings and shared the results with the design and the product teams. The new design for the speech pricing page has better user experience in exploring and calculating the prices. The findings will affect the design of the pricing pages for all services across the Azure platform.

Sample 2

Company: Microsoft.

Role: Lead UX researcher.

Problem: Usability of MS365 Business.

Goal: Identify usability issues to improve the product and provide better experience for customers.

Study Design

Heuristics evaluation and expert reviews. In addition, a competitor analysis was needed to compare the experience in MS365 Business to other products’ experiences in the market. I used Jakob Nielsen's 10 general principles for interaction design to identify the usability issues, and I summarized the finding in a rainbow spreadsheet. I conducted 5 expert reviews with stakeholders from the design, the product, and the engineering teams where I was thinking loud as an end-user and going through different interfaces in MS365 Business and other products, followed up with discussion with the group

Impact

A list of usability issues and suggestions to improve the experience prioritized as (High – Medium – Low). These issues were addressed by MS365 product and engineering teams and updated to all customers.

Sample 3

Company: LexisNexis Risk Solutions.

Role: Lead UX researcher.

Problem: LexisNexis was introducing a new venture -Gravitas network- that aims to unlock the power of real-world data (RWD) for healthcare. Research was needed to get insights about potential customers and the value we are adding to the market.

Goal: identify personas, paint points and needs, and create wireframes for the tool that the end-user uses to interact with the network.

Study Design

Generative research to understand the problem and address it. I conducted secondary research and interviews with internal stakeholders and led meetings with external stakeholders to define personas, pain points and needs. I also ran a design workshop. I was working closely with the product team to translate the research findings into features, and with the design team to create user interfaces based on the findings.

Impact

I identified personas and their pain points and needs in the market, features, and the UI design for CAT (Cohort Analysis Tool) that is used by users to interact with the Gravitas network.

Sample 4

Company: SLB

Role: Lead UX researcher.

Problem: SLB aims to build an integrated solution for all customers in oil and gas, for Cross-domain workflows where data is needed from both Production and Subsurface systems. It’s a new solution and there is not much research done in this direction.

Goal: Identify Cross-domain workflows scenarios, personas, end-users' need and pain points. In addition, identify the Data types that are exchanged between Production and Subsurface systems in each cross-domain workflow.

Study Design

Generative research to understand the problem and address it. I I conducted secondary research and ran 2 workshops with production and subsurface stakeholders. The production stakeholders were asked about scenarios where they need data from the subsurface domain and vice versa (including personas, pain points and needs). Some of the workshops’ participants were interviewed later to clarify points that were raised during the workshops. I also interviewed the engineering team to collect technical insights about the data types and mechanism in exchanging data between domains.

Impact

I identified 5 cross-domain workflows with the personas, pain points and needs that were shared with different teams to evaluate the business value in the market. I also identified 6 engineering approaches to address the data exchange in cross-domain workflows based on the customers settings (on-prem, hybrid, on-cloud)

bottom of page