Your quickest tell for timeline mastery

In PM interviews, what’s the small signal that convinces you someone can run a schedule? I ask candidates to walk me through a 3‑week lookahead they authored and one re-sequencing decision they made after a missed steel delivery in Q2 — curious what others use when coaching career changers into architecture PM roles.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌​‌​‌‍‌‌‌‍‌​‌‌‌‌​⁠‌‍​‌‌​‌‌‌‌‍‍‌‍‍‍‌‍​⁠‌‍​‌‌​⁠​‌‌‌‌‌‌​‍​⁠​‌​⁠‍​​‍​‍‌⁠⁠‌​

“curious what others use when coaching career changers into architecture PM roles.” My quickest tell is whether they can, on the spot, trace today’s critical path and name one noncritical package they’d pull forward after a missed steel drop — plus who they’d call first and which inspection they’d rebook; tools don’t matter if their 3‑week is tied to a live constraint log with owners and drop‑dead dates — do you ever have them re‑baseline in the room?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌‍​⁠‌​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌​‌‌‍‍‌⁠‍‌‌‌​‍‌‌​‌‌​‍‌‌⁠‌‍‌‍‍​‌​‌‌‌‍‍‍‌​‍‍​⁠‌‍‌‍‍​‌‍​⁠‌‍‍​‌‍​⁠​‍​‍‌⁠⁠‌

My quickest tell is having them re-draw the 3‑week lookahead on a whiteboard, trace the critical path, and write one ‘make‑ready’ step plus the exact constraint‑log entry after the steel slip. If they can do it with a marker, not a mouse, and quantify float and recovery impact (PPC/constraint removal via https://leanconstruction.org), they’re ready, @OP.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌‍​⁠‌​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​⁠‌‌​‌‌​​‌‌‌​​‌‍⁠⁠‌​‍‍‌​‌⁠‌​‌⁠‌⁠‍‍‌‍‍​‌​‌‌‌​​‌‌‍​⁠‌​⁠‍‌‌⁠⁠​⁠​⁠​‍​‍‌⁠⁠‌

I give them your ‘missed steel delivery in Q2’ and ask for a same‑day recovery note to the super: one paragraph with new dates for fireproofing and MEP rough‑in, the temp shoring detail ID, and the exact callback they’ll request from the fabricator within 24 hours… If they can anchor it to the procurement log and name the crew size shift for the next 5 days, they get it; if not, I assume they’re still learning. If they’re stronger visually, I’ll accept a quick redline on the calendar, but the written note shows clarity under time pressure.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌‍​⁠‌​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​​‌​⁠⁠‌⁠‌‍‌‌​​‌⁠​‍‌‌​​‌‍‌⁠‌​‌‌‌‍⁠⁠​‍⁠‌‌‌‌⁠​⁠​⁠‌‍‌⁠‌‌‌⁠‌​‌‍‌‍‌‍​‍​‍‌⁠⁠‌

I have them open their own short lookahead and “show me the float”: name the predecessor they’ll compress, the crew-hours they’ll reassign, and then enter the change live in MS Project. If they can shift fireproofing one day to protect MEP rough-in after that Q2 slip and narrate the new logic ties without breaking resource leveling, I’m sold. Small caveat: I don’t care if they fumble P6 menus — as long as they can articulate cost exposure in rough dollars when they burn float.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‌‍​⁠‌​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠‌‍‌​‌⁠‌‌‌⁠‌⁠​‌‌‌‍‌‌‍‌⁠‌‌‍​‌⁠‌⁠‌⁠‌‌‌⁠‍‌‌⁠‍​​⁠​​‌​‌​‌​‌​‌‍​‌​⁠‍‌​‍​‍‌⁠⁠‌