TTASK · Independent Concept · Solo Product Design
Decide less. Do more.
A task & schedule app built on one idea: people don't fail because they have too many tasks — they fail because every list forces another decision.
Working professionals juggle scattered tasks and schedules — capturing and prioritizing work costs too many steps and too much attention.
Solo end-to-end product design: research, information architecture, flows, wireframes, UI, prototype, and iterative usability testing.
All five participants completed the selected task set across both testing phases, with standardized facilitator support available when they became stuck.
Independent concept product — evidence is usability-based; no launch metrics are claimed.
Today, already triaged.
Three lenses on one day — a dashboard that answers “what now?”, a timeline that gives the day a shape, and projects that carry their own priority.
The Problem
Every open list is a decision the user hasn't made yet.
Listening before drawing.
Five one-on-one interviews with people juggling overlapping projects and deadlines — asking not which features they wanted, but where the day actually broke down. Three failures kept surfacing.
- Method
- Semi-structured interviews
- Sample
- n=5
- Recruitment
- Convenience sampling through personal contacts and referrals
- Phase
- Discovery
I feel like a plate spinner in a circus — trying to keep all my tasks up in the air without dropping any. I'm constantly trying to catch up with my own schedule.
Interview participant · working professional
Feeling overwhelmed
The volume of tasks isn't the problem — the lack of a clear starting point is.
Constant interruptions
After every interruption, users rebuilt their plan from memory — the most expensive part of being distracted.
Deadline pressure
Deadlines were known — but urgency stayed invisible until it was too late.
Three rules, from evidence.
Every screen that follows had to pass three principles — anything that didn't was cut.
One glance,
one decision
The dashboard leads with a single progress ring and today's list — everything else stays one level down.
Grounded in“Feeling overwhelmed” — users needed a starting point, not more storage.
Priority is a
first-class object
Stars, color-coded projects, and persistent filters keep importance visible at the moment users choose what to work on.
Grounded in“Deadline pressure” — urgency stayed invisible until it was too late.
Fewer steps,
fewer doubts
Creating a task — title, priority, date, reminder — happens in one sheet, launched from one thumb-reach button on every screen.
Grounded in“Constant interruptions” — recovery has to be cheaper than distraction.
Everything is two taps
from today.
Today sits at the root; projects and tasks organize around it; creation is reachable from everywhere.
Two lenses on the same day — list to act, timeline to plan
Containers for context, never a required detour
Detail exists for editing — not for deciding
One sheet, launched from the center of the tab bar
Utilities stay at the edges of the map
Today is the root — not an inbox
“All tasks” restates the problem. TTASK opens on a day already triaged: what's done, what's next, what can wait.
Creation lives in the center
Capture is the most frequent action, so it takes the most reachable pixel — the raised “+” in the tab bar's center, on every screen.
Five tabs, zero hamburgers
Home, Search, Create, Alarm, Profile — always visible, because hidden navigation is another decision to make.
The structure earned
its pixels.
Grayscale until the architecture stopped changing — navigation problems got solved cheaply, before pixels made them expensive.
01 · Problem — low fidelity
Early frames stored tasks but didn't answer “what now?”
02 · Iteration — mid fidelity
A summary card takes the top slot; the “+” moves to the tab bar's center.
03 · Solution — final UI
The summary becomes a progress ring — hierarchy carried intact from grayscale.
Every interaction removes
a decision.
Recordings of the working prototype — each interaction tested against one question: does it reduce the choices between the user and done?
Decision 01 · Task Creation
One sheet, no wizard
Everything lives on a single sheet with smart defaults — users fill in what matters and skip the rest; there's no “step 2 of 4” to abandon.
OutcomeIn one final-round session, the participant completed the selected capture flow and did not request changes to that flow.
Decision 02 · Project Organization
Projects carry their own color
Creating a project assigns it a priority and a color in the same breath — and that color follows it everywhere: the grid, the dashboard, the timeline.
WhyColor is processed before reading — recognizing a project anywhere becomes a glance, not a label read.
Decision 03 · Priority Management
Triage is one tap, not a re-sort
Every list carries the same persistent filter chips — All, In Progress, Over Due, Priority. Overdue work can't hide in the scroll.
OutcomeIn one final-round session, the participant completed the reprioritization task and requested drag-to-reschedule as an improvement.
Decision 04 · The Day, as a Timeline
The day has a shape
Tasks render as time blocks on a vertical timeline, with a “current” line marking now — users see their capacity, not just their obligations.
WhyAfter an interruption, recovery is a glance at the timeline — nothing to reconstruct from memory.
Decision 05 · Reminders & Detail
Reminders with sensible defaults
The detail page holds what shouldn't interrupt daily triage: repeat rules, reminder timing, categories. Reminders default to “on time of event, one hour before” — a toggle, not a form.
OutcomeIn one final-round session, the participant responded positively to the reminder detail and requested a faster setup, which informed the revised default.
Tested, changed,
tested again.
Moderated, task-based rounds throughout the project — in person and over Zoom. Early rounds broke the design in useful ways; the final round measured whether the fixes held. The protocol is documented below.
- Method
- Moderated usability testing
- Sample
- Same five participants across initial and final phases
- Protocol
- Identical selected task set · standardized facilitator support
- Completion criterion
- Selected tested functions completed without critical usability breakdowns
Min — capture
Scenario“You want to add tasks and a schedule in this app. Show me what you would do.”
ObservedFound the “+” immediately and completed both tasks without confusion.
✓ Completed · no friction
Jisoo — reprioritize
Scenario“A project's priority and deadline changed. Update them.”
ObservedCompleted the task — then asked to drag items directly on the daily schedule.
✓ Completed · improvement filed
Evelyn — plan & remind
Scenario“Schedule next week's plan for an important project and set a reminder.”
ObservedSet the reminder smoothly and praised its detail — but wanted the setup to be even faster.
✓ Completed · defaults simplified
Earlier rounds → clearer wayfinding
Early sessions reshaped icons, labels, and screen order. In the final round, all five participants completed the selected tested functions without critical usability breakdowns.
Reminder setup → one-toggle defaults
Evelyn loved the reminder's precision but not its cost. The response: “on time + one hour before” became the default, turning the common case into a single switch.
Drag-to-reschedule → next iteration
Jisoo's request to drag tasks on the timeline is the roadmap's top item — it removes a navigation decision entirely — it simply arrived after the testing window.
A calmer way
through the day.
01 — Dashboard
Today, already triaged
One progress ring, active projects, and today's tasks — the day answered before a single tap.
Today's TasksThe day as a list — filters keep overdue and priority work impossible to miss.
Task Detail & ReminderRepeat rules and reminders with defaults that make the common case one toggle.
ProfileProgress made visible — 2,653 tasks completed and counting.
08 — Reflection
Every decision here — from research plan to pixel — was mine to defend. Research told me what to build; testing told me where I was wrong. The honest limit: five participants recruited by convenience sampling, with facilitator support available — encouraging evidence, not proof. Next: build drag-to-reschedule, the top request from final-round testing.
This project taught me that productivity isn't about adding features. It's about reducing unnecessary decisions.
