Director vs. PM vs. Lead: Understanding the Roles

Imagine a client says, "I'll check with the Director." The Director responds, "That's a PM decision." The PM says, "For anything design-related, please confirm with the Director."

This three-way impasse is not unusual. The result: decisions stall, revision loops begin, and the client ends up in a state of "I don't know who to contact."

In one outsourced project, time spent on design change approvals exceeded 40% of the entire design phase. The root cause: the three-step confirmation flow — Design Lead proposes a visual direction, Director checks alignment with client needs, PM evaluates schedule and budget impact — was nowhere formally documented. Each person assumed someone else was responsible, and decisions kept being deferred.

Concrete losses when roles are undefined:

• Decision delays: Without knowing who to ask, a single confirmation takes 2–3 business days
• Conflicting instructions: PM and Director issue different directives, throwing the production team into confusion
• Accountability gaps: A zone emerges where everyone assumes it's "not my responsibility"
• Client trust erosion: From the client's view, the vendor appears disorganized and hard to rely on

A surface-level understanding of the difference between PM and Director — and the role of Lead — is not enough. Undocumented organizational structures create project failure by design.

The most practical way to distinguish the three roles is to ask: what is each person's primary obligation to protect?

Project Manager (PM) — Guardian of Budget, Schedule, and Resources

The PM's accountability axis is compliance with constraints. The PM ensures the project completes within budget, on time, and within the available team.

Primary PM decisions include:

• Task prioritization and work allocation
• Calculating the impact of scope changes on schedule and budget, and deciding whether to approve
• Risk identification and mitigation planning
• Progress reporting and escalation to stakeholders

A common point of confusion between PM and Director is this: the PM does not decide what gets built. The PM manages how, when, and at what cost something gets built. Responsibility for the content and quality of deliverables rests primarily with the Director.

Director — Accountable for Deliverable Quality and Client Value

The Director's accountability axis is alignment between deliverables and client goals. The Director understands the client's business objectives and defines, oversees, and ensures the deliverables achieve those objectives.

Core Director responsibilities:

• Requirements definition: Translating vague client requests into buildable specifications
• Quality assurance: Verifying that deliverables match client intent and business goals
• Communication design: Building the information flow between client and production team
• Change management: Identifying the impact of specification changes and handing the information to the PM

The Director is the owner of what gets built, but does not typically get involved in how it is technically implemented.

Lead (Design Lead, Engineering Lead, etc.) — Technical Authority in a Specialized Domain

The Lead's accountability axis is quality and technical correctness within their specialty. A Design Lead ensures visual consistency and design quality; an Engineering Lead ensures code quality and architectural soundness.

Primary Lead decisions include:

• Selecting methods, tools, and technologies within their domain
• Reviewing and coaching junior members' work
• Flagging technical risks or constraints to the Director
• Setting best practices and quality standards in their area

Leads are not responsible for the overall progress of the project. Their primary role is to deliver the best possible outcome in their domain.

Summary of the three accountability axes:

| Role | Accountability Axis | Primary Decision Domain | Authority Limits | |------|---------------------|------------------------|-----------------| | PM | Budget, schedule, resources | Scope, workload, risk management | Deliverable content and quality | | Director | Deliverable quality, client value | Requirements, quality standards, change management | Final approval of budget and hours | | Lead | Technical quality in specialty | Methods, tools, domain-specific judgment | Other domains; overall project |

When the PM and Director roles remain ambiguous in operation, specific trouble patterns recur at the project level.

Pattern 1: The PM Makes Quality Calls

A PM approves and presents deliverables to the client without routing them through the Director, often because the PM is prioritizing schedule. The Director later reviews the work and finds it below quality standards, triggering a rework. What looks like a "production quality issue" is actually a process bypass.

Pattern 2: The Director Starts Managing Resources

A Director responsible for deliverable quality, anxious about schedule slippage, begins directly adjusting team members' workloads. This resource management happens outside the PM's visibility, creating conflicts between the Director's adjustments and the PM's capacity plan. Team members face competing instructions and don't know whose to follow.

Pattern 3: The Lead Gets Pulled Into Client Negotiations

A client requests to meet directly with the Design Lead. The Lead makes technically sound proposals but lacks context on the client's business constraints and budget. The client feels that the proposals are technically impressive but don't reflect their actual business needs. The relationship deteriorates.

Pattern 4: Accountability Gaps Emerge

There is often work that PM, Director, and Lead each see as "not my area." A typical example: receiving scope change requests from clients and performing an initial impact assessment. The PM redirects to the Director for quality considerations; the Director redirects to the PM for scope evaluation. The client is left waiting.

Pattern 5: Upstream Role Confusion Cascades Downstream

