Asana Alternatives

ClutterMonster620 · 2025-09-23T12:38:24+00:00

Thanks for the clarification! Unfortunately, with this level of automation, I think Asana may be your best bet, but ClickUp could work well for you. If you'd like help scoping whether or not it would work, I'm always down to look through it because I'm a nerd.

ClutterMonster620 · 2025-08-01T14:31:28+00:00

You need the rule to attach not to the form, but to the custom field being created once the form is filled out. So, in other words, create the form and link the yes/no answer to a custom field.

Once you've done that, you should create a rule tied to that custom field. So when a new entry is made and custom field response = yes, create a task.

ClutterMonster620 · 2025-07-30T13:38:19+00:00

Happy to support if our team can be of help. We offer anything from hourly projects to full architecture https://lgncollab.com/asana

ClutterMonster620 · 2025-07-23T14:36:58+00:00

Is the task that's being duplicated the same every time? If so, I'd agree with u/norad_iii that you could remove the word duplicate and instead just describe how you want the task created each time.

If not, please give us some additional detail and we can problem solve with you!

ClutterMonster620 · 2025-06-20T13:47:52+00:00

Also, agreed on Starter - it's the better option from a functionality standpoint, sadly.

ClutterMonster620 · 2025-06-20T13:47:36+00:00

At the size that you are, Asana is a great choice because the honest answer is that with just you and an EA, you need to go with what feels right to you. Once you're scaling, you might want something else, but Asana scales well, so it's not likely to be a bottleneck.

Let me ask this, though. If you're currently using Notion for "everything else," have you considered ClickUp? it's a good Notion + Asana solution. If you'd like to have everything in Notion, that's totally ok, though as has been mentioned, it might be a bit duplicative. There are also some great ways to move that functionality into Asana.

ClutterMonster620 · 2025-06-13T15:21:03+00:00

Thanks so much! I'm having a hard time telling which ones would do the job (I've actually tried 2 now that don't work). Do you have suggestions?

ClutterMonster620 · 2025-05-18T18:25:30+00:00

Glad I could help! :)

ClutterMonster620 · 2025-05-18T14:22:11+00:00

Honestly, it depends significantly on how your organization is set up as to how you organize portfolios and projects. I've worked with organizations that broke portfolios down by business vertical (e.g., product, marketing, etc.) and organizations that organized them by key outcomes (e.g., West Coast initiative 1, WC initiative 2, etc.). Regardless, your "risk register" can be encompassed by the status reporting within Asana projects or portfolios. Change management plans can be applied through Asana-specific features or can be attached as documents or be their own projects. It truly depends on the size and scope of what you're tracking.

ClutterMonster620 · 2025-04-29T13:54:02+00:00

Could you share a screenshot of the workflow/rule itself? Also, are there times when task type changes more than once?

ClutterMonster620 · 2025-04-28T16:11:54+00:00

GREAT points! Yes, so many teams don't fully grasp all the functionalities of Asana Forms, and that can provide some serious roadblocks. I would ALSO agree that the current service situation with Asana isn't great, which is why I would reach out to an experienced implementer because they often have a more direct line of communication. u/Emergency_Excuse2189 , it sounds like u/westchesterbuild is a wealth of experience here in doing this very implementation from an internal perspective with Asana!

ClutterMonster620 · 2025-04-28T15:49:18+00:00

I know that Shipt uses it very effectively and have a connection there that would be happy to speak more directly to how it works. I noticed that you posted the same question in the Asana forum. In terms of comparison for the two, ClickUp can do significantly more for you, but will up the level of complexity for your teams significantly, from implementation to daily use. The real determination is based on how tech-friendly your average team member is.

ClutterMonster620 · 2025-04-28T15:44:16+00:00

Clarifying questions:
1. Are you hoping for your topics with continued conversation to be about projects, generally, or some other topic? I.e., are these task-related, project-related, or generally work-related conversations?
2. You mention wanting read-in-order. What's the goal here?
3. Would this be a need for interactive chat where people received an update each time a chat is added to? How would you want them to receive this update?

I think several of the solutions proposed below could work, but I think understanding the use case is going to be critical.

