How Structured Thinking Can Supercharge Your Design Projects
This article explains structured thinking, outlines top‑down and bottom‑up methods, and demonstrates their practical application in a data‑science platform redesign, showing how clear hierarchies improve problem analysis, user experience, and communication for designers and product teams.
When planning a trip, many people feel overwhelmed by choices such as destination, timing, route, accommodation, and packing. The author proposes using a structured‑thinking diagram to break down these elements, turning a complex task into manageable steps.
What Is Structured Thinking?
Structured thinking means analyzing a problem from multiple angles, identifying root causes, and creating systematic action plans to achieve high performance, as defined by Baidu Baike. It involves decomposing a complex issue into simple, clear sub‑problems that the brain can process more efficiently.
Methods to Structure Your Thinking
Two approaches from Barbara Minto’s The Pyramid Principle are presented:
Method 1: Top‑Down Structure
When familiar with a domain, you can quickly recall existing frameworks and expand them (e.g., “eat, stay, play, travel” for trip planning) to build a complete diagram.
Method 2: Bottom‑Up Structure
For unfamiliar problems, follow four steps to create a clear hierarchy:
Information categorisation
Information grouping
Structure extraction
Structure refinement
The author illustrates this with a real design case from the “Mammoth” project, a one‑stop big‑data development platform at NetEase Data Science Center.
After gathering user feedback and usability test results, the team listed problem items and applied the four‑step method.
Step 1: Information Categorisation
Problems were linked based on similarity (e.g., two issues about feature discoverability were connected), producing an information‑link diagram.
Step 2: Information Grouping
The linked items were grouped into four major categories, visualised in a diagram.
Step 3: Structure Extraction
Each group was described in formal language, revealing issues such as unclear task scenarios, poor feature discoverability, insufficient guidance, and mismatched user expectations.
Step 4: Structure Refinement
The refined framework was further expanded, for example splitting “feedback” into pre‑action and post‑action categories, and identifying missing cues such as upload progress indicators.
Resulting design improvements include:
Pre‑action: Provide Guidance – Added hover highlights and click animations to indicate draggable nodes.
During Action: Offer Thoughtful Feedback – Implemented loading animation and location hint after uploading a project package.
Post‑action: Clearly Communicate Results – Replaced brief icons with persistent dialog prompts for success/failure, added textual explanations to result icons, enhanced node status indicators, and enlarged operation tips with longer fade‑out animations.
What Can Structured Thinking Give Designers?
Designers who apply structured thinking achieve clearer, defensible design proposals, smoother communication with team members, and a systematic knowledge base that integrates fragmented information into a cohesive framework, ultimately enhancing problem‑solving efficiency.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
网易UEDC
NetEase UEDC aims to become a knowledge sharing platform for design professionals, aggregating experience summaries and methodology research on user experience from numerous NetEase products, such as NetEase Cloud Music, Media, Youdao, Yanxuan, Data帆, Smart Enterprise, Lingxi, Yixin, Email, and Wenman. We adhere to the philosophy of "Passion, Innovation, Being with Users" to drive shared progress in the industry ecosystem.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
