Foundations 2 - Becoming an Effective Project Manager

Google Project Management Certificate · Course 1: Foundations of Project Management

---

What this module is about

The goal here is to understand the unique value a project manager (PM) brings, describe the roles and responsibilities of the role, and list the core skills that make a PM effective. A useful reassurance up front: much of what makes a good PM is transferable - many people already have relevant organizational and people skills from earlier jobs or everyday life and simply need to name and sharpen them.

Note

Project management = applying knowledge, skills, tools, and techniques to meet project requirements and achieve the desired outcome. The PM is the person who makes that actually happen - day to day and by stepping back to see the big picture.

---

Key responsibilities of a project manager

PMs generally follow a repeatable process: plan and organize, manage tasks, budget and control costs, and juggle other factors so the project finishes within its approved budget and timeframe. Below are the concrete responsibilities you’d expect to see in a job listing.

Responsibility	What it looks like in practice
Planning & organizing	Set up productivity tools and processes; create plans, timelines, schedules, and documentation to track completion - and maintain those docs for the whole project.
Managing tasks	Track a project task (an activity to be done in a set time by you, the team, or stakeholders). Task tracking manages workload and shows progress to people outside the team.
Budgeting & controlling costs	Monitor and manage the budget as changes arise; track issues and risks.
Managing quality	Mitigate issues and risks; remove barriers (anything blocking progress) before they derail the work.
Controlling change / scope	Keep changing stakeholder needs from turning into endless rework for the team.

Tip

Why task tracking matters (quiz favourite): it does double duty - it keeps the team’s workload manageable and it demonstrates progress to stakeholders outside the immediate team.

Removing barriers - the escalation reflex

A barrier is anything that gets in the way of progress. Typical move: spot the barrier early → escalate it to a stakeholder → secure the resource so the team can move forward. Removing barriers is a core, recurring part of the job, not a rare event.

Responsibilities that lean on interpersonal skills

Beyond the “concrete” duties, PMs carry a set of people-focused responsibilities that are just as important to project success.

Teaching & mentoringBuilding relationshipsControlling changeEmpowering the teamCommunicating status & concerns

Interpersonal responsibility	Core idea
Teaching & mentoring	Explaining expectations fully removes rework, confusion, and frustration. Passing on lessons lets the team build on your experience and exceed their own sense of potential.
Building relationships	Knowing team members, customers, and vendors as people makes everyone more invested. Note their work styles and follow up on earlier conversations.
Controlling change	Projects change as stakeholder needs become clearer. Stay flexible but protect the team - document the initial expectations, name each requested change, and make sure stakeholders understand its budget/schedule impact.
Empowering the team	Let members work directly with stakeholders, delegate real decisions, and use their input in planning. Empowered teams bring fresh ideas and passion. Good mentoring tends to produce more empowered teams.
Communicating status & concerns	The PM sets the tone. An open-door policy, trust, and a positive stance carry the project.

Caution

Controlling change is not blocking change - it’s absorbing it gracefully while shielding the team from constant churn. “The only thing that never changes is that everything changes.” Undocumented, unquantified change requests are how scope quietly balloons.

---

PM role vs. the team’s role

A common trap is hearing “manager” and picturing a boss. A PM is usually not the direct/day-to-day manager of the people on the project - they manage the tasks, and guide the people.

Note

Key distinction: Each team member is the expert on their own slice of the work (design, copywriting, engineering, marketing…). No one - including the PM - is an expert on every part. The PM’s expertise is project management itself: guiding the team and making sure they have the support they need.

Think of organizing a group camping trip: you plan and coordinate, but you don’t have to be the camping expert - you assign the tent decision to whoever knows tents best. You’re not doing the task; you’re making sure it gets done.

Required responsibilities that flow from this guiding role:

1. Hold members accountable for their assigned tasks - task ownership gives each person a clear piece to answer for.
2. Make issues and risks visible and establish escalation paths (know how to get risks to the right people at the right time).
3. Choose and enforce the right workflow / PM style - you’ll usually have the best sense of which style fits the work, then keep the team adhering to it.
4. Collaborate across teams (e.g. marketing, finance) so the project meets everyone’s needs on scope, schedule, and budget.

---

Core skills of a project manager

Four skill sets are singled out as essential - with optimism/positivity running through all of them.

