Привет, меня зовут Миролюбов Владимир
Я очень интересуюсь продакт-менеджментом и бизнесом.
В своем блоге я делюсь разными идеями и мыслями на этот счет. Больше обо мне тут.
4 October, 2015 in Blog , Asana (13), features (6)

How to organize your Asana in to the wiki base

Hi, Asana! How are you? Hope, you well and I congratulate you with your redesign – looks very good!

Today I want to share something very important for each startup or project. And as you can see, this tips will be for your users and I published this post in Blog category. Like as everything, before I start I want to make some intro in the beginning.

Asana main goal is to give some tools to projects organize. Very flexible and functionality online tools, wich used many IT-startups. But what are the startups? It’s team and products. And all team generate and make a product with many derivatives: images, texts, docs, discusses etc. Each of this things is very important for the product because it collect much valuable information about product (goals, decisions, ideas). A try to explain something.

For example, you have a task about creation new function. When your team work on this process, they collect tons of information in each task.  And as I say before, this is very important and helpful information about your product and this function and how it work and how your team develop this function.

And what happen when you click on “Done” button? Yes, congrats, you finished and released this function. Product manager, project manager, and developer team drink a beer and every user will be happy. And this task hides from your task list because it completed.

But what next? I mean, what happen if you need to know about this function in the future? Or some similar function. Or some function from this part of tasks? Or if you have a new team member – how he can understand all specification and function list? What should you do as product/project manager? Ask your guys about this? What if your team changed (its common case in startups)? Use a search? Maybe, but it’s so hard and non-useful for everybody.

In this case, you should use something, what can collect all your functions in one place. Something, what can help you find and understand all product functions via sorted and clean function list. Something like Wiki. This base can help you to collect all information about previous and current works, task and specifications.

Let’s see on my example of wiki base for Asana (new window)


This is simple Asana project named as Wiki. It’s not a similar “to-do” tasks. This is some base of your product functionality and how you can collect all information about your product changes.

In the middle screen, you can see your functions list of your product. All technical part of your product should be here.

I split all functions by two type:

1. Main functions

1.1 Sub-function.

This is “what you’re working on”. When you click on some function name you can see a new window with the function description and activity.

Let’s see how we can use Asana features for this goals:

Function description. You can add any information about how this function works. If description too big, you can write it in doc and attach a file.

A full list of task. It’s simple – all task what your team working on this function. It’s easy to add this task via @taskname and everybody can see this task like a link on this task.

All files. All files, associated with this function: features, roadmap, brief, specifications, images, etc. Also, you can use version control (do you remember the importance to control your product changes?) in separate doc and write here all function changes.

Function activity. Yes, you can use Asana comments like activity feed. Type @taskname and add some quick information about it. Asana will index this info and you can use search (good post about Asana search) anywhere to find the desired task.

This is an easy and simple way to organize your wiki base in your Asana project. Just ask your product or project manager copy all important information in this Asana Wiki base. And no task won’t be lost.