Google Tasks
Three ways to plan in Google Tasks, and 4 of 5 testers would use them
- Role
- Product Designer
- Team
- Product Designer
- Scope
- Research, Interaction Design, Prototyping, Usability Testing
- Timeline
- 2025

Overview
Google Tasks was one of the first task apps I used. I loved its simplicity, but as my responsibilities grew, I found myself moving to more powerful tools, only to keep returning.
Over seven weeks, I explored how Google Tasks could offer more organizational flexibility without losing what made it appealing.
I designed and tested a sorting and grouping feature within Google's Material Design language, drawing on familiar patterns from Gmail and Google Calendar.
The idea: change how you see your tasks without changing how they're stored.
Problem
Easy to capture. Harder to plan.
Google Tasks makes capturing work effortless, but reviewing responsibilities across separate lists requires more effort.
A student might want to see assignments by class while studying, then switch to upcoming deadlines when planning their week.
The tasks haven't changed. Their priorities have.
How might we make Google Tasks more flexible without sacrificing its simplicity?

Solution
One task list. Multiple perspectives.
I designed a system that lets people switch between three views without reorganizing their tasks.
- By List: Group tasks by class or project.
- By Due Date: Compare deadlines across lists.
- Next Week: See what's coming up.
An All Tasks view brings everything together, while a Gmail-inspired side panel houses the organizational controls.
The familiar add button remains accessible, and existing interactions like swiping to complete or dragging tasks between lists support everyday management.
No new tags, categories, or setup required.


Process
01 / Understanding how people organize
People wanted flexibility, but not another system to maintain.
I began by trying to understand what users value in their task management app, I interviewed four students and early-career professionals, ages 22–25, who used Google Tasks, Notion, or Apple Reminders.

Quick capture worked well, but planning meant comparing deadlines and responsibilities across different lists.
The opportunity was to make existing task information useful in more situations, rather than asking people to organize everything again.
02 / Finding the right moment for organization
My first concepts asked people to organize too early.
Three participants tested low-fidelity concepts that introduced organizational choices during onboarding and task creation.

Both approaches interrupted the primary goal: capturing a task quickly.
I moved the controls into the task view, allowing people to switch perspectives when reviewing their workload.
"I change my view on tasks everyday, sometimes I want to see the ones due in the next week, sometimes I want to see them by class, it changes everyday."
— Riya, Testing Participant
Organization needed to adapt to the moment, not become another upfront decision.
03 / Designing within Google's ecosystem
Making the feature feel native, not added on
Research revealed no strong preference for a particular task organization system. Rather than introducing an entirely new interaction model, I looked to Google's existing ecosystem for familiar patterns.
I audited Gmail and Google Calendar, studying how they approached navigation, grouped controls, and persistent actions. These patterns informed the side panel and placement of the primary create action.
Working within Material Design also meant recreating components that weren't publicly available in Figma. Using Google's interfaces as references, I built them from scratch to maintain consistency across the prototype.
The goal was to make the new functionality feel like a natural extension of Google Tasks, rather than a separate feature layered on top.

04 / Balancing flexibility and simplicity
More options don't always create a better experience.
I compared Apple Reminders and TickTick to understand how other task managers exposed organizational features.
TickTick demonstrated the possibilities of extensive customization, but also the risk of overwhelming a lightweight experience.
I chose a smaller set of views, keeping additional controls in the side panel rather than competing with task content.
Two participants with different task-management habits tested the revised navigation. I also explored showing only the three to five most urgent tasks, but excluded that direction from the final concept.
Outcomes
4 of 5 participants would use the concept
Five participants evaluated the final prototype, including people who had tested earlier iterations. Four said they would use it.
The fifth wanted greater customization, highlighting the trade-off between simplicity and personal control.
"I would go back to Google Tasks with these features. Allowing me to see my tasks in multiple views is why I switched to my current app."
— Aisha, Testing Participant
I kept the final concept focused and identified deeper customization as a future opportunity.
These results indicate interest, not measured long-term adoption.
Reflection
Familiarity is a design constraint worth embracing.
If I revisited this project, I'd audit Google's existing interaction patterns before beginning wireframes.
Recreating Material Design components taught me to look beyond visual consistency and understand how familiar systems behave.
My biggest takeaway: flexibility doesn't always mean adding more. Sometimes it means making better use of what's already there.
You're a curious one!Let's talk