Foundations 4 - Organizational Structure & Culture

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

---

Why structure and culture matter

The way a company is arranged and “how things are done” here both shape how much room a project manager actually has to steer a project. Structure tells me who reports to whom and where my authority ends; culture tells me which values to appeal to when I want buy-in. A project only truly succeeds when the organization adopts its outcome - so this module also covers change management, the discipline of handing a finished project over and getting people to actually use it.

Note

Organizational structure - the way a company is arranged: how job tasks are divided and coordinated, and how members of the organization relate to and report to one another. It is usually drawn as a reporting chart (org chart) showing who each person or group reports to.

Tip

My role as a PM is not identical everywhere - it flexes with the structure. Knowing the structure is like having a map: it shows where I fit, who to communicate with, and how often.

Two structures to know: Classic vs Matrix

The course focuses on two common families. Everything downstream - my authority, how I get resources, who I chase for approvals - follows from which one I am in.

Classic (functional / top-down)

A traditional chain of command: CEO and executives at the top, then directors/managers, then their direct reports, and so on. It is also called functional because the company is split into departments by function (Marketing, Sales, HR, Finance, Engineering…), each led by a functional manager, with employees grouped by their specialty. Think of a military rank ladder - authority flows from the top down, and status updates flow back up.

CEO / Executives

↓

Marketingfunctional mgr

Financefunctional mgr

Engineeringfunctional mgr

Operationsfunctional mgr

↓

Team members

Team members

Team members

Team members

Classic / functional structure - one line of authority filtering top-down, employees grouped by department function.

In a Classic org a project team is assembled across departments but keeps its existing reporting lines - members do not leave their function. So as PM I often have to consult functional managers to learn what resources and capacity I can borrow, and to learn each function’s internal processes and approval chains. My authority tends to be slightly limited by competing priorities and approval hierarchies - setting expectations up front is how I still get the project done.

Matrix

Employees have two or more managers: their permanent functional manager and, for the duration of a project, a project manager. Adjacent departments cross paths frequently, and whoever owns the work in question holds the most authority for it. I can think of the PM as a temporary manager while the person is assigned to my team; the functional manager stays constant across whatever projects come and go.

CEO

↓

Functional mgr - Marketing

Functional mgr - Engineering

Functional mgr - Design

↕ team members answer to BOTH ↕

Project Manager A →horizontal line across functions

Project Manager B →horizontal line across functions

Matrix structure - functional authority runs vertically (down each department), project authority runs horizontally (across departments). A team member sits at an intersection and reports on both axes.

Note

The matrix in one line: functional managers own the vertical reporting (your discipline/home department); project managers own the horizontal reporting (the project cutting across departments). Each team member sits where the two lines cross.

Classic vs Matrix at a glance

Dimension	Classic (functional)	Matrix
Managers per person	One (functional)	Two or more (functional + project, sometimes more)
Chain of command	Clear, top-down	Less clear-cut; shared across leaders
Team grouping	By department/function	By function and by cross-functional project
PM authority	Often limited; leans on functional managers	Generally more autonomy to decide & gather resources
Getting resources	Request up the approval chain; managers control budget/people	Negotiate & share resources across leaders
Project focus	Project built from existing departments	Strong, explicit project focus
PM’s key move	Set expectations up front, consult functional managers	Identify every stakeholder & who controls what before start

Tip

Great interview question: “What organizational structure does the company use, and where would my role sit in it?” It signals you understand the impact of structure and gets both sides clear on who you’ll engage with daily.

How structure changes my authority and resources

An org’s structure is the framework for accountability and communication. Two levers it moves for me directly:

• Authority - my power to make project decisions that affect the organization (e.g. sometimes I choose the vendors; other times a vendor list is handed to me). Level of authority varies project to project.
• Resource availability - how easily I can reach the people, equipment, and budget I need.

In a Classic structure

Expect less authority and a tighter scope. People on my team and the resources I need are usually controlled by department managers, so I rely on their approval to move. Need a budget increase? I report it to my manager, who escalates up their management chain for sign-off. Advocate early and often through the approval chain.

In a Matrix structure

My team members answer to their functional manager and me - and possibly more managers if they’re on several projects. That means I must cooperate with multiple leaders, share resources, and negotiate priorities. The chain of command is fuzzier, so the win is identifying and talking to everyone I’ll need approval from well before the project begins. Once that’s set, matrix work runs efficiently and I generally enjoy more autonomy to decide and gather resources.

The Project Management Office (PMO)

Inside either structure there may be a group dedicated to project management itself.

