DeAtH bY meEtiNgs. Yuck!

We’ve all felt it. Meetings to prepare for meetings. Meetings. And then debrief meetings to review past meetings. Planning meetings. Status meetings. Overlapping meetings. Meetings on mute. Multi-tasking meetings. Redundant meetings. And, also… redundant meetings. :wink:

The person who requests the meeting may think it’s meant to support our work, but really, the meeting usually just gets in the way of our work.

[For some brief empathetic comic relief re: meetings, click below]

So, what’s the problem? Well, there are lots of problems with meetings. But, one of the most egregious and common is the staggering amount of time we spend on things that DON’T need to be said or done in a meeting — namely, status reports, among other things. And, yet, that’s what drives so much of our meeting time.

However, with Asana, that problem can be reduced or eliminated! If we use Asana reliably to plan, do, and report on our work, we can massively reduce the wasteful status discussions and instead focus our valuable time together on strategizing and problem-solving.

How do we accomplish this? It starts with creating Asana templates and tools built specifically for efficient and meaningful meetings.

Exactly what defines an efficient and meaningful meeting?

In my experience, these are some essential guidelines:

  1. PURPOSE: Clearly articulated reason for the meeting
  2. PREPARATION: Communicated in advance, with time for attendees to prepare
  3. DATA-DRIVEN: Clear, accurate data as the basis for meeting topics whenever possible
  4. LIVE COLLABORATION REQUIRED: Only meet when the purpose requires live collaboration: strategizing, brainstorming, problem-solving. If the meeting topics don’t absolutely require live collaboration, then, as the saying goes, “that meeting could have been an email”; or in this case, “that meeting could have been an Asana message, task, dashboard, or saved search.”

With those essentials in mind, let’s get you set up with a meeting template built for efficient and meaningful meetings, starting with your 1-on-1s!

Introducing the one-click import link for efficient and meaningful 1-on-1 meetings! Here’s how to load this template into your account:

  1. Make sure you are logged into the Asana organization where you want the template to go
  2. Click this link: >> INSTANTLY ADD THE MEETINGS TEMPLATE TO MY ASANA WORKSPACE

The instructions for how to use it are built into the template, but I’ll provide you a high-level overview of the structure and the template setup here as well.

Overview of Structure and Setup Process

The primary purpose of this 1-on-1 meetings project template is to make the standard and time-wasting meeting topics easy to answer with a couple clicks and mere seconds of effort so that the important topics can become the focus of your meetings.

Let’s start with the meeting task template, because that’s the central element of this project.


1-ON-1 MEETING TASK TEMPLATE:

(Est. time to complete: 5-10 mins)

There is a placeholder task waiting for you in the “:busts_in_silhouette:1-ON-1 MEETINGS” section, ready to be customized.

Here’s a sneak peek of the pre-loaded agenda, which I encourage you to customize to fit your 1-on-1 meeting needs:

:backhand_index_pointing_right::black_square_button:YOUR ACTION ITEM: Follow the instructions in the “MEETING: TOPIC | DATE” task in the :busts_in_silhouette:1-ON-1 MEETINGS section to customize the task and then save as your 1-on-1 meeting task template.


SECTIONS:

(Est. time to complete: 3-5 mins)

We’ve included the following sections:

  1. :inbox_tray:TO SORT(default: open): For tasks or discussion items that get routed to this project, ready for processing (whether to add to the next meeting agenda, to work on, or to hold for future work). Positioned at the top to “catch” all incoming tasks. Because most tasks will be for upcoming work, later work, or as meeting agenda items, I recommend aiming to keep this section empty. New tasks arrive, and you sort or process them.
  2. :open_file_folder:BACKLOG/QUEUE (default: collapsed): For tasks that have been moved into the “Queue” for upcoming work but are not yet “In Progress”.
  3. :busts_in_silhouette:1-ON-1 MEETINGS (default: open): For generating and storing meeting tasks (from our meeting task template)
  4. :sunrise:PTO (default: collapsed): For generating and storing time-blocking tasks like PTO and offsites/work travel.
  5. :blue_square:IN PROGRESS (default: open): For tracking “In-Progress” ad-hoc tasks either from the backlog or delegated by the manager.
  6. :white_check_mark:DONE/ARCHIVE (default collapsed): For non-meeting tasks that have been completed.
  7. :open_file_folder:LATER (default collapsed): For tasks that we don’t want to forget about, but are not going to be worked on in the near future.

