Employee Directory

Find people by team, role, location, manager, and status while keeping the information useful for everyday collaboration. The screen connects People and Teams so product teams can find the “Add employee” action while checking headcount and teams.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Maya Chen · Product and Jon Bell · Sales, rather than an empty visual shell.

Employee Directory
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Add employee

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Add employee” action without losing sight of headcount, teams and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Add employee is clearly available where the task happens.
  • Main view: People keeps the starting point obvious.
  • Connected view: Teams supplies nearby context.
  • Metric: Headcount is visible with a meaningful value.
  • Another signal: Teams helps people judge what to do next.
  • Representative record: Maya Chen · Product makes the example specific.
  • Second record: Jon Bell · Sales shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading people without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for teams; clarify who can continue.
  • Success after choosing Add employee; 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

People → Teams → Add employee → Review outcome

Patterns used

Workspace, People, Teams, Org chart, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Maya Chen · Product with Jon Bell · Sales. Make headcount clear, then use teams 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 “Add employee” action. The happy path alone is not enough.

Related UI examples: Hiring Pipeline, Leave Management, Performance Reviews.

Start from this in Figr

Design a employee directory screen for our existing software product. Use our real design-system tokens, components and product language. Show People and Teams, include believable records such as Maya Chen · Product, and make add employee easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr