Guides
Part of What actually turns a technology purchase into an easy call?
How to build a technology shortlist before you compare a single price
Build a technology shortlist by diagnosing the need, writing pass conditions, normalizing specs, pricing complete setups, checking support, and resolving unknowns.
What to take away
- Diagnose the problem before deciding that a new device is the answer.
- Write pass conditions in plain language, then map them to specifications.
- Eliminate any candidate that fails a must-have requirement.
- Compare complete configurations at the same ownership period.
- Keep unknown claims visible until an authoritative answer resolves them.
A shortlist should reduce uncertainty. Three well-documented candidates are more useful than twenty tabs that mix models, optional features, old reviews, and incomplete prices. This method is the comparison stage of the wider technology buying guide.
1. State the decision
Write one sentence: "I need to decide whether to repair, upgrade, or replace X so that I can do Y within Z budget and deadline."
Repair, Upgrade, or Replace?
Does the device still meet your task?
Repair or upgrade
Replace
This sentence keeps repair and upgrade in view. A failing battery, full drive, damaged cable, poor router placement, or unsupported application can resemble a need for a whole new product. And when the real question is which category fits, the tablet, e-reader, and laptop comparison settles that before any model list.
2. Observe the existing failure
Record exact symptoms, frequency, error messages, conditions, and recent changes. Check storage, power, network, temperature, software support, and known recalls where relevant. If safety signs such as swelling, burning odor, smoke, exposed conductors, or liquid damage appear, stop ordinary testing and follow product-specific safety guidance.
3. Define pass conditions
Turn each task into a statement that can be verified.
Define pass conditions
Weak wording
- remote calls
- good webcam
- travel
- light
- external storage
- fast port
- software use
- powerful
- long ownership
- future-proof
Pass condition
- remote calls
- supports required app and produces acceptable audio and video in the actual room
- travel
- complete carried setup is under a chosen weight
- external storage
- exact port and cable support the drive's required protocol
- software use
- meets the publisher's supported requirements with stated headroom
- long ownership
- receives updates through a stated date and has a viable repair route
4. Set the evidence rule
Use the manufacturer or standards body for supported functions, the seller for price and delivered condition, the software publisher for compatibility, the warranty provider for coverage, and credible independent testing for measured performance.
Marketing may imply more than the headline literally says. The FTC's advertising substantiation policy requires advertisers to hold a reasonable basis for objective claims before those claims run, and it covers wording such as "tests prove" as well as what an advertisement merely implies. Read qualifiers, footnotes, images, and omissions together.
5. Build the first table
Give each row one requirement and each column one exact candidate. Mark:
Weak Wording vs Pass Conditions
Task
- remote calls
- good webcam
- travel
- light
- external storage
- fast port
- software use
- powerful
- long ownership
- future-proof
Weak wording
- remote calls
- supports required app, acceptable audio/video
- travel
- complete setup under chosen weight
- external storage
- exact port and cable support protocol
- software use
- meets publisher requirements with headroom
- long ownership
- updates through stated date, repair route
Pass condition
- remote calls
- travel
- external storage
- software use
- long ownership
Build the first table
- Passcurrent evidence confirms the requirement.
- Failevidence shows it does not qualify.
- Unknownthe answer is missing, ambiguous, or tied to another configuration.
Remove fails. For unknowns, ask specific questions: "Does model ABC-123 support two 2560 by 1440 displays at 60 Hz while charging through this port?" beats "Does it support monitors?"
Category guides like the laptop buying guide list the requirement rows that matter for each device type.
6. Normalize the numbers
Convert sizes, rates, capacities, energy, and prices to the same units. Label each result as maximum, typical, minimum, or independently measured. Do not treat a lab battery loop and a reviewer's mixed-work day as matching methods.
A benchmark is a standard test run to assess relative performance. Put a score in your table only when the same test and conditions produced every number in that row.
For storage, distinguish installed capacity from available space. For network rates, separate bits from bytes. For weight, include the charger and required adapter. For dimensions, include a stand or mounting clearance.
7. Price the complete setup
Add every required item and service:
- Product and taxes.
- Essential cables, adapters, docks, or mounts.
- Storage, memory, battery, or accessory configuration.
- Required subscriptions.
- Migration or installation.
- Likely service during the ownership period.
Do not add optional accessories to one candidate and ignore them for another. Balancing price against performance and lifespan over one ownership period keeps the totals honest.
8. Check ownership and exit
Compare return rules, warranty, support period, parts, and repair labor. Also data handling, resale, trade-in, recycling.
A device can meet today's task but create a poor ownership path if it loses updates early or needs costly proprietary service for common wear parts. Update windows are the sharpest phone example, so the smartphone buying guide checks support life before price.
9. Choose and save the record
Select the lowest-cost candidate that passes every must-have and wins enough should-have rows to justify any premium. Save the table, source pages, seller terms, warranty, receipt, and test plan.
Common questions
How many candidates should reach the final shortlist?
Usually two to four. More can make exact verification harder without improving the decision.
Should an unknown count as a failure?
For a must-have, yes until reliable evidence confirms it.
Can a review prove compatibility?
It can provide evidence for the tested configuration, but official support terms still matter.
What if no product passes the budget?
Change the deadline, task, condition, repair plan, or budget openly. Do not hide the failed requirement.
