I believe everyone knows there are comments to tasks in Nozbe. Yet, it seems not all see a point in that. Therefore a question - to comment or not to comment - arises.
All about comments
Most of us are aware of the definition and the basic use as per instructions found on Nozbe Help Page. Their principal function is to facilitate communication on issues relevant to a given task within a team.
And that’s just great. Once your team gets disciplined about it, the function can replace emailing almost entirely and thus save much time.
Attachments that can be added to comments are a great way of speeding up your work and storing relevant reference materials in order to make everything clear.
You can also email tasks already with comments to Nozbe or add comments via email at later time.
That’s all great, you may say, but what is the point then of this post? Well… here it is:
Alternative uses of comments - notes
One of the most obvious secondary uses are simply notes. If you do not share the project with anyone, or even when you do, you might wish to add things to your own tasks.. in that case they become your notes.
Track records
Of recent, I have met with some more creative ways of using comments. An example of such is as a track record for tasks. Some users have high need for tracking this or that task and to see what happens to it at all times.
Although it is in a sense a duplication of the project activity feature, I do find it quite interesting. Basically, a comment, apart from being a comment or a note becomes also a spot to mark things like “passed to John”, “moved from project:x”, “sent to a client on 12/09/” and so on.
Reminders
Even more creative way is what some users who don’t share any projects with anyone have come up with. Namely, let’s say I have a large project that I do not wish to share, but I do have tasks in it that should be done by someone else than me.
It is obvious I can’t simply delegate it to them as it is my private project and I wish it to keep it so. Thus, I make a comment - Tom’s task - and inform Tom in another, mutually agreed upon way, that he should get it done so I can push forward the whole project. Once he is done, he lets me know and I mark the task as done, yet having the background info that it was done by him.
Let’s say, the same as above situation, with the exception that I do not want to share this particular project but do have some other project that I share with Tom… what can be done?
Simple. Make a comment - task from project X- then I move it to the project we do share, delegate it to Tom and once he is done I move it back to the original, privately owned project.
So? To comment or not to comment?
I say comment, but under no circumstance limit yourself to seeing this feature as only comments. It is so much more. Examples given above are just examples… it is up to you to use the hints creatively and as your team sees fit.
The comments could make your mutual communication way more effective and save you much time in the process… do not fret them.. they are your friend.
- Delfina (VP Support)
