How I would create a tracking plan for Asana to track its product features

Dear Data-Traveller, please note that this is a LinkedIn-Remix.

I posted this content already on LinkedIn in September 2022, but I want to make sure it doesn’t get lost in the social network abyss.

For your accessibility-experience and also for our own content backup, we repost the original text here.

Have a look, leave a like if you like it, and join the conversation in the comments if this sparks a thought!

Link to Post

Screenshot with Comments:

Screenshot of Timo Dechau's LinkedIn post with text about a product tracking plan for Asana

Plain Text:

Create a product tracking plan for Asana

How would you create a tracking plan for Asana to track its product features?

Sure, this is a question for Asana data people but we pretend they just hired us to help them.

When defining product events, I learned one important thing:

Don’t get into the “we want to know all clicks” rabbit hole.

Defining product events should first be on a pretty high level. So you can easily measure a product feature usage with 3-4 events.

Also, make sure that you find some powerful properties. Properties are the juice of all analysis. They enable you to break down usages by plans, user groups, company sizes, ….

Learn in this video (link in the comments) how I define the product entities (aka features) for Asana, then define the major activities and finally get some properties to better describe the product features and their usage.

Link to video: