Director's Field Notes
Director's Field Notes · Part 8 of 10
What I Expect From a Project Controls Manager
The best controls managers I have worked with are not the ones with the tidiest programmes. They are the ones who own the number, challenge what does not add up, and tell me what to do about it.
When I think about what separates a good Project Controls Manager from a competent one, it is not the software. Competence with P6 and the reporting is the entry ticket, not the differentiator. What I actually look for is a smaller set of things — and most of them are about judgement and ownership rather than technique.
Technical competence, assumed. The mechanics have to be right — logic, progress, forecasting, the critical path, the analysis. But I take that as the baseline, not the achievement. A perfectly maintained programme that no one interrogates is administration, not control.
Ownership of the number. I want a controls manager who owns the programme position rather than transmitting it. “The contractor says 62%” is relay. “The contractor says 62%, I have tested it against the record, and here is where I do and do not believe it” is control. The difference is whether the person stands behind what they report.
Evidence, not opinion. When I ask why a date has moved, I want the answer grounded in the programme and the record — the window, the driving path, the event — not a general impression. A controls manager whose answers rest on evidence is one whose answers survive scrutiny.
Challenge. I expect a controls manager to challenge what does not add up — a recovery that cannot be resourced, progress that does not reconcile, a critical-path claim that runs through improbable activities — and to challenge it professionally, on the evidence. A function that accepts everything is not assuring anything.
Anticipation. The real value is seeing the problem while there is still time to act on it. I want the near-critical path that is about to take over flagged this month, not explained next month. Controls that only report what has already happened is a mirror; controls that surfaces what is emerging is an instrument.
Clarity and communication. A controls manager has to be able to take a complex programme picture and give leadership the two things that matter without the twenty that do not. Precision is not the same as volume. The skill is deciding what to leave out.
Escalation. I expect judgement about what to escalate and when — not everything, which is noise, and not nothing, which is negligence. Knowing which exposure needs to reach the person who can act on it, while there is still time, is a core part of the role.
Decision support. Above all, I expect the output to help a decision get made. The point of project controls is not to describe the programme; it is to give leadership what they need to act. A controls manager who consistently converts programme evidence into a clear “here is the decision this requires” is doing the job at the level it is meant to be done.
None of this is unreasonable, but it is a higher bar than “keeps the programme updated.” It is the difference between a function that records the job and one that helps run it — and at Director level, that difference is the whole point.
The takeaway: competence with the tools is the baseline. What makes a Project Controls Manager valuable is owning the number, challenging what does not add up, anticipating the problem, and converting evidence into the decision it requires. That expectation runs through the whole Director’s Playbook.