Google Drive
Feature Add
Project Overview
Google Drive is widely loved for document creation, sharing, and real-time collaboration. However, as Drive becomes the default workspace for individuals and businesses alike, its file-management tools lag behind competitors like Finder, OneDrive, and iCloud Drive.
This project explored how Google Drive could better support organization, sorting, searching, and file movement (especially for users working inside large, deeply nested file systems).
Role
UX Designer
Timeline
1 month
Jump to Section
Empathize
Competitive Analysis
|
User Interviews
|
Secondary Research
The inspiration for this project was frustration. Specifically, I was tired of an angry red popup-
Hypothesis
Google Drive doesn’t give many options for bulk deletion so most people must struggle with clearing out old files.
There should be bulk deletion options!
Is bulk deletion a widely desired feature?
To find out, I looked to the competitors!
But much to my surprise, I found that Google Drive’s limited bulk deletion options were pretty similar across different platforms.
OneDrive
Deletion
- Bulk select same level of discoverability as Google Drive
Strengths
- Clear and structured layout
- Familiar, native system feel
What We Can Learn
- Make cloud file organization feel predictable and consistent
finder
Deletion
- Bulk select same level of discoverability as Google Drive
Strengths
- Visible tree views
- Clear breadcrumbs
- Efficient keyboard shortcuts
What We Can Learn
- Make hierarchy visible at all times
- Ensure file paths are easy to scan
ICLOUD
Deletion
- Bulk select same level of discoverability as Google Drive
Strengths
- Tags for flexible organization
- Smart folders for dynamic grouping
What We Can Learn
- Reduce reliance on deep folder nesting
- Offer alternative ways to organize files
Was it industry standard to not make deletion more obvious to users then? Did users not care about bulk deletion?
Noting the strengths and weaknesses of competitors, I started looking for firsthand information through community forums and direct user interviews
Instead of complaints about deletion, I found complicated opinions on the following areas:
It turned out, my hypothesis was wrong! Users didn’t care about deletion because they could just make a new account.
Define
Affinity Map
|
Persona
|
Problem Statement
So what are the real problems?
Grouping direct participant feedback revealed a completed different theme than I had originally suspected.
Notably, concerns about deleting files or storage limits appeared infrequently and lacked urgency.
Instead, users consistently emphasized the need to find, sort, and organize files more easily. This insight corrected the initial hypothesis and clarified that the real problem was not cleanup, but discoverability and organizational clarity.
Next I turned the research into a primary user persona to make sure our design decisions stayed grounded in real user needs.
Considering these priorities, we established the following problem statement:
How might we help high-volume Google Drive users
organize and access files more efficiently?
Ideate
Feature List
|
MoSCoW & Effort v Value Matrix
|
User Flows
With many problems clearly defined,
I began prioritizing.
What are the most critical elements to focus on?
Potential Features
Based on user research and pain points, I identified 6 potential features that could improve the experience:
Breadcrumbs
users can only see the parent folder, not their full path
Smart Search Filter Chips
advanced search features are hidden and underused
Bulk Actions
many users don’t know bulk actions are available
Bulk Actions Within Apps
users must return to Drive to manage files
Custom View Columns
cannot sort by file size or date created
“Move to…” Dialog
users can’t see the full destination path
Evaluate
Effort vs. Value Matrix
The MoSCoW method prioritizes features as Must, Should, Could, or Won’t Have, helping teams focus on what’s critical versus nice-to-have.
Each feature was evaluated based on user impact, technical feasibility, and alignment with project scope.
prioritize
Essential Features by Priority
Features organized by priority level based on the matrix evaluation:
MUST-HAVE
- Persistent breadcrumbs
- Smart search filter chips
- Tree view “Move to…” dialog
NICE-TO-HAVE
- Customizable list views
- In-context sorting options
DEPRIORITIZED
- Batch deletion
- File merging
- Advanced admin actions
Now that we knew what features were most important, we began drafting the user flow for each.
Because Google Drive is a complex, multi-entry system, each proposed feature touches multiple surfaces and states. User flows were created to ensure these features behaved consistently across contexts and did not introduce new friction or ambiguity.
Persistent Breadcrumbs
Breadcrumbs are not just a visual element—they reflect system state. User flows were needed to map how breadcrumbs update as users navigate between folders, use search, open files, or move items. Mapping these paths ensured breadcrumbs remained accurate, persistent, and trustworthy across navigation patterns.
Tree View “Move to…” Dialog
Moving a file is a high-risk action. User flows were essential to map how users expand folders, view hierarchy, confirm destinations, and recover from errors.
Smart Search Filter Chips
Search in Google Drive occurs in multiple contexts: the main Drive view, shared folders, and within creation tools like Docs, Sheets, and Slides. User flows helped define when filter chips appear, how they persist across searches, and how they reset or combine. This prevented filters from feeling hidden, overly complex, or unpredictable, and ensured users always understood why certain results were shown.
Prototype & Test
LofI Wireframes
|
Usability Testing
|
Iterations
With a new process designed, we needed to prototype each screen before creating the interface details.
The focus at this stage was purely on layout, information hierarchy, and task flow efficiency. These wireframes allowed us to test the new progressive layout early and observe whether users understood the flow without UI polish or visual cues.
To validate my changes to the design, I conducted Usability Testing.
Comparative usability tests were conducted to evaluate all three proposed features, with a primary focus on the redesigned “Move to…” dialog and its tree-view structure. Participants completed identical file-organization tasks using both the existing Google Drive flow and the prototype.
80%
Preferred Prototype
45%
Faster Completion
100%
Task Completion
Key Wins
Faster task completion
Users completed file-movement tasks significantly faster with the tree view than with the existing drill-down model.
Increased Confidence
Users reported less hesitation, fewer backtracks, and reduced second-guessing during file movement.
Strong user preference
4 out of 5 participants strongly preferred the prototype over the current Drive experience.
Improved accuracy
Visual hierarchy reduced misplacement errors by making folder relationships explicit.
Afterwards, I again asked for their overall thoughts on the website. Here’s some of what they had to say:
“It’s nice to be able to move in and out faster.”
“That’s way better.”
“Wow, I can actually see where I’m moving it.
“I can visually map it out now.”
Some insights from usability testing informed refinements aimed at reducing friction without increasing complexity.
Post-Testing Improvements
Displaying documents within the tree view (greyed out) to reinforce context without clutter
Adding drag-and-drop support to align with existing mental models
Larger expansion hit areas for easier scanning and interaction
Improved spacing and alignment to increase readability at a glance
Simplified iconography to reduce visual noise and cognitive load
Final Design
High Fidelity Wireframes
|
Mockups
Persistent Breadcrumbs
Previously Google Drive would collapse breadcrumbs after two folders.
With this feature add, persistent breadcrumbs keep users oriented at all times by clearly showing where they are in the folder hierarchy. This reduces unnecessary clicks, prevents disorientation, and builds trust when navigating deep or shared file systems.
Tree View “Move to…” Dialog
The tree view replaces repetitive drilling with a scannable, side-by-side view of folder structure. Users move files faster, make fewer errors, and feel more confident choosing the correct destination.
Smart Search Filter Chips
Smart search filter chips bring advanced filtering directly into Docs, Sheets, and Slides rather than only in Google Drive. By surfacing filters where users already work, search becomes faster, more precise, and less dependent on memory or exact file names.
Impact & Takeaways
Project Impact
Usability testing demonstrated clear improvements compared to the existing Google Drive experience. Participants completed tasks faster, placed files more accurately, and reported higher confidence during navigation and file movement.
The redesigned concepts reduced hesitation, minimized second-guessing, and improved overall orientation within complex folder structures.
Key Metrics
Preferred Prototype
85%
Faster Completion
63%
Task Completion Rate
100%
Reflection
While user experience and visuals are not the same, a bit part of a user experience is dependent on trust. Many interviewees expressed that they would not rent a boat through this website because it was suspicious and they couldn’t trust it to process a card payment.
Additionally, information architecture plays a huge role in what users a willing to learn. Prior to the redesign users didn’t want to know anything extra about Boat Dockter but by making it a structured part of the booking process that only disclosed info as it was relevant to each booking situation, users were not bothered.
1
Users don’t want to delete more — they want to search better
Initial exploration focused on file cleanup, but research revealed that users tolerate clutter as long as retrieval is fast and reliable. Organization and discoverability matter more than reduction.
2
Visibility drives trust
When users can clearly see file hierarchy and location, they feel more confident taking action. Structural clarity reduces hesitation and error-prone behavior.
3
Clarity matters more than minimalism
Minimal interfaces can hide critical context. In high-volume, collaborative environments like Google Workspace, exposing hierarchy at the right moments improves usability without overwhelming users.
Note: I completed this case study in October 2025. In January 2026, Google Drive added breadcrumbs within the “Move to” dialog, aligning with my project’s proposed improvements.