Hello @Shannon_McNeil,
Thanks for the feedback! Appreciate it
Workspace Audits are important from my point of view to guarantee long term success of Asana implementation and to guarantee the compliance of the agreed Asana Convention.
It is also a great situation to further help people to integrate their processes into Asana.
I did this the first time when I worked at Home24, see the screenshot below:
So how to read it:
-
Green means everything is OK
-
Yellow means there are some smaller issues e.g. sometimes assignees are missing, or some tasks are over due which is ofter the case
-
Red means there are some big issues e.g. important projects are missing, people do not stick to agreed Asana Convention
-
The color coding is to ensure that the manager and I can see easily where we have to fix first - high level overview
-
Inside the cells you find details for a better feedback, because specific feedback has more impact - and I also tell people what they are doing good and encourage them to share their best practices!
So how is the process:
-
I fill out the basics in the sheet template, which you will find below. Basics are the different departments/ teams, the responsible heads, if these people had previous Asana experience and which trainings they and there teams have participated in
-
Then the real work takes place and I dig deep into the team with their projects and tasks: I look for issues which are usually no assignees, no due dates or past due dates, missing objectives and pros and cons in task descriptions, missing files attached, important tasks not in the roadmap etc… ; And I check other things which we have agreed on in the Asana Convention Workshop.
-
Afterwards, I do 1on1s with the team leads, I find it important not to do a public blaming email with all the issues etc. the Results of the Workspace Audits are for the overall manager and me only. In the 1on1s I ask the heads about their experience so far with Asana and give them some feedback. During these 1on1s most of the heads asked very specific questions how they can implement certain processes into Asana which we will also clarify during the meeting if an immediate solution is obvious
-
I encourage the heads to share their learnings and best practices in a “Success or best practice meetings” since this keeps the “Momentum” alive
Such a Workspace Audit should be done ideally after 2, 4 and 12 weeks.
Workspace Audit template (is constantly adapted and improved):
At REWE Digital, I did not have time to do these Workspace Audits and it resulted in: People not sticking to the Convention, teams using Asana differently, many overdue tasks or not assigned tasks
I hope this helps!
@paulminors, @Todd_Cavanaugh Since you two are also doing Workspace Audits, what is your opinion about it? What do you do differently? How often do you do it?
All the best,
Sebastian