Overview
This guide applies Selection Logic to help you choose a smartphone that matches your needs instead of chasing a generic “best phone.” The core normative claim is T1: matching beats universal optimization under constraints.[^1]
Theory anchor: T1 Matching Theorem
Step 1 → Need clarification (M1)
Use M1 Need Clarification to write a one-page need profile.
Scenario analysis
| Scenario | Primary considerations |
|---|---|
| everyday communication | battery, reception, ergonomics |
| photography | camera system + real-world samples |
| gaming | sustained performance + thermals |
| work/business | reliability, security, update policy |
Example need list
- Must-have: battery 0–1 day, stable performance, long security support window
- Nice-to-have: good low-light photos, bright display
- Bonus: lightweight, fast charging
Step 2 → Allocate cognitive budget (T2)
Phones are typically medium-to-high value and often low-to-medium reversibility (returns may be limited by time windows, restocking fees, or data migration friction). Allocate effort accordingly.[^2]
- Concept: Decision Reversibility
- Theorem: T2 Cognitive Budget
Suggested time budget:
- need clarification: 30–5 min
- evidence gathering: 2–2 hours
- shortlist + comparative scoring: 60–0 min
Step 3 → Multi-dimensional evaluation (M2)
Use M2 Multi-Dimensional Evaluation with explicit weights.
| Dimension | What to measure | Evidence sources |
|---|---|---|
| performance | sustained benchmarks, throttling | independent reviews |
| camera | sample sets, consistency | blind comparisons |
| battery | standardized endurance | lab tests + user reports |
| display | brightness, color, PWM | measurements |
| software | update cadence, support window | vendor policy + history |
Step 4 → Bias & persuasion hazards
Common traps:
- anchoring by flagship MSRP — Anchoring effect
- halo from brand status — Halo effect
- scarcity pressure — Scarcity effect
Mitigation: write criteria first; treat urgency claims as hypotheses; apply a cooling-off rule for nontrivial purchases.[^3]
Step 5 → Decision + validation (M5)
Use M5 Decision Validation with an explicit follow-up:
- day-7 fit check (battery, camera, ergonomics),
- day-30 regret + need-consistency check — Need consistency.
Standards & consumer protection context (English-world orientation)
Jurisdictions differ. Practical consumer stance:
- Treat regulator/label compliance as a minimum floor, not proof of overall quality.
- Treat return policy as part of reversibility (a decision variable).
- Treat security update policy as a measurable, long-run quality dimension.
References
- Simon, H. A. (1955). A behavioral model of rational choice. Quarterly Journal of Economics, 69(1), 99–18.[source]
- Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.[source]