Friday, April 22, 2016

Time is of the essense

If you are in service industry then there's no other option for you but to respond on time. I know I would not sound wise when I say that. But such small and petty things are tossed big time in some organizations. It is really difficult for me to fathom 'why people do that?'

If you are not equipped with information as to what needs to be responded to client or any other stakeholder then I can probably understand. However, when you have everything that is required to notify the other person and yet you don't do that then it raises a question on your ability to work in professional setup and sensitivity towards other people who are waiting for your response.

I remember one such incidence when one of the department was expected to respond to some client query. The function got this update on day 0. The news got circulated to concerned people internally on day 1. The required information and the solution was provided back to the team with all other required explanation on same day i.e. day 1. Nothing happened on day 2. The person who should have sent the information on day 1 offloaded the responsibility of response to somebody else on day 3. And I really don't know when client actually received the information.

Such things would pose a great difficult for the growth of the organization. And organization that will work on such small and little human things will succeed for sure.

Tuesday, April 12, 2016

Agile team at work

Few things we see and experience on a daily basis and that make us blind or ignorant about them. We start taking them for granted. We never think about gravity every time. We just know that whatever goes up is bound to come down. We slowly forget cause and remember only effect. 

I had some work with another team working in my office. As part of my job I interact with different teams and people on a daily basis. So today I approached a person from this team for work. He was occupied with some client work and it was not possible for him to help me with my task. He then asked his teammate a favor. A 'favor' because his teammate was not bound to help him on this request. His teammate nodded and my task was passed on to him. Such a simple thing. But wait. 

Things that appear simple have complex systems working behind them silently. I am sure this kind of experience is not new for many of us. But we have become ignorant about the great spirit that goes in to building these agile and connected. Let’s dissect. 

  • The team members had respect for each other. And hence respect for each other’s commitment. 
  • There was no reason for a guy to take shoulder some other guy’s responsibility. Could be an investment for return favor but I can pass that as a positive sign. 
  • The guy who offered help was not proficient at task I was asking for but he agreed to jump in. He demonstrated risk taking ability. 
  • The first guy had courage to give the task to another guy when he knew that other guy is not as good as him at it. And even if another guy was doing the job his name would be tagged with the deliverable. This shows faith in ability of fellow team members. 
  • One guy takes job and understands the concept and another guy works on it calls for same vocabulary. Unless they interpret things in right way they can’t deliver the output. 

So many things are at play here. So next time you see any cohesive team give it a thought. Unless you understand what makes a great team you can’t build yours.