Note

PMO (Project Management Office) - a group that defines, sets, and maintains project-management standards and processes across the organization. It acts as a coordinated center for all the org’s projects, so they run more smoothly and everyone pulls in the same direction. PMs may sit inside the PMO or out in other departments.

Core functions of a PMO:

Function	What it does
Strategic planning & governance	The most important one - defines project criteria, selects projects that fit business goals, and makes the business case to management.
Best practices	Shares processes, tools, metrics, and lessons learned to keep projects consistent.
Common project culture	Trains employees on optimal approaches so PM practice is uniform org-wide.
Resource management	Allocates people and equipment across projects by budget/priority/schedule; defines roles; mentors and coaches PMs.
Documentation, archives & tools	Provides templates and software, and archives closed-project documents to preserve project history and lessons learned.

Tip

A PMO’s real value is community: PMs normally work alone among client teams and other disciplines, so a PMO is where they swap templates, reuse tools, and learn how a peer solved the same problem - a bird’s-eye view of how all the project pieces connect.

Organizational culture

Note

Organizational culture - the values employees share plus the organization’s own values, mission, and history: essentially the company’s personality and “how things are done here.” Beyond visible things, it includes beliefs, norms, rituals, and customs.

Why a PM must read the culture: it shapes how decisions get made, how people communicate, and how much support a project attracts. As the management thinker put it, “culture eats strategy for breakfast” - culture influences success regardless of how good the business model is. Culture touches three things especially:

• Identity - how the company conducts itself internally and externally; its values are part of its identity. Read the mission and value statements to learn why it exists and how it behaves.
• People - a strong, positive culture retains and attracts good talent; a toxic one repels it. Find a culture that fits you.
• Processes - culture is baked into how work gets done (e.g. a company that values feedback builds comment opportunities into its processes).

How to learn a culture

1. Ask questions - ideally at the interview and when starting. Probe atmosphere (dress code, sharing credit, attitude to risk/failure, how managers motivate, how feedback is given, traditions), policies (leave, flexibility), processes (onboarding, measuring impact), and values (mission statement, career growth).

2. Listen to people’s stories - how employees portray the company reveals a lot; ask about past similar projects and about key stakeholders and customers.

3. Note the rituals - birthdays, holidays, shared lunches. Rituals drive culture and shared purpose.

4. Watch interactions - formal or informal? Are ideas solicited from every level? Tailor my own style to the norm.

5. Understand my impact - sit down with management to learn what’s expected of me.

6. Sharpen communication - how a company communicates is its culture. Ask the small conventions: sign team emails as the team or as me? Present solo or with team members?

Culture steers project decisions

Aligning a project with the company’s mission and values wins executives’ support and easier approvals. Reading what leaders prioritize tells me how to decide:

If the culture values…	It tends to favor…
Stability & user feedback	Extending the timeline to test, then deciding on results
Innovation & revenue growth	A shorter timeline, shipping faster, taking some risks

Note

Change agent - someone inside the organization who helps it transform by improving organizational effectiveness and development. As a PM I become one: even my mere presence can shift office dynamics.

Caution

Don’t over-reach as a change agent. The company may reject changes that clash with its mission, vision, or culture. Gauge how extreme a change is, seek feedback and approval early, and respect the limits of what’s beneficial. Approaching a project differently from “how it’s always been done” can meet resistance - showing appreciation for the culture helps team members accept the improvement.

Tip

Culture and structure are linked - the way an org is structured usually influences the culture it has - so weigh both when planning and running a project. And remember each culture is different and can change over time, so it’s always worth relearning.

Change management

Note

Change management - the process of delivering a completed project and getting the people in the organization to adopt it. Adoption is the first step to a project actually having its intended impact once it goes live.

A new tool or process is only a success if people use it - a new time-tracking system nobody adopts is a failed project. Changes ripple onto people: new processes, budgets, schedules, roles - even cosmetic changes (a new logo means swapping all stationery and getting everyone to use it correctly). Thinking through those ripples up front is what sets adoption up to succeed.

Three core concepts (shared by all change models)

Countless change models exist, but they share the same ideas:

1. Create ownership & urgency - get people to feel empowered and responsible for finishing their tasks (ownership) and to grasp why the project matters and what to do now (urgency). Together these raise interest, motivation, and engagement.

2. Right mix of skills & personalities - pick team members whose knowledge complements each other; if the team is pre-selected, at least influence who does what and connect with them so they become advocates for the change. Communicating a clear vision is a strong motivator.

