Leigh Arriane Buendia
Back

ABAS ERP Redesign: Avega Bros. Integrated Shipping Corporation

Redesigning a legacy ERP used daily by 100+ employees at a 40-year-old Philippine logistics company.

ABAS

Overview

ABAS (AVega Business Automation System) is the internal ERP platform used daily by 100+ employees at Avega Bros., a Philippine shipping and logistics company with 40+ years of operations. The system manages everything from HR and attendance tracking to recruitment, crew movements, payroll, and employee relations. When I joined the project, ABAS was functional but deeply outdated, built on legacy UI patterns that made it difficult to navigate, hard to learn, and slow to use. Employees routinely bypassed the system in favor of spreadsheets.

Role

Lead Product Designer: led the full redesign of the HR module, built a design system from scratch, and established a scalable design framework for future modules, while managing design interns and running iterative design reviews with stakeholders.

Team

Design Lead + Design Interns + Developers + Stakeholders

Timeline

Ongoing (2026-Present)

Platform

Desktop Web Application

Client

Avega Bros. Integrated Shipping Corporation

Tech Stack

Figma

Case Study

Full
TL;DR

The Problem

ABAS served a critical function, it was the operational backbone for managing 100+ employees across multiple departments and vessel crews. But the interface hadn't evolved with the company's needs. Through employee interviews and a heuristic evaluation of the existing system, I identified three categories of problems.

Legacy ABAS interface
01
Navigation was flat and overwhelmingThe old sidebar presented 25+ menu items in a single, uncategorized list, Employee DTR Monitoring, Authorize Employee Requests, Action Memos, Crew Movements, AWOL Cases, Leave Applications, OT Applications, and more. There was no grouping, no hierarchy, and no way to understand what belonged together. Related functions like Departments, Divisions, Sections, Sub-sections, Positions, Salary Grades, Leave Credit Codes, and Leave Types each had their own dedicated entry, forcing users to scroll through a wall of links to find what they needed.
02
Data-heavy screens lacked focusThe Employee Masterlist displayed a 10-column table spanning 3,854 rows with only a single "Show by Employee Status" filter and a basic search bar. There were no advanced filters, no column prioritization, and no way to surface the information that mattered most for a given task. The table showed everything: Employee ID, Fullname, Company, Designation, Group, Department, Division, Position, Employment Status, and Actions.
03
Forms consumed the screen without guiding the userThe Leave Applications page dedicated over half the viewport to a filter panel (date range, employee name, type, paid/unpaid, and six status checkboxes) before showing any results. There was no progressive disclosure, every filter option was visible at all times, regardless of how often it was used. The actual data table sat below the fold with a "No matching records found" message, requiring users to configure filters before seeing anything useful.
04
Employees defaulted to spreadsheetsDuring interviews, the most consistent finding was that employees were working around the system rather than within it. The friction of navigating ABAS, finding the right page, understanding dense tables, filling out forms, was high enough that many tasks were being tracked in personal spreadsheets instead. This created data silos, inconsistent records, and duplicated effort across the organization.

Research & Discovery

Employee Interviews

I conducted interviews with employees across roles and departments to understand how they actually used ABAS day-to-day. I transcribed every session, broke each transcript into individual observations and quotes, then clustered them on a board. Four themes surfaced again and again, and almost all of them traced back to a single behavior: people had quietly moved their real work out of ABAS and into spreadsheets.

“I just use Sheets instead”

ABAS wasn't the system of record, personal spreadsheets were.

Honestly? I keep my own Excel file. It's faster than opening ABAS.

Our team's leave tracker lives in one Google Sheet, that's the real source of truth, not the system.

When payroll needs numbers, I export to Excel and fix everything there anyway.

I built my sheet years ago and I've never stopped using it.

“I can never find anything”

25+ flat menu items + weak search = users gave up navigating.

I type a name into search and half the time nothing comes up.

Search only works if you spell it exactly how they encoded it.

There are 25 things in the sidebar, I can never remember which one I need.

For anything I don't do every day, I just give up and ask a colleague.

“Building a table takes forever”

Getting a clean, filtered list out of ABAS was slower than rebuilding it by hand.

Pulling a clean list out of ABAS takes me half an hour. In Sheets it's two minutes.

I can't sort or filter the way I need, so I copy it all out and do it myself.

Making a simple report means re-typing everything into a table by hand.

The masterlist is 10 columns of everything, I only ever need three.

“I don't trust it, so I keep my own copy”

Confusion bred low confidence; people defaulted to what they could control.

I'm never sure what's in there is up to date, so I keep my own copy.

It feels like one wrong click and I've broken something.

New hires take weeks before they'll touch ABAS on their own.

Why rely on the website when my sheet has never failed me?

01
Spreadsheet dependency was systemicEmployees maintained their own tracking sheets because finding information in ABAS took too long or felt unreliable.
02
Navigation was the biggest friction pointUsers couldn't remember which of the 25+ sidebar items led to the function they needed, especially for infrequent tasks.
03
The system felt intimidating to new employeesOnboarding onto ABAS was slow because there was no clear mental model for how the system was organized.
04
Approval workflows were opaqueEmployees submitted requests (leave, OT, OB) but had limited visibility into where those requests were in the process.

