Next Actions for Delegating
As an individual contributor, I am accustomed to identifying next actions for myself.
As a project lead, I need to 'farm out' a lot of those next actions.
Rather than identify such next actions on a project-by-project, day-by-day basis, I am thinking that it might be useful to brainstorm a complete list of recurring delegatable tasks that make up my work days (and maybe the rest of my days too).
Am thinking this may open up my mind to possibilities, identify what I really like and want to keep for myself, identify what I am willing to accept help with, and free up some cycles for myself.
What do you think? Do you have a best practice for making such a migration?
Thanks,
Rob
Are you delegating next actions or projects?
This is a challenge I face. Clarifying to the next action level produces a very clear task that can be delegated, but unless you want to micromanage your delegatees, sometimes you will be delegating projects. In this case you will need to be very specific about the outcome you expect, but leave the next action planning to the individual.
For example:
Project: Identify new software supplier
Outcome: Costed proposal for new supplier to meet requirement x
Next actions might include:
- Interview business stakeholders to identify requirements
- Create list of must have and nice to have requirements
- R&D Google search for suppliers covering this area
- Shortlist 3 appropriate suppliers
- Call Supplier 1, 2, 3 to setup demonstration
Obviously your life will be easier if some of your delegatees use GTD, but if not, some gentle nudges/coaching may help.