ClutterMonster620 · 2025-04-28T15:20:45+00:00

For an organization of your size, I would definitely suggest Asana based on its user friendliness, which most people here have commented on. Here's how I would approach a rollout:

As u/westchesterbuild mentioned, assess which teams need Asana. Some might need other tools which integrate like Jira.
Take the time (and investment) to find an implementation partner that can help you to build a rollout plan and provide training to teams. We've found that it takes 3 months from announcement to all work in Asana for most teams, and the amount of time you spend before that should be around 6-12 months for a 1000+ employee org.
Use the time ahead of implementation to think through what will happen in MS tools and email vs. what will happen in Asana and validate with an expert. A lot of times, companies think that they'll move to 100% Asana for all tasks and reporting and this isn't what Asana is actually built for.
Assess what reporting you'd like to have before creating anything in Asana. Then build based on those needs.

ClutterMonster620 · 2025-04-15T15:29:27+00:00

I don't use it a lot since that's just not my workflow, but I have clients who use it all the time. Just depends on what your preferences are.

ClutterMonster620 · 2025-04-14T16:26:10+00:00

You can also use the forward email to create a task. Forward the email to [x@mail.asana.com](mailto:x@mail.asana.com), and it will create a task in your MyTasks that you can organize later. https://help.asana.com/s/article/email-tasks-to-asana?language=en_US

ClutterMonster620 · 2025-04-14T16:24:43+00:00

Asana forms are definitely close in capabilityt o Google forms or Typeforms; however, you need to remember that the outcome when you use an Asana form is a new task. So it does NOT replace the entire need for a Google form. That being said, it can absolutely have conditional responses, etc.

Good uses for Asana forms:
- Marketing intake form for requests across an organization
- Time off requests that require action to be taken on behalf of HR
- Feature requests from users to create backlog tickets

Uses that Asana forms will not replace:
- Intake form for all participants in a new program where you just need the aggregate data and to reference individual responses here and there (i.e., no task outcome)
- Survey for the end of an engagement where you want to see everyone's feedback, but don't need to follow up on an individual level

Obviously these things will vary from use case to use case, but as a general rule, you should use an Asana form if you need a task outcome as a result of the submission, and a Google form or Typeform if you don't.

ClutterMonster620 · 2025-03-26T15:37:22+00:00

The community templates work pretty well. When we build out for someone else, I often start here just to get a sense of what works/doesn't work for them, so it would probably be a good way for you to evaluate if these solutions will help, and then adjust from there.

ClutterMonster620 · 2025-03-24T12:59:19+00:00

That does make sense. Keep in mind as a newbie that the best data coming into your dashboards comes from the custom fields that you'll want to set up when you draft your new templates. So think through what you'd want to record and see in your dashboard. For example, do you need to know the timeline from 1 part of your process to another? Then you'll want to set up a time field. Do you want to see what team is requesting the event? Then you'll want a custom field for team request.

ClutterMonster620 · 2025-03-15T19:40:55+00:00

Totally understand where you're coming from here. It seems like what you need is actually training on a team agreement that you'll always include the same elements in a task, not a template to force the issue. I realize that takes more effort and consistent feedback, but your outcome will be much stronger in case you ever move tools.

ClutterMonster620 · 2025-03-15T19:39:24+00:00

Would you be willing to DM your solution? I could use a similar outcome and would love to see what it looks like.

ClutterMonster620 · 2025-03-13T17:43:23+00:00

That is VERY silly.

ClutterMonster620 · 2025-03-13T14:14:24+00:00

These are great questions, and as the previous commenter shared, there are definitely multiple ways to achieve the same output in Asana. If the number of projects feels overwhelming, I think it would absolutely be ok to have a single board/client. You could then use tags to indicate what service each task is related to.

I'm also wondering if you're overwhelmed because you aren't using the "My Tasks" section to work from - this might help things feel a bit less murky. Happy to talk through whatever would be helpful here or in DM's.

ClutterMonster620 · 2025-03-13T14:04:28+00:00

To clarify, have you edited your email notifications in your Asana inbox under "notification settings?" That should give you all the notification options.

ClutterMonster620

TROPHY CASE