How Task‑ and Goal‑Oriented Information Architecture Shapes Data Product Design

What Is Information Architecture

Information architecture involves analyzing, organizing, and researching a product’s content, functions, framework, and objectives, creating a rational structure for information.

In interaction design, it is seen as the process of comprehensively planning organized information units for specific target users, including analysis of business content and workflows, essentially building a bridge between information and users.

Task‑Oriented Information Architecture

Tool‑type products aimed at a single goal but with complex task structures have larger content volumes and richer functions, requiring careful consideration of content collection, content review, and information grouping.

Content collection: gather product information such as product goals, user goals, requirements, sources, and business processes.

Content review: assess accuracy, usability, and effectiveness.

Information grouping: define relationships among content/pages/functions and organize them into groups.

Example: NetEase YouShu, an agile data‑visualization platform, targets professional data analysts. Its focus is enabling analysts to quickly enter analysis mode, allowing them to directly access needed modules or functions.

Through functional classification, content grouping, and user flows, the product can be broken into three interrelated but distinct information units: data sources, reports, and dashboards.

Users typically move to the data module to prepare data, then to the report module for analysis, and finally to the dashboard to compile reports.

Connect data source → Create report → Build dashboard

This mirrors a home‑buying process where analysts act as real‑estate professionals, knowing exactly which steps and materials are needed.

In summary, task‑oriented architecture dissects scattered tasks, arranges modules and functions according to logical workflow, and may involve multiple module switches, risking interruptions if the process is lengthy.

Goal‑Oriented Information Architecture

In 2016, the product shifted its target to business users in traditional enterprises, making “reports” the new product focus. Business users expect to create simple charts and reports for monitoring, sharing, or presenting to leadership.

Designers must therefore rethink product emphasis, reorganize the information architecture, and clarify the relationship between functional modules to support a goal‑oriented structure.

The resulting design retains only two modules: a data‑preparation module for IT staff and a “report” module for business users, allowing them to complete the entire reporting task on a single page.

Report creation → Need charts → Charts need data

This approach aligns with users’ mental models, reducing unnecessary module switches and streamlining the workflow.

Summary

Complex, task‑heavy B2B tools benefit from task‑oriented architecture, while products with single‑goal but complex tasks suit goal‑oriented architecture. Professional users favor task‑oriented designs; ordinary or amateur users benefit from goal‑oriented designs that guide them step‑by‑step toward their objectives.

Both approaches are valid; the key is to match the architecture to the product’s characteristics and user needs.