TaskFlow — Designing a Smarter Way to Manage Team Work

This project started as a design challenge: prototype a SaaS platform for project management.

But instead of treating it as a simple UI exercise, I approached it as a real product problem—focusing on how teams actually plan, communicate, and collaborate.

The result is TaskFlow: a SaaS concept designed to simplify project management by combining task organization and team communication into a single, intuitive experience.

The Problem

Most project management tools are powerful—but not necessarily easy to use.

Through initial research and benchmarking, a clear pattern emerged:
teams often struggle not because tools lack features, but because they have too many, poorly organized.

Common issues included:

• Fragmented communication across different tools

• Overloaded interfaces filled with notifications and information

• Difficulty in tracking tasks and team responsibilities

• Confusing navigation between sections

The core problem wasn’t functionality.
It was clarity and coordination.

So the challenge became:
How can we design a tool that helps teams stay aligned without overwhelming them?

My Approach

Designing beyond the brief

Even though this was an interview project, I treated it like a real product.

I followed a design thinking approach to ensure every decision was grounded in user needs—not assumptions.

Understanding how teams actually work

I structured the research phase around three key questions:

• How do teams currently manage projects?

• Where do breakdowns happen?

• What do users actually need vs. what tools provide?

To answer these, I defined a research plan including:

• User interviews

• Surveys

• Benchmark analysis of existing SaaS tools

This helped me identify a recurring insight:
teams don’t need more features—they need better flow between them.

From features to flow

Instead of designing isolated functionalities, I focused on how everything connects.

I translated insights into:

• A clear information architecture

• A simplified sitemap

• Structured user flows for key actions

The goal was to reduce friction between:
→ planning
→ execution
→ communication

One key decision was integrating communication directly into the platform, reducing the need to switch between tools.

Designing with clarity in mind

I developed wireframes and progressively moved to higher-fidelity prototypes, always focusing on:

• Reducing cognitive load

• Making navigation predictable

• Prioritizing essential information

Rather than showing everything, the interface was designed to show the right things at the right time.

Testing, failing, improving

Testing revealed important friction points:

• 50% of users felt overwhelmed by notifications

• 75% struggled with resource management

• 20% experienced confusion navigating between sections

These insights were critical.

Instead of refining visuals, I went back to structure:

• Simplified notification systems

• Improved resource visibility and allocation

• Clarified navigation patterns

I also used A/B testing (e.g. for notifications) to validate which solutions reduced friction most effectively.

The Outcome

The final concept resulted in a more focused and usable project management experience:

• A streamlined interface with reduced information overload

• Integrated communication flows within task management

• Improved navigation and feature discoverability

• A scalable design system supporting consistency

TaskFlow demonstrates how a complex SaaS product can be simplified—not by removing functionality, but by organizing it more effectively.

What this project shows about my approach

This project reflects how I think as a designer:

• I don’t start from screens—I start from behaviors

• I prioritize structure and flow over visual complexity

• I use testing not just to validate, but to rethink decisions

Even within the constraints of an interview challenge, I focused on creating a solution that is:
strategic, user-centered, and grounded in real-world product thinking.

Final thought

Project management tools are not just about managing tasks—they’re about enabling teams to work better together.

This project reinforced a principle I apply in all my work:
good design doesn’t reduce complexity—it organizes it.