2] Deploying Project Management Principles with Asana

Earlier in April, I wrote about you can deploy project management principles using Asana.
I referenced Project Management Institute and the PMBOK guide and I covered two domains - stakeholders and delivery approach.

Today, I share the second post in this series and I will cover one new domain: Teams.

Team performance domain addresses activities and functions associated with the peopke who are responsib;e of producting project deliverables.” (PMBOK Guide 7th Edition, PMI 2020).

This domain is focused on those doing the work, including the project manager who should facilitate the removal of opbstacles, acting as a shield diversion and encourgaing the team and developing opportunitities to increase team productivities. They refer to this as servant leadership.

With Asana, there is a list of features you can deploy to ensure you are fostering an environment of serant leadership.

Obstacle Removal:
There are few features you can use to help you support your team and remove obstacles.

  1. Using a ‘progress custom field’ which inlcudes at risk status. If this is too broad, you can introduce a custom field to your project called - Support needed: Yes / No. You can then create
  2. Rules that once Yes is selected, the task is added to your 1-1 project with your team member, a comment is added to the task with "@’ mentioning you so you get notified.

This approach could help you get notified immediately, and keep the support you are providing in an environement that is actionable and trackable.

Acting as a Shield Diversion

  1. Intakes: The best way to manage work load and ensure the requests are aligned with the goal of the project is to introduce an intake process. This can be donw via:
  • Forms: create a form where your stakeholders can submit requests for support within the project. This can be useful if you have a large number of people who are not asana licensed.
  • Sections (whether in list view or in Board view) and call it Incoming Requests. This helps that any new task added to the project is captured under this section. You can ensure that requests are reviewed in this section and approved (if required) before they are assigned to a project team member to work on them.

:bulb: I tend to use the Project Overview. I capture the project objective, key resources, any portfolio or goal it is associated with. When you have project stand ups and regular catch ups, always start with this on view for the project team. It acts as a focus and reminder of what is required. It also helps keep the project scope in check as its life progresses

Developing Opportunities for efficencies and Encourgaing the team:

  • Celebrating Success does not need to happen at milestones or once at the end of the project. You can do this at every task that requires a level of effort. Make sure you are specific in providing your gratitude. Keep it fun, precise! Asana’s celebrations/appreciations help you achieve just that
  • Efficiencies: As you review the progress of your project, keep in mind 3 things:
    i) Status updates provided
    ii) Due dates that are missed
    iii) Blockers that tend to have a common theme

If you work in an Agile enviornment, and have daily progress meetings, these meetings are good to explore progress, and keep the work moving. If you plan to develop opportunities for efficiencies, try and create a separate space to review and explore those opportunities. I, for example, have a private project where I keep track of feedback given and dev opportunities given to team members. I also have in the 1-1 projects a section to track professional development for my team. This could be for intitiatives they sign up to, or suggestions I bring. It is very useful to ensure this opportunities are linked directly to the work they are actively involved in.

One thing to keep in mind is project teams as a domain is different to Teams set up in Asana. Teams set up in asana relate to the a hirarchical term as such where by you group people by the funtion they operate it. If you are a small organisation, I personally do not see a use case to clutter your set up with many teams. But this of course is not a one size fits all. You can read more about Teams set up here:

:bulb: if you have workflows that are always used by the same group of people, a function, then crearting a team and housing these workflows in that space become very handy.

Resources from Asana Guide:

Happy Team Engaging!

Coming up next, strategies to deal with uncertainty in your project and maximising on Asana features.


I am loving this series! Thanks for putting this together @Rashad_Issa!


That’s great! Thanks a lot Matt for the feedback :pray:

1 Like