Account Readiness Overview
Key indicators of account health are surfaced in a single view, allowing users to quickly assess readiness before processing an order. Additional details are revealed on demand, keeping the interface focused and efficient.

Executive Summary

---

This case study explores an experience-layer enhancement for Pacific Meridian, a fictional medical and surgical supply distributor headquartered in Anaheim, California, with $640 million in annual revenue and approximately 1,400 employees. Pacific Meridian is a mid-sized regional distributor of medical and surgical supplies, serving hospitals, long-term care facilities, and government agencies under state and federal contracts.

The organization has relied on Microsoft Dynamics GP (internally referred to as MedCore) since 2008. Like many legacy ERP environments, years of customization have made system replacement costly and operationally risky. Rather than replacing the ERP, Pacific Meridian has adopted targeted modernization initiatives designed to improve usability while preserving the existing architecture.

This project introduces an Account Readiness Overview Screen, a decision-support interface that consolidates critical financial, operational, and compliance signals into a single view. The goal is to help customer service representatives quickly determine whether a customer account is ready for order processing.

By surfacing risk indicators earlier in the workflow, the design reduces decision latency, improves operational clarity, and helps prevent late-stage transaction failures.

What This Screen Does

---

• Shift risk evaluation earlier in the order workflow
• Consolidate fragmented signals from financial, warehouse, and reporting modules
• Introduce clear system logic that reduces interpretation errors
• Reduce reliance on institutional knowledge held by experienced CSRs

Rather than rebuilding the MedCore, this initiative improves decision clarity and risk visibility within the existing architecture, reduces operational friction, and strengthens the reliability of order processing.

Design Challenge

---

Pacific Meridian operates in a highly regulated, margin-sensitive environment where reliability is essential. Like other companies in its sector, as the company grew, operational demands increased, resulting in gaps in the ERP system. A credit and risk module, a warehouse management system (WMS), and multiple business intelligence tools were “bolted on.” While these addressed specific business needs, the overall user experience was disjointed, resulting in fragmented customer data and inconsistent decision-making.

UX Context

---

The following user roles represent key stakeholders involved in evaluating account readiness prior to order processing, each with distinct responsibilities and risk considerations.

1. Customer Service Representative (Primary User)

Role

Processes customer orders and serves as the first point of contact for account-related transactions

Goals

• Quickly determine if an order can proceed
• Avoid processing orders that will fail due to credit or operational issues
• Serve customers efficiently under time pressure

Pain Points

• Critical account information is scattered across multiple systems
• Requires manual cross-checking before processing an order
• High risk of errors when working quickly

Needs from the System

• A clear, consolidated view of account readiness
• Immediate visibility into risks or blockers
• Confidence that all required checks have been completed

2. Credit / Finance Team

Role

Manages customer credit, payment status, and financial risk

Goals

• Ensure orders align with credit policies
• Minimize financial exposure
• Maintain accurate and up-to-date account status

Pain Points

• Downstream teams may bypass or misunderstand credit signals
• Lack of visibility into how credit data is used during order entry
• Rework caused by invalid or risky orders

Needs from the System

• Clear representation of credit status at the point of use
• Consistent interpretation of financial data
• Reduced reliance on manual intervention

3. Operations / Fulfillment Leadership

Role

Oversees order fulfillment, inventory allocation, and operational execution

Goals

• Ensure orders can be fulfilled without disruption
• Prevent downstream failures caused by inventory or contract issues
• Maintain efficient operational flow

Pain Points

• Orders entering the system without full validation
• Operational conflicts discovered too late in the process
• Lack of alignment between systems and frontline decision-making

Needs from the System

• Visibility into operational readiness before order entry
• Early detection of fulfillment risks
• Consistent decision-making across teams

Operational Workflow Context

---

Customer service representatives play a critical role in Pacific Meridian’s order intake process. Before an order can be submitted, CSRs must evaluate whether a customer account is financially and operationally ready for fulfillment.

In the existing MedCore environment, this evaluation typically requires navigating multiple system modules to review:

