NEW TOOL

Task Center – Exchange Platform

Designing a scalable task system to bring clarity, ownership, and efficiency to cross-team workflows.

Lead UX Designer Discovery, Information Architecture, User Flows, Wireframes, Prototyping, Final UI

Task Center Exchange Platform

Summary

The Exchange Platform is used by multiple internal teams to manage high volume operational workflows such as orders, payments, and customer requests. Despite this complexity, there was no native way for users to track their tasks, owners, or deadlines. This led to missed follow-ups, unclear ownership, and constant context switching.

I designed Task Center as a net new feature that centralizes task creation, assignment, and tracking into one place. It gives every user a clear view of what they need to work on today and creates a scalable foundation for future automation and reporting.

Role

Lead UX

Partners

Product Manager, Engineering Lead, Operations Stakeholders

Responsibilities

  • Discovery research
  • User flows & information architecture
  • Wireframes and prototyping
  • High-fidelity design & design handoff
  • Iteration with PM and engineering

Timeline

8 weeks (Discovery → Approved Phase 1 designs)

Context & Problem

  • The Exchange Platform supports internal operations teams who handle orders, payments, and customer facing workflows.
  • Work often spans multiple teams, which makes ownership and follow-through critical.
  • Before this project, the product did not have any native task management capability.
  • As workflows evolved, task complexity increased, but the product did not evolve with it – leading to manual workarounds and lost accountability.

Key Problems

  • There was no single list of "what I owe" for individual users.
  • Tasks were scattered across email, chat, and personal notes.
  • Managers had limited visibility into who owned what and what was blocked.
  • Important follow-ups were easy to miss, which increased operational risk and context switching.
  • Existing tools like Jira or spreadsheets were too heavy or disconnected from the core product.
  • No clear system of ownership existed, which created bottlenecks and slowed down cross-team workflows.

Research & Insights

Methods

  • 1:1 interviews with operations team members across different roles
  • Shadowing sessions to observe how tasks were currently tracked
  • Workflow reviews of email, Slack, and spreadsheet-based task management
  • Workshops with PM and Ops leads to understand cross-team dependencies

Key Insights

  • Users were juggling multiple active tasks per day but tracked everything manually.
  • Users were constantly switching between the Exchange Platform and external tools just to manage tasks, which slowed them down and increased cognitive load.
  • Tasks assigned verbally or via chat were easily lost if not written down immediately.
  • Users needed a single, trustworthy view of "what I need to do today."
  • A heavy, Jira-like interface would not be adopted – the solution needed to be lightweight and fast.
  • Ownership was unclear, causing delays and unnecessary follow-ups.

Representative Quote

"If I don't write a task down the minute I hear it, it's gone. There's nowhere in the product that shows me what I owe."

Design Principles

Reduce cognitive load

Only show information needed to decide what to work on next.

Minimize friction

Creating and updating tasks should feel effortless, or users will avoid the system.

Prioritize clarity over density

Task states, priorities, and due dates should be instantly recognizable at a glance.

Create predictable patterns

Consistent actions and structure reduce confusion, especially during cross-team handoffs.

User Flows & Information Architecture

I designed the Task Center flows to minimize friction and help users understand what they owe, complete their work quickly, and keep ownership clear. The information architecture introduces a new structured space in the Exchange Platform that unifies task-related views for the first time.

Primary Flow

Task Created → My Tasks → Task Detail → Completed

Information Architecture (IA)

  • Exchange Platform
  • — Dashboard
  • — Orders
  • — Payments
  • — Communities
  • L Task Center
  • — My Tasks
  • — Assigned Tasks
  • L Task Detail

Early Concepts & Wireframes

I explored low-fidelity concepts to understand user preferences for viewing, navigating, and acting on tasks. These wireframes validated core layout, task hierarchy, and interaction patterns for fast scanning, strong ownership clarity, and low context switching.

Task Management

Task Management Interface

Exploration of a lightweight list view focusing on scannability and prioritization.

Task Management Interface with Detail Panel

Exploration of combining list + detail to reduce context switching.

High-Fidelity Designs

After validating task flows and interaction patterns through wireframes, I moved into high-fidelity designs. These mocks reflect the first functional release of Task Center Version 1. The UI emphasizes clarity, predictable patterns, and reducing context switching – enabling operations teams to triage and complete tasks faster.

To-Do List (Condensed)

To-Do List (Condensed) - Optimized for fast scanning of large task volumes. Users see only the essentials: task title, assignee, activity, and due date. This view supports high-speed triage when hundreds of tasks come in daily.

To-Do List (Expanded Detail Panel)

To-Do List (Expanded Detail Panel) - Expanding a task reveals an inline right-side detail panel. This reduces context switching by letting users read descriptions, update status, add comments, and review activity without losing their place in the list.

Completed Tasks View

Completed Tasks View - Completed tasks are locked to maintain ownership history. Users can still reopen tasks by changing the status from "Completed" to "To-Do," which moves it back into the active queue.

Design Considerations & Interaction Rules

Design Considerations

  • The right-side detail panel helps users review tasks without losing their position in the list.
  • Status chips are color-coded for fast scanning across hundreds of tasks.
  • Tabs reflect natural workflow priorities: To-Do → Assigned to Me → In-Progress → Completed.
  • Pagination ensures high performance at scale.
  • Elements follow Exchange's existing design system patterns for consistency.

Interaction Rules

Status & Movement Rules

  • A task marked Completed is automatically removed from the active task list.
  • Changing a task from Completed → To-Do moves it back into the To-Do tab automatically.
  • Changing a task from To-Do → In-Progress updates its position and highlights urgency.
  • Tasks always appear in the tab that matches their status to reduce confusion.

