Document everything you do in the Asana comments

When you’re working with a tool like Asana, here’s one very important tip: document everything you do.

Got a task to fix a piece of software? Use the comments to write down the instructions you plan to follow. Paste in the links to the docs you used. Drop in a few screenshots of your progress.

This applies to any task. Document the decisions you made, the reasoning behind them, the reasons for choosing one approach over another, and even the options you decided not to try.

Why? Because there’s a good chance you’ll find yourself in the exact same situation weeks or months from now. And when you do, you’ll be grateful to stumble across that old task with everything neatly documented in the comments.

What to do if there are people as collaborators? I’d say: don’t worry about them, but let them know you are entering deep work mode, this is a complex topic, and you’ll be dropping a lot of comments. Let them know they can leave the task if they want to.

I cannot count how many times I was thankful for a bunch of silly comment I wrote months prior.


Bastien, Asana Expert
i.DO (Asana Partner: Services & Licenses)

20 Likes

This is great advice, and something we’ve been starting to advocate for during meetings when someone mentions some work they’ve done related to an Asana task. Several of my teammates have also picked up that ball, so it’s more and more common these days to hear “That’s great insight and sounds like it was hard to figure out. Can you drop a summary in the Asana task so we can avoid solving this problem again later?”

The team is picking it up and it’s giving us a great place to track our accumulated wisdom in near real-time. :slight_smile:

While I agree it’s great to document anything important in Asana, frequently the Comments contain a lot of noise, and the task Description can be a better alternative, often for this kind of information.

Updating the Description instead of adding comments will avoid notifying collaborators. On the other hand, if you want a notification generated, a good best practice is just to add a “See Description change” notification, and optionally summarizing it in a phrase, or just letting anyone click the diff link that appears in the task detail pane’s All activity tab:
image

Thanks,

Larry

6 Likes

I believe that decisions should always go in the comments, so we clearly see who decides and when. But the result of discussions should go in the description (or be pinned)

9 Likes

Glad to see we’re in agreement on “result of discussions should go in the description (or be pinned).”

“Comments … [to] see who decides and when” is good too, though sometimes I streamline this by only putting it in the Description in this form:

  • 2026 01 16 Larry: Mentions description
  • 2026 01 16 Bastien: Concurs

where the date is a text expander shortcut I use about 6,000 times daily!

1 Like

@Bastien_Siebman , @lpb , glad to see you two stick to your principles over the years:

:sweat_smile:
(found in :sparkles: Related, below)

Actually because of

I was gonna say that maybe we would really struggle to work together as we seem to have such different approaches to everything :rofl:

I didn’t say you agree on the same principles.. :rofl:

Very funny, @Richard_Sather!

I know you don’t mean this because of :rofl:, but I’m surprised because I thought it’s Subtasks about which we most like to debate, not Comments :slight_smile: !

But re that original 2020 topic, I actually convinced you then, partially at least, and you changed your OP there! And since that was several years before AI, I’d update my stance to say it’s more important to document details, even if it had to be in comments.

2 Likes

Knowing that you are both experts and consider various use cases, it seems…

2 Likes

One can make cases for documenting in the description or the comments, but I think the most important thing, which (going out a little on a limb) I think both @Bastien_Siebman and @lpb are pointing at, is the importance of, and the value of Asana, for capturing institutional memory of decisions made and a summary of the discussions that led up to them.

Capturing institutional memory helps to preserve organizational knowledge and context so as to avoid repeating the same mistakes, and to help make better-informed decisions over time. It can also help with onboarding and with continuity after job turnover.

Asana is the perfect place for doing this!

2 Likes

Thanks, @Phil_Seeman; I’ll sign on to that…provided we can quickly come up with another topic to harangue, nitpick, and argue about :slight_smile:

1 Like

Which we started doing with “toolboxes”. Those are projects where the data is clean, organised and consolidated. And it also makes everything easier with AI, because in most cases it only has to look at those toolboxes instead of all projects

2 Likes

I totally agree! This habit is so helpful in the long run or even for people like me who sometimes can’t recall decisions that were made last week or after a vacation lol. BUT, our operations team prefers not to see all our project set up comments. My solution is to create a subtask for project set up comments and on handoff the operations team can have their own comments tab. Any better ideas?

1 Like

You’re so right about this! I’ve been leaving comments or follow ups for myself in certain instances and it has helped me multiple times.

1 Like

“Yes, but” :slight_smile:

  • Be mindful of PII
  • Asana is missing today the ability to track who saw the comment and whether from Asana app itself vs email vs other (something monday.com has been doing for a long time)

Interesting, I would not want that. Because seeing that would make people assume seeing=agreeing, and I strongly disagree…

1 Like

Hello - “Seeing” (with timestamp) means “read receipt” - same as for emails.

In project management this makes a significant difference.

Thank you

I can’t think of any way to use that info in a meaningful way. Do you have an example?

I’ve been doing this from the start - and you’re so right!

Btw, you’re my favorite poster. Just sayin’ … and keep up the great work!

1 Like