3. Effective communication - be transparent and up front; keep the team and the wider organization updated so everyone feels included. This one cannot be overstated.

Tip

Agile ↔ change management overlap: being receptive to change is a core Agile value - Agile teams live in constant evolution - so Agile principles line up neatly with good change management.

Best practices when the change hits resistance

Change doesn’t happen overnight, and push-back is normal. Move it along by helping people adjust, rewarding their efforts, and reminding them of the long-term value.

Do	Don’t
Be proactive - flag upcoming changes to impacted stakeholders early	Spring changes on people at launch
Bake change management into the project plan (feedback docs, demos, Q&A forums, marketing videos)	Treat it as an afterthought that dents the timeline
Communicate regularly among stakeholders, the change team, and the project team	Go silent between milestones
Follow a consistent, documented process for every change	Improvise each change differently
Practice empathy for the anxiety change brings	Dismiss resistance as obstruction
Use tools - surveys/feedback, flowcharts, culture mapping	Rely on hope that people will “just adapt”

The PM’s role vs the change-management role

Change management is a big undertaking - a project in itself - and I may not lead the whole end-to-end transition. Often a manager, a team member, or a senior leader carries the formal authority to make people adopt the change. But even when I’m only participating, I still integrate the two disciplines and support adoption.

Before planning, I ask myself the guiding questions:

• How will the organization react to change?
• Which influencers can affect the change?
• What are the best means of communication?
• Which change-management practices will make my project’s implementation succeed?

Tip

Integrating project management and change management is my responsibility as PM - both aim to raise the odds of success. Even without formal authority to enforce a change, I participate by communicating throughout the project how the new tool/process will improve the end user’s experience, so people feel prepared to adjust at launch.

Same change, two structures/cultures

How I participate depends on structure and culture. Consider one deliverable - renaming a check-in system - playing out two ways:

Classic + informal culture

I route the need through the existing hierarchy: a senior executive emails the leadership team to instruct their teams to implement the name change. Budgets are managed separately, so a department needing extra funds (e.g. to reprint store posters) sends that request back up its own approval chain. I hold multiple meetings to help each group understand what’s changing and why.

Matrix + formal culture

I meet representatives across functions (e.g. marketing and technology) to explain the overall budget impact, then - matching the formal culture - write a document covering budget, timeline, and training impacts. I circulate it to gather feedback and alignment from stakeholders and share that back with leadership, who may have a formal memo drafted and distributed to explain why the change is happening.

Governance

Note

Governance - the management framework within which decisions are made and accountability/responsibility are assigned. In plain terms: who is in charge.

• Corporate governance - the standards and practices that direct and control an organization and balance the needs of stakeholders, management, and customers. It touches action plans, internal/external controls, and performance measures. It pairs with change management by giving people a precise, clearly-defined map of who makes decisions during a change. Steering committees are one example - an advisory board that sets priorities and helps approve strategic decisions.
• Project governance - the framework for how project decisions are made: the policies, processes, procedures, and responsibilities that keep a project on time and on budget. It’s the slice of corporate governance specific to project activity, tailored to the organization.

Good corporate governance supports project governance - providing oversight, mitigating risk, and helping PMs secure resources, unblock issues, avoid decision delays, get stakeholder buy-in, and gain executive visibility. When interviewing or starting a role, weigh an org’s governance the same way I weigh its structure and culture.

Revision summary

• Structure = the map. Classic/functional is a top-down hierarchy grouped by department with one manager per person; matrix gives people two-plus managers (functional + project) with work cutting across departments.
• Authority follows structure. Classic → less authority, tighter scope, resources gated by department managers and approval chains. Matrix → more autonomy but must negotiate priorities and identify every controller/stakeholder before starting.
• PMO sets project standards, does strategic planning & governance, shares best practices, manages resources, and archives project history - plus a peer community for PMs.
• Culture = the company’s personality (values, mission, norms, rituals). Learn it by asking questions, listening, observing rituals and interactions; align the project to the mission to win support. I’m a change agent, but I respect cultural limits.
• Change management = getting the org to adopt the deliverable. Core concepts: ownership & urgency, right team mix, and above all communication. Be proactive, consistent, empathetic; use feedback tools. I may only participate, not lead, but I still integrate change management into the project.
• Governance answers who is in charge - corporate (whole org) and project (my project) governance intersect and support each other.

Tip

Before starting any project or accepting any role, size up structure, culture, and governance together. They tell me how much authority I’ll have, where to get resources, who decides what, and how to get people to actually adopt what I deliver - the difference between finishing a project and having it stick.