:backhand_index_pointing_right::black_square_button:YOUR ACTION ITEM: Remove any sections you do not intend to use.


PROJECT VIEWS:

(Est. time to complete: 5-10 mins)

Project views are an amazing way to customize Asana to fit your various work use cases with minimal clicks during active daily use.

I’ve included guidance for the following purpose-specific views to help you navigate this project much more efficiently:

  1. :black_square_button:ALL INCOMPLETE: For seeing all incomplete tasks in a single view, regardless of recency or due date
  2. :bullseye:TODAY (WORK DATE): For tasks you’ve committed to work on today (using a custom field I recommend, called “:date:Work Date”)
  3. :date:DUE SOON: For tasks that are overdue or due within the next 14 days
  4. :stop_button:RECENT/NEW: For newly assigned tasks, regardless of whether they have due dates or not
  5. :white_check_mark:COMPLETED: For showing recently completed work

In the template, I’ve included the tasks with instructions for how to create and customize each of these views.

:backhand_index_pointing_right::black_square_button:YOUR ACTION ITEM: Follow the instructions in the ":yellow_square:PROJECT SETUP CHECKLIST, in the subtasks under the subtask section “PROJECT VIEWS”.

RULES (ASANA AUTOMATIONS):

(Est. time to complete: 5-10 mins)

“Rules” are simply Asana automations, and they are a fantastic way to take any repeating or predictable pattern and automate it. As an example scenario, for a team meeting tracker, once a meeting is given a due date, auto-add these 3 collaborators. In this template, we can add a few rules to make meetings tracking work smoothly for you.

  1. :plus:NEW TASK → ASSIGN ME: For seeing all incomplete tasks in a single view, regardless of recency or due date
  2. (Optional rule in My Tasks) :bullseye:NEW TASK ASSIGNED → ADD TO PROJECT: If you’d like all the employee’s assigned tasks to automatically show up in this project so that you can see all assigned work as you discuss and plan together, you can go to the employee’s My Tasks and help them set this rule up.
  3. (Optional) :sunrise:PTO REQUEST → CREATE APPROVAL SUBTASK: Because planning for upcoming PTO/OOO time is usually a key part of a 1-on-1 manager-employee work relationship, you can add a rule to automatically generate an approval subtask for every PTO request that your employee creates.

Wrap-up

Congrats! Once you have added the template and followed the instructions, you are now set up for extremely efficient and meaningful meetings, including with 1-click access to the data for how last week went, what next week looks like, and follow-ups from previous meetings!

You can now roll out this same template for all 1-on-1 manager-employee pairs in your org. You can also adapt this for managing team meetings, project meetings, portfolio meetings, client meetings, and more!

Or, if you’d like help customizing this setup to your team’s specific needs,…

:backhand_index_pointing_right::black_square_button:YOUR ACTION ITEM: Reach out to your Asana rep or head on over to the Asana partner directory and set up a…. Well… I hesitate to say it, but, a meeting (an efficient and meaningful one, of course) to get some help from the people who’ve done this dozens or hundreds of times.

:tada:Kudos for taking a very important step toward productivity improvements in work management for you and your team!


BONUS IDEAS FOR EVEN MORE POWERFUL MEETINGS MGMT:
Handwritten notes to Asana text and tasks (great idea from @David_Jane):

