Mastering Problem Analysis: A Six‑Step Framework for Clear Requirements

Background

A project’s requirement review was blocked because an expert considered a feature design unreasonable. The team initially tried a quick fix, but the issue persisted, revealing a lack of understanding of the core concept.

Analysis Framework Overview

A six‑step problem‑analysis framework can clarify the issue within a short time.

1. Clarify Business Goal

Restate the business objective in plain language, without technical jargon, to verify whether the feature is necessary.

2. Clarify Core Concept

Identify the core concept (e.g., “A”) and examine its:

Intension (internal attributes) : essential properties that define the concept.

Extension (applicable scope) : the range of objects or scenarios the concept can cover.

Relations and boundaries : how the concept differs from or overlaps with other concepts.

3. Objectively Decompose the Problem

Engage the problem proposer to ensure correct understanding, then ask targeted questions such as:

Is the issue a denial of the concept’s intension?

Is it a denial of the concept’s extension?

Is it a denial of the concept’s boundaries?

Is it a denial of the concept’s practical implementation?

4. Map the Current Solution Logic

After breaking down the problem, compare the existing design against the clarified business goal and core concept to locate logical flaws.

5. Propose Possible Solutions

Generate concrete alternatives, highlight the most suitable one, and discuss trade‑offs.

6. Final Conclusion and Planning

Present the selected solution to stakeholders, confirm it meets expectations, and outline implementation details such as timeline, resources, and responsibilities.

Why This Matters

The method helps teams avoid ad‑hoc troubleshooting and adopt a structured, business‑oriented mindset. Weak object‑oriented analysis is a common root cause of design defects.