The Daily Question Your Project Managers Can't Afford to Forget

Picture a project manager at a mid-sized aerospace manufacturer. At any given moment they're juggling 100 to 500 active work orders across multiple programs, each one a deliverable that takes days or weeks to complete, with planning horizons stretching across quarters. Customers keep updating purchase orders while engineering makes changes of its own, and the ERP reflects all of it in real time. And somewhere in that sea of information is a single part with a 32-week lead time that should have been ordered last month, or a work order that's been sitting in assembly three days longer than planned and nobody's noticed yet.

The project manager is good at the job and checks the reports regularly. But they're human, and a human can't reliably ask the same simple question about every work order every single day, especially when the answer is almost always "everything's fine." That's the edge-case problem: the volume makes consistency impossible, even for careful people.

Why long-lead items are different

In aerospace manufacturing, some components have lead times of 19 to 52 or more weeks. Specialized connectors and custom machined parts aren't things you can rush order when you realize you're short.

When a long-lead part misses its order date, the math is brutal. A 32-week lead time plus four weeks to notice the gap is a 36-week program slip. You can expedite at three times the cost and still add 12 weeks, and sometimes there's no recovering the delivery window at all. For manufacturers competing on reliability and on-time delivery, a single long-lead miss can damage a customer relationship that took years to build.

Project managers know to check. The manual version of that checking, done consistently across hundreds of work orders, is what can't be sustained.

The simple questions that matter

When we sat down with the project managers at one manufacturer, we asked them: "What questions do you wish you could ask every day about every work order?" The list was surprisingly straightforward.

On procurement: has this part been ordered? What's the lead time? When do we need it? Do we have it in inventory already? Does anything look off about the timing?

On production: how long has this work order been in its current stage? Is that normal for this type of work? Do we have the labor allocated that we said we'd need? Are we on track to hit the committed delivery date? Is anything stuck or moving slower than expected?

These are basic sanity checks, the kind of thing you'd ask about every work order if you had infinite time and perfect memory. But when you're managing 300 active work orders, each with its own bill of materials and production timeline, asking them manually means thousands of checks per day. It's not realistic, so the questions don't get asked, and occasionally something slips through.

Building the safety net

The fix is to automate the simple, consistent questions so the humans can spend their attention on the judgment calls.

Every morning, the system we built with them connects to their ERP with read-only access and pulls every active work order. For each part in the BOM it checks order status, lead time against the delivery date, inventory, and anything that looks off about the timing. For the work order itself it checks the current stage and how long it's been there, labor hours logged against estimate, stage timing against historical norms, and delivery date risk.

The system doesn't make decisions, and it never auto-orders parts or reassigns labor. It asks the questions and surfaces only the exceptions that need human attention. A part with a 40-week lead time that hasn't been ordered against a delivery in 35 weeks gets flagged, and so does a work order that's been in assembly for 5 days when similar jobs typically take 2. When everything looks on track, the system stays quiet. Project managers get a daily digest of the things that actually need their attention instead of a firehose of data.

The UCLA basketball principle

There's a story about John Wooden, one of the most successful college basketball coaches in history. Every season he'd gather his team, freshmen and seniors alike, and the first lesson was always the same: how to tie your shoes properly. These were championship athletes, and he started with shoe-tying, because if your shoes come untied mid-game nothing else you've practiced matters, and doing simple things consistently is how excellence gets built.

That's the philosophy behind this system. The questions we're automating are the equivalent of "are your shoes tied?", asked about every work order, every day.

Before these models existed, building this wouldn't have made economic sense. You'd need a team of developers to parse the ERP and write business logic for every edge case, then maintain it all as your processes evolved. That's IBM-scale consulting work. Your options were hiring more project managers, which is expensive and doesn't solve the consistency problem, or paying for enterprise consulting that takes years and seven figures and still can't surface the edge cases. Today a competent developer can build a functioning version in a week, and the system gets smarter as it learns which questions matter most for your specific operation. The capability overhang here is real, and my guess is most manufacturers don't realize this kind of tooling is now economically viable for them.

What it looks like in practice

The project manager starts the morning with a digest: "Here are the 8 items across your 300 work orders that need attention today." Eight specific callouts arrive with context attached, instead of 300 status updates or a dashboard to comb through.

Work Order #4782, Customer XYZ Program. Part #AN-48321 (connector assembly). Lead time: 42 weeks. Delivery required: 38 weeks from today. Status: quote received, not yet ordered. Action needed: expedite the order or negotiate a delivery extension. > Work Order #5194, Customer ABC Program. Current stage: assembly. Time in stage: 4.5 days (average for similar work: 2.1 days). Labor hours logged: 18 (estimated: 24). Action needed: check for a bottleneck or resource constraint.

The project manager sees them and makes the calls, and the programs stay on track. The system moves those items back to green and keeps monitoring everything else. All it's doing is enforcing consistency at a scale a human can't sustain manually.

The biggest fear when we proposed this system was alert fatigue. "We're already drowning in information. You're going to make it worse." What happened was the opposite. Because the system only surfaces exceptions, project managers get less noise than before: most days most work orders show green, and the system confirms "everything's fine" silently, speaking up only when something needs attention. One project manager described it as "finally being able to sleep at night, knowing the simple questions are getting asked, about procurement and production, even when I'm not thinking about them."

That's the goal: a safety net built from consistent, automated fundamentals that catches the edge cases before they cascade into program delays.

What you need to build this

Three things: read-only ERP integration covering work orders, BOMs, inventory, order status, and production tracking; a question framework, which your project managers already carry in their heads and mostly just needs capturing, for both procurement and production; and exception logic that defines what yellow and red look like for your operation, across the supply chain and the shop floor.

The technical implementation is straightforward once you have those pieces. The hard part is sitting down with your team and asking: "What are the simple questions we should be asking every day but can't scale manually?" That's where we come in. We help you find those questions and build the tooling that asks them consistently, wired into the daily workflow so it actually gets used.

If you're managing hundreds of active work orders and relying on human memory to catch timing issues, in procurement or in production, you're carrying risk you don't need to carry. The checks can be automated now, and the economics work.