• Customer maintenance records
• Receivables aging and credit exposure
• Open orders and invoice history
• Contract and pricing program eligibility
• Compliance and account status indicators

Because these signals are distributed across separate modules, CSRs often must manually reconcile information before determining whether an order can proceed.

This process introduces decision latency during time-sensitive transactions. The Account Readiness Screen was designed to provide a consolidated operational view to support faster, more confident account evaluation prior to order entry.

Problems Identified

---

Pacific Meridian operates in an environment where individual hospital orders can exceed six figures. Customer service representatives must evaluate a customer’s account health and assess the company’s financial exposure by manually analyzing multiple data sources to determine the customer’s financial readiness.

Although the underlying systems contain accurate financial and operational data, critical risk signals are distributed across multiple modules.

• Aging receivables are tracked in the credit system
• Inventory conflicts are handled within the warehouse management module
•  Contract status is stored in administrative records

Because these indicators are embedded in operational data rather than surfaced during account reviews, customer service representatives must manually piece together account health information before proceeding with an order

Under pressure, this fragmentation slows decision-making during time-sensitive transactions. Critical information—such as aging receivables, credit utilization, or fulfillment constraints—may not be visible at the time of order entry, increasing the risk of financial exposure and operational disruption.

Proposed Solution

---

In the legacy MedCore environment, customer health indicators are distributed across separate financial, warehouse, and reporting modules, requiring manual reconciliation during time-sensitive order entry.

This user-layer enhancement delivers a real-time operational snapshot highlighting critical signals at the time of decision.

Key Enhancements:

• The legacy system is built using ASP.NET 4.5 Web Forms, limiting modern frontend frameworks
• UI components must remain compatible with ASP Web Forms controls (radio buttons, checkboxes, and data grids)
• Backend modules (credit, WMS, BI) cannot be integrated; the interface can only surface signals from existing systems
• Page load performance must remain fast within the legacy architecture
• Client-side rendering must remain minimal
• Animation and heavy visual frameworks are avoided to preserve performance
• Interface changes must remain familiar enough for existing CSR workflows
• Desktop-first design baseline: 1366×768 resolution

These changes shift the experience from reactive error handling to preventative visibility.

The result is improved order integrity, earlier risk awareness, and reduced workflow interruption. The goal is not to add more data but to surface the right data at the right moment.

Design Constraints

---

• Made with ASP.NET 4.5 Web Forms
• The screen must load quickly
• Minimal client-side rendering
• No Animation
• No dramatic UI paradigm shift
• Must look familiar enough for adoption
• Desktop-first design, with a minimum resolution of 1366×768

Design Decisions

---

The redesign was developed within the constraints of a legacy ERP system, necessitating a careful balance between updating it and maintaining compatibility.

The Account Readiness Screen is organized into six sections:

• Customer information
• Account ownership
• Financial readiness
• Credit status
• Receivables
• Data integrity, Operational readiness, and Compliance readiness

Explicit Account Status:

• Clear credit approval
• Only show snapshot consolidation

Jump menu placed next to “account readiness menu” containing links to:

• Credit Department
• Business Intelligence
• Accounting (Receivables)
• Invoices
• Transactions
• Warehouse Management System (WMS)

Additionally:

• All signals and information are read-only
• No ambiguous icons
• Responsive breakpoints are established for desktop and laptop views, with plans for a limited-features design for smartphones and tablets (landscape view) and a progressive-reveal/collapse design for tablets.

Performance Considerations

---

To prevent the Account Readiness screen from impacting system performance, the following measures are implemented:

• Data sets are intentionally constrained to account-readiness information only
• All visualizations implemented without animation
• The layout uses a responsive grid rather than a JavaScript-heavy SPA architecture

Impacts

What This Work Represents:

---

Legacy enterprise systems are long-lived, operationally critical platforms that cannot be easily replaced. Rather than pursuing full system overhauls, this work demonstrates how targeted experience-layer modernization can improve usability, reduce cognitive load, and support better decision-making within existing constraints.

My approach centers on:

