**Projects** are how your team puts the [[Strategy]] into action. These are short-term, high-impact initiatives—typically scoped for **1–3 months**—designed to move the company closer to its long-term goals. While strategy defines _where_ you’re going, projects define _how_ you’ll get there. Each project should meaningfully contribute to your organization’s future, helping build long-term competitive advantages through focused [[Work|execution]]. ### 📁 What is a Project in Forge? Projects aren’t just collections of tasks—they are **purpose-driven initiatives**. Each project should have a clearly defined objective and [[Goals|metrics]] to evaluate success. When you define projects well, your team gets clarity on what matters, how to contribute, and what success looks like. Projects become the engine of forward momentum—transforming your [[Vision]] and [[Strategy]] into measurable progress. ### 🔍 Defining what matters **Objective** - What [[Problem Definition|problem]] are we solving, or what outcome are we targeting? - How does this work tie back to our [[Strategy]]? **Success Metrics** - How will we know this project made an impact? - Consider metrics related to: - [[Customers]] (e.g. adoption, satisfaction) - Financials (e.g. revenue, CAC, LTV) - Internal improvements (e.g. efficiency, collaboration) - Learning (e.g. validated hypotheses, reduced uncertainty) **Key Skills and Stakeholders** - What teams or disciplines need to be involved? - Do we need support from [[User Research]], testing, or design? **Execution Plan** - What’s the rough timeline? - What are the major milestones or checkpoints? --- ### Further Reading **“Measure What Matters: OKRs: The Simple Idea that Drives 10x Growth” by John Doerr** While not specifically a strategy book, OKRs (Objectives and Key Results) are invaluable for setting strategic goals and driving execution. Based on Doerr’s experience at Intel and Google, this book is widely regarded as a guide for aligning strategic objectives with actionable results.