aims-vs-objectiveslisted

## Overview Proposals collapse when aims, objectives, hypotheses, and milestones are used interchangeably — reviewers notice the muddle and score the logic down. This skill clarifies the hierarchy (goal → hypothesis → aims → objectives/tasks → milestones), writes each level correctly, and uses the structure to make any proposal — NIH, NSF, ERC, foundation — logically airtight. ## When to use - Structuring a proposal's logic: what's an aim vs an objective vs a task - Fixing reviewer comments like "aims are really objectives" or "no testable hypothesis" - Writing milestones and go/no-go criteria for translational proposals - Adapting between agency formats (NIH aims, NSF objectives, ERC work packages) - Teaching proposal logic to students and postdocs ## Core concepts - **The hierarchy:** long-term goal (the vision) → central hypothesis (the testable idea) → specific aims (the major questions, each with a working hypothesis) → objectives/tasks (the concrete work units) → milestones (verifiable checkpoints). Each level answers a smaller question than the one above. - **Aims are questions; objectives are deliverables:** an aim asks something ("Determine how X regulates Y"); an objective produces something ("Establish a cohort of 200 patients with X"). Confusing them gives you aims that sound like todo lists. - **Hypotheses live at two levels:** the central hypothesis organizes the whole proposal; each aim has a working hypothesis — a proposal without either is descriptive, n