---
title: "Initiating the Project"
section: "Project Management"
sectionId: "project-management"
date: "2026-05"
---

Without a clear and shared picture of the outcome, the project is doomed. Most projects fail because nobody is clear on what they are actually trying to achieve.

**Front-loading is a basic principle of project success.** The more clarity you establish now, the less chaos you manage later.

---

## Questions to Answer Before You Start

You must successfully answer all four of these before the project proceeds:

1. Who will this project impact?
2. Who determines success, and what are their expectations?
3. What are the project's constraints and limitations?
4. How do we create a shared understanding of the project outcome?

---

## Step 1: Identify All Stakeholders

Brainstorm every person involved in or impacted by the project. Include other people in this exercise — they will identify stakeholders you would have missed on your own.

The goal is to ensure you are never blindsided. If someone is affected by the project and you didn't know about them, they become a risk.

---

## Step 2: Identify the Key Stakeholders

A **key stakeholder** is anyone who determines the success or failure of the project. Not everyone on the stakeholder list is a key stakeholder — identify which ones are.

---

## Step 3: Interview the Key Stakeholders

Get as much input from key stakeholders as early as possible. Your goal is to understand:
- Their unique perspective on the problem
- Their definition of a successful outcome
- Their constraints, concerns, and non-negotiables

Early input reduces surprises later. People who are consulted upfront are far more likely to support the project when it gets difficult.

---

## Write the Scope Statement

The scope statement gives all stakeholders a single place to see the why, what, when, and how of the project. It describes what success looks like, and explicitly states what is and is not in scope.

**The three-step process:**
1. Draft the statement
2. Review it with key stakeholders
3. Get formal approvals

A good scope statement prevents arguments later about whether something was always part of the project.

---

## Key Principles

- Clarify expectations at the outset — don't assume shared understanding
- Include others in stakeholder identification so you don't miss anyone
- The more input you get early, the fewer surprises you face during execution
- A signed scope statement is a commitment, not a formality