# 👻 Medium and Low priorities are usually an illusion

**URL:** <https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970>\
**Category:** Forum Leader tips\
**Tags:** forum-leader-tip\
**Created:** [20 January 2021 08:33 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970 "2021-01-20T08:33:35Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [20 January 2021 08:33 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/1 "2021-01-20T08:33:35Z")

</div>

Bear with me. The default priority custom field in Asana contains High-Medium-Low.

Apart from the fact that they should not have colored them all (but only color High), I believe having a Medium and Low priorities adds complexity where things used to be simple.

Something is usually either urgent, or is not. It is a high priority or a normal one. And, for the sake of clarity, when something has a default value, use an empty value! Your Asana project will be clearer, with less words and colors, and the actual high priorities will pop on the screen.

My revised version of the priority field? A single value « High » in red. Nothing else.

🇫🇷 [Version française](https://forum.asana.com/t/les-priorites-moyennes-et-basses-sont-generalement-une-illusion/155760)

---

<div class="post-metadata">

**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\
**Post date:** [20 January 2021 19:04 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/2 "2021-01-20T19:04:13Z")

</div>

I agree, and would go even further:

- Avoid use of a Priority custom field (as found in many Asana-provided project templates, unfortunately); it’s often not really meaningful and extra work to set such a value for every single task. (Sometimes projects can be set up to allow the tasks to appear in rough priority order.)
- Instead, consider an “Urgent?” custom field with a default value of blank and a single other option of either 🔥or “Urgent” in red. (Often with similar on/off custom fields I use the lighter-weight value of just ✔ but in this case it likely helps to see the word “Urgent”.)
- Since priority is now reduced to just a single value, Basic (free) Asana accounts could use a tag instead of custom field, and this may even be desirable for paid accounts too because it’s even more lightweight–no devoted column required. That tag value could either be “Urgent” or simply 🔥.

Hope those ideas help some,

Larry

PS I can’t believe I had to encourage @Bastien_Siebman to use an emoji❗

---

<div class="post-metadata">

**Author:** ![Denis\_Sooma](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/denis_sooma/32/81249_2.png) [@Denis\_Sooma](https://forum.asana.com/u/Denis_Sooma)\
**Post date:** [21 January 2021 01:50 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/3 "2021-01-21T01:50:32Z")

</div>

Hey @Bastien_Siebman !

That actually makes total sense. I will update some projects havind that in mind. Thanks!

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [21 January 2021 21:30 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/4 "2021-01-21T21:30:59Z")

</div>

> [@Larry\_Berger\_lpb](#):
>
> PS I can’t believe I had to encourage @Bastien_Siebman to use an emoji❗

Sorry to disappoint Larry but I do have the emoji already 🙂

 ![Capture d’écran 2021-01-21 à 22.30.38](https://us1.discourse-cdn.com/asana/original/3X/2/9/29a7f6613ced6efd8b59778d6db79da4abdaa5b1.png)

---

<div class="post-metadata">

**Author:** ![anon36108714](https://luna1.co/8d76cd.png) [@anon36108714](https://forum.asana.com/u/anon36108714)\
**Post date:** [22 January 2021 09:10 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/5 "2021-01-22T09:10:06Z")

</div>

It depend on where you are using them. In a project / product back log these are create for understanding customer prioritise as a starting point. You then only promote the high priority ones.

---

<div class="post-metadata">

**Author:** ![Getz\_Pro](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/getz_pro/32/13546_2.png) [@Getz\_Pro](https://forum.asana.com/u/Getz_Pro)\
**Post date:** [23 January 2021 19:41 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/6 "2021-01-23T19:41:36Z")

</div>

Disagree completely.

Often when scoping out work it is necessary to set the level of _want_ for an item. This helps determine it’s priority in sprints as well as descoping if time/budget constraints come in or additional scope is requested.

If any of the above I can easily provide as list of low priority items to be descoped or moved to a different version.

I can also prioritize resources based on what has been identified higher priority. It may have impact on other projects but isn’t urgent. It may be a nice to have but should never be coded above other work.

So many different reasons to set priority on tasks. Nothing is ever black and white or Urgent or Not.

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [23 January 2021 19:58 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/7 "2021-01-23T19:58:25Z")

</div>

@Getz_Pro I agree several levels are sometimes needed or interesting, but in many cases that brings more complexity and manual work to manage 🙂

---

<div class="post-metadata">

**Author:** ![Getz\_Pro](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/getz_pro/32/13546_2.png) [@Getz\_Pro](https://forum.asana.com/u/Getz_Pro)\
**Post date:** [23 January 2021 20:02 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/8 "2021-01-23T20:02:36Z")

</div>

To _your_ work perhaps. But not to _most_ work.

For your use case why bother at all with a priority level? Just put urgent tasks at the top with the expected due date. Urgent means now or this week. No need to also call it out via a field.

There is zero manual work with Rules.

Also, having the levels allows for a lesser scoped item to move up to a higher priority if budget suddenly allows or use case changes. Then you can rule a chain reaction accordantly.

Agree that any of this denotation for the ‘doers’ is pointless, but for the ‘planners’ it is vital.

---

<div class="post-metadata">

**Author:** ![Jason\_Woods](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jason_woods/32/2601_2.png) [@Jason\_Woods](https://forum.asana.com/u/Jason_Woods)\
**Post date:** [12 February 2022 11:15 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/9 "2022-02-12T11:15:23Z")

</div>

Came across this post again… Mainly because I was interested to see what Name of the Field that was used.

I wanted to create a New Field to handle A Priority Theme but couldn’t call in “Priority” because I can’t add a field called that to my Organisation because Asana already has one…

So I have mixed Larry and Bastien and came up with this;

Field Name: Urgent  
Drop Down Values:  
💥Hell Yeah  
☀Nah Maybe  
Not

For Me this should give me a bit of combination of Priority and Impact, it also mixes in MOSCOW. Must is Hell Yeah, Should & Could are Nah Maybe and Won’t is Not.

Will see how I go… Now the fun job updating all the current projects.

Jason.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/system/32/276370_2.png) [@system](https://forum.asana.com/u/system)\
**Post date:** [30 May 2025 18:52 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/10 "2025-05-30T18:52:59Z")

</div>

Closed on 30 May 2025 18:52 UTC



---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/system/32/276370_2.png) [@system](https://forum.asana.com/u/system)\
**Post date:** [30 May 2025 18:52 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/11 "2025-05-30T18:52:59Z")

</div>

Unlisted on 30 May 2025 18:52 UTC



---

<div class="post-metadata">

**Author:** ![Emily\_Roman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/emily_roman/32/283076_2.png) [@Emily\_Roman](https://forum.asana.com/u/Emily_Roman)\
**Post date:** [3 June 2025 09:09 UTC](https://forum.asana.com/t/medium-and-low-priorities-are-usually-an-illusion/106970/12 "2025-06-03T09:09:56Z")

</div>

Listed on 3 June 2025 09:09 UTC


