In my opinion, the ability to create complex Gantt charts is becoming less important. With agile and other flexible methodologies, a single, all-encompassing chart often isn't as helpful as it once was. What's your take on this?
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Syed Ashir Riaz Great question — and I agree that the ability to build complex Gantt charts is becoming less central, especially in adaptive environments.
But rather than saying it's "less important", I’d say it’s less universal. Gantt charts still have value — particularly in industrial, sequential or compliance-heavy projects — but they're no longer the centerpiece of modern project leadership.
This reflects a broader shift:
- From rigid planning to contextual adaptability
- From tool mastery to decision clarity and team empowerment
- From micromanagement to trust-based delegation
In fact, several other skills are following a similar path:
- Micro-management is giving way to leadership by purpose and trust
- Over-reliance on technical certifications is giving way to experiential learning and impact
- Static reporting is giving way to real-time, meaningful dashboards
The message is clear: the project manager of today is not just a scheduler — but a strategic integrator, a sensemaker, and a catalyst of purposeful action.
Thanks for sparking this reflection!
...
1 reply by Syed Ashir Riaz
Sep 08, 2025 11:21 AM
Syed Ashir Riaz
...
I agree, Gantt charts still have their place in sequential or compliance-heavy projects, but they’re no longer the centerpiece of modern project leadership. The shift is clear: from rigid planning to adaptability, tool mastery to decision clarity, and micromanagement to trust. Today’s project manager is less a scheduler and more a strategic integrator and catalyst for purposeful action.
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
I agree with you, complex Gantt charts don’t hold the same weight they used to. With agile boards, burndown charts, and real-time dashboards, teams now prioritize adaptability over rigid planning. What matters more today is the ability to visualize work in a way that’s transparent and easy to adjust, rather than producing one “master plan” that quickly becomes outdated.
...
1 reply by Syed Ashir Riaz
Sep 08, 2025 11:20 AM
Syed Ashir Riaz
...
Absolutely; flexibility and transparency outweigh static plans. Tools that adapt in real time keep teams aligned and responsive, which is far more valuable than a single rigid chart.
1) It's going to vary by field/industry.
2) In my 20+ years experience in IT, it's mostly only been important to me. Even when I've been expected to create one, it was rare that someone other than me wanted to see it. However, when you're deploying large ERP & CRM systems, globally, it's a valuable tool even if you're the only one looking at it. If I'm working with a 3rd party implementation partner, on just about anything, I want more than a burn-down chart and release plan to validate the schedule and make sure that both internal and external team members are on top of things.
...
1 reply by Syed Ashir Riaz
Sep 08, 2025 11:23 AM
Syed Ashir Riaz
...
That’s a great perspective. While communication plans or detailed schedules may not always be widely consumed, they’re still valuable as a PM’s tool for alignment and validation, especially in large, complex rollouts with multiple stakeholders or vendors.
Agree with Aaron, it depends on the industry, but one thing I see less of in project management artifacts/documentation is a formalized communication plan. Usually this is because the projects I work on (digital transformation) rely on operational standards/pre-existing 'ways of working' and it's not seen as necessary to formalize this in a written document.
...
1 reply by Syed Ashir Riaz
Sep 08, 2025 11:22 AM
Syed Ashir Riaz
...
Agreed, in many digital transformation projects, formal comms plans are often replaced by existing workflows and standards. Still, even a lightweight written plan can add clarity and alignment when multiple stakeholders are involved.
Saving Changes...
Khai Ng.IT PMO | IT Project Manager| TTGROUPHanoi, Viet Nam
I think the importance of a Work Breakdown Structure (WBS) and a Gantt Chart varies by industry and how tasks are organized. Although agile or hybrid approaches are common, the WBS is still essential. A high-level Gantt Chart that shows major project deliverables is still very useful for the project team and steering committee when they need to make decisions. While a detailed Gantt Chart may be less important, a project manager's ability to create a high-level one demonstrates their capacity to view the project as a whole.
...
1 reply by Syed Ashir Riaz
Sep 08, 2025 11:21 AM
Syed Ashir Riaz
...
Well said, WBS remains foundational, and a high-level Gantt is still valuable for steering committees and decision-making. Even if detailed charts matter less in agile contexts, the ability to create a top-level view shows a PM’s capacity to see the big picture.”
I agree with you, complex Gantt charts don’t hold the same weight they used to. With agile boards, burndown charts, and real-time dashboards, teams now prioritize adaptability over rigid planning. What matters more today is the ability to visualize work in a way that’s transparent and easy to adjust, rather than producing one “master plan” that quickly becomes outdated.
Absolutely; flexibility and transparency outweigh static plans. Tools that adapt in real time keep teams aligned and responsive, which is far more valuable than a single rigid chart. Saving Changes...
Syed Ashir Riaz Great question — and I agree that the ability to build complex Gantt charts is becoming less central, especially in adaptive environments.
But rather than saying it's "less important", I’d say it’s less universal. Gantt charts still have value — particularly in industrial, sequential or compliance-heavy projects — but they're no longer the centerpiece of modern project leadership.
This reflects a broader shift:
- From rigid planning to contextual adaptability
- From tool mastery to decision clarity and team empowerment
- From micromanagement to trust-based delegation
In fact, several other skills are following a similar path:
- Micro-management is giving way to leadership by purpose and trust
- Over-reliance on technical certifications is giving way to experiential learning and impact
- Static reporting is giving way to real-time, meaningful dashboards
The message is clear: the project manager of today is not just a scheduler — but a strategic integrator, a sensemaker, and a catalyst of purposeful action.
Thanks for sparking this reflection!
I agree, Gantt charts still have their place in sequential or compliance-heavy projects, but they’re no longer the centerpiece of modern project leadership. The shift is clear: from rigid planning to adaptability, tool mastery to decision clarity, and micromanagement to trust. Today’s project manager is less a scheduler and more a strategic integrator and catalyst for purposeful action. Saving Changes...
I think the importance of a Work Breakdown Structure (WBS) and a Gantt Chart varies by industry and how tasks are organized. Although agile or hybrid approaches are common, the WBS is still essential. A high-level Gantt Chart that shows major project deliverables is still very useful for the project team and steering committee when they need to make decisions. While a detailed Gantt Chart may be less important, a project manager's ability to create a high-level one demonstrates their capacity to view the project as a whole.
Well said, WBS remains foundational, and a high-level Gantt is still valuable for steering committees and decision-making. Even if detailed charts matter less in agile contexts, the ability to create a top-level view shows a PM’s capacity to see the big picture.” Saving Changes...
Agree with Aaron, it depends on the industry, but one thing I see less of in project management artifacts/documentation is a formalized communication plan. Usually this is because the projects I work on (digital transformation) rely on operational standards/pre-existing 'ways of working' and it's not seen as necessary to formalize this in a written document.
Agreed, in many digital transformation projects, formal comms plans are often replaced by existing workflows and standards. Still, even a lightweight written plan can add clarity and alignment when multiple stakeholders are involved. Saving Changes...
1) It's going to vary by field/industry.
2) In my 20+ years experience in IT, it's mostly only been important to me. Even when I've been expected to create one, it was rare that someone other than me wanted to see it. However, when you're deploying large ERP & CRM systems, globally, it's a valuable tool even if you're the only one looking at it. If I'm working with a 3rd party implementation partner, on just about anything, I want more than a burn-down chart and release plan to validate the schedule and make sure that both internal and external team members are on top of things.
That’s a great perspective. While communication plans or detailed schedules may not always be widely consumed, they’re still valuable as a PM’s tool for alignment and validation, especially in large, complex rollouts with multiple stakeholders or vendors. Saving Changes...
Community Champion
