ENTERPRISE · WORK MANAGEMENT · REDESIGN
Turning a dense task popup into a focused workflow
Open prototype ↗
Tl;dr
I redesigned task creation for a complex RTL work-management system. The new popup establishes a clearer hierarchy, keeps essential fields visible, separates activity from task editing, and turns advanced actions into progressive, understandable choices.
-
Clear hierarchy
Primary task actions stay visible and predictable
-
Progressive detail
Advanced fields appear when they become relevant
-
Working prototype
The redesigned flow is interactive and testable
Overview
One surface for creating, assigning, tracking, and discussing work
The popup sits at the center of a feature-rich enterprise system. It has to support task details, people, dates, dependencies, files, subtasks, comments, activity, sharing, and cross-project context - without making the first interaction feel like a form users have to decode.
Problem
The old popup exposed complexity before establishing priority
Information was distributed across dense regions with competing visual weight. Task editing, sharing, files, comments, and secondary actions all asked for attention at once, making it harder to scan the task and understand what to do next.
Core task fields competed with secondary sharing and collaboration tools.
The page structure did not clearly distinguish editing from activity.
Advanced capabilities were always visible, increasing perceived complexity.
Goals
Make the task understandable at a glance
User goalPreserve enterprise depth without showing everything at once
Product goalKeep activity close without letting it interrupt editing
User goalCreate a reusable hierarchy for future task capabilities
Product goalArchitecture
From a dense popup to a clear task path
A flowchart of the work - from the problem, through the attention model, into the three screen changes, and a coded prototype.
Everything competed at once - actions, sharing, files, and activity.
Make the task readable at a glance, keep depth, reveal advanced tools only when needed.
Sequence attention so the task stays readable while depth stays available.
Project path, task name, and completion stay fixed so the task is always readable.
One toolbar and one Share control hold the primary moves without competing chrome.
Status, dates, and description sit in a calm body users can scan before going deeper.
Comments, files, and dependencies open from a fixed sidebar - on demand, not by default.
Primary actions live in one row under the task name.
Permissions collapse into a single Share entry point.
Comments, files, and dependencies open on demand.
Coded interactions so the hierarchy could be tested, not only presented.
Before → After
What changed on the task screen
Each change is shown separately - what it was before, and what I fixed after. Then drag to compare the full screens.
01 Unified actions into one toolbar
Actions and info were scattered, and it wasn’t clear where to start.
All actions live in one row, right under the task name.
02 One share button instead of scattered permissions
Edit and view permissions appeared as separate cards and took half the screen.
One Share button consolidates all permission types in a single place.
03 One sidebar for every content world
Files, comments, and secondary content mixed into the main task details.
Files, dependencies, related tasks, and comments live in a fixed sidebar and open on demand.
Before
After
Design decisions
A hierarchy built around the task, not the feature list
Persistent task context
Project path, task name, completion, and primary actions anchor the experience before users reach detailed fields.
Grouped metadata
People, tags, priority, dates, dependencies, and files are organized into compact, recognizable controls.
Dedicated activity pane
Comments and history remain adjacent to the task but occupy their own stable region, reducing context switching.
Prototype
The interaction model, not just the static layout
The coded prototype demonstrates task actions, expandable controls, dates, dependencies, activity, comments, and the relationship between sender and recipient views.
Explore the interactive prototypeReflection
Complex products need stronger sequencing, not fewer capabilities
The redesign reinforced that enterprise UX is often less about removing features and more about revealing them in the right order. A clear task hierarchy can preserve power while making the interface feel significantly lighter.
Also check out..
