[et_pb_section fb_built=”1″ _builder_version=”4.6.3″ background_enable_image=”off” background_enable_video_mp4=”off” custom_padding=”0px|||||”][et_pb_row _builder_version=”4.0.11″][et_pb_column type=”4_4″ _builder_version=”4.0.11″][et_pb_video src=”https:\/\/www.youtube.com\/watch?v=XFKuiCVj5IE” image_src=”https:\/\/cjwray.com\/wp-content\/uploads\/2021\/04\/2021-04-29-YouTubeVideoThumbnail-800x450px.jpg” thumbnail_overlay_color=”rgba(0,0,0,0.6)” _builder_version=”4.6.3″ custom_padding=”||||false|false”][\/et_pb_video][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.3.4″][et_pb_column type=”4_4″ _builder_version=”4.3.4″][et_pb_text _builder_version=”4.6.3″ text_font_size=”16px”]<\/p>\n
As part of my consulting business, I help SME\u2019s implement Asana, the collaborative Project Management platform. In this video I\u2019m going to talk about some of the more common mistakes I see when working with clients. The idea being that with a little more planning and consideration of these things you can avoid some of these pitfalls. These are all people and process issues rather than the software so should be helpful to anyone considering implementing Asana. <\/p>\n
00:00 – Intro
\n00:53 – Setting Up Asana
\n02:17 – Using Asana consistently
\n03:39 – Process vs Asana
\n04:53 – Any system is only as good as the data
\n05:45 – Collaboration not control
\n07:35 – Connect and Automate[\/et_pb_text][et_pb_image src=”https:\/\/cjwray.com\/wp-content\/uploads\/2021\/03\/2021-03-17-YouTubeVideoThumbnail-800x450px.jpg” alt=”Airtable vs Asana” title_text=”2021-03-17—YouTubeVideoThumbnail-800x450px” disabled_on=”on|on|on” _builder_version=”4.6.3″ _module_preset=”default” disabled=”on”][\/et_pb_image][et_pb_toggle title=”Transcript” admin_label=”Transcript Toggle” _builder_version=”4.6.3″]<\/p>\n
As part of my consulting business, I help SME\u2019s implement Asana, the collaborative Project Management platform.
In this video I\u2019m going to talk about some of the more common mistakes I see when working with clients. The idea being that with a little more planning and consideration of these things you can avoid some of these pitfalls.<\/p>\n
These are all people and process issues rather than the software so should be helpful to anyone considering implementing Asana.<\/p>\n
Mistake #1 – Not Setting up projects correctly.<\/strong><\/p>\n Here it’s good to think about the structure of your work first before diving in an setting up your projects. So its good practice at the start to take a review of all of the projects you\u2019ll be setting up and consider how the tasks relate to projects, sections and tasks. {Switch to Asana view}<\/p>\n Mistake #2 Teams not using Asana consistently<\/strong><\/p>\n Within reason, everyone in your organization should use Asana, but more importantly they should use it the same way. Ensure there\u2019s consistency across teams and use custom fields, tags and task content in the same way. It\u2019s really good to get the input of the key stakeholders before you start to implement Asana, and also good to go through a few short training sessions with each team to ensure that consistency.<\/p>\n I did have one client where one country office simply refused to use Asana and wanted to stick to Basecamp. Now this is a people management issue rather than a software issue but we all make assumptions, so good to manage major issues like this up front.<\/p>\n Mistake #3 Trying to get your process to fit into Asana \u2013 rather than Asana supporting your process<\/strong><\/p>\n Asana should improve things for your team. Making task management, communication, hitting project milestones better for your organization. You need to get that return on investment. Mistake #4 Any system is only as good as the data in it<\/strong><\/p>\n Get into the habit of regularly updating tasks, archiving your inbox, checking the My Tasks section and marking tasks complete as soon as they are done. Mistake #5 Collaboration not control<\/strong><\/p>\n This is one for the control freaks and some Project Managers and again is a people issue rather than Asana.<\/p>\n It’s important to remember that Asana is built for collaboration and is not a tool to control people. Ensure the structure allows people autonomy to create, update and close tasks and add value to others. Mistake #6 Connect and Automate<\/strong><\/p>\n When things are working well within Asana. Look at connecting Asana to other systems to get data in and out, and trigger actions and data flow in other systems. Asana now integrates with more and more applications as well as working with Zapier the automation tool. If you need help with setting up Asana do please contact me, I work with clients across the globe to get the best out of Asana and other technology platforms.<\/p>\n [\/et_pb_toggle][et_pb_text _builder_version=”4.6.3″ text_font_size=”16px”]<\/p>\n Take a look at my Asana Consulting<\/a> page.\u00a0 For more about Asana see here.<\/a><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" The Biggest Mistakes in Asana, and how to avoid them. As part of my consulting business, I help SME\u2019s implement Asana, the collaborative Project Management platform. In this video I\u2019m going to talk about some of the more common mistakes I see when working with clients. The idea being that with a little more planning […]<\/p>\n","protected":false},"author":1,"featured_media":2111,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[13,14],"tags":[],"_links":{"self":[{"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/posts\/2109"}],"collection":[{"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/comments?post=2109"}],"version-history":[{"count":0,"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/posts\/2109\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/media\/2111"}],"wp:attachment":[{"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/media?parent=2109"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/categories?post=2109"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cjwray.com\/wp-json\/wp\/v2\/tags?post=2109"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
So what is a project, and where do sections, tasks and subtasks fit in. The trick is to try and keep things to the higher levels of projects sections and tasks. I often see people with too many subtasks and then looking for another level of detail beyond that. It would perhaps have been better to split the project up to try and raise the level of these details.<\/p>\n
If you find yourself struggling to get Asana to work for you, or you\u2019re having to make big changes to your process, maybe you should consider if you\u2019re investing in the right tool.
Of course there are always small changes to make. Asana isn\u2019t a perfect solution for everyone, and I have seen clients review their processes and ask if they could work better. But if this is a battle to implement, there\u2019s likely to be an issue elsewhere.<\/p>\n
There\u2019s nothing worse than looking at overdue tasks, poor descriptions and no communication. People will stop using Asana if the data isn\u2019t accurate and updated regularly.<\/p>\n
Where you need a strict structure, use templates, custom fields, and make sure your processes are documented and up to date. Regular communication is always helpful of course. I\u2019ve seen some Project Managers insisting that they are the only person to close tasks. This really doesn\u2019t work, as it just causes bottlenecks and problems as people will try and work around this. For issues like this take a look at why someone needs this control, and fix that issue rather than use Asana in ways that it wasn\u2019t intended.<\/p>\n
This is one of my specialist areas, connecting systems together and automating processes. There\u2019s a link to a video here (point up) that describes connecting Pipedrive CRM to Asana to automatically create a project when a deal is won.<\/p>\nThe Biggest Mistakes in Asana, and how to avoid them.<\/h3>\n