Heuristic Evaluation

To complement the interviews, I audited the existing ABAS interface against Nielsen's 10 usability heuristics, walking through the core HR screens (sidebar, Employee Masterlist, Leave Applications) and rating each violation on Nielsen's 0–4 severity scale. The audit gave the spreadsheet workarounds a concrete cause: the system was working against the heuristics that make software learnable and efficient.

Severity scale4 Catastrophic3 Major2 Minor1 Cosmetic
HeuristicIssue identifiedSeverityRecommendation
Recognition rather than recallThe flat sidebar lists 25+ uncategorized items, forcing users to memorize which one maps to each task. No grouping, no meaningful icons, and no breadcrumbs to show where they are.4 · CatastrophicGroup items into collapsible categories, add a breadcrumb trail, and use recognizable section icons.
Aesthetic and minimalist designThe Employee Masterlist renders a 10-column table across 3,854 rows, and Leave Applications devotes half the viewport to an always-expanded filter panel before any data loads.3 · MajorPrioritize columns by task, collapse advanced filters behind progressive disclosure, and surface results first.
Visibility of system statusApproval workflows (leave, OT, OB) give no feedback after submission, employees can't see where a request sits in the pipeline or who needs to act next.3 · MajorAdd a clear status indicator (Pending → Approved / Rejected) and a timestamped activity trail on each request.
Consistency and standardsButton styling is inconsistent (green "Add" vs. gray "Back"), sidebar spacing is uneven, and there is no unified color system across screens.3 · MajorEstablish a design system with tokenized colors, spacing, and a standardized button hierarchy.
Flexibility and efficiency of useThere are no accelerators for frequent tasks. The Quick Access search exists but is buried, and there are no recents, favorites, or saved filters for power users.3 · MajorPromote global search, add saved views and favorites, and provide bulk actions for repeat workflows.
Match between system and the real worldLabels mirror database fields ("Sub-sections", "Leave Credit Codes") rather than the language employees actually use to describe their work.2 · MinorRename entries to task-oriented, human language grouped around real workflows.
Help users recognize, diagnose, and recover from errorsEmpty states like "No matching records found" give no cause or next step, and form errors aren't tied to the field that triggered them.2 · MinorWrite actionable empty and error states ("No results, try clearing filters") with inline, field-level validation.

Ideation & Design Decisions

Information Architecture Overhaul

The most impactful change was restructuring the entire navigation. I consolidated 25+ flat sidebar items into 13 grouped categories with collapsible sub-menus.

Departments, Divisions, Sections, Sub-sections (4 separate pages)Consolidated into Roles & Structure with tabbed sub-navigation
Positions (separate page)Roles & Structure → Positions tab
Salary Grades, Leave Credit Codes, Leave Types (3 separate pages)Consolidated into Compensation & Benefits (collapsible group)
Organizational Chart (separate page)Roles & Structure → Org Chart tab
Recruitment (single flat page)Recruitment & Onboarding → Career Postings / Hiring Pipeline
Leave, OT, UT, OB Applications (4 separate pages)Consolidated into Attendance & Time (collapsible group)
After: 13 grouped categories

The core principle: related data should live together. Positions, Departments, Divisions, and Org Chart are all facets of the same concept, organizational structure. They don't need four sidebar items; they need one page with four tabs.

Tab-Based Sub-Navigation

Instead of scattering related content across separate pages, I introduced horizontal tab bars within pages. The Roles & Structure page now has tabs for Positions, Departments, Divisions, and Organizational Chart, all accessible without leaving the page or losing context. Each tab shows a count badge so users can see the scope at a glance.

/Roles & Structure

Roles & Structure

Defines organizational roles, departments, reporting lines, and access levels.

Positions

85 positions
CodePositionHierarchyDivisionDepartmentActions
234Marketing ManagerSupervisorMarketing and OperationsMarketing
932Marketing AssociateManagerCorporate ServicesHuman Resources
143Lead DeveloperPresidentAsset ManagementSales
420Content ManagerSection HeadAsset ManagementOperations
124Business AnalystSub-section HeadCorporate ServicesProject Management
816DirectorManagerMarketing and OperationsTechnology
← PreviousNext →

Breadcrumb Navigation

Every page now includes a breadcrumb trail (e.g., Home → Recruitment & Onboarding → Career Postings) so users always know where they are in the system and can navigate upward without relying solely on the sidebar.

Breadcrumb navigation

Status-Filtered Tabs with Counts

For workflow-heavy pages like Career Postings and Hiring Pipeline, I added status tabs with real-time counts (All 12 · Drafts 5 · Submitted 2 · Approved 3 · Rejected 2). This eliminates the need for a separate filter panel for the most common filtering action, checking items by status, and gives managers an instant overview of their pipeline without any clicks.

