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

Popular posts from this blog

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 ...

Understanding and managing constraints for success

We all know and acknowledge that all situations and challenges come with their own set of constraints. All solutions to the problems have to be compliant to those constraints.  However, as leaders and managers it is important to understand the nature of constraints and juggle them well. Constraints can be mainly of three types: time, money, and knowledge. As you can see, there can be multiple combinations of these three resource constraints that act on a challenge differently.  If your situation has equal amounts of all the three constraints, you have to strategically arrive at a trade-off.  Otherwise, set clear priorities to your team as to what are the constraints and what is the levy.   Some managers are apprehensive about giving levy in any resource for the fear of abuse. However, it is important to articulate so that teams do not get demoralized by an unachievable goal.  As a leader, it is also important that you have clarity on the ratio of these thre...