self initiated
Taskflow — Productivity Suite
Unifying Enterprise Task Management into a Single Cohesive SaaS Experience
- Role
- Product Designer & Design System Lead — Interface Architecture, Component System (120+ tokens), and Cross-Platform Handoff.
- Scope
- Dashboard design, four distinct task views (list, board, timeline, calendar), team collaboration features, notification system, settings and permissions, and a reusable component library of 120+ documented components.
- Timeline
- 12 weeks
- Category
- Web Application
Overview
A 40-person SaaS company was running task management across four different tools. Departments had adopted their own workflows, and there was no shared view of priorities. They needed a single product that could unify without disrupting existing habits.
Challenge
Context was being lost between tools. A task created in one app had no visibility in another, deadlines were missed because notifications lived in different places, and new team members took weeks to understand which tool to use for what.
Objective
Design one platform that replaces four tools — handling personal tasks, team projects, cross-department visibility, and enterprise-level permissions — without overwhelming individual users with enterprise complexity. Replace 4 fragmented productivity tools with 1 unified platform Accelerate new feature delivery by at least 30% Reduce new employee onboarding time from 3 weeks to 3 days
Approach
Modelled the four tool boundaries the brief describes as one object model, then built the token layer before any screen so the views would share a vocabulary rather than resemble each other. Designed the four task views against that model, checking each pattern against what a component library could realistically render.
Selected decisions
I built a density-aware layout system: personal views show clean, focused lists while team and enterprise views surface more metadata without changing the navigation structure. The component library used composable primitives — buttons, cards, and inputs that snap together — so new features could be assembled from existing parts rather than designed from scratch.
Responsibilities
Cross-Department User Interviews 120+ Component Tokenized Design System 4 Task Views (List, Board, Timeline, Calendar) Design System Documentation & Developer Guidelines
Deliverables
Full application UI across web and mobile, a Figma component library with 120+ components and usage documentation, user flow diagrams, interactive prototypes for key workflows, and annotated handoff specs with implementation guidance.
Outcome
The exercise ended with one workflow spanning what had been four separate tool boundaries in the brief, a component library covering every task view, and a written rationale for collapsing them into a single object model rather than linking four apps together. Nothing shipped; the deliverable is the system and the reasoning.
Reflection
The component library was the real product. Individual screens are temporary — they change with every sprint. But a well-structured design system compounds: every new feature built on it is faster than the last.