Enabling decision-making

Communicating & escalating

Flexibility

Strong organization

Four core competencies of an effective PM

1. Enabling decision-making

Keep the project moving by gathering information from teammates and turning it into informed decisions - or by pulling a decision from the right leader when needed. Make the process collaborative: state the goal of a deliverable, then invite the team’s approaches (they may be more creative or efficient than yours). Giving people a voice builds responsibility, accountability, and closeness - and frees you to focus on higher-level management.

2. Communicating & escalating

Communication touches almost everything: documenting plans, sending status emails, running meetings, clarifying roles, and giving constructive feedback.

Tip

Escalation done well (test tip): bring management the problem and a proposed solution/suggestion, not just the problem. It shows initiative and speeds up the decision.

3. Flexibility & handling ambiguity

Plans will change - company goals shift, people leave, priorities move. “The only constant is change.” Flexibility keeps you effective when they do.

Flexible planning

• Assess external constraints - build in time for holidays, vacations, and sick leave up front.
• Plan for risks & challenges - line up backup people/contractors in advance; use historical data from past projects to anticipate issues.
• Calculate float (slack) - how long a task can wait before it threatens the schedule. Covered later with the critical path.

Handling ambiguity

• Keep calm - poise under uncertainty sets the tone for the team.
• Express empathy - acknowledge what the team is feeling and that you’re there to support them.
• Communicate what you know - pin down what is confirmed and won’t change.
• Make decisions and stick to them - don’t second-guess in front of the team; if you must change course, explain why.
• Trust the team’s expertise - surface what’s known vs. unknown, then brainstorm how to fill the gaps.

4. Strong organizational skills

The role runs on many processes at once; organization keeps nothing from slipping. If the leader visibly stays organized, the team follows suit. Useful tool categories:

Category	Examples
Planning & scheduling	Templates, workflows, calendars
Collaboration	Email, collaboration software, dashboards
Documentation	Files, plans, spreadsheets
Quality assurance	Evaluations, productivity trackers, reports

Tip

Building on the core skills: pair them with industry knowledge, tools/templates, and familiarity with popular methodologies (Waterfall, Agile) - all covered later in the program.

---

How a project manager adds value and impacts the organization

A PM delivers value in five broad ways.

Focus on the customer

Build a great team

Foster relationships & communication

Manage the project

Break down barriers

Five ways PMs add value and impact organizations

Note

Customer = the person or organization that defines the project’s requirements and sets key guidelines like budget and deadlines.
Internal customers: within your org - management, team members, resource managers, other departments.
External customers: outside - clients, contractors, suppliers, consumers.

Focus on the customer

The customer sits at the centre of a successful project - the deliverable has to meet their standards, so you must clearly understand their expectations. Dig into the “why” behind the request:

• What problem do you want solved?
• How is it impacting your organization?
• Why ask for help now?
• What is your hope for the outcome?

The better you understand their goals, the more likely you produce what they actually want.

Build a great team

The team is the project’s biggest asset. Match skills to requirements (and available resources) - the right expertise is non-negotiable, and no amount of effort compensates for a missing skill set. Make each person feel valued, trusted, and appreciated by letting them give input, ask questions, and have their needs addressed quickly.

Foster relationships & communication

Both of the above rest on relationships and communication. The PMs who add the most value invest time to connect, communicate, and treat people with respect - daily check-ins go a long way toward people feeling heard.

Manage the project (connect tasks to the big picture)

Work is handed from person to person, and members don’t always see the whole picture. The PM sees how each piece impacts the others and communicates those impacts, so everyone understands both their task goal and the big-picture goal. (A designer who knows the campaign must appeal to educators can tailor the work accordingly.)

Break down barriers

When the answer to “why do we do it this way?” is “because we always have,” a PM adds value by clearing the path: support the team as they try new approaches, model ingenuity and collaboration, advocate for extra resources, and chase down answers from other organizations yourself to keep the team on schedule.

---

Working with cross-functional teams

Note

Cross-functional team = members with different backgrounds, expertise, and job functions - often different departments, locations, and leadership - all working toward one common goal: completing your project.

Members are sometimes called “T-shaped professionals”: the horizontal bar = ability to collaborate broadly across functions; the vertical bar = their own deep area of expertise. Each brings a unique perspective.