Building on your excellent insights, I’d like to add one more, inspired by the new Studio AI.

  • If you take handwritten notes or make drawings, simply take a photo of the page(s) and upload it to a task. Studio AI (via Rules) can then transcribe your notes, format them as needed, and even generate subtasks automatically.
13 Likes

Great post @Bryan_TeamKickstart !

Building on your excellent insights, I’d like to add one more, inspired by the new Studio AI.

If you take handwritten notes or make drawings, simply take a photo of the page(s) and upload it to a task. Studio AI (via Rules) can then transcribe your notes, format them as needed, and even generate subtasks automatically.

7 Likes

This is very helpful, Bryan, thank you! I added the board and have started to go through it, and I saw something that I’ve been wanting to do but never knew how to do it…under the TO SORT section, and inside the PROJECT SETUP CHECKLIST task, you have titled areas to separate the subtasks such as “TEMPLATE TASKS” and “SECTIONS” - how do you create those titled lines??

Thank you!
Beth

1 Like

@Beth_Kurtz - Those are somewhat of a “hidden” feature of Asana, available with the keyboard shortcut: TAB + N. Click on a subtask from the task details pane on the right, then use keyboard shortcut, and that should give you the bolded subtask section. :slight_smile:
Thanks for asking!

2 Likes

surprised

Kurtz, Beth reacted to your message:

@David_Jane - I absolutely LOVE your addition! Do you mind if append your comment directly to the bottom of the post?

Great, great idea for how to really leverage AI for an otherwise tedious process of moving handwritten notes to Asana!

Of course, you can. It would truly be a great honor! :slight_smile:

1 Like

Nice workflow and Countdown post, @Bryan_TeamKickstart!

I have a similar one-click link for my clients for recurring team meetings. Some overlap, and some different techniques.

One thing I recommend to clients (or I do for them) is the one-time action to convert my one-click link from a project to a proper project template in the client’s organization. You could also do that with yours. Each org can then customize that to their organization’s preferred style/defaults/etc. and instantiate the 1:1 projects from their organization-specfic template instead of your more generic one.

Thanks,

Larry

1 Like

@lpb - great input and a pretty important oversight on my part. :slight_smile: Would you mind if I included your suggestion in my post?

1 Like

@Bryan_TeamKickstart,

Not such a big oversight, and in fact, you may not want to make it a real project template because that would mean you couldn’t offer those custom tabs/views.

So, one of three options might be of interest to different clients:

  • Just use your one-click link if they’re fine with the defaults you use,
  • Turn that one-click link project into a proper project template (but lose views, etc.; include setup tasks in the template to remember to do those each time upon project creation), or
  • Modify the project created from your one-click link once and then use that project as the “model” (not your one-click link anymore) by using Project actions > Duplicate each time to generate a new 1:1 project.

You’re certainly welcome to include any of this jibberish in your OP!

Thanks,

Larry

2 Likes

@Bryan_TeamKickstart - Quick question, when I created the project it indicate that I had to fix the “PTO Request” rule
and for some reason when I click on the Set Task Title “Do this” in the TimeBlock selected rule it crashes Asana.

Does this project have functionality that is not available to “Asana Starter” level?

Jason.

@Jason_Woods - no. It should all work on starter. You have access to custom fields and rules, which are the only two special features used for this. Starter has access to both.

But, I did some testing just now and found the same issue that you are having, which is extremely unfortunate – because it worked a few days ago when I was testing this prior to publishing.

In the meantime, you might consider just creating a new rule to auto-create a subtask for approval based on the use of the TimeBlock field. I tested that just now and that seems to be working fine.

Hi @Bryan_TeamKickstart - Just checking do in your “PTO Request” rule do you use the special Approval Task? if so that task type is not available in Starter edition which might be the cause…

Jason.

No, I made it a regular subtask, not an approval subtask.

I hope whatever the issue is can be resolved. Thanks for the heads up!

1 Like

Just what I wanted to ask too, really nifty trick!