Projects
Temporary, structured endeavors with a defined scope, timeline, and deliverables that translate goals into concrete outcomes through coordinated sequences of tasks.
Also known as: Project, Initiatives
Category: Productivity
Tags: productivity, planning, strategy, frameworks, practices
Explanation
A project is a bounded initiative with a clear beginning, end, and desired outcome. It is the level in the strategic hierarchy where abstract goals become concrete plans — where 'increase revenue by 20%' becomes 'launch the new product line by September.'
**Projects in the Strategic Hierarchy**:
1. **Mission**: Why we exist
2. **Vision**: Where we're going
3. **Goals**: What we'll achieve
4. **Projects**: How we'll get there ← *you are here*
5. **Tasks**: What we do today
**What Defines a Project**:
- **Finite**: It has a start and end date. If it has no end, it's an ongoing process, not a project
- **Scoped**: It has clear boundaries — what's included and what's not
- **Outcome-oriented**: It produces a deliverable, result, or change
- **Multi-step**: It requires more than one action — otherwise it's a task
- **Goal-connected**: It exists to advance a specific goal (if it doesn't, question why you're doing it)
**Projects vs. Other Concepts**:
| Concept | Key Difference |
|---------|----------------|
| **Project** | Finite, has deliverables, requires planning |
| **Goal** | The target the project serves — one goal may need multiple projects |
| **Task** | A single action within a project |
| **Process** | Ongoing, repeating — no end date |
| **Area of responsibility** | A continuous domain you maintain (health, finances, career) |
| **Habit** | A recurring behavior — projects end, habits continue |
**Projects in Personal Productivity (GTD/PARA)**:
David Allen's GTD defines a project as 'any desired outcome that requires more than one action step.' This deliberately low threshold ensures nothing complex falls through the cracks. Tiago Forte's PARA method (Projects, Areas, Resources, Archives) uses projects as the primary organizing principle for active work — everything you're actively committed to delivering.
**Why Projects Matter**:
- **They make goals tractable**: A goal like 'write a book' is overwhelming. A project like 'complete first draft of Chapter 1 by March 15' is actionable
- **They create accountability**: Projects have deadlines, milestones, and deliverables you can track
- **They enable prioritization**: You can only actively run a limited number of projects. Choosing which ones forces strategic decisions
- **They provide closure**: Completing a project gives a sense of accomplishment that sustains motivation for the next one
**Common Project Pitfalls**:
- **Too many active projects**: Spreading attention too thin means none get done well. Most people can handle 5–10 active projects across work and personal life
- **Zombie projects**: Projects that should have been completed, cancelled, or paused but linger on your list consuming mental energy
- **No clear next action**: A project without a defined next task is stuck but invisible
- **Scope creep**: Gradually expanding what the project includes until it becomes unmanageable
- **No review cadence**: Projects need regular check-ins to stay on track or be killed
Related Concepts
← Back to all concepts