Skip to content
How to ThinkIn the Age of AI

Define the specific job the tool must do in one sentence…

Define the specific job you're hiring a tool to do in one concrete sentence before evaluating candidates—vague category labels ('note-taking app') produce feature-based comparison while specific job definitions ('capture ideas on phone, retrieve on laptop at night') produce fitness-based selection.

When This Fires

Common Failure Mode

Category-based evaluation: "I need a project management tool" → compare Asana vs. Monday vs. Notion vs. ClickUp across 50 features. Weeks later, you've read every comparison article and can't decide because each tool wins on different features. The actual job — "I need to track 5 active projects with weekly status updates for 3 team members" — would have eliminated half the options immediately.

The Protocol

(1) Before evaluating any tool, write one sentence: "I'm hiring a tool to [specific job including context, frequency, and success criteria]." (2) Test the sentence: does it contain enough specificity to eliminate candidates? "Note-taking app" eliminates nothing. "Capture voice memos during walks and auto-transcribe to searchable text within 1 hour" eliminates 90% of note-taking apps. (3) Use the job definition to generate 3-5 requirements (Pick a tool with 5 minimum requirements, select the first…): the capabilities the tool MUST have to do this specific job. (4) Evaluate candidates exclusively against the job definition and requirements. Features not relevant to the job are noise, not advantages. (5) The best tool for the job may not be the "best" tool by feature count. That's correct — you're hiring for fitness, not impressiveness.