/Recruitment & Onboarding/Hiring Pipeline

Hiring Pipeline

Track applicants and manage their progress from application to onboarding.

Applicants

17 applicants
NamePosition AppliedDate AppliedLocationSourceStatusResumeActions
John ParkerMarketing AssociateFebruary 24, 2026ManilaEmailAppliedDOCResume12…
Miguel SantosSales OfficerMarch 5, 2026CebuWebsiteAppliedPDFResume.pdf
Ella RiveraHR AssistantMarch 18, 2026DavaoWebsiteAppliedDOCXResume.docx
Lyra BuendiaLead DeveloperApril 24, 2026CebuReferralShortlistedDOCXResume.docx
Noah CruzProject CoordinatorApril 2, 2026ManilaReferralShortlistedPDFResume.pdf
Maya ReyesUX DesignerMay 11, 2026CebuWebsiteShortlistedDOCXResume.docx

Multi-Step Modal Wizards

The old system had no structured workflow for complex processes like hiring. I designed a 4-step wizard for the hiring pipeline, with a progress indicator, clear step labels, and a persistent activity trail so the hiring manager can see who took what action and when.

Multi-step modal wizard
01
Applicant InformationBasic details, position applied for, and document upload.
02
Applicant ScreeningResume preview displayed inline alongside a screening checklist, meets minimum qualifications, relevant experience, aligned salary range, location/availability. No more switching tabs or downloading PDFs to review a candidate.
03
Assessment PlanningExamination scheduling (written exam, trade test) and interview stage assignment with interviewer selection.
04
Assessment SummaryFinal review with a full activity trail showing who took what action and when.

Consistent Design System

I built the design system from scratch, establishing four pillars that every module now inherits.

ColorAvega brand red (#D92D20) as the primary action color, with semantic status colors, green for Active/Approved, yellow for Draft, blue for Submitted/Shortlisted, red for Rejected/Inactive, purple for Onboarding.
TypographyClean hierarchy with consistent sizing across page titles, section headers, table headers, and body text.
ComponentsStandardized tables, modals, form inputs, buttons (primary red, secondary outline), status badges, breadcrumbs, and sidebar navigation.
PatternsEvery list page follows the same structure, page title with description, status tabs with counts, action button + filters, data table with pagination.
Component library
GradientGradient
Darker Red#D80000
Red#E60000
White#FAFAFA
Lightest Gray#EFEFEF
Lighter Gray#BFBFBF
Light Gray#787878
Black#171717
TypefaceNeue Haas Grotesk Display Pro
Display32px · Bold
HR Management System
Heading24px · Bold
Employee Masterlist
Subheading20px · Semibold
Leave Applications
Body16px · Regular
Manage employee records, track attendance, and process requests.
Label12px · Medium
ACTIVE · PENDING · APPROVED

Final Design & Key Screens

Authentication Flow

A branded login experience with the Avega "AV" logo, OTP verification with clear 6-digit input fields, and a forgot password flow. The right panel features brand imagery that reinforces the company identity from the first interaction.

Login pageOTP verification

Roles & Structure

A single page with four tabs replacing what was previously four separate sidebar items. The Positions tab displays a clean 6-column table with hierarchy and department context. The Org Chart tab visualizes reporting structure with interactive "Add Position" placeholders for building out the hierarchy.

Positions tabOrg chart tab

Career Postings

A recruitment management view with status-filtered tabs showing counts, a publish toggle for live postings, and an "Edit Position" modal for quick updates without leaving the page.

Career postings listEdit position modal

Hiring Pipeline

The most complex flow: an applicant tracking system with status-filtered tabs (Applicants 17 · Shortlisted 5 · For Interview 2 · Accepted 3 · Rejected 2 · Onboarding 2), inline resume file icons, and a 4-step wizard for progressing candidates through screening, assessment planning, and final evaluation.

Hiring pipeline list
Wizard step 1: applicant informationWizard step 2: applicant screening

Current Status

🟡 This project is ongoing. The HR module redesign is in testing and partial rollout. Results, impact metrics, and a full retrospective will be added once the redesigned system has been in use across the organization.

What's been delivered so far

Complete HR module redesign: navigation, employee masterlist, roles & structure, recruitment, hiring pipeline, and attendance tracking
Design system built from scratch: reusable components and patterns that will scale across future modules (fleet management, finance, payroll)
Structured hiring workflow: a multi-step process replacing an untracked, spreadsheet-based approach

My role & contributions

Led all UX research (employee interviews, heuristic evaluation)
Defined the new information architecture and navigation model
Designed all high-fidelity screens and interactive prototypes in Figma
Built the product design system from scratch
Managed and mentored design interns, running weekly design reviews and revision cycles
Collaborated with developers on implementation feasibility and handoff

What's next

Rollout of remaining modules (fleet management, finance, payroll, crew movements)
Collecting quantitative impact data (task completion time, spreadsheet dependency reduction, onboarding speed)
Iterating based on employee feedback post-launch