Google PM Certificate Course 2: Project Initiation Explained

Course 2 (Project Initiation) teaches you how to start projects right. You'll learn to define goals, analyze stakeholders, create project charters, and set up success criteria. This deep dive covers what to expect and how to excel.

What Is Course 2?

Project Initiation is the second course, diving into the initiation phase of the project lifecycle. You learn that how you start a project significantly impacts its success. Poor initiation leads to misaligned expectations, scope creep, and failure. Strong initiation prevents these problems.

Course 2 teaches the PM tools and frameworks for starting projects professionally.

Duration and Workload

Estimated time: 40-50 hours (4-5 weeks at 10 hours per week)

Course 2 is slightly more involved than Course 1. You're creating documents (project charters, stakeholder analyses) and working through more detailed concepts. First peer-graded assignment appears here, which adds to workload but is valuable.

Major Topics in Course 2

Defining Projects and Their Goals

What you learn: How to define what a project is trying to accomplish in clear, measurable terms. Distinguishing between projects and operations. Understanding business cases (why is this project necessary?).

Key concept: SMART Goals — Specific, Measurable, Achievable, Relevant, Time-bound. Course teaches you to write goals that meet these criteria.

Example: Vague goal: "Improve our website." SMART goal: "Increase website conversion rate from 2% to 3% by improving landing page design and UX, measured monthly, within 90 days and $50K budget."

Identifying and Analyzing Stakeholders

What you learn: Who cares about a project and what they want? How do you identify stakeholders? How do you manage competing stakeholder interests?

Tools introduced:

• Stakeholder Analysis: List stakeholders, understand their interests, assess power/interest
• Power/Interest Matrix: Plot stakeholders on axes (high/low power, high/low interest) to guide engagement strategy
• Communication Plans: How often and how will you communicate with each stakeholder group?

Real example: For a website redesign, stakeholders might include: CEO (high power, high interest), designers (high power, moderate interest), users (low power, high interest), IT department (moderate power, moderate interest). You manage each differently.

Creating Project Charters

What you learn: The project charter is the founding document of a project. It officially authorizes the project and defines its parameters.

Charter components:

