Idaratech
2026
Designing Predictable Project Planning for Enterprise Teams
Designing advanced planning experiences that help teams understand project health, manage task dependencies, visualize delivery timelines, and adapt project data to their workflows.
Overview
Making complex project planning easier to understand and act on
s the Project Management product evolved, teams needed more than a place to organize tasks. They needed clearer ways to understand project health, coordinate dependent work, and reason about delivery over time.
I focused on turning complex planning logic into interactions that remained understandable for everyday users while providing enough depth for more advanced project workflows.
marwaorabi768@gmail.com
Project Visibility
Turn project data into clear signals for action
As planning became more complex, teams needed a faster way to understand what required attention without reviewing every task.
I designed the dashboard to connect high-level project health with the work underneath it, giving managers a clear starting point for planning, follow-up, and decision-making.
A planning layer that surfaces the project signals that matter before teams dive into task-level detail.
Dependencies
Make task relationships clear before they become blockers
As projects become more interconnected, tasks rarely exist in isolation. A change in one task can affect the work that follows it, so teams need to understand those relationships before adjusting the plan.
I designed dependency interactions to make relationships visible and actionable without forcing users into a complex planning model.
Connect tasks in context
Dependencies are created directly from the task workflow, keeping the relationship close to the work it affects. The interaction makes the connection explicit so users can understand what is driving or waiting on another task.
Keep collaboration attached to the work
Comments, mentions, files, and activity were designed inside Task Details rather than separated into another destination. This keeps discussion, decisions, and supporting material connected to the work they explain.
Planning Timeline
Turn task relationships into a plan teams can read
Once relationships between tasks are defined, teams need a clear way to understand how they affect delivery over time.
I designed the Gantt experience to make sequencing, duration, milestones, and dependencies readable in one place—so teams can reason about the schedule instead of reconstructing it from individual task records.
Project timeline with dependencies A single planning view connects task relationships, timing, milestones, and progress so teams can understand how work moves through the project.anning layer above individual tasks, while progress connects that view back to the work underneath. Together, they give teams a shared view of delivery without requiring constant manual status updates.
Flexible Planning Models
Adapt the product to different workflows without adding complexity
Different teams need different information to manage their work. I designed custom fields as a structured extension of the existing project and task model, giving organizations flexibility while keeping configuration and usage consistent.
Configure once, use consistently — Admins can define custom fields and their values within a structured configuration model, extending project data without changing the core workflow.
