Make adding AI to a rule a concious decision

I was sad to see my idea for the AI Studio toggle switch removed.

I’d like it back, but maybe there are other ways to improve the user experience.

The core is this:

:bullseye: Adding AI to a rule should be a concious decision.

Why? because we shouldn’t use AI when there are other options.
Because :

  • deterministic automations don’t hallucinate, which makes them more reliable
  • deterministic automations don’t consume credits, which increases value for money
  • deterministic automations don’t consume as much energy, which is better for the planet

Elimination would be even better than automation, but let’s not go there in this topic.

Some examples:

When you add a Create task or Create subtask action, the “Let AI decide the number of tasks to create” automatically gets selected.

Although it is visible from the box that has the action that there is AI included, I do not think it makes sense to assume that when someone creates a (sub)task, they want AI to determine how many.

Now the same goes for Create with AI

If I do not specify that I do not want to use AI in the rule, chances are it will be added. I don’t think that’s a suitable solution.

I think this design nudges people to consume more credits than they need, and introduces rework to later hunt for and remove unintended AI logic.

Although the superior option is likely the other way around, I’d even think I’d be fine with a cearly coloured opt-out to “Include AI automations” (like illustrated below) or something similar. As long as it’s not a surprise that AI is included.

Related: 📈 Mind your AI Studio credit efficiency!

2 Likes

I voted and hope others will too.

Asana subtly opts the user in to write an AI Studio rule and use up AI credits.

That will be surprising to most, does not put the user in control, and is not a good user experience.

Thanks,

Larry

3 Likes