1. Pattern-Based UX Assumptions

Because this case study is based on a fictitious organization, no formal user interviews or usability studies were conducted. Instead, the redesign applies established UX best practices commonly used when modernizing legacy ERP systems.

These assumptions reflect patterns frequently observed in enterprise environments, including:

• Users navigate multiple modules to assess account status
• Manual interpretation of credit exposure and receivables data
• Reliance on spreadsheets or side tools to reconcile account information
• High cognitive effort is required to interpret large tables and fragmented signals

The design approach focuses on consolidating operational signals, prioritizing decision-critical information, and reducing the mental effort required to evaluate account readiness before processing an order.

2. Information Prioritization

Legacy reporting often provides raw data without context, necessitating interpretation. The pattern introduced in this redesign structures account readiness and key risk factors into logical groups, improving clarity.

• Quickly identifies the status of the account and, if a blockage is present, the status provides a visible indicator on how to resolve the problem
• Data integrity, agreements, certifications, flags, etc.
• Compliance, terms, and billing information are highly visible
• Financial readiness information that includes credit and receivables information
• Operational readiness, backordered items, open returns, shipping restrictions
• Compliance readiness, contracts, pricing information, discount program, etc.

This enhancement provides at-a-glance views of financial and operational risk indicators.

3. Cognitive Load Reduction

Legacy systems often suffer from “cockpit clutter,” where large amounts of information are displayed simultaneously without regard for priority or relevance. This forces customer service representatives to manually scan multiple data points and interpret account risk under time pressure.

Using progressive disclosure, the experience-layer enhancement highlights the most important signals first while secondary details stay accessible but unobtrusive. The Account Readiness screen emphasizes essential information needed to evaluate a customer’s status before an order begins. By prioritizing account health indicators such as credit exposure, aging risk, and operational holds, the design reduces cognitive load and enables customer service representatives to assess account readiness more quickly and make more confident decisions by:

• Eliminating fragmented information scattered across multiple tabs
• Reducing workflows that rely heavily on modals
• Proactively eliminating validation errors at late stages
• Implementing an Information Hierarchy
• Replace dense tables with focused views that surface only relevant signals

The objective is to display only the necessary information to assess account health and to reduce the mental work required to understand it.

4. Modular Modernization

This redesign focuses on user-layer enhancements to improve CSR clarity and decision-making without altering the underlying ERP architecture. By consolidating account health metrics onto a single screen, this interface reduces cognitive load and improves the order evaluation process.

Key improvements include:

• Introducing visual indicators for aging and credit exposure risk factors
• Adding account readiness messaging to indicate operational constraints earlier
• Replacing modal-heavy workflows with inline validation and contextual feedback

These enhancements improve how information is surfaced and interpreted without modifying the ERP system’s core business logic.

5. Designing Within Constraints

Legacy ERP modernization doesn’t have to involve a complete ‘rip-and-replace” approach. Instead, working within the system’s existing constraints helps ensure a smooth transition. The newly designed account readiness screen ensures:

• Maintain compatibility with existing ERP modules
• Avoid introducing new backend dependencies
• Preserve familiar interaction patterns to support user adoption

Why This Matters

---

In high-volume medical supply distribution, order processing speed and accuracy are critical. Hospitals and surgical centers rely on dependable supply chains, and even small delays in order processing can disrupt operations. Customer service representatives are therefore responsible not only for entering orders, but also for evaluating the financial and operational readiness of each customer account.

When account health indicators are scattered across multiple modules, customer service representatives must manually reconcile information before proceeding with an order. This creates decision latency, increases cognitive load, and raises the risk that critical signals — such as credit exposure or receivables aging — may be overlooked.

The Account Readiness Screen addresses this problem by consolidating key operational signals into a single decision surface. By surfacing credit status, aging risk, and account readiness indicators in one place, the design enables customer service representatives to quickly and confidently assess risk before initiating an order.

