CHALLENGE
Too much information. Not enough guidance.
Users struggled to find the right answer without navigating a maze of categories and articles.
Quentic's help center had evolved into a large and comprehensive documentation ecosystem. While rich in information, users often had to navigate deep category structures, lengthy articles, and product-focused navigation before finding the guidance they needed.
This project reimagined the support experience from the ground up. By redesigning the help portal, restructuring article templates, and introducing a more intuitive information architecture, the experience shifted from information-first to task-first—helping users find answers faster and complete their work with confidence.
Year
11.25
Scope
Branding
01_ Help portal redesign
From browsing to doing
The original help portal was organized primarily around content categories. While comprehensive, it required users to know where information lived before they could find it. The redesign shifted the experience toward common tasks and user goals. Quick actions, guided entry points, and clearer pathways helped users reach relevant information faster and with less effort.
Introduced task-based navigation
Surfaced common user actions directly on the homepage
Reduced dependency on deep category structures
02_ Help article redesign
Same content. Better structure. Easier to act.
Many articles contained valuable information, but dense layouts and inconsistent structures made them difficult to scan. Users often had to read large sections before finding the answer they needed. The new article template focused on clarity and actionability. Information was reorganized into predictable sections, visual hierarchy was strengthened, and procedural guidance became easier to follow.
Clear step-by-step structure
Improved readability and scanning
Consistent patterns across all documentation
03_ Information architecture redesign
Designed around user goals, not product structure.
The original help center mirrored the structure of the software itself, organizing content around modules, administrative functions, and technical concepts. While comprehensive, it required users to understand the product before they could find the information they needed. The redesigned information architecture prioritized user goals, common tasks, and learning pathways. By introducing task-based entry points and clearer navigation patterns, the experience became easier to navigate, learn, and scale.
Task-based navigation
Clear learning pathways
Reduced content complexity
