In July 2017, policy promises sounded optimistic while contractors reported healthy backlog and difficulty finding workers. Economist Anirban Basu also saw signs of excess in parts of the market. The conversation placed those conditions beside each other instead of treating them as unrelated headlines.
That 2017 outlook stays in its original time. The planning habit from the episode remains useful: examine the labor assumption and the broader market assumption together before relying on a capital plan.
Policy headlines are not the same as capital movement
One of the first corrections Anirban Basu made was political. In 2017, pro-business sentiment and big infrastructure talk were easy to hear. He said owners needed to ask what had actually changed in legislation, financing, and capital movement.
That distinction matters in any cycle. Optimism can move faster than policy. By the time a project team acts on the mood alone, it may still be waiting on the practical conditions that were supposed to support the work.
Owners do not need to become economists to use that insight. They do need to separate what is being promised from what is operationally visible.
Labor shortage is not only a hiring problem
Anirban also treated labor as an execution issue, not just a staffing complaint. In that 2017 setting, he said contractors' principal challenge was “finding enough good workers to get the work done.” Backlog alone therefore did not settle the staffing question.
If labor is thin, the question is not only whether the project can win the work. The question is whether the team can staff the work well enough to deliver it with the quality and timing the owner expects.
He also tied that constraint to deeper issues in education, workforce exposure, and who the industry has failed to recruit. That broadens the conversation beyond immediate project needs without pretending those pipeline fixes happen quickly.
Productivity pressure makes controlled production more attractive
Anirban's comments on modular delivery fit inside that same labor discussion. He described controlled manufacturing as one response to the variability of field conditions and the difficulty of finding enough skilled workers. He was not arguing that every project should become modular. He was pointing to a business logic. Repeatable work becomes easier to scale when fewer parts of the process depend on different site conditions every day.
Because the conversation happened in 2017, the example stays in that time. Owners can carry forward a narrower review question without carrying forward the forecast: which parts of the proposed work depend most on field variability, labor availability, or repeatability?
Late-cycle discipline matters even when demand still feels strong
The other side of the episode was caution. Anirban warned about low cap rates, aggressive pricing, and the possibility that the market was moving late into the cycle. His advice then was not to panic. It was to recognize when enthusiasm had started to outrun discipline.
That matters because owners can face two temptations at once. They may rush to secure work because the market seems busy, and they may underweight the risk of entering or expanding too aggressively when asset values are already stretched.
For one upcoming capital decision, write down the labor assumption built into the schedule or scope and the market assumption built into the return case. Ask the project and investment owners what changes if either assumption proves weaker than expected. Record that response beside the decision instead of relying on a single headline forecast.
The 2017 forecast belongs to its moment. The owner habit does not depend on repeating it: make both assumptions visible before deciding how much confidence the plan deserves.
