Case Study 2 — The Swap: Two Project Managers Who Traded Places

A Tier-3 illustrative composite. Vanguard National Builders is invented, as are the people and the numbers. Kestrel Construction Group is the book's standing composite contractor.

Setup

Two project managers changed companies in the same eighteen months, in opposite directions, and ended up on opposite sides of the same coordination meeting three years later — which is how Ray heard both versions.

Aaron Delacroix spent nine years at Vanguard National Builders, a large national contractor with regional offices in a dozen markets, formal salary bands, a two-week annual training program, a corporate safety department of eleven people, and a project portfolio that includes hospitals, data centers, and airports. He was a project manager there. He left for Kestrel Construction Group — roughly $410M in annual revenue, one metro area, 340 salaried employees.

Yolanda Ferris spent eleven years at Kestrel, the last four as a project manager, and left for Vanguard.

Neither move was a rescue. Both were leaving companies they liked.

What Happened

Aaron: national → regional

At Vanguard, Aaron's last assignment was a $310,000,000 hospital tower. His title was project manager and his actual scope was the interiors and finishes package on levels four through eleven — about $41,000,000 of work — with two project engineers reporting to him, a dedicated scheduler he did not manage, a dedicated safety manager he did not manage, and a project accountant three offices away who produced the cost report he reviewed but did not build.

In nine years at Vanguard he had never bought out a job, never negotiated a subcontract from a blank exhibit, never sat with an owner alone, and never seen a work-in-progress schedule.

He was very good at what he did. He could run a coordination meeting with fourteen trades and hold a hard sequence together for eleven months. He had never once been asked what the company made on the job.

His first Kestrel assignment was a $24,000,000 community college classroom building with an assistant project manager and a superintendent, and that was the entire staff.

"Where's the scheduler?" he asked Ray in week one.

"You are."

"Who does the buyout?"

"You do. Tomás's estimating file is the starting point, and every scope gap between those packages belongs to you personally. Chapter and verse: if it's not in somebody's subcontract, it's in yours."

Aaron's first four months were the hardest of his career. He blew a scope gap between the drywall and the acoustical ceiling packages — the gridline soffit framing, which each bidder had assumed the other carried — and it cost about $46,000 to resolve. At Vanguard, that gap would have been caught by a scope-review process run by a preconstruction group he never met.

By month fourteen he was running the whole job, and he could tell you the gross margin to two decimal places on any given Tuesday.

Yolanda: regional → national

Yolanda's last Kestrel job was an $18,000,000 recreation center: she ran it end to end — estimate handoff, buyout, subcontracts, cost report, pay applications, changes, the owner, the closeout, the whole thing, with one APM and one superintendent.

At Vanguard, she was hired as a project manager on a $480,000,000 data center campus and given the electrical and low-voltage scope across three buildings — about $96,000,000 — with three project engineers and two assistant project managers reporting to her.

Her first month, she asked the project executive for the job's cost report.

"You'll get your scope's report on the ninth," he said. "The whole-job report goes to me."

"How do I know if the job's making money?"

"You don't. That's mine. Your job is your scope."

She has described that conversation as both the most frustrating and the most instructive of her career — frustrating because it removed the thing she had learned to care about, instructive because it took her about a year to understand that on a $480M job, the whole-job view cannot be everyone's job, and the discipline she was mourning was a small-company discipline.

What she got instead: the largest and most technically demanding scope she had ever touched, a commissioning process with a rigor she had not seen, a safety program with resources behind it, five direct reports to develop, and a formal path to a project executive role with written criteria attached to it.

What she lost: the owner. She has not had a real client relationship since she left Kestrel. On the data center campus, the client relationship belongs to the project executive and to a national account team, and she is not in those meetings.

The comparison, honestly

Analysis

The two moves are the same move, in opposite directions, and both were about acquiring the thing the previous employer structurally could not teach. Vanguard cannot teach whole-job commercial ownership to a project manager, because on a $310M job nobody has whole-job commercial ownership except a project executive. Kestrel cannot teach $480M-scale execution, because Kestrel does not build $480M projects. Neither is a deficiency; both are consequences of size. This is exactly the trade in §42.6: large teaches systems and scale, regional teaches breadth, and the correct question is not which is better but which one do I need next.

Notice how differently the same title behaved. Aaron and Yolanda were both "project managers" before and after, and the job changed completely in both cases. A title in this industry describes a rung on somebody's specific ladder, not a portable definition. This is the argument in §42.4.5 for asking which project would I be assigned to — a question that would have told either of them more than the whole rest of the interview.

The $46,000 scope gap is the most useful number here. Aaron did not fail because he was careless. He failed because a process he had never had to perform had been performed for him, invisibly, for nine years. Every large-company professional carries an inventory of skills they believe they have and have never actually executed, and the way to find them is to write out the steps of a job you have "done" and mark the ones somebody else did. Do that before you move, not four months after. It is the same discipline as the self-assessment in §42.10, applied to institutional support rather than to talent.

The compensation comparison is a lesson in structure, not in size. Aaron's base barely moved and his bonus became line-of-sight — his job's margin, his check — which is motivating and also volatile, because one bad job is his bad job. Yolanda's base rose within a published band and her bonus became more structured and more diluted, which is steadier and less responsive to how well she personally performs. Neither structure is superior; they are priced for different risk appetites, and §42.4.3 is the map. What matters is that both of them knew the structure before they signed, and that Yolanda asked what the plan had actually paid for the last three years and Aaron did not.

And the thing Yolanda lost is the one that is hardest to get back. Technical skill can be acquired on the next job. Client relationships take years and are built in rooms you have to be invited into. If you take a role that removes you from the client, be deliberate about it: volunteer for pursuits and interviews, go to the association meetings, and keep the relationships you already have warm (§42.9.4). Otherwise you arrive at the project executive interview with a superb technical record and no answer to the only question that matters at that level, which is: who would follow you here?

Discussion Questions

1. Aaron says he should have made the move at year five instead of year nine. What did the four extra years actually cost him, and what did they buy? Argue the other side.
2. Yolanda's project executive told her she does not get the whole-job cost report. Was that the right call on a $480M project? Under what circumstances would you change it, and what would it cost to change?
3. Aaron's $46,000 scope gap was a skill he thought he had. Write down three tasks you believe you can do that you have never actually performed end to end without help. Be specific about which step somebody else did.
4. Both of them changed employers to acquire a capability. Name a capability you can only acquire by changing employers, and one you are currently telling yourself requires a change but does not.
5. If Aaron and Yolanda swapped again in five years, what would each of them bring back that they did not have before — and would either company value it correctly?

Your Turn

Write the capability inventory described in the analysis. Take your current role and list every step of a full project cycle you are nominally responsible for: estimate handoff, buyout and scope review, subcontract preparation, schedule development, submittal and procurement planning, cost loading, forecasting, change pricing and negotiation, pay applications, delay analysis, closeout, and the client relationship.

Mark each one D (I have done this end to end alone), H (I have done it with help), or S (somebody else did it and I watched or reviewed).

Then count your S items. That count is the honest gap between your title and your capability, and it is the list you should be quietly closing over the next two years — whether or not you ever change companies.