When the PM-Director distinction remains unclear, the production team also begins to wonder whose instructions take priority. When conflicting directives arise, there is no decision framework, and work stops. This stoppage originates in upstream role ambiguity, but it tends to be perceived externally as "the production team is slow."

From the client's perspective, verifying that the vendor's organizational structure is properly designed before the project begins is one of the most effective ways to reduce project risk.

Four questions to ask before kickoff:

1. "Are the PM and Director separate people, or the same person?" If one person holds both roles, ask how they separate their decision-making. A trustworthy vendor can clearly explain: "For budget and schedule decisions, I act as PM; for deliverable content decisions, I act as Director."

2. "Who are the Leads in each area, and how do they relate to the Director?" Ask about the review flow between Leads and the Director. Look for vendors who say, "Lead proposals are filtered through the Director from the client's perspective before being presented."

3. "When a specification change request comes in, who is the point of contact, and who gives final approval?" The clarity of the change management flow directly affects how frequently problems arise in the middle and later stages of a project. A standard contractor structure has the Director assessing scope impact and the PM calculating cost and schedule impact before presenting both to the client.

4. "Does progress reporting come from the PM or the Director — or both?" A clear structure has schedule progress reported by the PM and deliverable quality and direction reported by the Director. If one person handles both, confirm that they hold decision authority across both axes.

Request an organizational chart:

Asking a vendor for a chart showing who is responsible for what is a legitimate right as a client. A standard organizational chart lists PM, Director, each Lead, and team members, along with their respective roles and reporting lines.

What to look for in the chart:

• Is there a clear hierarchy (PM → Director → Leads), or is it flat?
• Who is the single point of contact for the client? (If multiple, what are the contact rules?)
• Is there a stated obligation to notify the client of organizational changes, such as a change in personnel?

On the contractor side, starting a project with ambiguous role definitions is the single greatest source of downstream problems. Roles should be progressively formalized across three stages: proposal, contract, and kickoff.

Proposal stage — Introduce the organizational structure

Include a "Project Structure" section in the proposal that names the PM, Director, and each Lead along with a brief description of each person's role. Communicating "who does what" at the proposal stage increases client confidence and reduces misalignment later.

Minimum required information:

• Name and title of each team member
• The single point of contact for the client (limit to one person as a rule)
• Primary accountability area (e.g., "responsible for quality control," "responsible for schedule management")

Contract stage — Document roles and responsibilities

In the contract or a separate "Project Role Definition" attachment, explicitly state:

1. Scope of responsibility for each role: What decisions does each person have final accountability for?
2. Decision-making flow: Who decides in the event of changes, additions, or problems?
3. Personnel change rules: Notice obligations and approval processes if a team member is replaced
4. Escalation path: Who makes the final call if an issue cannot be resolved at the working level?

Kickoff stage — Share the structure with all stakeholders

At the start of the kickoff meeting, use the organizational chart to walk through each person's role with everyone present — including the client side. Make it explicit which person to contact for which types of issues.

Practical examples:

• "Please direct design revision requests to Director A."
• "For negotiations about deadlines or budget, PM B is the point of contact."
• "Technical questions can be directed to Engineering Lead C."

Making this explicit at kickoff prevents the "I don't know who to ask" state that commonly emerges mid-project.

In smaller projects and lean teams, one person often covers PM, Director, and Lead responsibilities simultaneously. This is common in freelance engagements and two- to three-person production teams.

Conditions under which role stacking works:

1. Scale: Budget under 1 million yen, timeline under 3 months, and fewer than 5 people involved is a rough guide
2. Complexity: Few specification changes expected; deliverable types are limited
3. Client setup: A single point of contact on the client side with fast decision-making
4. Individual capability: The person can consciously switch between PM thinking and Director thinking depending on context

Signs that role stacking is starting to break:

• Being asked to run a quality check while mid-calculation on a scope change impact — two accountability axes are running simultaneously
• Direct client inquiries and production team requests arriving at the same time — information management can no longer keep up
• Losing track of whether a given decision is being made in "PM mode" or "Director mode" — the internal separation has collapsed

Deciding when to separate roles:

Consider splitting roles or bringing in outside support when a project reaches any of the following states:

• The number of weekly decisions exceeds roughly 20
• Client meetings and internal team reviews begin to overlap chronologically
• Quality problems and schedule problems emerge simultaneously, and there is no clear prioritization framework

Covering multiple roles solo is possible, but without the habit of consciously switching between modes, role confusion reproduces itself inside a single person — and produces the same downstream damage it would in a larger team.

Regardless of project scale or complexity, understanding the distinct accountability axes of PM, Director, and Lead provides a structural foundation for quality outcomes. Whether you are on the client or contractor side, consistently asking "who decides what" prevents confusion on the ground and builds the trust that sustains long-term working relationships.