SUSaurabh UkeyCase study / Operative
OperativeEnterprise · UX/UI design

Make complexity navigable.

Client work completed during my time at Persistent.

Broadcast CRM workflows and a shared interface system for media and advertising sales teams.

Contribution & scope

UX/UI design and design-system work with product managers and engineers

Broadcast CRMDense workflowsDesign systems
5 chapters · Original project artefacts
Selected original design · Operative
01 / Context

Many records. One coherent way of working.

The supplied designs cover detailed sales operations: line items, statuses, bulk actions and supporting information. The challenge is to keep these relationships legible when a workspace contains many records.

Read the state

Distinguish the status of an item from the action available on it.

Keep context

Make related information available within the operational workspace.

Repeat consistently

Use shared controls across similar tasks.

02 / Workflow detail

Design around the work inside the table.

The table is the main working surface. Selection, ordering and status information need to coexist with secondary details without obscuring the record being edited.

03 / Repeated operations

Give repeated actions a recognisable structure.

The source includes multiple operation states and confirmation patterns. Presenting the steps in a consistent way helps communicate scope and gives users a chance to inspect a change before completing it.

Scope

Keep the target records visible or clearly identified.

Action

Make the operation and its available options explicit.

Feedback

Provide a recognisable result or confirmation state.

04 / Shared foundations

Consistency is built at component level.

The design-system board specifies button sizes, styles and interaction states, alongside other reusable interface patterns. These foundations allow detailed workflows to share the same visual and behavioural vocabulary.

05 / Overview & detail

Support both scanning and inspection.

Dashboard and record views offer different levels of information. The portfolio pairs these original artefacts to show how the work moves between an overview and the detail needed to act.

Takeaway

In a dense enterprise product, clarity comes from consistent states, predictable controls and careful information hierarchy—not simply removing detail.