3 ms·
I think the fundamental problem with project management software is poorly defined scope. There are features that involve project and portfolio-level reporting
by timoth3y 5y ago
I think the fundamental problem with project management software is poorly defined scope.
There are features that involve project and portfolio-level reporting, forecasting, task assignment, feature definition, change-request management, team collaboration, etc.
All of these are important, but maybe bundling is not the right answer at this point.
I think that's why do much discussion comes down to "feature debate". Users talking about features they hate in their PM software and new software explaining they don't have those features.
It's a discussion focused on reducing pain rather than productive benefit.
It would be good to rethink what we really want from PM software, specifically, and how to optimize one or two core use cases.
This is not criticism of Wormhole. It might be a great software, but it follows the same pattern of discussion "You know all those features you hate in your current PM software? Well, this software doesn't have those features."
I don't want software that just sucks less. I want software that makes my life better.
- qudat 5y agoThanks for the feedback! > It would be good to rethink what we really want from PM software, specifically, and how to optimize one or two core use cases. I love this line of thinking. What do you really want from PM software?
- timoth3y 5y agoIt's hard to say. There is much more clarity about what makes good reporting software or task management software or spec management software. I guess good PM software should be more than the sum of its parts. Using a bunch of best-of-breed solutions with no integration is a pain, but that's usually better than well-integrated mediocrity. Although at larger scale, the integration becomes more and more important.