Task Board

Plan and move product work through clear states with owner, priority, due date, and blockers visible on every card. The screen connects Board and My work so product teams can find the “New task” action while checking open tasks and blocked.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Billing migration and Mobile onboarding, rather than an empty visual shell.

Task Board

Template facts

Screen

Board

Primary action

New task

Pattern

Board

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “New task” action without losing sight of open tasks, blocked and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New task is clearly available where the task happens.
  • Main view: Board keeps the starting point obvious.
  • Connected view: My work supplies nearby context.
  • Metric: Open tasks is visible with a meaningful value.
  • Another signal: Blocked helps people judge what to do next.
  • Representative record: Billing migration makes the example specific.
  • Second record: Mobile onboarding shows the pattern works beyond one item.

States worth designing

  • No items in a stage; show what people can do instead of leaving a blank panel.
  • Loading board without changing the layout unexpectedly.
  • Move blocked by access rules; explain the problem and preserve work.
  • Permission denied for my work; clarify who can continue.
  • Success after choosing New task; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Board → My work → New task → Review outcome

Patterns used

Board, Board, My work, Projects, accessible states, contextual actions

Why these choices work

Use meaningful stages and clear ownership. Keep the next action visible on each card; confirm high-impact moves.

In this design, people should be able to compare Billing migration with Mobile onboarding. Make open tasks clear, then use blocked to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New task” action. The happy path alone is not enough.

Related UI examples: Project Timeline, Sprint Planning, Product Roadmap.

Start from this in Figr

Design a task board screen for our existing software product. Use our real design-system tokens, components and product language. Show Board and My work, include believable records such as Billing migration, and make new task easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr