Asana tip: How to give clear descriptions when delegating tasks

Reading Time: 1 minutes

Do you sometimes experience disappointing results when delegating?

Do other people delegate tasks to you with vague requirements or expectations?

Do you ever look at your to-do list and wonder what the heck you’re actually meant to do?

This is what happens when you create or delegate tasks without a clear task description.

The answer:

✅ Provide context in the description area when creating tasks.

It’s important to provide clear instructions and expectations. So, here’s an example framework that will help…

The CREDIT™ Framework

You can use my CREDIT™ Framework to help remember the 6 key elements of effective delegation:

Context:

  • What is this task about?
  • Why does it need doing?
  • What is your reasoning for creating it?
  • How does it fit into the big picture?

Resources:

  • What is needed to complete it?
  • Standard Operating Procedures?
  • Reference files, attachments or links?
  • What logins or access credentials are needed?

Examples:

  • What makes them good examples?
  • How similar should it be?
  • What needs to be different?
  • Where can more examples be found?

Deliverables:

  • What format should it be delivered in?
  • What structure should it take?
  • What location should it be saved to?

Implications:

  • Is it critical or just helpful?
  • What are the potential consequences?
  • What stands to be gained or lost?
  • How should it be prioritised?

Time:

  • How long is it likely to take?
  • What’s the deadline?
  • When can they get started on it?

Use this template

💡 TIP: If you use TextExpander or save canned messages, here’s a template you can use:

This task is about [[CLARIFY THE TITLE]]

This needs to be done because [[REASON WHY]]

The resources you’ll need for this task are: [[LIST THEM]]

The deliverables for this task are: [[LIST THEM]]

Here are some examples for reference: [[LIST THEM]]

The implications of this task are [[DESCRIBE]]

This should take approx [[TIME]].

Don’t overthink it, though. Not everything needs a big description like this. If the task is self-explanatory, don’t waste time writing a long description.

You’ll know when it counts.

If you’re creating a task for yourself:

  1. Firstly, dump whatever is top of mind in the description area
  2. Secondly, add any useful resources (such as website URLs or attachments)

Trust me, it only takes a second, but when you come back to it in the future, you’ll thank yourself!

(Or at least you won’t be kicking yourself)

📝 Note: Don’t overthink it. Sometimes, it might only be a sentence or a few words.

Give it a try!

Dave J Mason
Solutions Partner
How to give clear descriptions when delegating tasks

Like this? Want more?

Read one more tip every day…

Asana is an incredibly flexible and powerful tool. But there are many features and best practices to learn. Subscribe now to receive one new idea daily. Each email takes only about 60 seconds to read.

Daily tips & tricks emails

Simple and effective tactics, delivered daily.

  • Which contact referred them?
  • Which email in the series did they refer from
  • This field is for validation purposes and should be left unchanged.

More Asana Tips

How to easily brain dump tasks into Asana

How to easily brain dump tasks into Asana

When we’re in “Deep Work” mode, we can’t afford distractions. But quite inevitably, ideas and thoughts will pop to mind and distract us. We will have ideas, and we will remember something that needs doing. One of two things happens usually happens: We make a mental...

read more
How to set important task deadlines.

How to set important task deadlines.

There’s no stress quite like the frantic rush to hit a looming deadline. But panic-stricken working doesn’t have to be the status quo. A little extra consideration when setting due dates can go a long way to help plan your work schedule. First of all, always build in...

read more
How to plan your day based on required effort

How to plan your day based on required effort

Setting realistic expectations is critical when planning and prioritising your day's work. It's particularly important to consider the time/effort required to complete each task. At a glance, to-do lists have no clear way to distinguish effort. Without closer...

read more
How to ensure task transparency

How to ensure task transparency

Collaboration flourishes when work is visible and accessible. Nothing kills productivity and collaboration quite like teams working in silos. If your team can’t see your work: Nobody will know how busy you are.Or what you’ve been working on.It will make collaboration...

read more
Why every task needs ONE owner

Why every task needs ONE owner

Unless a task is “owned” by somebody, it’s very unlikely to get done. For that reason… Assign every task/project ONE owner. Asana calls this person the “assignee”. …but many people can work on the same task, right? So why only one owner?  Apple famously coined...

read more
How to write meaningful task titles

How to write meaningful task titles

Your task list is probably pretty big. So it helps if it’s not confusing to look at. If you want an easier life… Give your tasks a name that will make sense to other people and your future self. This will save you countless headaches and help to overcome inertia,...

read more

See how I can help.
Book a discovery call.