Compressing the schedule, managing constraints, and preventing failures.
A project schedule is never "done". It evolves continuously as work progresses, new information emerges, and constraints change. The key insight:
Reexamining the schedule isn't a sign of failure —
it's how successful projects are managed.
Effective project management follows a continuous cycle:
Update Progress
Record actual completion percentages, actual start dates, any changes to remaining duration. The schedule should reflect reality, not the original plan.
Recalculate
Let the scheduling engine recalculate all dates based on current progress. The critical path may have shifted. New violations may have appeared.
Analyze
Review the updated critical path. Check for constraint violations (FNLT warnings). Identify risks and opportunities.
Optimize
Look for ways to compress the schedule: reduce duration on critical path tasks, parallelize work, add resources. Then return to step 1.
Want the project to finish earlier? You must shorten the critical path. There are only a few ways to do this:
Reduce duration
Can a 10-day task become 8 days with more resources or better methods?
Remove or relax dependencies
Does Task B really need to wait for all of Task A? Can they overlap?
Split work for parallelization
Can a single large task become two smaller tasks that run concurrently?
Fast-track procurement
Can materials or approvals be obtained earlier than planned?
Key insight: Shortening a non-critical task won't speed up the project. Shortening a critical path task by even one day makes the project finish one day earlier (until another path becomes critical).
When deadlines are hard — regulatory submissions, contractual milestones, external events — you need proactive constraint management. Here's a proven pattern:
For any critical deadline, create two gated activitieswith FNLT constraints:
Gate 1: Internal Review Deadline
Set this one week before the actual deadline. Create a milestone like "Regulatory submission ready for internal review" with an FNLT one week early.
Gate 2: Final Submission Deadline
The actual external deadline. Create a milestone "Regulatory submission filed" with an FNLT on the true deadline date.
Why this works: The first gate gives you early warning. If Gate 1 shows an FNLT violation (red flag), you have a week to correct course before the real deadline is at risk. Without this pattern, you might not know you're in trouble until it's too late.
If "Prepare FDA submission" takes longer than expected, Gate 1 turns red first, giving you time to add resources or expedite before the real deadline.
For any task with a hard deadline, understand and document its entire predecessor chain. A delay anywhere upstream flows down to your critical milestone.