The Tiny Asana Habit that Helped Me Turn Chaos into Calm (... most days)

If I had to describe 2025 in one sentence, it would be:

“A beautiful, organized tornado… inside an Asana project.”

Between onboarding new clients, Q4 curveballs, and building stronger systems for our internal teams, my days felt like a mix of color-coded zen and “wait… why is this task named Final Final FINAL edits?”

Somewhere in the mix, I learned something that completely changed how my team is working:

Clarity is the ultimate productivity hack.

Not big, glamorous clarity.

The tiny, almost boring kind that lives inside task names, rules, and fields (tied back to mandatory questions on forms).

Here’s how I accidentally stumbled into my favorite habit of the year, and why I’m taking it straight into 2026:

1. Adding context became my new love language :writing_hand::growing_heart:

I stopped letting everyone assume that assignees magically understood the “why” behind a task.

Now we have mandatory clarifying questions in our forms (which turn into briefs).

It takes 2 minutes and saves 10 headaches.

2. Naming rules: the unsung heroes :label::sparkles:

We ditched mystery tasks like “Check this plz” and replaced them with clear naming conventions that instantly tell you:

  • What the task is
  • Which project it belongs to
  • Which stage it’s in

It’s like giving your whole team a pair of glasses they didn’t know they needed.

3. Dashboards became less “report” and more “team therapy session.” :bar_chart::teacup_without_handle:

Instead of treating dashboards as static charts, we started using them as conversation starters:

  • “What’s slipping?”
  • “Which client is heating up?”
  • “Do we need more resources… or just more snacks?”

It brought transparency, honesty, and more proactive planning.

What changed? :dizzy:

  • Automations clicked into place
  • Creative briefs actually worked the same way every time
  • Our PMO structure became less theoretical and more real
  • And my team spent way less time asking “Wait, what does this mean?”

Tiny clarity habits = big calm energy.

10/10 recommend.

And with that, here’s the thought I’m taking into the new year:

:fortune_cookie: Clarity turns chaos into progress :fortune_cookie:

22 Likes

@Erica_Tay I love all of this! I’d love to learn more about exactly how you implemented the ‘context’ piece of your forms - is it just a text line for them to fill out? How do you word the request?

5 Likes

This is awesome! Thanks for sharing your habits. My team has also been trying to find better ways to provide the “why” behind tasks + providing more context helps in the long run! Having clarity can be very helpful.

I absolutely love the fortune cookie quote too! :smiley: :clap:

2 Likes

This is great. I love the reminder about naming rules!

2 Likes

Great read, Erica! I feel like naming rules (even though super simple) create so much context. But because it is so simple, people overlook implementing them. Also love the idea of looking at dashboards as a tool the team can use to discuss.

2 Likes

Absolutely (& thanks for reading)!

I’ll start by saying, we completely overhauled our creative requests so that it better mirrors a traditional brief. All creative requests HAVE to be filled out using our forms now & that in itself has added more clarity.

Yes, we added mandatory text lines for context, but we’re specific in what we’re asking (and we’re using a lot of branching so that the context depends on the creative needs). For example:

  1. The first step is to choose the type of creative request (copy only? strategy? creative build?) – the answer depends on the type of questions that follow.

  2. Lets say it’s a creative build, you’ll first have to select the client or project (which will be built into the name of the task) & if the request is a static or motion (this allows PM to identify the potential designers we can utilize faster)

  3. Next we ask how many concepts and how many iterations (this gives us the number of creatives being made & helps us better estimate the time the project will take)

  4. Next we choose the platforms the creative is being built for. From there, each platform branches off into the sizing for those platforms and the requestor has to choose what sizes they’ll need.

  5. From here we have fields (questions) that dive deeper into the “context”, so that our creative team can be really intentional about their designs (ie. What’s the main objective? Is it to drive conversions? Increase CTR? Improve engagement? / What are the primary KPIs? / Who is the target audience?)

  6. Last we have questions for creative requirements (ie. specific messaging, testing hypotheses, brand or legal mandatories, and historical insights), timelines (launch date, asset delivery deadline, and priority level), and approvals (who gets final approval, if it’s external, their information)

    It’s a large form, but doesn’t take the requestor more than 5 minutes to put together. Plus, by doing so, we’ve eliminated countless phone calls & back-and-forth between creative, PM, and our media teams.

6 Likes

Thanks, Xand!! Hope you’re doing wonderfully since we last spoke :star_struck:

Naming rules has become SUCH a game-changer for my “future-self”. You know… when Asana goes and makes what was once a work-around a very simplistic rule OR when things could be more easily updated with the AI rule builder? Having the earlier-built rules named made it much simpler to go in and update (or in some cases, delete).

1 Like

Naming a task in a specific way has become key for me. It makes things easier to find, doesn’t clutter things up and straight to the point. I like the KISS method … keep it simple stupid :slight_smile:

2 Likes

The ‘Final Final FINAL edits’ trap is SO real, @Erica_Tay! :laughing:

It’s easy to overlook those tiny habits, but they really are the difference between a project feeling like a ‘tornado’ or a calm workspace.

Really appreciate you sharing these insights with the Community! :heart_hands:

1 Like