I don't get the point the author is trying to make:
* The article starts off by arguing that Gantt charts are for factories not for information work; therefore, software providing "bygone ways" of project management (such as Gantt charts) is bad.
* Then it criticizes that software that masters multiple project management methodologies is also bad because SaaS companies are trying to make money by adding features.
* Then, we find that the issue is that project management software is a simplistic UI in front of a relational database. They don't work because project management is not a problem that can be put into databases.
* Then the problem is that the smartphone generation will
never understand relational databases because they are used to smooth UIs, and the problem is that there is no undo button.
* Next, the problem is that we aren't all thinking like managers, so PM methodologies... don't apply at all to us?
* However the supporting example instead says that the problem is that we aren't all thinking like developers, and developers dogfooding their PM software is not necessarily a great selling point for everyone else (this is a take I find somewhat convincing).
* Finally, the issue is poor planning, and no software will
ever solve it.
Maybe I am not commenting on the "most charitable reading" of this article, but it leaves me confused. The author is echoing a broadly-felt frustration with the world of PM tools. They further various criticisms of PM tools, but it feels like they struggle to find what their own criticism actually is.
* The article starts off by arguing that Gantt charts are for factories not for information work; therefore, software providing "bygone ways" of project management (such as Gantt charts) is bad.
* Then it criticizes that software that masters multiple project management methodologies is also bad because SaaS companies are trying to make money by adding features.
* Then, we find that the issue is that project management software is a simplistic UI in front of a relational database. They don't work because project management is not a problem that can be put into databases.
* Then the problem is that the smartphone generation will never understand relational databases because they are used to smooth UIs, and the problem is that there is no undo button.
* Next, the problem is that we aren't all thinking like managers, so PM methodologies... don't apply at all to us?
* However the supporting example instead says that the problem is that we aren't all thinking like developers, and developers dogfooding their PM software is not necessarily a great selling point for everyone else (this is a take I find somewhat convincing).
* Finally, the issue is poor planning, and no software will ever solve it.
Maybe I am not commenting on the "most charitable reading" of this article, but it leaves me confused. The author is echoing a broadly-felt frustration with the world of PM tools. They further various criticisms of PM tools, but it feels like they struggle to find what their own criticism actually is.