PRODUCT DESIGN CASE STUDY · ERPPriority Software

Automation RulesRules in a complex system — from a decade-old tool to a modern rule builder.

I led the end-to-end redesign of Priority's business-rules automation tool: user research, ideation, prototyping, and usability testing — turning an outdated feature into a clear if… then… experience.

Read the case study
The redesigned rule builder: conditions on the left, actions on the right
The redesigned rule builder — conditions and actions side by side.
MY ROLELead product designerResearch to usability testing
PRODUCTBusiness rules automationPriority ERP
PLATFORMWeb applicationPart of the Priority suite
TEAM & TIMELINEMulti-phaseProduct, R&D & users
01 The problem

A decade-old tool.

Confusing flow between conditions and actions, no flexible rule logic, outdated visuals, and lists users could not scan.

02 The approach

If… then…, side by side.

A chronological rule flow, a card-based list with the key data in view, and action settings that appear only when needed.

03 The result

A new standard.

Overwhelmingly positive user feedback — and a design standard for future automation tools in Priority, later extended with AI-powered options.

01 / CONTEXT

A decade-old automation tool inside a leading ERP

Priority Software is a leading ERP platform used by over 75,000 organizations worldwide, providing a full suite of management tools for operations, finance, logistics, and more.

Its automation feature — business rules that trigger actions from conditions — was built over a decade ago. It suffered from poor usability, unclear logic, and outdated visuals, and no longer met modern usability standards.

As the lead product designer, I owned the end-to-end redesign process: from user research and ideation to prototyping and usability testing.

02 / EMPATHIZE

What users told us

We conducted interviews with users from various industries — including manufacturing, healthcare, and education — to identify the key pain points:

  • Confusing flow between conditions and actions
  • No support for multiple recipients or flexible rule logic
  • Outdated design and unclear visual hierarchy
  • Hard-to-scan lists with missing key information

These findings shaped our goal: to redesign the tool for clarity, efficiency, and modern usability.

03 / DEFINE

Maya, the system administrator

PersonaMaya Patel

Priority System Administrator at FreshNest Foods, a national food distributor. 30 years old, 5 years of experience implementing and integrating Priority. Curious, methodical, tech-savvy, results-oriented, collaborative.

Her dayScattered information

Maya tracks inventory, monitors shipment statuses, and keeps operations smooth. She is analytical and thrives on efficiency — yet spends hours manually updating data across multiple systems, with limited real-time visibility.

What she needsAutomation that works

“Why work hard if a machine can do it?” Maya needs automation that simplifies repetitive work and delivers accurate, actionable insights.

04 / IDEATE

Auditing the old tool, learning from the ecosystem

We started by researching the current tool — what it does, how it works, and what users like about it. In the standard Priority screen, the user opens the automation tool through a robot icon, manages existing rules from a list, and creates or edits rules from buttons at the bottom of the screen. Actions hide inside a dropdown.

The old business rules screen: a dense table with buttons at the bottom
The old tool — a dense rules table, with actions hidden at the bottom of the screen.

The audit confirmed what users felt: the tool had been developed many years ago, felt outdated and unpleasant to use, included unclear or confusing elements, and was missing key features that had become standard among competitors.

We expanded the research to other products in the ecosystem — from direct competitors like Monday and Azure to experience-driven platforms such as Wix and Apple. These insights helped us identify opportunities to modernize the experience and align it with today's user expectations.

We sketched new layouts that made workflows transparent and intuitive, reducing clutter and focusing on logical hierarchy.

05 / PROTOTYPE

From a vertical form to a side-by-side rule builder

The existing flow between actions and conditions was inconsistent — in some areas actions came first, in others conditions did. Several components, like email, text message, and user verification actions, looked identical even when their states or purposes differed. Users also asked for more flexibility, such as adding multiple recipients or combining multiple actions; due to feasibility constraints, we started by implementing multi-recipient functionality.

The rules list itself was a major pain point: important data wasn't visible, and the side buttons were unclear. We began sketching ideas and building an interactive prototype that reimagined the experience from the ground up.

The rule — first design

An if… then… sequence

Usability testing showed users struggled to connect conditions with their resulting actions, so we redesigned the process to follow a chronological sequence — if… then… — aligning the layout with how users naturally think through logic. The action list became a set of clear icon buttons, and a collapse option let users switch between a detailed view and a summarized version of each rule.

The first prototype introduced a modernized toolbar and a card-based rule list. Users appreciated the refreshed look, but feedback highlighted two key issues: excessive scrolling and oversized icons.

The first design of the rule: a vertical if… then… sequence
The first design — a vertical if… then… sequence.
Phase two

Side by side, with the data in view

We redesigned the layout into a side-by-side structure — conditions and actions visible and editable at the same time — with filters, data highlights, and contextual actions directly in the rule card. The rules list became a card-based layout showing more key information at first glance; irrelevant actions were removed, and rule-specific actions were added directly to each card.

We also introduced refined microcopy throughout the flow, aligned with users' terminology. Usability testing confirmed the improvements, with users describing the experience as clearer, faster, and easier to navigate.

The redesigned rule builder: When conditions on the left, Then actions on the right
The redesigned rule — When and Then, side by side.
The redesigned rules list: cards showing conditions, actions, and key details
The rules list — each card shows the conditions, the action, and the key details at a glance.
Actions

Settings that appear only when needed

Each action in the “Then” section serves a different purpose — “Send Email” includes multiple configuration options, while “User Verification” initially had none. To keep the experience consistent, we designed a dynamic interface where each action's settings appear only after the action is selected.

Action settings appearing after selection: email, webhook, and user verification
Each action opens its own settings — email, webhook, and user verification each get the fields they need.
06 / TEST & IMPACT

A new standard for automation in Priority

After launch, we collected feedback from real users. The overall feedback was overwhelmingly positive — users described the experience as both intuitive and helpful.

We also gathered valuable improvement suggestions, such as increasing spacing in the “of” dropdown and adding data filtering options to the rule list.

The redesign not only improved usability but also set a new design standard for future automation tools within Priority. In the latest version, the feature was elevated even further with AI-powered options that suggest relevant actions and automations based on the user's input — showcased in a short video created with the marketing team.

07 / LOOKING BACK

Designing for complex systems

This project strengthened my understanding of designing for complex systems.

I learned how to bridge the gap between user needs, technical limitations, and business goals — while maintaining a clean and consistent user experience.

I'm proud of how our team transformed a legacy tool into an efficient, modern experience that truly empowers users.