Internship
Internal Notes
A documentation log to increase users' confidence and ability to troubleshoot during data pipeline maintenance.
Internship
Internal Notes
A documentation log to increase users' confidence and ability to troubleshoot during data pipeline maintenance.
Internship
Internal Notes
A documentation log to increase users' confidence and ability to troubleshoot during data pipeline maintenance.
Timeline
3 months
Jun-Aug 2024
Company
Shipt
Role
Product Designer
Team
Walt, Product Manager
Katie, Data Analyst (user)
Timeline
3 months
Jun-Aug 2024
Company
Shipt
Role
Product Designer
Team
Walt, Product Manager
Katie, Data Analyst (user)
Timeline
3 months
Jun-Aug 2024
Company
Shipt
Role
Product Designer
Team
Walt, Product Manager
Katie, Data Analyst (user)
Context
A look into Shipt's online marketplace
During my internship with Shipt's Internal Tools design team, I got to know the ins and outs of catalog operations. I learned how important it is for the data that retailers send over—like product names, inventory, and prices—to be correct when it's shown to customers on Shipt's marketplace.
Context
A look into Shipt's online marketplace
During my internship with Shipt's Internal Tools design team, I got to know the ins and outs of catalog operations. I learned how important it is for the data that retailers send over—like product names, inventory, and prices—to be correct when it's shown to customers on Shipt's marketplace.
Context
A look into Shipt's online marketplace
During my internship with Shipt's Internal Tools design team, I got to know the ins and outs of catalog operations. I learned how important it is for the data that retailers send over—like product names, inventory, and prices—to be correct when it's shown to customers on Shipt's marketplace.
Problem
Fixing bugs in a data pipeline is challenging without documentation of previous changes
Shipt's Catalog team loads retailer data onto the Shipt marketplace. However, when working on the data pipeline, the team often has to guess how it operates, leading to delays during troubleshooting.
Problem
Fixing bugs in a data pipeline is challenging without documentation of previous changes
Shipt's Catalog team loads retailer data onto the Shipt marketplace. However, when working on the data pipeline, the team often has to guess how it operates, leading to delays during troubleshooting.
Problem
Fixing bugs in a data pipeline is challenging without documentation of previous changes
Shipt's Catalog team loads retailer data onto the Shipt marketplace. However, when working on the data pipeline, the team often has to guess how it operates, leading to delays during troubleshooting.
Design Question
How might we enable Catalog Operations to record and share knowledge during the data pipeline process?
How might we enable Catalog Operations to record and share knowledge during the data pipeline process?
How might we enable Catalog Operations to record and share knowledge during the data pipeline process?
Solution
A way to add documentation streamlining users' workflows.
Internal Notes allow users to record changes made to a retailer's data pipeline.
Uncovering the Who, what, where, why, and how
Research
Uncovering the Who, what, where, why, and how
Research
Uncovering the Who, what, where, why, and how
Research
Who are the users?
The Catalog Operations team loads retailers’ data onto Shipt’s marketplace
👤 Catalog Operations
Objective: Ingest, clean, and transform data from retailers.
Actions: Implement business logic in data pipeline such as in-store purchase limits and promotions on items.
Who are the users?
The Catalog Operations team loads retailers’ data onto Shipt’s marketplace
👤 Catalog Operations
Objective: Ingest, clean, and transform data from retailers.
Actions: Implement business logic in data pipeline such as in-store purchase limits and promotions on items.
Who are the users?
The Catalog Operations team loads retailers’ data onto Shipt’s marketplace
👤 Catalog Operations
Objective: Ingest, clean, and transform data from retailers.
Actions: Implement business logic in data pipeline such as in-store purchase limits and promotions on items.
Painpoints
What I learned from 3 discovery sessions with users
Painpoints
What I learned from 3 discovery sessions with users
Painpoints
What I learned from 3 discovery sessions with users
🔨
Lack of centralized documentation
There isn’t current documentation outside of scattered Slack messages.
🔨
Lack of centralized documentation
There isn’t current documentation outside of scattered Slack messages.
🔨
Lack of centralized documentation
There isn’t current documentation outside of scattered Slack messages.
ℹ️
User benefits
Users will experience easier information sharing and increased confidence in troubleshooting.
ℹ️
User benefits
Users will experience easier information sharing and increased confidence in troubleshooting.
ℹ️
User benefits
Users will experience easier information sharing and increased confidence in troubleshooting.
⏰
Inefficient troubleshooting
Users spend additional time trying to locate and understand historical information. This makes it challenging to maintain retailer pipelines.
⏰
Inefficient troubleshooting
Users spend additional time trying to locate and understand historical information. This makes it challenging to maintain retailer pipelines.
⏰
Inefficient troubleshooting
Users spend additional time trying to locate and understand historical information. This makes it challenging to maintain retailer pipelines.
UX AUDIT
Exploring existing design patterns
There are already existing instances of notes in other parts of Shipt's admin tool. These served as a reference point as I considered what changes were needed to tailor the feature to my specific use case.
UX AUDIT
Exploring existing design patterns
There are already existing instances of notes in other parts of Shipt's admin tool. These served as a reference point as I considered what changes were needed to tailor the feature to my specific use case.
UX AUDIT
Exploring existing design patterns
There are already existing instances of notes in other parts of Shipt's admin tool. These served as a reference point as I considered what changes were needed to tailor the feature to my specific use case.
USER FLOW
Defining the entry point to the Notes feature
From user interviews and shadowing, I learned more about the technical data pipeline process to figure out when and where the Notes feature would be exist.
USER FLOW
Defining the entry point to the Notes feature
From user interviews and shadowing, I learned more about the technical data pipeline process to figure out when and where the Notes feature would be exist.
USER FLOW
Defining the entry point to the Notes feature
From user interviews and shadowing, I learned more about the technical data pipeline process to figure out when and where the Notes feature would be exist.
Designing through feedback loops
Design deep dive
Designing through feedback loops
Design deep dive
Designing through feedback loops
Design deep dive
Entry point
Goal
Users want to have context before working on the data pipeline.
Solution
Distinguish notes from the existing wizard flow.
Entry point
Goal
Users want to have context before working on the data pipeline.
Solution
Distinguish notes from the existing wizard flow.
Entry point
Goal
Users want to have context before working on the data pipeline.
Solution
Distinguish notes from the existing wizard flow.
Note visibility
Goal
Users want to have context before working on the data pipeline.
Solution
Display a preview of notes at the top of the page to boost visibility without using too much space.
Note visibility
Goal
Users want to have context before working on the data pipeline.
Solution
Display a preview of notes at the top of the page to boost visibility without using too much space.
Note visibility
Goal
Users want to have context before working on the data pipeline.
Solution
Display a preview of notes at the top of the page to boost visibility without using too much space.
Badges
Goal
Users need to distinguish between different kinds of notes.
Solution
Badges call out which notes are the launch and which are most recent.
Badges
Goal
Users need to distinguish between different kinds of notes.
Solution
Badges call out which notes are the launch and which are most recent.
Badges
Goal
Users need to distinguish between different kinds of notes.
Solution
Badges call out which notes are the launch and which are most recent.
Design Question
“It'd helpful to see all notes at once. I need to quickly read through everything that has happened in the past to get up to speed on how this pipeline works today.”
Design Question
“It'd helpful to see all notes at once. I need to quickly read through everything that has happened in the past to get up to speed on how this pipeline works today.”
Design Question
“It'd helpful to see all notes at once. I need to quickly read through everything that has happened in the past to get up to speed on how this pipeline works today.”
Before and after
Summarizing the main changes
The final feature would entail adding a new section on the retailer details page to house the notes.
Before and after
Summarizing the main changes
The final feature would entail adding a new section on the retailer details page to house the notes.
Before and after
Summarizing the main changes
The final feature would entail adding a new section on the retailer details page to house the notes.
What's the Impact?
Helping users and meeting business objectives
I handed the design off to engineering. This feature is currently in development and we anticipate the following outcomes upon launch:
What's the Impact?
Helping users and meeting business objectives
I handed the design off to engineering. This feature is currently in development and we anticipate the following outcomes upon launch:
What's the Impact?
Helping users and meeting business objectives
I handed the design off to engineering. This feature is currently in development and we anticipate the following outcomes upon launch:
🚀
Immediate user adoption
At launch, 5 users will immediately start using the Notes feature. Within the next 6-9 months, we expect 15 additional users to adopt the feature.
🚀
Immediate user adoption
At launch, 5 users will immediately start using the Notes feature. Within the next 6-9 months, we expect 15 additional users to adopt the feature.
🚀
Immediate user adoption
At launch, 5 users will immediately start using the Notes feature. Within the next 6-9 months, we expect 15 additional users to adopt the feature.
📈
Business impact
The Notes feature will support the launch of 10 new retailers onto the Shipt marketplace in Q3 2024.
📈
Business impact
The Notes feature will support the launch of 10 new retailers onto the Shipt marketplace in Q3 2024.
📈
Business impact
The Notes feature will support the launch of 10 new retailers onto the Shipt marketplace in Q3 2024.
🛠️
User benefits
Users will experience easier information sharing and increased confidence in troubleshooting.
🛠️
User benefits
Users will experience easier information sharing and increased confidence in troubleshooting.
🛠️
User benefits
Users will experience easier information sharing and increased confidence in troubleshooting.
User Feedback
“This feature would make understanding the logic of the retailer’s data pipeline extremely quick and easy.”
User Feedback
“This feature would make understanding the logic of the retailer’s data pipeline extremely quick and easy.”
User Feedback
“This feature would make understanding the logic of the retailer’s data pipeline extremely quick and easy.”
Reflection
My second summer at Shipt...
Challenges
Predicting user behavior was difficult without a current documentation process for reference.
My initial user flow assumption was incorrect. I had to be open to redirection and adapt my design.
Understanding the technical data pipeline was key to accurately capturing user needs.
Successes
Effectively handed off the design file to engineering after considering technical limitations.
Collaborated successfully with PMs and users using FigJam.
Worked efficiently within a scrum team for the first time.
Overall, my return internship at Shipt was a fantastic experience. I reconnected with coworkers, deepened my design skills, and gained confidence working cross-functionally. Thanks to my team for making it such a rewarding time!
Reflection
My second summer at Shipt...
Challenges
Predicting user behavior was difficult without a current documentation process for reference.
My initial user flow assumption was incorrect. I had to be open to redirection and adapt my design.
Understanding the technical data pipeline was key to accurately capturing user needs.
Successes
Effectively handed off the design file to engineering after considering technical limitations.
Collaborated successfully with PMs and users using FigJam.
Worked efficiently within a scrum team for the first time.
Overall, my return internship at Shipt was a fantastic experience. I reconnected with coworkers, deepened my design skills, and gained confidence working cross-functionally. Thanks to my team for making it such a rewarding time!
Reflection
My second summer at Shipt...
Challenges
Predicting user behavior was difficult without a current documentation process for reference.
My initial user flow assumption was incorrect. I had to be open to redirection and adapt my design.
Understanding the technical data pipeline was key to accurately capturing user needs.
Successes
Effectively handed off the design file to engineering after considering technical limitations.
Collaborated successfully with PMs and users using FigJam.
Worked efficiently within a scrum team for the first time.
Overall, my return internship at Shipt was a fantastic experience. I reconnected with coworkers, deepened my design skills, and gained confidence working cross-functionally. Thanks to my team for making it such a rewarding time!