IAS/
INFORMATION ARCHITECTURE
From current-state complexity to a clearer architecture
From current-state complexity to a clearer architecture
I mapped the existing QBOA navigation to understand how functions, routes and product areas were organised. Bringing the entire experience into one view exposed where complexity had accumulated and created a baseline for exploring a clearer architecture for Accountant Suite.
I mapped the existing QBOA navigation to understand how functions, routes and product areas were organised. Bringing the entire experience into one view exposed where complexity had accumulated and created a baseline for exploring a clearer architecture for Accountant Suite.
I mapped the existing QBOA navigation to understand how functions, routes and product areas were organised. Bringing the entire experience into one view exposed where complexity had accumulated and created a baseline for exploring a clearer architecture for Accountant Suite.
01 / CURRENT STATE
Current QBOA navigation
Current QBOA navigation
The current-state map revealed how the product had evolved across multiple areas, creating overlapping routes, competing contexts and ambiguity around where some tasks belonged. Mapping the full experience made those relationships — and the accumulated complexity — visible.
The current-state map revealed how the product had evolved across multiple areas, creating overlapping routes, competing contexts and ambiguity around where some tasks belonged. Mapping the full experience made those relationships — and the accumulated complexity — visible.
The current-state map revealed how the product had evolved across multiple areas, creating overlapping routes, competing contexts and ambiguity around where some tasks belonged. Mapping the full experience made those relationships — and the accumulated complexity — visible.
Current-state QBOA information architecture.
WHAT CHANGED
A clearer and more scalable structure
Clearer contexts
Practice-level and client-level work were given more deliberate places within the architecture.
Practice-level and client-level work were given more deliberate places within the architecture.
More consistent routes
Functions were organised around clearer entry points, reducing ambiguity around where tasks should begin.
Functions were organised around clearer entry points, reducing ambiguity around where tasks should begin.
Built to scale
The structure created clearer foundations for new products and capabilities as Accountant Suite evolved.
The structure created clearer foundations for new products and capabilities as Accountant Suite evolved.
02 / PROPOSED ARCHITECTURE
Proposed navigation for Accountant Suite
Proposed navigation for Accountant Suite
The proposed architecture brought the research findings and design principles into a clearer product structure. It aimed to better reflect how accounting firms worked, give functions more logical homes and provide a foundation that could accommodate future capabilities without recreating the complexity of the existing experience.
The proposed architecture brought the research findings and design principles into a clearer product structure. It aimed to better reflect how accounting firms worked, give functions more logical homes and provide a foundation that could accommodate future capabilities without recreating the complexity of the existing experience.
The proposed architecture brought the research findings and design principles into a clearer product structure. It aimed to better reflect how accounting firms worked, give functions more logical homes and provide a foundation that could accommodate future capabilities without recreating the complexity of the existing experience.
Proposed information architecture for Accountant Suite.