If youâre not up to speed with custom task types, make sure to discover what they can do for your workflows! Within that linked post, there is a tip I wanted to surface here; which is how best to name your task type!
As Iâve began working with customers that are discovering the wonders of using task types, Iâve noticed that they are naming them similar to their status fields, particularly, including the word âstatusâ within their task type name which isnât really ideal. Why?
Hereâs a few checkpoints to make sure youâre naming your task types correctly:
1. Name it after an object - answer the question âwhat type of task is this?â
Existing examples within Asana are the ânative typesâ such as âTaskâ, âMilestoneâ, âApprovalâ. So it makes sense to follow along those lines, such as a To-do, Lead, Client, Quote, Proposal, Contract, Invoice, Expense, Post, Campaign, Bug, Applicant, Vendor, Order, Property etc.
2. Name it in the singular - it should be âaâ thing, not many things
Instead of naming it âBugsâ, just name it âBugâ
3. Donât include the word âstatusâ or similar terms like stage or phase
Instead of naming it âRequest statusâ or worse âRequest statusesâ, just name it âRequestâ
4. Canât think of a name?
If youâre stuck on what to name your task type, a clue may lie with the name of your project, especially if it is an ongoing process. If your project is called âCreative requestsâ, your task type should be called âCreative requestâ (in the singular! 
).
5. Does the task type name look right?
Once you go to the Customize/Workflow button â Project settings and set your task type as the default, or via the Task types and templates menu, like thisâŚ
âŚmake sure that it looks correct and reads well in the UI, which will now display your task type name in various surfaces:
Richard Sather
Asana Solutions Partner & Forum Leader
See all of our top tips & tricks on our website.