home
hello
homemax
pixel

2019

2020

INTRODUCTION

INTRODUCTION

Several software applications and tools aid Google's test engineers, business stakeholders and product manufacturers to have a greater visibility into the Google's hardware product development workflows. I'm contributing to these efforts by designing experiences that matters to the users most.

Why is this project important?
Achieve high quality Google hardware products that reach hands of millions around the globe.

Users
Google's engineers, business stakeholders, product manufacturers

Goal of this project
Transform complex and massive amounts of manufacturing data into actionable insights, provide visibility into data patterns.
 

My approach in short
A sprint based design process. Working closely with engineers, PMs, and business stakeholders while continuously iterating with the feedback.

 

Several software applications and tools aid Google's test engineers, business stakeholders and product manufacturers to have a greater visibility into the Google's hardware product development workflows.

Why is this project important?
Achieve high quality Google hardware products that reach hands of millions around the globe.

Users
Google's engineers, business stakeholders, product manufacturers

Goal of this project
Transform complex and massive amounts of manufacturing data into actionable insights, provide visibility into data patterns.
 

My approach in short
A sprint based design process. Working closely with engineers, PMs, and business stakeholders while continuously iterating with the feedback.

 

Several software applications and tools aid Google's test engineers, business stakeholders and product manufacturers to have a greater visibility into the Google's hardware product development workflows.

Why is this project important?
Achieve high quality Google hardware products that reach hands of millions around the globe.

Users
Google's engineers, business stakeholders, product manufacturers

Goal of this project
Transform complex and massive amounts of manufacturing data into actionable insights, provide visibility into data patterns.
 

My approach in short
A sprint based design process. Working closely with engineers, PMs, and business stakeholders while continuously iterating with the feedback.

 

Several software applications and tools aid Google's test engineers, business stakeholders and product manufacturers to have a greater visibility into the Google's hardware product development workflows.

Why is this project important?
Achieve high quality Google hardware products that reach hands of millions around the globe.

Users
Google's engineers, business stakeholders, product manufacturers

Goal of this project
Transform complex and massive amounts of manufacturing data into actionable insights, provide visibility into data patterns.
 

My approach in short
A sprint based design process. Working closely with engineers, PMs, and business stakeholders while continuously iterating with the feedback.

 

Several software applications and tools aid Google's test engineers, business stakeholders and product manufacturers to have a greater visibility into the Google's hardware product development workflows.

Why is this project important?
Achieve high quality Google hardware products that reach hands of millions around the globe.

Users
Google's engineers, business stakeholders, product manufacturers

Goal of this project
Transform complex and massive amounts of manufacturing data into actionable insights, provide visibility into data patterns.

My approach in short
A sprint based design process. Working closely with engineers, PMs, and business stakeholders while continuously iterating with the feedback.

 

Due to NDA associated with this project, I cannot disclose complete details about design process, deliverables.

Due to NDA associated with this project, I cannot disclose complete details around design process, deliverables.

MY ROLE

MY ROLE

During the design process, I had the opportunity to work with UX designers, Program managers, Engineers, and other stake holders to craft experiences for Google's internal applications and tools.

During the design process, I had the opportunity to work with UX designers, Program managers, Engineers, and other stake holders to craft experiences for Google's internal applications and tools.

my role – desk 01

THE CHALLENGE

MY ROLE

Huge amount of manufacturing data is gathered for several products during their mass production, prototyping phases. As it was crucial to explore and understand this data, it presented challenges in terms of inconsistent data specifications, inefficient access modes and data security.

A race to minimize product returns by manufacturing quality ones was always on. This in turn put more pressure on the need to address existing problems as early as possible.

My goal was to overcome data hurdles and establish a clear plan for design process.

During the design process, I had the opportunity to work with UX designers, Program managers, Engineers, and other stake holders to craft experiences for Google's internal applications and tools.

RESEARCH AND INSIGHTS

MY ROLE

With the help of my awesome teammates and easy-to-reach end users, I was able to aggregate research data to form my first insights.

  • Semi-structured interviews
  • Lab visits to understand user's work environment, process, equipments used
  • Shadowed users to understand their Day-in-the-life-of-a-user.

 

During the design process, I had the opportunity to work with UX designers, Program managers, Engineers, and other stake holders to craft experiences for Google's internal applications and tools.

INITIAL INSIGHTS

INITIAL INSIGHTS

  • Longer orientation for first-time users as a result of numerous tools, applications, visualization libraries.
  • Inexistence of data specification led to out-of-sync user operations.
  • Product managers disliked the data-intensive/engineering centric experience of the tools, applications.
  • Engineers perceived data-intensive applications are more efficient and less clicks means good usability.
  • Users often had hard time  translating feature-based questions into numerous data search filters on the dashboards.
Boardwork

Affinity mapping research data. Validating and converging ideas from the brainstorm session

THE PROBLEM

MY ROLE

