Skip to main content

Assigning clear ownership of tasks

We understand that many tasks in today's world require great collaboration.  A complex system will have many components, integrations, and sub-systems managed by many members of a team.   However, that does not mean everyone knows everything or everyone can "get it done" when it comes to a specific item.  

As a manager, when assigning tasks, or, as is more common, asking for things to be done, it is essential to establish ownership.  I am sure you have seen emails exchanged with many people in the To field and with single line delegations like, "Can we fix this?" "Can we make sure this does not happen again? "Can we find the root cause?" etc,.  The issue with such shared allocation of responsibility is the bystander effect.  No one seems to know who is taking up the task or at least some part of it.  

Furthermore, it gets worse when managers randomly start asking questions to one team member about why "we did not do that" referring to such a "can we do..." email.  There is too much scope left open for assumptions.

For efficiency reasons, it is better to establish a clear owner when you are requesting something to be done.  More importantly, make sure you follow up only with that owner about its progress.  That owner in turn may choose to delegate as necessary, but the chain needs to be established. This may sound too "process-oriented" or "pedantic" but it saves lot of time and gets results. 

For psychological reasons, it is better to establish ownership because that entails proper accountability as well.  In a "can we.." delegation, due to the shared nature of ownership, there is a shared nature of accountability as well, which means no accountability at all.  However, when the manager requests status, it may very well be pointed to one person.  It won't be uplifting if that one person was under the assumption that someone else was going to do it.  

In a nutshell, when you are asking something to be done, also make it clear who you are assigning it to and then let everyone else know that they should collaborate with that "owner".  All of this can still happen in the email conversation with 100 people in the chain.  But make sure there is only one person in the To field and 99 in the CC field.

Comments

Post a Comment

Popular posts from this blog

Along with productivity and efficiency, encourage improving competence

 It may appear that improving efficiency automatically improves competence. But that may not be the case.  Either for an individual, team, or a system.  While the other way is true; that is,. improving competence improves efficiency.  Let us say there is a task that a team member takes one day to complete. Let us say you can buy a tool that can do it in one hour.  The net result is increased efficiency of both that team and that member in terms of overall productivity.  However, did that increase that team member's competence? That depends on what that team member does with the gained time.   I encourage leadership to focus on competence and treat it as capital reinvestment.  With new technologies emerging every day to solve various problems, it is important to invest in training and continuous learning.   More importantly, it is important to have competence in your metrics for success. Otherwise, it is easy to miss that contributin...
Post a Comment
Read more

If you join a recurring meeting occasionally, do not praise or blame in that meeting.

If you are joining a recurring meeting occasionally, then refrain from praise or criticism during those meetings.  The simple reason for this is to avoid inconsistencies.   Let us imagine a situation where you are in a meeting and one of the team leads mentions how their team performed beyond expectations the previous week.  As a leader, you may be praising them.  But if that praise is anything more than just part of the flow of conversation, you ought to be cautious.  What if another team did something great during one of the previous meetings that you were not present and hence you did not get your praise or attention.  It will be perceived as being unfair.   Even if the team members can logically accept the chain of events, morally it may be demotivating.   Try to make it a part of your job to regularly collect positive feedback from your team leads and appreciate the team members. Doing this consistently and genuinely will help ...
Post a Comment
Read more

Say no until you can say yes - know when that is

All organizations need to stretch beyond their core competencies to be able to stay competitive, relevant, and innovative.  However, it is important to plan this strategically.  Either pace it out or budget it out. Do not aggressively promote a service or product that you do not know you can deliver with good quality at a profitable rate.   Keep in close contact with the sales and marketing teams as they come in contact with changing demands and needs of clients faster than other teams.  Record all predictions and compare variances between previous predictions. Use indicators that prove to be more successful. Once you have set intention to go in a direction, get team members on board and share your vision. Encourage them to prepare. Guide them with resources required. Motivate them to learn. It is better to say no to something than to deliver mediocre quality products or services; worst case is to not deliver acceptable product at all.  Saying no may only c...
Post a Comment
Read more