How do you manage Pipeline straight from My Tasks

English Forum Use Cases
1

Hi there,

one of the best ways to manage a constant stream of tasks, in my opinion, is to define a Pipeline.

This allows you to see the workload at every stage of the Pipeline and the prioritize accordingly.

In our case, we are using these sections in every project in order to differentiate the stages a task goes through (we are a client service software company):

  • Unprocessed:
  • Estimating:
  • Waiting to be planned:
  • In Progress:
  • Testing:
  • Client verifies the project:
  • PAUSED:

Everything works fine except that we cannot see and cannot change the Section (i.e. Pipeline status) of a task from My Tasks. See this screenshot:
https://screencast.com/t/nN0Rlj47K5I

Would like to know, how do you manage your Pipelines?

Custom fields would not work as they are not visible in My Tasks.

Tags are visible, but then every team member needs to remember which are the tags for every pipeline stage and which are the transitions in the pipeline.

Thanks for any input you may have.

Regards,
Marius

2

Unfortunately it is a catch22 in this case.

my best solution would be to use tags, but as you mentioned you need to remember to check the stage of the task every now and again.

A possible solution would be:

  1. instead of adding the custom field EVERYWHERE, just add all the tasks to one common project which has the custom field set
  2. when you need to check the status, you browse that project and organise the tasks by user

In this way you can still have a clear overview of the status and manage the tasks in a very simple way

Does it make sense?

Ciao
Carlo

1 Like
3

What Carlo mentioned is what I do. I manage a design team in part, and I have it set up so thereā€™s a ā€˜Design Pipelineā€™ project. Literally everything they do that involves design assigned to them is there, sectioned off with all the required fields that I use with the design team, so I never have to go and add those to random projects.

I understand that you want them to be able to look at the tasks and prioritize their work based on where it is in the pipeline, I would simply say that this comes down to reviewing the tasks as you move them.

Example: Iā€™m starting my day today and am looking through the upcoming items,I click on each one typically as/before I move it around to Today or leave it there. They should do the same - do they see a task is in the ā€˜Pausedā€™ section? Cool, move it to upcoming. ā€˜Testingā€™? Same thing (maybe, depending on the person).

Also adding a convention (if there isnā€™t one already) that requires that people add a comment when a task is moved from section to section might be beneficial. So if theyā€™re notified it was moved to testing theyā€™ll manage it in their pipeline or whatever.

Tags arenā€™t a bad idea if you want them to be visible in my tasks, itā€™s not crazy to expect them to remember the tags for each section if you use the section names as tags. At least, I would have issues if they couldnā€™t remember that the ā€˜unprocessedā€™ tag means xyz =D

Hope this helps, happy to chat about other issues/ideas!

1 Like
4

You can see the section from the task view in the right pane, next to the project. Did you know that? But it does not give you the overview you might need in the center pan.

Tags also look the way to goā€¦

Donā€™t people know the pipeline after a few weeks of use? And why not have one tag per stage, instead of one tag per stage per project?

5

I arrived here after searching on how to set up a ā€œsales pipelineā€ with Asana but it seems like dedicated tools such as a CRM are a much better solution than Asana. The thing is that at the end of the day both systems need to communicate and somehow create a unified action view.