The tools and applications that are employed to analyze data posed a constant need to technical know-how from non-technical users such as vendors and product managers. Also, they led to inconsistencies in data specifications defined in different teams.

While users look at data with feature-based queries, data failed to support that, instead required users to pick several parameters/attributes everytime.

"How might we design for feature-based insight exploration and support high-level glanceable view alongside data-intensive dashboard?" 

 

During the design process, I had the opportunity to work with UX designers, Program managers, Engineers, and other stake holders to craft experiences for Google's internal applications and tools.

OUR SOLUTION - 'Quantum'

MY ROLE

We designed an enterprise web application with both internal and external Google users in mind.

During the design process, I had the opportunity to work with UX designers, Program managers, Engineers, and other stake holders to craft experiences for Google's internal applications and tools.

Top insights

Leveraging the power of AI/Machine learning to synthesize high-level insights that are glanceable, quick and most-value added to our users.

Based on our research, users' top preferences and decision targets indicated Trends, Yield and Failures important picks for top insights.

top insights 2

Feature-based data exploration

An intuitive, simple and conversational way to explore manufacturing data without the need to force users to deal with data complexity.

narrative query

Intuitive way to explore patterns in multi-dimensional data

In-app supported visualization capabilities to enable users to explore data both at high-level and in-depth.

CPK

DESIGN PROCESS

DESIGN PROCESS

We emphasized on using the Google's material design system for Quantum and following our initial insights, problem statement at hand, we dived straight into creating personas and user journeys.

Considering we had several users, personas helped us focus on particular users to whom this solution would matter most. We employed 'Product playbook' and 'Critical User Journeys' to surface user goals, motivations, pivotal journeys Vs frequent journeys. This in turn paved a way to empathize with users (Understand contextual details) and not just user inputs.

PERSONAS

We identified two user profiles - Test engineer, Product manager
Test engineers mostly hold specific responsibilities and often explore data in-depth and are technical savvy. On the other hand, Product managers are interested in high-level insights for a specific product and create opportunities to put forward cost-effective solutions in manufacturing process.

Test Engineer
Product Manager

USER JOURNEY MAPS

To better understand design opportunities, we created CUJs and maps spotting pain points and which aspects drive user motivations at task level.

Journey map

Journey maps exploring scenario-based opportunities for introducing design solutions. Primarily, the users' journey was split between four phases.

SKETCHES & MOCKUPS

REFLECTIONS

The UI layout is composed with side navigation panel as a primary navigation within the application. Additionally, the breadcrumbs at the top serve as the placeholder for intermediate pages. While the default landing page would show top insights comprised of three items, users have the ability to drill-down data of interest.

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

first sketch
second sketch

We explored some of the dashboard ideas with yield trends, factory production trend and having high-level details about build schedule. Along with this, we narrowed down on data-centric view of Quantum

20 A Quantum Copy 5

CONVERGING ON IDEAS

REFLECTIONS

FOCUS ON WHAT IS NECESSARY

In contrast to showing a detailed table with 20+ columns of data, we picked collapsible records view that only surfaces necessary data enabling quick and easy user decisions.


Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

20 A Quantum Copy

 


Vs

 Vs

20 A Quantum Copy 2

CAPTURING RELATIVE MEANINGS IN DATA

While we ideated on visualizations to explore device tests in production and reliability phases, we inclined towards plot that was easier to surface relative measurments between tests in both the phases.

 

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

20 A Quantum Copy 3

 


Vs

 Vs

20 A Quantum Copy 4

ACCESSIBILITY

REFLECTIONS

Adopted Google's accessibility guidelines along with A11Y to achieve inclusive design. We approached each UI component and visualization in particular for the initial release of Quantum.


Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

colorblind02
colorblind03
colorblind01

IMPACT

REFLECTIONS

Migration of Quantum outside to other teams

Radical ideas first

Other teams at Google adopted Quantum's experience for structuring and exploring data

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

Higher unit production per day - increase by 18% of overall production

Radical ideas first

With more informed decisions enabled by Quantum's adoption, hardware products manufacturing showed 18% increase in later month.

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

Lower troubleshooting times - decrease by 1.5 hours for stations issues

Radical ideas first

Having the ability to explort data from Quantum outside and being able to quickly explore data patterns reduced test engineer debug times by 1.5 hours for station related problems at the factory.

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

REFLECTIONS

REFLECTIONS

Radical ideas first

Radical ideas first

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

Exploring constraints through radical concepts leads to positioning our perspectives in the best spot and early during the design process.

Purpose over features

Purpose over features

Users don't care how many features the product has if they can't use the product to fulfill their purpose or goals.

Users don't care how many features the product has if they can't use the product to fulfill their purpose or goals.

Best solutions take time

Best solutions take time

Brainstorming sessions often fail as our knowledge can be limited during that time. For ideas to mature and work better, it takes time and constant improvements.

Brainstorming sessions often fail as our knowledge can be limited during that time. For ideas to mature and work better, it takes time and constant improvements.

© 2020 Pruthviraj

© 2019 Pruthviraj