What Are Typical Project Management Skills?

The Project Management Skills Worth Developing, and the Ones Worth Avoiding

Here’s the deal. There is a book called Built to Fail by Todd Zabel that is not particularly well written, and its early chapters carry genuinely important content, especially read alongside How Big Things Get Done. The book traces distinct eras in how construction has treated the people doing the work, and understanding those eras explains exactly why so much of what gets called project management today does not actually help a project succeed.

Era One: Disrespect Dressed Up as Efficiency

The first era traces back heavily to Frederick Taylor’s Theory of Scientific Management, a body of thinking responsible for one of the most dehumanizing management philosophies our industry ever inherited. Taylor’s own writing described workers using genuinely degrading language, and that framing helped justify pushing people too fast, segregating labor, running piecework systems, and building a toxic classical business management model that prioritized output over the people producing it. A lot of that thinking is still embedded in how our industry operates today, even when nobody realizes where it came from.

Era Two: Solving the Wrong Problem With More Paperwork

The second era emerged as a reaction to the first, and it solved the wrong problem. If workers were assumed to be careless or slow, the logical response, from that flawed starting point, was for management to add more oversight. More forms. More meetings. More positions created specifically to manage and monitor the people doing the actual work. That is how the era of administration was born, and it is closely tied to the Project Management Institute’s model of the job.

I have gone through PMI’s materials directly, and in my own assessment, only around fifteen percent of the content genuinely adds value to running a real project. A lot of what gets emphasized, heavier RFI processes, more complex submittals, extensive project controls, does very little for the actual outcome of a construction project.

Why the RFI Process Is a Perfect Example

Here is a concrete illustration worth sitting with. Picture an RFI process where a designer, working collaboratively with financial approval already in place, simply posts corrected and updated information directly at the source, through a shared design platform, automatically distributed to everyone who needs it. Compare that against the standard process most projects still run, essentially writing a small document for every question, batching and queuing it, exchanging emails back and forth, with a standard fifteen day delay built into the whole cycle.

There is no version of that comparison where the traditional process wins. We have simply normalized these slow, administratively heavy habits and called the result project management. What the industry actually needs is project leadership, and that starts with genuinely loathing waste in this arena rather than treating it as an unavoidable cost of doing business.

Skill One: Planning, Not Scheduling

The first real skill worth developing is planning, and I mean that in the fullest sense, not simply scheduling. Planning means the environment, the rhythm, the integration, the collaboration, the design, the materials, the tools, the equipment, and the information are all prepared together, so the crew has genuine full kit, meaning materials, information, and permissions, available in their zone within their Takt time to complete a day’s work.

That is the actual job. The project delivery team’s ultimate customer is the crew and the trade partner executing the work. A project manager supports the superintendent, who supports the assistants, field engineers, and foremen, who in turn support the workers. The project manager’s role in that whole chain is making sure everything flows well enough that the crew genuinely has what they need.

Skill Two: Communication, Not Email

A project manager is fundamentally a professional communicator, and this applies equally to introverts and extroverts. I want to be direct about something. Email is not communication. There is nothing about email that actually delivers effective communication.

Real communication happens verbally, in meetings, through phone calls, through the ability to set genuine clarity, through interpersonal skill in the office, and through the principles found in how to win friends and influence people. A project manager who genuinely communicates well transforms the entire job. Communication sits at the center of everything else on this list.

Skill Three: Genuine Organization

Organization matters for superintendents too, but it is especially critical for a project manager. A person who consistently runs a disorganized desk, a cluttered computer screen, or a chaotic vehicle is signaling something real about how the rest of their role will function.

Watch for these signs organization has slipped in a project management role:

• Documents that are hard to locate quickly when a real question comes up
• Communication channels that are not consistently organized or easy to follow
• A general environment that reflects disorder rather than genuine control

A project manager needs everything filed appropriately, posted appropriately, and organized from day one. The entire jobsite becomes, in a real sense, a manifestation of that person’s organized mind.

Skill Four: Problem Solving, Built Around Timing

I once worked alongside a colleague who liked to say that problems are actually opportunities. Later, working in Japan, I heard the opposite framing, that problems are simply problems. Eventually I realized both were right, depending entirely on timing.

A problem genuinely is an opportunity if it gets caught before it ever impacts the crew. A problem only becomes an actual problem once it reaches and impacts the work. That distinction is exactly why a project manager needs to become a fanatical roadblock remover, clearing the path ahead of everyone else so real progress can happen, especially at the crew level. The framing I like best, borrowed from the Lean Builder philosophy, is that a project manager’s job is to keep all the lights green out ahead of the team.

Skill Five: Merging Field and Office Competence

A project manager genuinely needs competence in administration, planning, pre-construction, finances, and design coordination. None of that competence matters if it is not ultimately oriented toward how well the work executes in the field.

Here is a clear example of getting this wrong. A knowledgeable project manager decides to cut line items like field engineering or advanced planning from the job cost report to trim short term spending. That is not wise financial leadership, even though it looks disciplined on paper. The wiser approach treats field engineers and genuine pre-planning as an investment, consistent with the research behind How Big Things Get Done, because that investment is exactly what prevents losing far more money later through contingency draws and rework. Being financially wise and being field focused are the same skill, not two competing priorities.

Building These Skills Into Your Own Team

None of this happens automatically. It requires real investment in people skills too, the ability to provide clarity, connection, and relevance to a team, and the ability to engage in genuinely healthy conflict rather than avoiding disagreement entirely. Patrick Lencioni’s work through the Table Group covers this territory extremely well and is worth studying directly.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your project managers build these five skills deliberately, planning, communication, organization, problem solving, and merged field and office competence, rather than letting them default into the administrative habits our industry inherited from an era that was never actually designed to help projects succeed.

So here is the challenge. Look at your own project managers, or your own role if that applies, and check honestly against these five skills. Which one is genuinely strong, and which one has quietly been replaced by administrative habit instead of real leadership? That gap is exactly where to focus training next.

Jason Schroeder said it plainly: “What we really need is project leadership.” Build these five skills deliberately, and that shift becomes real rather than aspirational.

On we go.

FAQ

Why does the article criticize the traditional RFI process so directly?
Because a collaborative alternative already exists, where a designer posts corrected information directly at the source with financial approval, distributed automatically. Compared against a traditional RFI process built around written documentation, batching, queuing, and a standard fifteen day delay, the traditional version adds significant time without adding meaningful value, which is why the article treats it as a clear example of administrative waste.

What is the actual difference between planning and scheduling in this context?
Scheduling refers narrowly to dates and sequence. Planning, as described here, covers the environment, rhythm, integration, collaboration, design, materials, tools, equipment, and information all being prepared together so a crew has genuine full kit in their zone within their Takt time. Planning is the broader discipline that scheduling exists to support, not the other way around.

Why does the article claim that a problem can be both an opportunity and a genuine problem?
Because the distinction depends entirely on timing. A problem caught and resolved before it ever reaches or impacts the crew functions as an opportunity to improve the plan. The same underlying issue, left unaddressed until it actually disrupts the crew’s work, becomes a genuine problem with real cost attached. That is why the article frames a project manager’s core role as removing roadblocks before impact rather than reacting after.