For CIOs, CTOs & Executive Leaders
The Case for
Hiring a PM.
Project managers don't just keep things organized — they prevent million-dollar failures, align your leadership team, and turn strategy into execution. Here is what the data says, what PMs actually do, and why your next hire might be your most important one.
$97M
Wasted per $1B invested without mature PM practices
70%
Of projects fail to fully meet their original goals
2.5×
Higher project success rate at PM-mature organizations
Source: PMI Pulse of the Profession
The Stakes
The Real Cost of Unmanaged Projects
Every organization runs projects. The question is whether those projects are managed — or just happening. The gap between the two is measured in wasted budget, missed launches, and team burnout.
$97M
Wasted per $1B invested
PMI reports that organizations waste nearly 10 cents of every dollar invested due to poor project performance and lack of mature project management practices.
27%
Average IT project cost overrun
McKinsey research shows the average large IT project runs 45% over budget. One in six becomes a "black swan" — overrunning by 200% or more.
56%
Of projects deliver less value than expected
More than half of all projects are considered failures by their own organizations — not because the team lacked talent, but because execution lacked structure.
11.4%
Of investment wasted globally
PMI estimates that across all industries, 11.4% of every dollar invested in projects is wasted due to poor performance. For a $10M initiative, that's over $1M gone.
Budget Overruns
Without a PM tracking spend against plan in real time, cost creep happens invisibly. By the time leadership sees it, the damage is done — often with no clear explanation of where the money went or why.
Missed Deadlines & Lost Revenue
A delayed product launch, a late system migration, a missed regulatory deadline — each carries direct business consequences. Every week of delay has a cost, and those costs compound when no one is actively managing the schedule.
Scope Creep
Uncontrolled scope expansion — "just one more thing" — is the #1 cause of project failure. Without a PM to manage change requests formally, scope grows silently until it collapses timelines and budgets.
Team Burnout & Attrition
When engineers project-manage, you lose engineering hours and get poor PM. Context-switching, unclear priorities, and lack of coordination burn out your best people — and replacing a senior engineer costs 1.5–2× their annual salary.
Stakeholder Surprises
Without proactive communication, executives and stakeholders learn about problems at the worst possible moment. Loss of trust in the delivery team — and in technology leadership — is one of the most expensive outcomes of poor project management.
Rework & Duplicate Effort
Poor dependency management and misaligned requirements cause teams to build the wrong things, then rebuild them. Rework is invisible waste — it doesn't show up as a line item, but it consumes 25–40% of engineering capacity on unmanaged projects.
Source: PMI Pulse of the Profession 2023 · McKinsey Digital · Standish Group CHAOS Report
The Role
What a PM Actually Does
The most common misconception in business: "PMs just run meetings." In reality, a skilled project manager is the connective tissue of your organization — the person who makes sure your strategy actually happens.
Translates Strategy into Execution
A PM takes your organizational goals and breaks them into a sequenced, realistic plan with clear ownership. They close the gap between what leadership decides and what teams actually deliver — ensuring your vision doesn't get lost in translation.
What this means for you: Your strategic priorities become executable roadmaps with milestones you can track.
Identifies Risks Before They Become Crises
PMs don't wait for problems to surface — they actively search for them. A skilled PM maintains a live risk register, monitors leading indicators, and mitigates threats before they derail the project. Most executives only hear about problems after they've already caused damage.
What this means for you: Fewer surprises. Problems caught at the 10% mark cost a fraction of problems caught at 90%.
Aligns Stakeholders Across the Organization
Projects fail when stakeholders have different definitions of success. A PM maps every stakeholder, understands their interests and concerns, and creates the communication structure that keeps everyone rowing in the same direction — including when priorities conflict.
What this means for you: Fewer escalations to your desk. Decisions made at the right level by the right people.
Gives Leadership Real-Time Visibility
A PM translates complex project data into clear executive reporting — RAG status, budget vs. actuals, milestone completion, risk exposure — so you always know where things stand without having to ask. You lead with information, not intuition.
What this means for you: Confident board presentations. Informed resource allocation. No surprises at launch.
Manages Scope and Protects the Budget
Every "can we just add this?" request has a cost. A PM evaluates each change request against the triple constraint — scope, time, cost — and brings leadership a clear impact analysis before any change is approved. They are the financial guardian of your project investment.
What this means for you: Projects that stay within approved budgets. Changes that are visible, deliberate, and justified.
Manages Dependencies Across Teams
Modern projects involve engineering, design, legal, compliance, marketing, and vendors — all with interdependent timelines. A PM tracks every dependency, knows which delays cascade into critical path impacts, and actively coordinates across silos that would otherwise operate independently.
What this means for you: Teams that don't block each other. Delays caught before they compound.
Protects the Team from Noise
Engineers and specialists do their best work when they can focus. A PM absorbs stakeholder requests, manages communication channels, fields status questions, and shields the team from constant interruptions — allowing your most expensive people to do the work you hired them to do.
What this means for you: More engineering throughput from the same team. Less context-switching. Better code, fewer bugs.
Captures Lessons and Builds Institutional Knowledge
At project close, a PM documents what worked, what didn't, and what should be done differently. This institutional knowledge — rare in organizations without dedicated PM — prevents your teams from making the same expensive mistakes twice.
What this means for you: Every project makes your organization more capable. Delivery improves year over year.
"Managing a project is a full-time job. When your engineers project-manage, you lose both — engineering output and project discipline."
The hidden cost of PM-by-committee
The Numbers
The ROI of Project Management
Project management is not an overhead cost — it is a return-generating investment. Organizations that treat it as such consistently outperform those that do not.
28×
Return on PM investment
PMI research shows that for every dollar invested in project management, organizations save an average of $28 in avoided rework, cost overruns, and failed projects. The PM role pays for itself many times over.
89%
On-time delivery at high-PM-maturity orgs
Organizations with mature project management practices complete 89% of projects on time and 88% on budget. Low-maturity organizations complete just 36% on time. The gap is not talent — it's structure.
13×
Less money wasted vs. low-PM-maturity peers
High-performing organizations waste 13 times less money on poor project performance than their low-maturity counterparts. At scale, this difference is the delta between profitable and unprofitable technology investment.
Without Dedicated Project Management
Projects run over budget with no clear accountability
Deadlines slip and leadership learns about it late
Scope expands informally until the project is unrecognizable
Engineers context-switch between building and coordinating
Risks surface as crises rather than managed threats
Stakeholders have different expectations of the outcome
No lessons captured — next project repeats the same mistakes
Executive time consumed by status questions and escalations
With a Skilled Project Manager
Real-time budget tracking with variance alerts before overrun
Weekly executive reporting with clear RAG status and forecast
Formal change control — every scope addition is evaluated and approved
Engineers protected from coordination noise — focused on delivery
Risks identified early, owned, mitigated, and monitored continuously
Stakeholder alignment established at kickoff and maintained throughout
Lessons documented and applied — delivery improves with each project
Leadership informed, not involved — free to focus on strategy
Source: PMI Pulse of the Profession 2023 · PMI Project Management Salary Survey · McKinsey & Company
Interactive Tool
PM ROI Calculator
Put your own numbers in. See what poor project management is actually costing your organization — and what a skilled PM would save you.
Your Organization
Calculate Your PM ROI
Based on PMI & McKinsey Research
$2,000,000
Total budget across all projects this year
6 projects
Active projects running simultaneously or sequentially
8 people
Engineers, designers, analysts, and specialists
$120,000
Fully-loaded (salary + benefits + overhead)
Adjusts for industry-specific project risk profiles
Estimated Annual Savings with a PM
$—
Net of PM salary cost
Budget waste (no PM)
11.4% of project investment lost to poor performance (PMI)
—
Rework & duplicate effort
25–35% of team hours on unmanaged rework (McKinsey)
—
Scope creep overruns
Avg. 45% over-budget on unmanaged IT projects
—
Total estimated annual loss
Combined cost of unmanaged project delivery
—
PM salary cost
Mid-range PMP-certified project manager
—
PM recovers approx. 60–70% of losses
Conservative estimate based on PMI high-maturity data
—
Return on PM investment
Net savings ÷ PM salary cost
—
Adjust the sliders to see your estimate.
Estimates are directional, based on PMI Pulse of the Profession (2023), McKinsey & Company IT project research, and Standish Group CHAOS Report averages. PM recovery rate assumes a skilled, PMP-certified project manager. Actual results vary by organization, project complexity, and PM experience. This calculator is a starting-point for conversation — not a guarantee.
Self-Assessment
Does Your Organization Need a PM?
Most organizations that need dedicated project management already know it — they just haven't named it. If these patterns sound familiar, the diagnosis is clear.
Execution & Delivery Signals
✓
Projects consistently miss deadlines without a clear explanation of why.
▼
The answer is always "it's complicated" — but the real reason is that no one owns the schedule end-to-end. A PM tracks every dependency, flags slippage in real time, and keeps leadership informed before the deadline becomes a crisis.
✓
Budget overruns are a recurring theme across projects.
▼
You approve a budget and somehow the project always costs more. No one can explain where the money went. A PM tracks spend against plan in real time, flags variances early, and ensures every cost increase is a deliberate, documented decision — not a surprise at project close.
✓
Scope grows invisibly with no formal decision trail.
▼
Projects start well-defined and end up being something completely different than what was approved — without a formal decision ever being made. A PM enforces change control: every addition is evaluated for its impact on timeline and budget before it becomes part of the project.
✓
Teams are always firefighting instead of executing a plan.
▼
Your organization is perpetually reactive — solving the crisis of the week instead of working a plan. A PM builds the plan, tracks adherence to it, and proactively identifies the next problem before it ignites. Firefighting is what happens when project management is absent.
✓
Great ideas fail in execution despite capable teams.
▼
Your strategy is sound and your people are talented — but something between planning and delivery consistently breaks down. That gap is exactly where a PM operates. Execution failure is almost never a talent problem. It's a coordination, communication, and accountability problem.
✓
At least one expensive project failure in the past 24 months.
▼
A cancelled initiative, a failed launch, a major cost overrun — if it's happened once, it will happen again without structural change. The cost of that failure almost certainly exceeded what a PM would have cost for the entire project lifecycle, many times over.
Leadership & Communication Signals
✓
No one knows where the project stands at any given time.
▼
Ask three people for a project status and get three different answers. There is no single source of truth. A PM creates and maintains that source of truth — a live project dashboard that gives everyone, from the team to the CEO, a consistent, accurate picture.
✓
Executives are surprised by delays at the worst moments.
▼
Leadership learns about problems during board presentations, at launch, or when a client calls to complain. A PM's job is to make sure no stakeholder is ever surprised — by building a communication plan that surfaces issues proactively, not reactively.
✓
Conflicting stakeholder priorities escalate to your desk.
▼
Stakeholders have different expectations and no one is actively managing those conflicts — so they surface as escalations that consume executive time and attention. A PM owns stakeholder alignment, facilitates priority decisions, and keeps conflicts from reaching leadership unless a genuine executive decision is needed.
✓
Your engineers are doing PM work instead of engineering.
▼
Your developers spend significant time coordinating, attending status meetings, and managing requests instead of building. A senior engineer doing project coordination costs $80–150K+ per year in misdirected labor — and produces worse outcomes than a dedicated PM would. This is one of the most common and costly forms of waste in technology organizations.
✓
Team morale is declining on long-running projects.
▼
High performers are leaving, citing "chaos" or "lack of direction" in exit interviews. Unclear priorities, constant context-switching, and absence of a clear path forward burn out your best people. Replacing a senior engineer costs 1.5–2× their annual salary. A PM creates the clarity and structure that retains talent.
✓
You personally spend time on coordination that someone else should own.
▼
If a CIO, CTO, or VP is answering status questions, chasing deliverables, and mediating team conflicts — your most expensive resource is doing project coordinator work. That time has an opportunity cost measured in strategic initiatives deferred. A PM takes that burden off your plate entirely.
If three or more of these sound familiar, your organization is already paying the cost of not having a PM — you just haven't hired one yet. The question is not whether you can afford a project manager. It's whether you can afford not to have one.
Common Objections
Myths vs Reality
Executives who hesitate to hire PMs usually cite one of a handful of objections. Here is where those objections come from — and why the data tells a different story.
The Myth
The Reality
Myth
"PMs just run meetings. We can have our team leads do that."
Reality
Facilitation is 10% of a PM's job. The other 90% is risk management, dependency tracking, budget oversight, stakeholder alignment, change control, and executive reporting. When team leads "do PM," they do it part-time — and both roles suffer.
Myth
"We can't afford a project manager right now."
Reality
PMI data shows organizations waste an average of $97M per $1B invested without mature PM. The cost of a PM is a fraction of the cost of one failed project. The salary of a project manager is recovered many times over through avoided overruns, rework, and delays.
Myth
"PMs add bureaucracy and slow everything down."
Reality
Skilled PMs add just enough structure to prevent chaos — not more. The alternative to structured PM is not "moving fast." It's informal, untracked work with unclear ownership, invisible risks, and unpredictable outcomes. Process prevents the chaos that truly slows teams down.
Myth
"We're too small for a dedicated PM. Only big companies need them."
Reality
Small organizations with limited runway can least afford project failures. A $500K project failure is catastrophic for a 50-person company in a way it isn't for an enterprise. PMs protect investments at any scale — and the ROI is proportionally higher in smaller organizations.
Myth
"Our projects always go well. We don't have PM problems."
Reality
Organizations without PM structure often can't see their own problems — because there is no baseline to measure against. If no one is tracking schedule, budget, and scope formally, no one can report that these things are slipping. Absence of visibility is not evidence of success.
Myth
"A good PM can manage any project regardless of industry."
Reality
PM skills transfer across industries, but domain context accelerates time-to-value. A PM with both strong methodology and relevant industry experience will contribute faster. Prioritize PM competency first — domain knowledge can be learned; project management discipline cannot be improvised.
Practical Guidance
What to Look for When Hiring a PM
When you're ready to hire, knowing what separates a great PM from a mediocre one saves you from a costly mis-hire. Here is what to evaluate — and the red flags to avoid.
01
Certification & Credentials
Certification signals commitment and a verified baseline of PM knowledge.
- PMP (Project Management Professional) — the global gold standard. Requires 36+ months of PM experience. A strong signal for mid-to-senior hires.
- CAPM — entry-level cert for coordinators and junior PMs
- CSM / PMI-ACP — Agile certifications; valuable for tech-heavy teams
- PgMP — program management; required for directors managing multiple projects
02
What to Ask in the Interview
The best PM interview questions surface real experience, not rehearsed answers:
- "Tell me about a project that failed. What was your role in that failure?"
- "How do you handle a stakeholder who keeps expanding scope?"
- "Describe how you give bad news to a senior executive."
- "Walk me through how you build a project plan from scratch."
- "What metrics do you use to determine if a project is healthy?"
03
Key Competencies to Evaluate
Beyond credentials, assess these qualities directly:
- Structured thinking — can they break a complex problem into clear components?
- Executive communication — can they brief you clearly in 5 minutes?
- Stakeholder influence — evidence of managing up and across
- Risk mindset — do they proactively identify risks or react to them?
- Agile + Waterfall fluency — can they choose the right approach for context?
- Accountability — do they own outcomes, not just activities?
⚑ Red Flags — Signs to walk away from a PM candidate
Cannot describe a specific project failure or takes no personal accountability for it
Uses "we" exclusively — never "I" — when describing their own contributions
Cannot explain how they would handle scope creep with a clear, structured answer
No experience with formal risk registers, change control, or project baselines
Describes their role as primarily "keeping everyone updated" — not driving decisions
Cannot give examples of influencing a difficult stakeholder or pushing back on leadership
Ready to build a stronger project management practice? Let's connect.
Stephanie Urso, PMP · PMI-ACP · CSM · ITIL — available for consulting, speaking, and advisory engagements