Consumer productivity

Consumer productivity

About

Product designer

Product designer

Role

Personal

Personal

Project type

8 weeks

8 weeks

Duration

Work in progress

Work in progress

Status

Challenge

Freelancers struggle to track time, manage tasks, and pursue personal goals across multiple disconnected tools, creating mental overhead, missed billable hours, and making it difficult to achieve priorities.

Goal

Design a consolidated workspace where tasks, time tracking, and personal goals live together — so freelancers spend less time managing tools and more time doing their best work.

Success metric

Percentage of replacing this system with other tools.

  1. Overview

Role: End-to-end UX. Research · IA · Interaction · Handoff

Target user: Freelancers, designers, devs, consultants

The core tension I was designing against: Mental model mismatch.

Freelancers think in

Freelancers think in

  • This week feels heavy

  • I can't take more work

  • I need a light day tomorrow

Tools think in

Tools think in

  • Tasks

  • Dates

  • Streaks

  1. Why this is a strong design problem

High frequency: Daily planning decisions, every single workday

High emotional cost: Stress, guilt and burnout when system breaks down

AI opportunity: Context, prediction, load-aware adaptation

Most freelancers use a patch work ( root cause )

Most freelancers use a patch work ( root cause )

  • Tasks and deadlines - Notion/to-doist, Asana, clickup

  • Timelines and client work - Google calendar, mental math

  • Habit and personal goals - Notes app, streaks, hibitica

  • Thinking and planning - LLM

What this causes

What this causes

  • Work tasks, life habits, long term goals live in different apps

  • AI doesn't remember this or connected by default

  • Habits are tracked separately than workload

Where current AI helps in

Where current AI helps in

  • Generating plans

  • Explaining things

  • Breaking tasks into steps

AI cannot yet handle

AI cannot yet handle

  • Tradeoffs between work + habit

  • Load balancing across clients

  • Streak preservation under overload

Design decision: The product must hold context AI can't, workload, energy, client commitments- and surface it at the moment of planning.

  1. User research

What I believed and where I was wrong

Assumptions

Assumptions

  • I assumed freelancers wanted smarter features

Research discovery

Research discovery

  • Research showed they wanted fewer decisions

  • The real pain wasn't missing tools, it was the cost of switching between them

Research questions I structured interviews around

Process

Process

  • How do freelancers actually plan there week?

  • What triggers a planning session?

Behavior

Behavior

  • When do there systems break down?

  • What do they abandon and why?

Need

Need

  • What does "being on top of things" actually feel like for them?

A profile of my ideal customer

Who

Who

  • Who are my users?

Needs

Needs

  • Barriers to adoption

Basics

Basics

  • Age

  • Location

  • Gender

  • Career

  • Disability

Psychographics

Psychographics

  • Attitudes towards technology & change

  • Risk tolerance

Interview participant characteristics

Interview participant characteristics

Context of use

Context of use

  • When they use the product?

  • Where they use it?

  • Environmental constraints ( time, budget, tools, regulation)

  • Trigger events that prompt usage

Digital behavior

Digital behavior

  • Device type usage

Who is the end user

Freelancers ( Current focus )

Freelancers ( Current focus )

  • Designers, writers, consultants, developers, project managers

Independent creator

  • Future focus

  • Content creator

About freelancers ( core problem )

  • No external structure

  • Manage multiple clients and timelines

  • Maintain routines without burnout

  • Balance deep work, admin work

  • Avoid context switching

About freelancers ( this is strongest ideal customer profile )

  • Feel fragmantation pain

  • Activity search for systems

  • Are open to AI powered insights

  • Have higher switching motivation

  1. User persona

Understaning persona: Daily planning decisions, every single workday

I began by deeply understanding the target persona-their goals, challenges and daily routines.

This helped me design with empathy, ensuring the solutions were tailored to real user needs, ultimately improving usability and engagements.

Kishan, the freelancer this is designed for

  • Age - 30

  • Profession - Freelancer designer and developer

  • Location - Kerala, India

  • Experience - 3 yrs

  • Worked with early stage startups

  • 8-10 yrs in charted accountancy

Background summary

Background summary

  • Kishan is a designer & developer with a non-linear career path

  • After nearly a decade in chartered accountancy, he transitioned into startup environments and eventually into independent freelancing.

  • He currently manages 2 acquired clients through referrals.

  • His work schedule is inconsistent: some days extend to 8-12 hours, while others are limited to 4 hours.

  • This variability effects time tracking, billing accuracy and task consistency.

Personality profile

Personality profile

  • Moderately introverted

  • More analytical than creative in approach

  • Operates independently rather than as a team-oriented contributor

  • Moderately active in execution

  • Organised rather than messy

  • Shows relatively high risk tolerance

Interests

Interests

  • Using AI tools

  • Leveraging gen AI to accelerate execution

  • Building systems that provide small "dopamin wins" for completing tasks

  • Exploring lightweight productivity workflows

Influences

Influences

  • Attempted use of notion , but found it overly general purpose

  • Seeks a system athat minimizes tab switching and context loss

  • Tried trello but experience friction in accessibility and workflow

Goals

Goals

  • Reduce time spent on repitive workflows

  • Create a unified system for tracking clients and projects

  • Improve visibility into time allocation and work output

Needs & expectations

Needs & expectations

  • A simple browser-accessible system (not dependent on switching between multiple apps or tabs)

  • Clear client wise task tracking with due dates

  • Minimal setup friction

  • Centralized storage for context (files, meeting notes, transcripts, links)

  • Visible timeline and history of work

Motivations

Motivations

  • Saving time

  • Maintaining clarity in commitments

  • Avoid-last minute rush

  • Increasing operational efficiency

Pain points and frustrations

Pain points and frustrations

  • Undercharged clients due to inaccurate time tracking

  • Difficulty maintaining structured task discipline

  • Inconsistent tracking across multiple clients and projects

  • Productivity variability driven by energy and interest levels

Behavioral patterns

Behavioral patterns

  • Alternates between high-intensity work sessiosn and low-output days

  • Prefers independence in workflow decisions

  • Values speed and practicality over complex systems

  • Adopts tools quickly but abandons them if friction arises

  1. MVP scope

Total screens: 14

Core screens: 9

AI-powered views: 5

Post MVP screens: 4+

Daily command center

Today view

Today view

  • Task due today across all clients, active timer, quick add.

  • Replaces mental math and tab switching.

AI day planner

AI day planner

Client and project hub

  • Client list

  • Project workspace

  • Project context AI

Time tracking

  • Timer + time log

  • Billing summary

Tasks

  • Task list ( all projects)

  • Task detail

AI assistant surface

  • AI assistant

  • Weekly summary

Setup & settings

  • Onboarding/setup

  • Integrations

  • Habit tracker

Post MVP

  • Reports & exports

  • Knowledge base

  • Workflow automation

  1. IA decision

Client vs project

Iteration 1

Iteration 1

  • Initial instinct was to organize by projects — but research revealed freelancers think in clients, not projects.

Iteration 2

Iteration 2

  • However, one client can have multiple active scopes of work with separate deadlines, billing, and progress. A flat client-only structure would collapse that distinction

Design decision: Keep both layers — Client as the primary identity, Project as the work separator for time, invoicing, and progress tracking.