• Project name, description, goals
• Business case (why this project?)
• Success criteria (how will we measure success?)
• Scope (what's included/excluded?)
• Key stakeholders and roles
• High-level timeline and budget estimate
• Authority and approval

Why it matters: A charter is a single-page document that aligns everyone on what the project is trying to do. Without a charter, stakeholders might have different understanding of goals, scope, and success.

Understanding Scope

What you learn: Scope is what's included in the project. Scope creep (expanding scope without adjusting timeline/budget) is a major PM challenge. Managing scope prevents this.

Key concept: Scope Statement — Clearly defining what's in and out of scope. Prevents "but can we also..." requests that derail projects.

Example: Website redesign scope might include: new design, updated content, improved checkout process. Out of scope: adding new product categories, developing mobile app, changing payment processors.

Setting Success Criteria

What you learn: What does success look like? How will you know if the project succeeded? Success criteria guide decision-making and evaluation.

Types of criteria:

• Performance criteria: Does it work as intended? (e.g., website loads in under 2 seconds)
• Business criteria: Does it deliver business value? (e.g., 3% conversion rate improvement)
• User criteria: Do users like it? (e.g., 80% user satisfaction in post-launch survey)
• Delivery criteria: On time and on budget?

Key Frameworks and Tools

RACI Chart (Detailed)

Expanded from Course 1. Responsible, Accountable, Consulted, Informed. Who's responsible for what during project execution? Who's the decision-maker? Who needs to be consulted? Prevents confusion about roles.

Business Case and ROI

Why is this project worth doing? What's the return on investment? Course teaches you to understand business justification, not just execute the project.

Assumptions and Constraints

What are you assuming to be true? What constraints limit what you can do? Documenting these prevents surprises later.

Assessment in Course 2

Graded Quizzes

Number: Usually 1-2 quizzes

Content: Stakeholder analysis, SMART goals, project charters, scope definition

Example question: "You're managing a website redesign. A stakeholder requests adding a new feature outside the original scope. The charter was approved with specific scope. What should you do? A) Add it. B) Reject it. C) Evaluate it against scope and follow change management process. D) Ask the executive sponsor."

Right answer: C. This tests understanding of scope management.

Peer-Graded Assignment

Typical task: Create a project charter for a scenario (often expanded restaurant or similar initiative) OR conduct stakeholder analysis and create power/interest matrix.

What gets graded: Completeness (all charter elements or stakeholder details included), accuracy (appropriate goals, realistic stakeholders), clarity (easy to understand), depth (thought-through analysis).

Typical length: 2-4 pages

First time with peer review: This is often learners' first peer-graded assignment. Don't be anxious. Most peers grade fairly. Focus on meeting the rubric requirements.

How to Excel in Course 2

Create a Real Project Charter (Not Just the Assignment)

After learning the framework, create a charter for a real project you know (work initiative, personal project). Even if you don't submit it, writing a real charter deepens learning more than the assignment alone.

Practice Stakeholder Analysis on Projects You Know

Think of a project you've been part of. Who were the stakeholders? What did they want? Where did conflict arise because stakeholder interests weren't aligned? This application makes the concept stick.

Study the Charter Template Carefully

Course provides a charter template. Use it. Understand each section. For the assignment, follow the template structure. Peers expect familiar formats.

Spend Time on Scope Definition

Scope management is core to PM. Course 2 introduces it; Course 3 deepens it. Pay attention here. Understanding what's in vs. out of scope prevents many PM problems.

Read Examples Thoroughly

Course provides example project charters. Don't skim them. Read completely. See how others structure charters, write goals, define scope. Use these as templates for your own work.

Common Challenges in Course 2

Writing SMART Goals

Challenge: SMART is straightforward in theory but harder in practice. Learners struggle distinguishing specific from vague.

How to overcome: Use the template: "[Action] [Specific outcome] [Measure] [Timeline] [Resource constraint]." Example: "Design and launch new website homepage, increasing conversion rate from 2% to 3%, within 90 days, with $30K budget." That's SMART.

Stakeholder Analysis Overwhelm

Challenge: Identifying all stakeholders feels overwhelming. Who counts as a stakeholder? How detailed should analysis be?

How to overcome: Start broad. List everyone who cares about the project outcome. Then assess each for power/interest. Focus effort on high-power, high-interest stakeholders. Don't over-analyze minor stakeholders.

Scope Creep Concept

Challenge: You understand scope creep in theory but struggle imagining how to prevent it when "one small addition" is requested.

How to overcome: Remember: scope creep expands timeline and budget. "One small addition" is never free. Course teaches change management (Course 4) to handle scope changes formally. For now, understand scope defines deliverables. Changes to scope need approval and adjustment to timeline/budget.

How Course 2 Connects to Course 3

Course 2 defines the project (goals, scope, stakeholders, success criteria). Course 3 uses that definition to create a detailed plan. You can't plan a project until you've defined it clearly. Course 2 is the prerequisite.

Time Management for Course 2

Week 1: Goals and SMART framework

Week 2: Stakeholder analysis, power/interest matrix

Week 3: Project charters, scope definition

Week 4: Success criteria, charter finalization, quiz prep

Week 5: Complete assignment, revise based on rubric, take quizzes

This pacing gives adequate time for each concept before moving to the next.

Real-World Application

In real PM work, you'll spend 1-2 weeks in initiation phase: interviewing stakeholders, defining scope, getting charter approved. Course 2 teaches what happens in that phase. Seeing course content and real work aligned deepens learning and relevance.

Related reading: Google PM Certificate Course 1 Deep Dive: Foundations of Project Management and How to Study for the Google PM Certificate.

Next Steps

Course 2 teaches how to start projects right. Master stakeholder analysis, SMART goals, and project charters. These tools prevent many PM problems. After Course 2, you'll have clarity on what a project is trying to accomplish and who cares about its success. That foundation is essential for planning and execution in later courses. You're on your way to becoming a thoughtful, deliberate project manager.