Structured Thinking: A Guide for Test Engineers

Introduction

This year marks my tenth anniversary in the testing industry. Over the past decade I have worked with many people and often encountered questions such as why some engineers solve complex testing tasks quickly while others take much longer, or why some can articulate problems clearly and others cannot.

Facing the same complex testing task, some people can devise a solution within a day, while others linger for a long time?
  Some can describe work issues quickly, while others stammer and cannot be clear?
  When asked "What is the basis for your statement? Any concrete example?", some get stuck, while others present facts and reasoning in an orderly way?
  …

What Is Structured Thinking?

Structured thinking means that when facing a problem you can decompose it into solvable parts using a certain framework.

For example, as an interviewer you might ask a candidate how to test a shopping‑cart feature. Answers may range from adding and deleting items, checking price calculations, testing coupon usage, etc. These answers are often based on personal testing experience and may not be comprehensive.

Some candidates say: first add to cart, then delete, verify quantity; check price when items are selected; test how many items can be added; test coupon usage; …

Test categories such as UI testing, functional testing, performance testing, security testing, exception testing, and compatibility testing can be used to break down the analysis. By iteratively subdividing each category until no further division is possible, you obtain a clear, complete test plan.

The result is a structured, top‑down analysis that helps write test cases and organize test points more comprehensively.

Structured thinking is a process that turns chaos into order. It builds a hierarchical analysis starting from the overall problem down to details, often visualized as a pyramid‑shaped tree diagram.

Why Should Test Engineers Learn Structured Thinking?

Test engineers must handle complex products, communicate across roles, and sometimes manage projects, processes, and client interactions. Differences in how quickly people can pinpoint issues or organize test points often stem from whether they have an effective information‑processing and logical‑structuring method.

For instance, during an incident a colleague reported: "The previous code has a problem, some data was pushed to another platform, fixing it now would have a big impact, can we change it later?" Without a clear structure, the receiver lacks details about impact scope, timeline, and concrete solutions, leading to higher communication costs.

Structured thinking reduces such asymmetry, allowing clear, hierarchical presentation of ideas and improving problem‑solving efficiency while lowering communication overhead.

How to Improve Structured Thinking

After understanding its importance, you can train structured thinking using the pyramid model and various classification methods.

The pyramid has two logical directions: vertical (conclusion first, then supporting details) and horizontal (grouping, logical progression). This follows the principle of "argument analogy".

Vertical: higher‑level ideas summarize lower‑level ones; lower levels support the higher level.

Horizontal: ideas within the same level belong to the same logical category and are ordered logically.

Structured thinking can be broken down into three capabilities:

1. Information Summarization – Horizontal Analogy

Collecting massive information is insufficient; summarizing helps memory and logical clarity. The MECE principle (Mutually Exclusive, Collectively Exhaustive) ensures categories are independent and exhaustive.

Common MECE methods include:

1) Binary Classification

Domestic vs. overseas, others vs. self, married vs. unmarried, adult vs. minor, left vs. right, male vs. female, income vs. expense, professional vs. amateur, etc.

2) Process Classification

Daily schedules, six steps to solve a problem, three phases to achieve a goal – all belong to process classification, useful for project progress reporting.

3) Element Classification

Seven qualities of an excellent employee, organizational charts – breaking a whole into constituent parts, from top‑down or inside‑out.

4) Formula Classification

Price = UnitPrice * Quantity – the formula defines the elements, satisfying MECE.

5) Matrix Classification

Four work categories: important‑urgent, important‑not urgent, not important‑urgent, not important‑not urgent – placed into a 2×2 matrix.

6) Scenario‑Specific Rules

Beyond MECE, models like 3C (Company, Customer, Competitor), 7S (Strategy, Structure, System, Style, Staff, Skill, Shared values), SWOT, SMART, etc., provide tailored classification frameworks.

Applying these methods in the workplace, for example when drafting a meeting notice about recurring P1 incidents, the 5W2H model (Goal, Time, Place, Agenda, …) yields a clearer, more structured communication than a vague paragraph.

Goal: Raise quality awareness, avoid P1 incidents in the second half of the year.
Time: Oct 22, 3 pm.
Place: Building 3, Room 205.
Agenda: 1) Incident review. 2) Prevention strategy.

2. Conclusion Extraction – Vertical Reasoning

Two main vertical reasoning methods are deduction and induction.

Deductive Reasoning

Starts from a general rule and reaches a specific conclusion, e.g., Aristotle’s syllogism: All humans die; Socrates is human; therefore Socrates dies.

Known rule: Frequent requirement changes cause bugs.
Specific event: Release is near, business wants new feature.
Conclusion: Do not add the feature.

Key points: question the rule’s validity and maintain a rich knowledge base.

Inductive Reasoning

Abstracts commonalities from specific instances to form a higher‑level concept, e.g., apples and oranges belong to “fruit”.

Apples and oranges → “fruit”. The new concept requires background knowledge.

Key points: avoid bias, ensure representative samples, and broaden experience.

3. Information Presentation – Top‑Down

Effective communication presents conclusions first, then supporting evidence, and finally reinforces the conclusion.

1. Conclusion: Login API has a bug causing online issues; needs immediate fix.
2. Details: Cause is xxx, persisted for xx days, heavily affecting users, multiple support tickets.
3. Summary: Resolve urgently, preferably today.

Tips for practicing top‑down communication include using frameworks like Problem‑Cause‑Solution, SWOT, and visualizing the logical flow.

Conclusion

Structured thinking not only enhances the ability to convey information efficiently but also demonstrates strong analytical and problem‑solving skills in the workplace.

Hope this summary provides useful insights and inspiration for your professional growth.