It would be extremely helpful to use Asana for large-scale project mgt BUT there are some hinderances to that.
5 layers of tasks/subtasks visible - so all tasks for a large project can be seen at once – and a critical path for the project can be created.
Critical Path - We can “see” one on the Gantt chart graphic, but I’m not confident it is correct. (If we were to change a date, does the CP actually update like it should?) It would be good to also see it in a column - so we could filter on just those tasks.
Baseline columns – Baselines are in the Gantt chart view but aren’t very helpful. Having baseline columns built into the Asana would be valuable. It would be good to be able to filter on just what has changed - especially if part of the Critical Path.
Gantt Chart view columns - be able to add additional columns to it - like other views, so you could turn them off/on as needed as your main view for a project.
Asana could greatly benefit from this too - since it could finally be used for large-scale project mgt - instead of only initiative, workflow, and task management (small projects). Thanks!
I’m afraid the policy in the Forum for requests is to only specify one distinct request per topic in English Forum > Product Feedback. That allows targeted voting for each feature specifically.
Would you mind searching in English Forum > Product Feedback for existing threads for each of your requests and voting for each one you find, and adding your use case (large-scale projects) in a comment in each? (Click the title to scroll to the top and vote by clicking the Vote button at the top-left.)
For any request you can’t find, add a new topic, individually, and vote.
Sharing my workaround use cases just in case they are of use happy to elaborate if they are of use.
For Critical Path management, I’ve created a dedicated Critical Path section within the project. The key tasks are linked together using dependencies, and all associated task activities are anchored to those Critical Path tasks. This means that when a Critical Path task moves on the timeline, the dependent activities move with it, reducing the amount of manual date management required.
I’ve also implemented a custom task type within the section that triggers an AI-generated update whenever a Critical Path date changes. This automatically documents date movements and variations, giving us a record that can be reviewed during post-project evaluation and lessons learned.
Because not every project requires the same workflow in larger scale variations of project, I’ve also used custom task types that include “Required” and “Not Required.” When a task is marked as not required, it can be removed from the workflow, helping keep the project plan clean and focused on only the activities relevant to that project.
Regarding task visibility, Asana can display all tasks and subtasks within a project. In List View, click the project options menu (three dots) and ensure subtasks are shown/expanded. You can also use the “Expand all subtasks” option to view the full hierarchy, making it easier to review the entire project structure in one place.