Without a deep clarity on High/Low performance scenario, we may find every issue as alarming -like recruitment, attrition, people assets, HR, training, selling and even funds.
Too many issues are anyway there in IT service business but sorting them one by one by adding new talents and new departments/HOD could be suicidal, unless we realize what a HIGH PERFORMING scenario/environment is. Leadership, challenge mitigation etc comes only after we realize what makes a difference.
Let us take a general life experience scenario for case study - restaurant experience:
In a restaurant, 4 people are sitting for ordering food. They wait and wait for 5 minutes (restaurant of 30 seats, in lean hours). Waiter comes in and while chatting with another peer waiter seeks orders from this group waiting. Then when asked for water, he seeks what main order is. He appears to be in hurry and impatient.
Then after some insistence, water boy brings water in 4 glasses in one hand ( with one finger in each glass to hold the glass properly), and brings food also together. Patience is running out and one friend tells other to have patience as food is anyway good.
It is part of an example scenario and I am sure we can see what is avoidable behaviour which gives the restaurant a bad name or a low performing image. Waiting time is too high even in lean hours. Waiter does not treat just arrived customer with due courtesy and promptness. The delivery person brings water glasses with one finger in each glass (very much justified from water boy perspective, but creates an aversion to the customer).
Go to another good restaurant, serving equally good tasty food. Say, Saravana Hotel restaurant- well known south Indian restaurant or Udupi restaurant in Mumbai. Water will reach you in maximum 30 secs. In clean glass. You will never be allowed to empty them as at frequent intervals, someone fills it up or changes the water glass fresh with fresh filling. (process design and compliance)
Food ordered comes in few minutes time. Even when it takes longer time, the initial speed of response and cleanliness feel makes you comfortable with that extra wait. (merit of process, transparency and repeatability). Now we know what is low performing and high performing scenario. Food quality and taste being same, any new customer will prefer the later example by way of choice.
Now apply this episode to your IT co. Check out how long phone caller is forced to wait when phoned up. (High performing cos. have limits on no of rings, within which certainly someone will respond). Despite prior appointment fixed, customers (contract awarding or future recruits) are asked to wait unduly at reception, with promises that someone will attend soon.
Initial touch points of an IT organization shows how well it is ready to respond, time wise as well as transaction wise. Similar examples can be seen in RFP handling, customer follow up, negotiations.....which often leads to loss of business, while we often conclude falsely as loss due to prices, delivery time, technical capability or lack of high level contacts or CEO who did not take the lead seriously enough or competition knew some one closely in buying organization.
High performing IT service organizations will have proper lead collection templates, close review every day/week, re-shuffle low hanging fruits and high hanging fruits and target what must be closed this week/month. Simple excel sheet based templates are good enough to start with. Daily tracking (through documentary evidence) is essential by each sales person as well as Business Head. Weekly, same must be tossed with CEO- Head of the organization. Review every week for finding roadblocks, activate intelligence gathering, get them checked up and decide on counter- strategy to WIN.
High performing organization will always find ways to WIN and make life difficult for the competition or the buyer itself. Even if it a losing scenario it should be on 'my terms and game plan'. Thats is the spirit of a High performing selling orgn.Customer should feel discomfort and apologetic while awarding a WIN to your competitor, that helps BINDING for next opportunity.
Appreciating reasons, and roadblocks posed by buyer or competition is low performance, as that is planning for failure. (Vivek Paul, ex-Wipro mentioned recently that Indian cos do planning generally for failure and not SUCCESS)
IT service business is pure IDEA and DIFFERENTIAL business. None can forget that if we are holding responsibility and ownership towards our role. Satisfying internal hierarchy and bosses is less important, as in a crowded co, seniors may not have sufficient time to grasp/analyze and come with killer strategy. The sales owner (identify them)must own up issues, fight for internal awakening and fight externally with means and ways which can tilt the customer towards your cause. That attitude is itself High Performance factor.
This story gives enough idea of High Performance of individuals, teams and organization. Obviously growth depends on each one of them. CxOs have a duty to build that system, process, attitude and hunger in his set up. First get an idea of what is HIGH Performance in your business segment/subject domain. Then every issues becomes simple.
Key objective is to get contracts every week/month, with quarterly growth in top and bottomline, addition of new clients, retention of old clients, reduction in man-hours spent on same/similar kind of deliverables etc. Repeatability and sustenance is HIGH Performance. What is your Take???? We need to know and learn from each one of you ......