FIGR / UI TEMPLATE

Performance Reviews

Run a review cycle with self reviews, manager feedback, peer input, calibration, and overdue actions visible by person and team. The screen connects Cycle and People so product teams can find the “Start review” action while checking completion and self reviews.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Product · 78% complete and Engineering · 72% complete, rather than an empty visual shell.

Performance Reviews

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Workspace

Primary action

Start review

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

Product teams need a clear “Start review” action without losing sight of completion, self reviews and the affected records. Keep the decision and its outcome clear before moving to the next task.

What to look for

  • Primary action: Start review is clearly available where the task happens.
  • Main view: Cycle keeps the starting point obvious.
  • Connected view: People supplies nearby context.
  • Metric: Completion is visible with a meaningful value.
  • Another signal: Self reviews helps people judge what to do next.
  • Representative record: Product · 78% complete makes the example specific.
  • Second record: Engineering · 72% complete shows the pattern works beyond one item.

States to consider

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading cycle without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for people; clarify who can continue.
  • Success after choosing Start review; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where it fits

Cycle → People → Start review → Review outcome

Patterns in this screen

Workspace, Cycle, People, Feedback, accessible states, contextual actions

UX choices to review

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 Product · 78% complete with Engineering · 72% complete. Make completion clear, then use self reviews 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 “Start review” action. The happy path alone is not enough.

Related UI examples: Leave Management, Payroll Admin, Hiring Pipeline.

Try a similar screen in Figr

Design a performance reviews screen for our existing software product. Use our real design-system tokens, components and product language. Show Cycle and People, include believable records such as Product · 78% complete, and make start review easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