The result is a workflow that supports faster decision-making, reduces unnecessary interruptions during order entry, and improves visibility into account health across the organization. Rather than forcing users to interpret fragmented data, the system presents a clear operational picture, enabling teams to make consistent and informed decisions.

Design Before

---

The existing workflow required customer service and operations teams to move between multiple legacy ERP modules to evaluate whether an order could be safely processed. Customer information, account contacts, address data, and operational notes were maintained separately from financial risk indicators such as credit exposure, payment aging, disputes, and collection status. While each screen served a specific departmental purpose, users were forced to mentally assemble fragmented information across disconnected workflows in order to determine overall account readiness. This increased cognitive load, slowed decision-making, and created greater dependence on institutional knowledge and user experience rather than clear operational visibility.

Before: Legacy customer and credit workflows were distributed across separate ERP modules, requiring users to manually piece together operational and financial risk before processing orders. Critical account readiness signals were fragmented across disconnected screens, increasing cognitive load and slowing time-sensitive decision-making.

Account Readiness Overview

---

The Account Readiness Overview screen introduces a centralized decision layer within a fragmented legacy ERP environment.

Prior to this, critical account signals were dispersed across multiple systems, requiring customer service representatives to manually piece together account readiness before processing an order.

By consolidating financial, operational, and compliance indicators into a single view, the interface enables faster, more consistent decision-making in high-value transaction scenarios.

This approach reduces cognitive load while making account readiness immediately visible at the point of action.

Account Readiness Overview
By prioritizing essential signals and deferring secondary details, this interface reduces cognitive load and supports faster, more accurate decision-making within a complex ERP environment.

1. Account Status Summary

What it shows:
A centralized view of key account indicators, including credit status, outstanding balance, and overall account standing.

Why it matters:
Removes the need to navigate multiple systems, enabling representatives to quickly determine whether an order can proceed with confidence.

2. Risk & Constraint Indicators

What it shows:
Clear visual signals that highlight potential issues, such as credit holds, inventory constraints, or contract limitations.

Why it matters:
Surfaces critical risks at the point of decision, reducing delays and preventing orders that cannot be fulfilled.

3. Progressive Disclosure Panel

What it shows:
Secondary details such as compliance checks, data integrity, and operational readiness, accessible on demand.

Why it matters:
Reduces cognitive load by prioritizing essential information while still allowing deeper investigation when needed.

4. Shipping Verification

What it shows:
The most recent shipping address associated with the account is displayed for quick reference.

Why it matters:
Provides a lightweight verification point before order entry, helping reduce errors without interrupting workflow.

Design Artifacts

The account readiness workflow depended on a broader ecosystem of operational and administrative tools distributed across the ERP platform. In addition to customer and financial modules, users relied on supporting configuration, logistics, and audit systems to manage delivery requirements, compliance handling, routing rules, and account-level change tracking. These supporting artifacts illustrate how critical operational knowledge was often spread across multiple workflows, increasing the complexity of maintaining accurate account readiness and requiring teams to rely heavily on institutional knowledge and cross-department coordination.

Audit / Change History Screen

The Change History screen explored an earlier navigation and workflow concept focused on operational traceability and account-level auditing across customer locations and delivery environments. The interface was designed to surface historical configuration changes related to logistics, compliance, routing, and contact management in a centralized audit view, helping operational teams understand how account conditions evolved over time.

The left-side navigation represented an earlier design direction intended to consolidate related workflows into a broader operational workspace. During later iterations, this approach was simplified and removed in favor of a more focused account readiness experience that reduced navigation complexity and prioritized critical decision-support information more directly within the workflow.

The Location / Campus Detail Screen

The Location & Campus Detail screen explored how operational delivery requirements, contact management, and compliance rules could be centralized within a more structured account-management experience. The interface was designed to support the complexity of large healthcare systems where individual campuses, departments, and receiving locations often maintained unique routing instructions, delivery restrictions, and operational handling requirements. By consolidating logistics, compliance, and contact information into a single contextual view, the concept aimed to reduce the need for users to search across multiple systems or rely on undocumented tribal knowledge when coordinating time-sensitive medical deliveries.