Managing them effectively takes four things:

1. Clarify goals - make sure each person understands their role, how they support others, and the shared goals. Be direct and concise; define budget, deadlines, quality requirements, and key resources; invite questions; keep checking in. (Your project may be competing against other priorities, so communicate clearly and often.)
2. Get the right skills - the correct skill set for each function is critical. Five engineers but no mechanics means a key element is missing.
3. Measure progress - track and share progress (milestones, completed tasks, goals met on time/budget). Showing accomplishment keeps people motivated and lets everyone see their impact; communicate successes, delays, and issues alike.
4. Recognize efforts - some contributions get noticed more than others (the flashy fix vs. the person who quietly sourced the funding). Make sure every member’s value is acknowledged along the way.

---

Leading through influence, not authority

Because a PM usually isn’t anyone’s boss, they lead by influencing without authority - guiding teammates to complete work without formally managing them. This is one of the most critical and challenging parts of the job, and it runs entirely on interpersonal (soft) skills.

Skill	How it’s used to influence
Communication	Check in on progress; give clear feedback on quality of work.
Negotiation	Balance a teammate’s needs against what’s best for the project - e.g. compromising on a new deadline.
Conflict mediation	Defuse tension before it hurts the project - e.g. a meeting between two people who can’t agree on a shared task.
Understanding motivations	Learn what drives each person, how they like feedback, and how they prefer recognition - then tailor your approach.

Tip

Interview angle: you may be asked to describe a time you influenced without authority. Everyday examples count - e.g. getting a chronically late colleague to show up on time by changing how you communicate the impact, rather than by ordering them to.

---

Myth-busting: what you don’t need to be

Caution

These three misconceptions trip up new PMs - the reality is the opposite in each case.

Myth	Reality
You must be a technical expert in the field.	Not being buried in technical detail is an advantage - you can see how every cross-functional piece contributes. You hire the experts and handle communication, documentation, and organization.
Only long-tenured insiders can manage projects at an org.	You need the skills, knowledge, tools, and techniques of PM - not prior years at that specific company. (That’s what this certificate builds.)
You must know every detail at all times.	Details matter, but you must hold the big picture and strategy. Set clear objectives, trust the team with the details, and keep open communication so risks reach you early.

Note

Where you add value: direct communication, clarifying objectives, setting expectations, strategic problem-solving, and removing barriers - not out-expert-ing your specialists.

---

A quick note on AI as a PM tool

The module also introduces AI / generative AI as an assistant for routine work - drafting plans, proposals, and status reports; summarizing meeting notes and stakeholder feedback; researching best practices; and unblocking roadblocks - freeing time for strategic decisions.

Tip

Two things worth remembering for the quiz:
• Prompting framework - T-C-R-E-I: Task, Context, References, Evaluate, Iterate (“Thoughtfully Create Really Excellent Inputs”).
• Human-in-the-loop: AI complements - never replaces - human creativity, judgment, and critical thinking; always verify inputs and outputs and mind confidential data.

---

Revision summary

Theme	Remember this
Concrete responsibilities	Plan & organize, manage tasks, budget & control costs, manage quality/scope, remove barriers → deliver on budget and on time.
Interpersonal responsibilities	Teach & mentor, build relationships, control change (protect the team), empower, communicate status.
Role vs. team	PM manages tasks and guides people; each member is the expert on their slice - the PM’s expertise is project management.
Four core skills	Enabling decision-making · communicating & escalating · flexibility (+ handling ambiguity) · strong organization.
Adds value by	Focus on customer · build a great team · foster relationships & communication · manage the project · break down barriers.
Cross-functional teams	Clarify goals · right skills · measure progress · recognize efforts. T-shaped professionals.
Influence without authority	Communication · negotiation · conflict mediation · understanding motivations.

Tip

Top quiz takeaways:
• A PM is usually not the team’s direct manager - they lead by influencing without authority.
• You don’t need deep technical expertise, org tenure, or every detail - you bring the skills, tools, and techniques of PM and hold the big picture.
• When escalating, bring problem + proposed solution.
• Controlling change means documenting initial expectations and quantifying each change’s budget/schedule impact - not blocking change.
• Task tracking serves two audiences: it manages the team’s workload and shows progress to stakeholders.