Ben

Product strategy, research

Goal
Scale the number of clients the company is able to serve in a given amount of time.
Problem
Lot of manual work and resources needed to set up the environment and tweak the linguistic analysis for new projects
Solution
Improve automations and data sharing between projects, let user setup their own dashboard. How: creation of a shared data lake of product reviews
Stakeholders
Internal: operation specialist, linguists, pre-sale engineer.External: power users
Team
Cross-disciplinal team: engineers, PM, Operation Specialist, Linguists
My role in the project
UX Designer
When
Dec 2021 → Apr 2022

This case study is an ongoing project. I’ve decided to release even unpolished material, hoping that it could provide value and entice conversations.

Last update: October 11, 2022

Process

  • Business requirements
  • Information gathering
  • Problem Definition
  • Idea generation
  • Idea design & validation
What actually happened
  • Business requirement
  • Goal
  • OKR
  • Some internal research to understand the flow AS-IS
  • Stakeholder analysis, Personas
  • Created an OOUX diagram
  • Service blueprint to understand As-Is flow
  • Drafted flow To-Be
  • Understanding value: what to reach and when to stop
  • collected features, clustered by releases
  • Validation with stakeholder
  • Started creating Epics and user stories
  • Creating low level flows and validated with stakeholder
As is process mapping — seen from the perspective of a dev team supporting linguistic team
Mapping actors and relationship
The Object Oriented UX technique was useful to describe how different objects in a system interact with each other
A user flow to be validate
Flow Validation recap

Techniques and design deliverables

  • Discovery workshop
  • Stakeholder analysis
  • OOUX diagrams
  • User flow and use cases
  • Contributed creating the roadmap: Initiatives, epics, user stories
Outcome of the first workshop. We defined use cases, milestones, challenges
Initially i tried to map use cases with service blueprint, but it turned out not to be the effective tool given the resources
User flow
Airtable database to store research insights, my understanding of the system, stakeholder, use cases. It eventually evolved into an high level roadmap

Results and outcomes

  • Simplified linguistic analysis process
  • Creation of a product review data lake
  • Reduced 3x worker-days for setup
  • Envisioned the self service experience (interaction/UI case study— which has enabled to deliver 2x more frequently)
Hi-level list of milestones in the releases
Breakdown of epics roadmap
User flow
URL management panel, the access point to query URL to the data lake

What I learned

  • Shared understanding is pivotal to productive conversation
  • Facilitation is about letting other people shine.
  • Async communication is a very powerful when documenting complex project
Loom over loom over loom

Want more case studies?!

← Design system
Interaction, UI →