Editing Permissions

  • Completed tasks cannot be reassigned to preserve ownership history.
  • Completed tasks also lock certain fields (assignee, priority, due date) to prevent accidental updates.
  • Users can still add comments to completed tasks for recordkeeping.
  • Only specific user roles (Ops leads/managers) can reopen tasks that were closed by mistake.

Assignee & Ownership Logic

  • When assigning or reassigning a task, the system updates the activity log automatically.
  • If a task is reassigned, the new assignee sees it immediately in their To-Do list.
  • Users can only assign tasks to active team members within the organization.

Detail Panel Behavior

  • The right-side task detail panel stays anchored when switching between list items.
  • Updates (status, assignee, comments) do not navigate away from the list view.
  • The panel dynamically collapses or expands based on the content.

Comments & Collaboration

  • Comments support rich text and system-generated activity messages.
  • Users can tag people directly inside the task.
  • Comments stay with the task permanently, even when closed.

Sorting, Filtering & Search

  • Sort by status, due date, creator, assignee, or urgency.
  • Filters apply instantly and work across all task states.
  • Search indexes: task name, assignee, community, and ID.

Performance & Scale

  • Pagination prevents UI overload when volume exceeds 50 tasks.
  • Data loads instantly when switching tabs to support high-volume workflows.

Error Prevention

  • Prevents assigning a completed task.
  • Warns users before changing status from Completed → To-Do.
  • Prevents duplicate task names within the same community.

Version 1 Note

These designs represent the foundation for future releases. Phase 2 enhancements currently in exploration include file uploads, image attachments, richer media inputs, SMS alerts, and a centralized notification center for cross-team alignment.

Design Rationale: Why These Flows Work

1. Optimized for Rapid Scanning

Users manage dozens of tasks daily, so the UI must be scannable.

  • Clean table view highlights only essentials (title, assignee, status, date).
  • Dense rows reduce vertical scrolling for high-volume workflows.
  • Inline detail panel prevents context switching into new pages.

2. Reduces Cognitive Load

Ops members told us they juggle tasks across Slack, spreadsheets, and memory.

  • One consolidated Task Center unifies all task views.
  • Clear categorization (To-Do, Assigned to Me, In-Progress, Completed).
  • Each view removes noise and shows only what the user needs right now.

3. Prevents Ownership Confusion

Ownership was the #1 pain point during interviews.

  • Clear assignee label always visible in the table.
  • Ownership automatically updates when users take actions.
  • Completed tasks are locked to prevent accidental reassignment.

4. Minimizes Friction When Updating Tasks

Users complained that updating tasks across tools slowed them down.

  • Quick-edit fields allow instant changes (status, assignee, due dates).
  • Inline activity and comments eliminate the need to open new pages.
  • Task updates sync automatically across the platform.

5. Balances Detail + Simplicity

Ops users told us Jira-like tools felt 'too heavy'.

  • Condensed list view keeps tasks lightweight and fast.
  • Expanded detail panel gives more context only when needed.
  • Modular sections (Task Details, Dates, Activity) keep information structured.

6. Reduces Errors & Preserves History

Task mistakes create lost work and operational blockers.

  • Completed tasks lock fields to protect historical data.
  • Users cannot assign completed tasks to prevent workflow corruption.
  • Reverting status back to 'To-Do' automatically moves tasks to the right list.

These design decisions were shaped by user interviews, workflow observations, and technical constraints across the Exchange platform. Each principle directly addresses a real pain point uncovered in research.

Business Impact

Faster Workflows

Expected 30 to 40 percent reduction in time spent switching between Slack, email, and spreadsheets

Reduced Task Errors

Inline task details and locked statuses minimize accidental changes.

Stronger Cross-Team Alignment

Shared visibility improves coordination and reduces duplicate work.

Next Steps and Future Enhancements

I see opportunities to expand the Task Center further, which would allow Ops teams to manage more processes from a single place. For example:

Manual Matching Workflow

A way to match shipments and invoices when automated matching fails.

Bulk Actions

Select multiple tasks to quickly reassign or update statuses in one step.

SLA Alerts & Risk Flags

Automated alerts when tasks are at risk of violating service-level agreements.

AI Recommended Tasks

Use artificial intelligence to prioritize tasks based on patterns and past decisions.

These additional features would increase productivity and help ensure successful long-term adoption of the Task Center.

Final Reflection & Project Summary

What I Achieved

The Task Center project successfully introduced a centralized, intuitive workflow for Ops teams who previously relied on scattered tools like Slack, spreadsheets, and email. Through iterative design, user interviews, and collaboration with engineering, I created a system that reduces cognitive load, increases efficiency, and supports scalable growth for the Exchange platform.

What I Learned

Designing task-based systems revealed the importance of predictable interaction patterns, clear hierarchy, and minimizing unnecessary friction. I also learned how crucial it is to deeply understand an Ops user's mental model — their workflows are fast, detail-heavy, and high-stakes, so every interaction needed to feel effortless and reliable.

Collaboration & Impact

This project involved close alignment with PMs, engineers, and the Ops team. Their insights helped shape rules for task ownership, historical locking, status transitions, performance considerations, and technical dependencies. The resulting design dramatically improved speed, lowered error risk, and set a foundation for future automation and AI-driven enhancements.

Looking Ahead

Future phases like manual matching, bulk actions, SLA alerts, and AI-recommended tasks will further reduce operational blockers and expand what Ops can manage from a single place. These enhancements will help ensure long-term adoption and measurable business impact.