top of page

ERP Chart of Accounts redesign

A design-thinking approach to a Chart of Accounts that stakeholders saw as dated and overly complex, on a platform that had not been meaningfully evaluated since it launched.

pexels-pixabay-356043.jpg

Context

​

Stakeholders recognized that a significant rebranding effort, coupled with primary-page redesign, was needed to make their platform more intuitive and user-friendly. The experience had not been meaningfully evaluated since the product’s start, and stakeholders had noticed a dated and overly complex user experience. The work focuses on a Chart of Accounts redesign.

Role

UX design at LINQ, including competitor research, journey mapping, high-fidelity mockups, accessibility, iteration, and validation, with AI tools used in the process.

Problem

​

The Chart of Accounts was dated and overly complex, and it had not been meaningfully rethought since the product launched. Stakeholders wanted a more relevant, intuitive, and seamless experience that would still offer exceptional functionality — building on and enhancing the current platform, not discarding what it already did well.

Process

​

The work moved from stakeholder problem-framing into competitor research, AI tools, journey mapping, high-fidelity mockups, accessibility, iteration, and validation.

Users wanted a simpler layout with advanced functionality still available. Elevating key data points and offering more straightforward navigation was essential. Although the platform excelled at its overall purpose, users would have appreciated a smoother process for the tasks they needed to complete. Users and subject-matter experts confirmed the stakeholders’ key areas of focus, and acknowledged that other pages and operations were secondary to those focus features.

pexels-picjumbocom-196645.jpg
pexels-startup-stock-photos-212286.jpg

Governance and collaboration

​

Leadership in this work was in aligning stakeholders, users, and subject-matter experts on what mattered: confirming the stakeholders’ focus areas, treating other pages as secondary, and holding both simplicity and advanced functionality in the same design. Accessibility was part of the process.

Solution

Figma & PDF Versions

The designed direction was a more intuitive Chart of Accounts: a simpler layout that still holds advanced functionality, with key data elevated and navigation made more straightforward — a more relevant, seamless solution that builds on the current platform.

Outcome and status

Status: the business put the ERP project on hold. This page describes how the design problem was approached. It does not claim that the work launched or had product impact.

What the design process surfaced (not launch results): users wanted a simpler layout while maintaining advanced functionality; elevating key data and offering straightforward navigation was essential; users and SMEs confirmed the stakeholders’ areas of focus.

Learnings

Users wanted the platform to feel simpler without losing the advanced functionality they relied on. The design work treated that as a both/and problem: elevate what matters, straighten navigation, and keep the depth. Aligning stakeholders, users, and SMEs on a focused set of pages — and treating the rest as secondary — was part of keeping that work coherent. These are process learnings, not claims about a launched product.

Screenshot 2025-08-19 at 2.36.11 PM.png
bottom of page