PMBOK's technical domains — scope, schedule, cost — can be taught and applied mechanically. Leadership cannot. PM5335 treats leadership as a discipline students must actively practice: negotiating with stakeholders who don't report to them, and leading organizational change that people will actively resist.
Leadership theory for project managers
PM5335 surveys leadership models most relevant to project work: situational leadership (adjusting style to team maturity, building on Tuckman), transformational vs. transactional leadership (inspiring a shared vision vs. managing through rewards and corrections), and servant leadership (prioritizing team members' growth and needs, closely aligned with the Scrum Master role). The course emphasizes that a project manager typically has less formal authority than a functional manager over the same people, making influence-based leadership styles more essential than command-and-control.
Negotiation and leading organizational change
Students study principled negotiation (separating people from the problem, focusing on interests rather than positions, generating options for mutual gain) as the framework for resolving competing demands from sponsors, functional managers, and vendors. The course closes with organizational change management, using Kotter's 8-step model (creating urgency, building a coalition, forming a vision, and so on) to teach that a project's technical deliverable is often only half the challenge — getting the organization to actually adopt and use it is the other half, and it requires a distinct change-management discipline.
Key topics in PM5335
- Situational leadership: adjusting leadership style to team maturity across Tuckman's stages
- Transformational vs. transactional vs. servant leadership styles
- Sources of power and influence available to a PM without formal authority
- Principled negotiation: separating people from the problem, interests vs. positions
- Conflict resolution in high-stakes, cross-functional negotiations
- Kotter's 8-step change model for leading organizational adoption of project outcomes
- Emotional intelligence and its role in stakeholder and team leadership
Working on a leadership-theory analysis or an organizational change-management case study?
Our project management experts build PM5335-level graduate coursework grounded in real leadership frameworks.
Worked example: applying Kotter's model to project adoption
- Situation: A new project-tracking system is fully built and tested, but staff continue using their old spreadsheets
- Create urgency: Share data showing the old process caused two missed deadlines last quarter
- Build a coalition: Recruit respected team leads as early adopters and visible champions
- Form a vision: Frame the new system as saving staff time, not just adding compliance overhead
- Short-term wins: Highlight the first team that adopts it and reports faster reporting cycles
- Anchor the change: Retire access to the old spreadsheets once adoption reaches a critical mass
Get Help With PM5335
Leadership-theory papers, negotiation case studies, change-management analyses.
Place Your OrderView All ServicesRelated courses
Frequently asked questions
Transactional leadership operates through a clear exchange: the leader sets expectations and rewards or corrects performance based on whether those expectations are met — it works well for routine, well-defined work where the goal is consistent execution rather than innovation. Transformational leadership instead focuses on inspiring team members around a shared vision, encouraging them to exceed baseline expectations, invest personally in the outcome, and grow beyond their current role — it tends to produce higher engagement and is especially valuable for projects requiring innovation, significant change, or navigating high uncertainty. PM5335 teaches that most effective project leaders use both styles situationally rather than exclusively one: transactional clarity for routine deliverable tracking, transformational inspiration when the project needs the team to go beyond minimum compliance, especially during difficult phases like organizational change adoption.
Many projects fail not because the deliverable itself was flawed, but because the organization never actually adopted it — a new system is built and technically works, but staff quietly continue using the old process because no one managed the human side of the transition. Kotter's 8-step model (create urgency, build a coalition, form a strategic vision, enlist volunteers, enable action by removing barriers, generate short-term wins, sustain acceleration, and institute change) gives project managers a structured way to treat adoption as a deliverable in its own right, not an assumed byproduct of a successful technical delivery. PM5335 positions this model as essential precisely because project managers are often measured on whether the deliverable was produced, but organizational stakeholders judge success by whether the change actually stuck — and those are not automatically the same thing.