Before launching any project, answering key questions during the initiation phase ensures alignment, prevents scope creep, and sets the foundation for success. These questions help define the “why,” “what,” and “how” of the project, often formalized in a project charter or statement of work (SOW).

Overview: The 5 Ws of Pre-Kickoff

The most effective pre-kickoff approach centers on the 5 Ws + H:

• Why: What is the business purpose, problem to solve, or opportunity?
• What: What are the high-level objectives, scope, and deliverables?
• Who: Who are the stakeholders, sponsors, and team members?
• When: What are the milestones, hard deadlines, and time constraints?
• Where: Where will work take place (e.g., remote, onsite, systems used)?
• How: How will success be measured and how will communication work?

Detailed Description of Essential Pre-Kickoff Questions

1. Context & Rationale (“Why”)

• What is the core problem or opportunity? Define the “pain point” triggering this project.
• How does this align with company strategy? Understand why this project matters now compared to other priorities.
• What happens if we fail or do nothing? This identifies the true urgency.

2. Objectives & Success Criteria (“What”)

• What are the measurable goals? Define success (e.g., specific KPIs, revenue increase, time reduction) rather than just stating “improved efficiency”.
• What is explicitly in-scope? List the key deliverables.
• What is out of scope? Crucial for preventing scope creep—list items that won’t be delivered.
• What is the “Minimum Viable Product” (MVP)? What is the absolute bare minimum needed to launch?

3. Stakeholders & Roles (“Who”)

• Who is the Project Sponsor? Who is championing the project and ultimately accountable?
• Who has final sign-off authority? Identify the key decision-makers to avoid bottlenecks.
• Who is the target audience/end-user? Who is this being built for?
• Do we have the right skills on the team? Assess the need for external resources or specialized training.

4. Constraints & Logistics (“When” & “Where”)

• Is the deadline fixed or flexible? Are there immovable external dates (e.g., conferences, legal compliance)?
• What is the rough budget? Have all funds been secured?
• What are the key milestones? Identify early dependencies.

5. Risks & Dependencies

• What are the major threats? Identify risks to the schedule, budget, or quality early.
• What dependencies exist? What outside factors (e.g., vendor delivery, legal approval) must happen first?

6. Operating Model (“How”)

• How will the team communicate? Define tools (e.g., Slack, email) and meeting cadence (e.g., weekly, daily standups).
• How will we track progress? Where will documentation and tasks be stored (e.g., Jira, Asana)?

---

Summary Checklist for Pre-Kickoff Success

• Business Case Approved: Does a charter exist?
• Goals Aligned: Do stakeholders agree on what success looks like?
• Constraints Known: Deadline and budget are understood.
• Risks Documented: A preliminary risk list is started.
• Dependencies Identified: Known bottlenecks are mapped.
• Team Identified: Key players are assigned.

Tip: Before the main kickoff, hold one-on-one “sanity check” conversations with key stakeholders to identify unspoken concerns.