I have a steering committee meeting next week and my Gantt Chart has over 200 lines. I know if I show the whole thing, they will lose interest immediately. How do you condense a complex project schedule into a high-level view that still shows the critical milestones?
3 answers
The secret is "Summary Tasks" or "Roll-up" views. Most project management software allows you to collapse the detailed sub-tasks so only the main phases (e.g., Discovery, Development, Launch) are visible. For a steering committee, I would create a separate "Executive View" that only shows milestones and major work packages. I also recommend using a "Baseline" to show where you are compared to the original plan. Use green/yellow/red indicators for the status of each major bar. This gives them the "at-a-glance" info they need without them getting bogged down in the minutiae of individual task assignments or daily updates.
Do you find that stakeholders prefer a PDF snapshot or do they actually want to see you manipulate the live chart during the meeting to answer "what-if" scenarios?
I always use a "Milestone Trend Analysis" chart alongside the Gantt. It shows if your key dates are slipping over time, which is what executives care about most.
Exactly, Margaret. Combining a simplified Gantt with a milestone tracker ensures you are communicating both the current schedule and the overall health of the project timeline.
Richard, usually they prefer a static slide for the main presentation, but they often ask "what happens if we move this deadline?" during the Q&A. I usually keep the live tool open in the background just in case. However, I’ve found that demonstrating live changes can be risky if the dependencies aren’t perfectly set, as one change might move dozens of bars in ways that are hard to explain on the fly.