Mastering Product Information Architecture: Light vs. Heavy Structures

This piece is aimed at interaction designers or anyone interested in interaction design, discussing product information architecture without defining the term.

All products have an information architecture, ranging from simple to complex. The author categorizes them as “light‑architecture” products (e.g., consumer apps like WeChat, QQ Music, Tencent Video) and “heavy‑architecture” products (e.g., enterprise tools, CRM, business support systems).

Light‑architecture products require a clear, simple structure that minimizes learning cost and maximizes efficiency for a large user base, often achieved through reduction and focus.

Heavy‑architecture products demand a comprehensive, rigorous structure that supports extensive functionality, tolerates higher learning costs, and often requires user training; they need thoughtful integration and flexible layout to serve focused user groups.

The author reflects on personal experience designing both types at Huawei, noting that light‑architecture design is enjoyable but challenges innovation, while heavy‑architecture design sharpens interaction skills but demands deep business understanding and extensive user research.

Hierarchical Structure

Hierarchical structures organize nodes in parent/child relationships, making them intuitive for users and aligning with software’s natural operation. The author introduces a “balanced” use: top‑down (from product vision to features) and bottom‑up (from valuable features to product core). Both have drawbacks, so a middle “captain” layer is proposed to reconcile strategic goals with numerous low‑level features, resulting in a unified architecture.

Organic (Natural) Structure

Organic structures lack a fixed pattern, linking nodes freely, suitable for exploratory or evolving topics. They work well for browsing‑oriented consumer apps (e.g., entertainment) but are less effective for task‑oriented enterprise tools where users need predictable paths.

Sequential (Linear) Structure

Linear structures follow a straightforward, ordered flow, similar to books or videos, and are ideal for small‑scale content or scenarios where sequence is critical, such as tutorials or storytelling.

Matrix Structure

Matrix structures let users navigate along multiple dimensions (e.g., color vs. size), accommodating diverse needs but becoming unwieldy beyond three dimensions. The author likens this to design team KPI evaluation, balancing business goals and design growth.

Overall, mastering various information‑architecture models—hierarchical, organic, linear, and matrix—helps interaction designers handle both simple and complex products, enhancing design execution and impact.