Task manager

An internal task manager for the B2B application, developed for salespeople and managers. A big task loaded with complex business logic.

Senior Product Designer • 2019 – 2026

Senior Product Designer • 2019 – 2026

This functional is designed for two roles: creator and performer.

👩🏼‍💻

👩🏼‍💻

Creator –
a manager of various levels:

  • assigns the task

  • monitors its completion

  • approves the task or returns it for revision

👩🏼‍💻

Creator –
a manager of various levels:

  • assigns the task

  • monitors its completion

  • approves the task or returns it for revision

🧑🏻‍💼

Performer –
a regular employee:

  • accepts the task

  • writes a completion report

  • sends the task to the manager for approval

🧑🏻‍💼

Performer –
a regular employee:

  • accepts the task

  • writes a completion report

  • sends the task to the manager for approval

For communication between both roles, each task has a messenger with file attachments.

The Process

Research

At a meeting with the analyst and product manager, we decided to split this large task into three parts:

  1. Task creation

  2. Task management by performer

  3. Task management by creator

After that, I first researched best practices in the most popular task management services, such as Asana, Jira, Todoist, Google Tracker, Notion, Microsoft Teams and Yandex Tracker.

Various task managers

1. Task creation

This part is a great example of the Design System benefits, as it's built entirely on its foundation. Inputs, selectors, date/time pickers, file attachments, etc. – all these components are taken from the library we created.

The entry point to this section for any role is the app's main screen. The first screen of the section is a task list in the form of cards, sorted for convenience by various criteria.

When creating a task, the manager first gives it a name and description; selects the start and end dates / times; attaches photos / videos / documents if necessary.

Brief info adding flow

Next comes the step of identifying performers. This involves a flexible selection system depending on the manager's level. For example, a regional director might assign a task to all salespeople in all stores in a specific region. However, they can also select specific employees within any store. They can also appoint an observer and a responsible person.

Brief performer selecting flow

Once the assignees have been selected, the task is ready to be published. You can publish it immediately or save it as a draft and submit it later. Once published, the task appears as the first card in the task list. It is assigned the "New" status.

2. Task management by performer

The performer receives a push notification about the task assigned to them. The notification is also sent to their email address.

After opening the task, the performer reviews its description and attached documents, and by clicking the "Accept the task" button, changes the task status to "In Progress."

Comment sending flow

If an employee has questions about a task, he can send a comment to the author via messenger on the task screen.

A new message indicator is provided on the task card in the task list.

All participants also receive push notifications.

All task status transitions are also displayed in the task's messenger.

After completing the task, the employee must write a text report, attach files if necessary, and submit the task. The task status changes to "Under Review.”

Comment creating flow

3. Task management by creator

The manager receives a notification that the employee has completed the task. He selects a card with the status “Under review” from the task list and gets acquainted with the performer's report. If he is not satisfied with the report, he returns the task to work, accompanied by a comment. The task returns to the “In Progress" status.

Otherwise, the manager confirms and transfers the task to the status “Completed".

Task approval flow

Outcome

The final solution delivered a scalable task management system tailored to complex B2B workflows and multiple user roles. Clear separation of creator and performer flows reduced complexity, while the integrated communication and status tracking improved transparency and accountability.

A complete set of 160+ screens, including all states and edge cases, ensured a smooth handoff to development and efficient implementation.

All layouts and specs for development