M1: Need Clarification Method - Selection Logic

Overview

Turn vague wants into testable needs and constraints.

Theoretical basis

• T1 Matching: /en/wiki/theorem-1-matching
• A2 Conditional subjectivity: /en/wiki/axiom-2-conditional-subjectivity

Why it is necessary (zh-aligned)

Without explicit needs:
- you outsource weights to marketing or default rankings,
- you become more vulnerable to anchoring and social proof,
- validation is impossible (you don’t know what success means).

Procedure (template)

1. Scenario inventory: list 3–5 usage scenarios.
2. Must-haves vs nice-to-haves: define thresholds.
3. Constraints: budget, time, size, ecosystem, policy constraints.
4. Success criteria: what would count as “works well–after 2 weeks?
5. Stop rules: what disqualifies an option?

Common pitfalls

• writing needs after browsing (reverse causality),
• mixing preferences with marketing claims,
• failing to define measurable success.

References

1. Simon, H. A. (1955). A behavioral model of rational choice. Quarterly Journal of Economics, 69(1), 99–18.[source]
2. Keeney, R. L., & Raiffa, H. (1993). Decisions with Multiple Objectives: Preferences and Value Tradeoffs. Cambridge University Press.[source]

Further Reading

• M2: Multi-dimensional evaluation
• Decision validation