AI and Project Management
The projections are good. They are good for the coordination, not for the status report, and most of the week is the status report.
Project management looks like an occupation built for automation. It runs on artefacts (plans, schedules, status reports, risk registers, meeting notes), and producing artefacts from structured information is the thing these systems are best at.
The employment projections say otherwise, and emphatically. The Bureau of Labor Statistics expects project management specialists to grow 7 percent between 2025 and 2035, much faster than the average for all occupations, adding 73,200 jobs to a base of 1,094,300.
But the same handbook projects secretaries and administrative assistants, 3.5 million people whose work is also coordination and also artefacts, to decline 2 percent, a loss of 75,300 jobs, and it names AI directly. Two occupations that both keep other people organised, moving in opposite directions. The difference between them is the most useful thing a project manager can understand right now.
Two coordination jobs, opposite directions
Both roles exist because work involving several people needs someone holding the thread. Only one of them is projected to grow.
Coordination occupations, United States, projected 2025–2035
| Occupation | Jobs (2025) | Projected change | Net jobs | Median pay |
|---|---|---|---|---|
| Project management specialists | 1,094,300 | +7% | +73,200 | $102,320 |
| Secretaries and administrative assistants | 3,515,600 | −2% | −75,300 | $48,310 |
Source: U.S. Bureau of Labor Statistics, Occupational Outlook Handbook
“Technology, including artificial intelligence (AI) systems and digital tools, enables staff in many organizations to prepare their own documents without the help of secretaries.”
The line runs through the job, not between jobs
The distinction is not seniority and it is not the job title. It is whether the task is producing a document from information that already exists, or producing a decision from information that does not.
Writing the weekly status update is the first kind. Every fact in it is already in the tracker, the repository and the calendar. Assembling those into prose is genuinely automatable, and increasingly automated.
Deciding that the launch date is not going to hold, and that you are going to say so on Thursday rather than let it emerge on its own: that is the second kind. The information that makes it a good decision is not in any system. It is that the backend lead has gone quiet, that this is the third estimate revision, and that the VP will take the news badly on Thursday but disastrously in three weeks.
Rough exposure across a project manager’s week
Why the coordination role still grows
Three reasons, and none of them is that the work is technically hard.
The first is that coordination is mostly about disagreement. Two teams want the same engineer, the deadline and the scope cannot both hold, one stakeholder wants a thing another has vetoed. Resolving that is a negotiation between people with different incentives, and it is not a problem with a correct answer.
The second is accountability. When a project misses, an organisation wants a person who owns the miss. That is a structural requirement, like the lawyer who can be sanctioned, and it does not transfer to software.
The third is that the artefacts were never the point. They were the compressed evidence that someone was paying attention. Automating them removes the compression step, not the attention, and organisations are discovering that a beautifully generated status report from nobody in particular is worth very little.
Key Takeaways
- The parts of the job done alone, against systems of record, are the exposed parts.
- The parts done with other people, where the information is not written down anywhere, are the protected parts.
- The artefacts were evidence of attention, not the attention itself. Only the evidence automates.
The uncomfortable part
If most of your week is the exposed column, your title does not protect you, and the projection that describes your actual work is the one for administrative support rather than the one for project management.
That is worth being blunt about, because it is common. A large number of people with project manager on the business card spend most of their time updating trackers, chasing status and writing summaries that nobody reads closely. The role grew a lot during a period when that was necessary work. It is becoming less necessary quickly.
The reverse is also true and more encouraging: people whose titles are nowhere near project management, but who spend their days resolving disagreements between teams, are doing the part that grows.
What to do about it
The move is not to learn the tools, although you should. It is to change what the week is made of.
Four changes that move you across the line
- 1Automate your own reporting before somebody does it for you, and spend the hours you free on the conversations you have been postponing.
- 2Own an outcome, not a process. Being accountable for whether the thing ships is a different job from being accountable for whether the tracker is current.
- 3Get into the rooms where scope and priority are argued about. That is where the protected work happens, and it is not delegated to whoever writes the status update.
- 4Be able to explain, in one sentence, what judgement you supplied this week that was not in any system. If you cannot, that is the finding.
The short version
Project management as an occupation is projected to grow much faster than the economy. Administrative coordination is projected to shrink, with AI named as a cause. Both descriptions may apply to parts of your week.
Which one describes most of it is a question about your calendar, not your title.
Key Takeaways
- Project management specialists: +7% to 2035, 73,200 more jobs.
- Secretaries and administrative assistants: −2%, 75,300 fewer, with AI named by the BLS.
- The dividing line is whether the information you work from already exists in a system.
Sources & references
Check your own week
Get a task-level breakdown of your role rather than a projection for your job title.