Wednesday, February 6, 2013
Tabs - a fad?
Tuesday, January 22, 2013
Digital Socializing
Wednesday, October 24, 2012
Relevance - Old marketing principles in today's markets
Wednesday, May 16, 2012
Leadership
Integrity, Walk the Talk, Vision, Humility, Boardroom leadership, Networking, Trust, Motivate, Listener…
Monday, July 5, 2010
Is World Really Flat?
It may be a metaphor for “level playing field”; however, that itself is questionable. I do not know, as how do people consider world as flat, because I have not come across a “level playing field”, or “playing field is being leveled”.
Once Chankya said, a question cannot be an answer to a question; however, in current scenario, it would result in more insight as compare to listing of my thoughts alone. So, let’s start with some questions, which have been haunting me on this subject;
- It is understandable that technology has bridged the distances and gaps in communication; however, has it also been able to “level” the disparities across world?
- Do we have same social, economic and technological progress across the world?
- It is understandable that there is lot of outsourcing, cross border collaboration … etc., has those been without any constraints? Are governments not protecting their local businesses / citizens? Are they not coming up with new constraints?
- Will governments across world be working for the world, or their focus will be limited to their country / region first? If yes, why do we have divide across continents, and their economic growth?
- Play field is being leveled – by adding more constraints, by making new laws to protect local interests, by working against the economic principles….. list just goes one?
- Why do we have G8, G15…. OPEC, ASEAN etc.? The world is flat, why do we need those?
- Can everything be done remotely; assuming you have the access?
- Does internet make a world flat? Do “Collaboration”, “Social Computing”, “E-Commerce” …… make world flat?
- Can we do away with “Keep up with the Joneses”?
- Does world operate on needs, or it is “wants”, which drive the world?
- Can it ever be flat?
You can have many more questions to this list, and in no way it is either complete, or lists the top ten (10) questions / arguments. It just represents my thoughts.
The point that I want to highlight is that it had never been flat, and can never be flat. It can be flat in ideal situation, just the way we have “Perfect Competition” in Economics.
The environment that we live in is full of constraints, irregularities, and preferences, resulting in decisions through emotions and / or imperfect conditions than through logical thinking, or perfect conditions. It could be as simple as we work towards fulfillment of “wants” and not through “needs”. Two or more, human beings can have same basic needs; however, their wants differ, and get influenced by the environment they live in.
I can explain each point that I have listed above in detail; however, the essence of each is, we can’ ignore the irregularities that we have in environment. Till the time we have those, which I believe can never be overcome, world can never be flat. Can it be?
Tuesday, March 23, 2010
Critical Chain - Is this the answer for project monitoring?
Critical Chain Management
Critical Path: The longest chain of dependent steps, the longest in time (determines the time it would take to finish the project).
Critical Chain: It will be composed of sections that are path dependent and sections that resource dependent.
Critical Chain has been suggested an alternate to PERT and EV as both fail to take into consideration the “Critical Path” and / or “Critical Chain”. The critical path may change as you execute the project, and EV analysis won’t give you any information on this.
Before, we get into details “What each approach can, or cannot provide”, let’s see how “Critical Chain” principle works.
1. Assumption – 1: Persuading the various resources to cut their lead time estimates.
a. What it means is that all projects and their tasks have in-built buffers / safety built-in, in given estimates.
2. Assumption – 2: Eliminating milestones / tollgates; Eliminating completion due dates for individual steps / tasks.
a. It is the end goal, the project completion which should be the driving factor. Individual milestones / tollgates should not drive the project.
3. Assumption – 3: Frequent reporting of expected completion date.
a. The project progress should be monitored and reported frequently to check the deviation(s) in time.
4. There are four kind of buffers in a “Critical Chain”, namely, “Project Buffer”, “Feeder Buffer”, “Resource Buffer”, and “Constraint Buffer”. The idea is to have buffers at critical stages, rather than having those spread across tasks in a project.
5. Measurements should induce the parts to do what is good for the system as a whole.
6. Measurements should direct managers to the point that needs attention.
7. Progress is measured according to the amount of work or investment already done, relative to the amount still to be done.
8. Measurement did not differentiate between work done on the critical path and work done on other paths.
9. It is important to have tasks to be monitored on Critical Path; however, you can’t ignore the tasks on non-critical path. Non-critical path does not mean non-critical tasks. It all means is that those tasks do not fall on the path created by “longest” time period.
10. Dependencies cause delays to accumulate and advances to be wasted.
These truly are some good points, and may be because of this quality the “Critical Chain” has been considered an alternate approach for project monitoring. However, is it truly a unique one? Does it answer all points missed out by EV? Does it address tasks differently than PERT? Is it really a complete approach?
May be, may be not. Let’s find out.
The Critical Chain suggests that resources have their “safety” built-in in their tasks against the uncertainties; probably to a large extent this is true. If that were the case, what it essentially means people knowingly or unknowingly are making use of PERT in order to arrive at estimates. They give the pessimistic (loaded with buffers) effort to stakeholders, and work with optimistic or estimated one (the most probable one). May be this is what leads to “Student’s Effect”, which “Critical Chain” mentions in its literature.
However, safety / buffer in itself is not bad, it’s the wastage of it, or complacency that it brings in, which is bad. Even the “Critical Chain” does not forbid you from taking into consideration buffers (Project / Feeder / Resource / constraint), and quite rightly so. As even “Critical Chain” can’t predict the unpredictable and can’t remove the uncertainties.
The question is, if buffer / safety in itself is not bad, why is it that PERT can’t be an effective methodology / approach? The way I see / interpret it,
• Optimistic – Tasks with no or little buffer, or stretch goals
• Pessimistic – Tasks with built-in safety
• Estimated – Most likely cases
What it means is that “Optimistic” is the one by which project needs to be executed, “Pessimistic” is the reference point, and “Estimated” is the one for you to monitor the progress against, and to be warned against deviations.
What it also means is that you keep the buffer at places, which are critical from “switch over”, “dependency”, “constraints” and “lead time” perspective. As per my information, PERT did not suggest spreading of buffers across tasks; instead those were there for you to assess the “need” for buffer. Where you want to “host” those buffers is your call.
Interestingly, what it also means is that “tollgates” are important from above given attributes perspective; however, tasks / activities within those are flexible, as long as those do not violate the “time / buffer constraint”.
It is also interesting to note that, these buffers actually map to “Feeder”, “Project”, “Constraints”, and “Resource” buffer in “Critical Chain”. And, it is to be noted that these are the first two assumptions / points covered under “Critical Chain”.
The third assumption, or point of “Critical Chain” suggest, frequent monitoring and reporting of project. This understanding has been there for ages, may be since initiation of Project Management practice. However, the key is “frequent”.
What is frequent? Is it monthly, fortnightly, weekly, daily, or hourly? I would say, the project need defines it. If you are at a critical stage of your project / tasks, say UAT, SIT completion, Production Fix, even an hourly update would be justifiable. However, when you are executing a project where there is minimal interference from external factors / environment, even a daily, or weekly reporting can be justified.
So, even in that case there had not been any disagreement between “Critical Chain” and “conventional” project management approach / practice.
Another interesting point that comes out of above points is the emphasis on schedule. In fact, it had been the only point. However, is a measurement revolving around “schedule” enough to monitor the health of a project? What about effort, cost, quality, on one hand, and customer and employee satisfaction, on another? In fact, even if I leave out the soft aspects, still monitoring from effort, cost and quality perspective can’t be ignored.
Therefore, “Measurements are indeed important and should induce the parts to do what is good for the system as a whole. Hence, measurements should direct managers to the point that needs attention”.
If EV was guilty of not providing importance to “Critical Path”, then “Critical Chain” lacks providing due impetus to “Effort”, “Cost” and “Quality”. It assumes that there would not be any variations in planned / actual effort. Everything is limited to schedule. However, there could be cases where in order to meet the schedule more resources are deployed, thereby increasing the effort and cost.
What it also suggests is that EV in itself was not limiting, it is the “usage” of it, which made it limiting. EV had a purpose of providing the information on health of a project from Effort, Schedule, Cost, and Efficiency perspective. Of course, it does not provide information on “Critical Path” and “Buffer”, because it was not designed to monitor those. Just the way “Critical Chain” is not designed to provide progress made in terms of Effort, Work, and Cost.
EV can be interpreted as the progress measured according to the amount of work or investment already done, relative to the amount still to be done. However, that is where it leaves us. The other aspects of “Critical Path”, “Dependency”, “Constraints”, “Lead Time” (taking quality as given) would still need to be considered in conjunction with results of EV analysis, to come up with holistic monitoring of a project.
Even “Critical Chain” suggests monitoring of tasks on both the paths. Therefore, keeping a focus on “Critical Path” may lead you to a potential trap. Hence, whether you make use of Critical Chain, EV or any other approach, one has to take into consideration the tasks along critical and non critical path. May be the intensity and frequency would differ.
In nutshell, “Critical Chain” makes you aware of dependency on resources, or as matter of fact dependency on everything including the tasks dependency. Though, it had been there for ages, may be not so explicitly. The reason being, as I discussed earlier, evaluation of project progress from “switch over”, “dependency”, “constraints” and “lead time” perspective is also critical (assuming quality is given).
Where Critical Chain score over other conventional approaches is through its use of those individual approaches and combine those into one. For example, Critical Chain monitors from "What would it take finish the task?", than on "How much have we accomplished".
It combines the practices of EV, Critical Path and Influence of Dependencies in order to have an approach, which, is sensitive to inefficiencies and “efficiency” required to complete the task / tollgates / project.
The fact that Critical Chain monitors the health of a task / goal from “buffer management” perspective is different from traditional approach, where the focus is on managing the task date. The intent of Critical Chain is to manage the “withdraw from” and “contribution to” buffers. How do you manage it? It is obvious that you have to define date in order to “manage” these buffers; however, it does so with the help of EV, Critical Path and Dependencies.
There is no silver bullet for project monitoring; instead it’s a careful examination of various attributes, from effort, schedule, cost, work, and quality perspective (keeping the soft aspects aside). The buffers had always been there. It had also been maintained that we should not thin out / spread our buffers, instead accumulate and place those before “critical” (four attributes given above) points.
Can we reduce the tendency for having a buffer, yes, if you remove (or reduce) the uncertainty, and / or, there is an incentive for having an “advance” delivery. Incentive would drive what otherwise is difficult to achieve, i.e. “Reduce the wastage of advance delivery”.
Suggested Steps
Saturday, November 14, 2009
Managing and Measuring Project Profitability
Is that all about a project when it comes to profitability assessment; may be not.
One may usually start from ROI (IRR, NPV, and Payback Period (including McFarlan’s analysis,)) to assess from returns perspective; however, it may not be true for s/w projects that we carryout for customers because this step would have already been done by customer. Nonetheless, it is the starting point for a project, though this accountability may not lie at our end, or we may not carry out the analysis exactly under those heads.
Having said that, a project (unless it runs to some millions of dollars, or is of strategic importance) may not require these overall measures, instead we would be interested in data in terms of “Earn Vs. Burn” (Earned Value). This is profitability from “delivery” aspect. It has been in practice for more than a decade, and has matured over a period of time. Though, there are many variations and measures for this, a quick look upon CPI, SPI, and TCPI should provide enough pointers; getting into details, where these measures point trouble (may be potential one) is the subsequent step.
You can further develop it by introducing savings and environmental dimension to it. That is, by looking at it from COQ, IP reuse, and Quality Projections perspective on one hand, and from FOREX hedging, span (spread across financial years), resource pyramid change, promotions / increments, and business continuity perspective, for long duration (multi-year) perspective. What is means, is not only you should be vigilant on profitability measures, but on factors which can impact (positively / negatively) the profitability of a project.
Can this approach be further developed, the answer is yes. We can further consider the “opportunity” cost, and measure the profitability through Economic Value Added (EVA). It may sound extreme, and may be, it is for small projects; however, would be beneficial for large long running projects. What it means is that you are going beyond financial profitability and looking at true (economic) profitability. The reason being, a company can have a positive MVA; however, could still be operating at negative EVA. But it should definitely be at next level (maturity level), and would make more sense at an “aggregate” level.
Last but not the least, you may also see profitability in terms of “incentives”, i.e. all incentive based projects have the potential to contribute towards revenue, and take away from that pie. Whether it is applicable in a given case depends on the model adopted; however, incentive based projects are a reality, especially in a service organization.
In essence, you need to figure this out (project profitability) from “Fitment / Contribution”, “Financial”, “Delivery”, “Quality / Engineering / Productivity”, “Environmental”, and “Economic” factors. That is, each role and level has an opportunity to contribute to project’s profitability, and we should consider ALL, when it comes to project’s profitability.
As I mentioned in the beginning, you need not do all, or conduct this all the time, for all factors, and / or by all the people; instead, it is the context, which should drive your choice of tool / measurement.
Monday, May 11, 2009
SaaS, S/W+Service - Is this the end of licensed s/w?
Having said that, let me develop it a little further.
SaaS (Software as a Service) was started with much fanfare, and still is the buzz word at some (if not, many) places. It might have been started as an alternative to "Licensed" software; however, it is also a fact that it has to have revenue generating mechanism to survive. Therefore, the revenue mechanism could be "pay-per-use", "bulk-slot" or something else. What it essentially means is that instead of paying for the usage of s/w upfront, you pay as you use; essentially, staggering the cost over a period of time, instead of incurring at a point in time.
Has this been able to make a significant dent in "License" software world? Is it really a cost effective an answer to "Licensed" software? Or, is it really an alternative to "Licensed" software?
Before, answering any of these questions, let's have a brief look at "Software + Service". What it means is that you are combining the goodness of both and getting that delivered over locally, and over the cloud. However, the questions applicable in case of "SaaS" are also applicable in this case. However, is it really the silver bullet?
The answer to all of these questions, actually lie in backdrop, which I have used in the beginning of this blog. That is, it depends on the market (segment) that you are servicing.
The reason being, whether it is standalone s/w, SaaS, or S/W + Service, one needs to understand the needs (read requirements) from following perspective,
1. Customizations Vs. Standardization - Business specific implementation
2. Security - Data security, and security to business secrets / competitive advantages
3. Business Continuity - Backup, and Disaster Recovery
4. Scalability - On demand usage
5. CAPEX and OPEX Vs. Budgets
6. Statutory regulations (Data Centres, Data Sharing etc.)
7. Network connectivity and latency
What it essentially means is that depending on constraints a customer would need to trade-off in order to fulfil his / her requirements. These constraints, along with choice of trade-off would decide the segment a customer belongs to.
Now, after assessing all this, can we say that one is better over the other? Not really, as each has its limitations; however, is a right fit for given market segment. For example, a SaaS may not provide me a flexibility of “customization”; however, if my requirement is standard and is also provided by the vendor, why would I not be interested in that? For example, a simple mail service provided by Google to enterprise may not have the flexibility of customizations; however, it does meet the needs of small enterprises, who need basic mail facilities. Therefore, it is the right solution for this market; the contrary may holds true for large enterprises, and hence, the custom implementation.
A software plus service may be providing a platform to have the customizations along with goodness of SaaS; however, can everyone afford it? Even if for argument’s sake, if we accept the affordability, can it also negate / neutralizes other factors, as listed above, i.e. Security, Network Connectivity, Statutory and Regulatory requirements?
Obviously, it cannot. Therefore, the impact of these available options on product companies would be a function of presence in a given market segment. They would need to optimize the offering as per given market segment.
It means that if for a product company the segment now lies in “Software + Service”, it would need to make an investment in that, and realign its resources, and operations in line with this segment. The same holds true for SaaS, and standalone S/W.
At best the emergence of alternatives (as discussed above) would need realignment of focus, resources and operations, depending upon the exposure of that organization to given segment. However, it is also true that, companies relying on bloated "(Product) Gross Margins" would need to align their business direction from "S/W Product", to "S/W Service"; hence, requiring a change in pricing model, charging model, service model, and may be a change in workforce mix and skills.
In nutshell, whether you like it or not, the erstwhile, s/w product companies need to mend their ways the way they had been doing the business. They solely can't rely on fat "product margins"; instead, they need to adept, adopt, and excel in new game via realignment of business to suit the environment. The reason being, today's behemoth is no guarantee for future existence.
Thursday, October 23, 2008
My Two Cents on Post Lehman Episode
It is interesting that it took us fall of Lehman to realize the problem in investment instruments, and prior to that we assumed everything to be hunky dory. I see this as a failure of,
1) Credit / Rating / Risks assessing agencies / departments / resources,
2) SOX and other internal audits, and
3) Governance model adopted in a capitalist economy.
Whatever the technical reason for failure of this magnitude; I as laymen see it as an absence of market for “investments instruments” held by various financial institutions. This is one part of the problem, and may be a trigger point. Now, the nations after nations are realizing that they are in similar situation as US, because all of them either had had capitalist economy, or were having heavy influence of US economy, and had very little or none controlling regulations; especially, when it comes to financial institutions, and investments.
There is no harm in having this kind of model (read governance model); however, it has very “simplistic” underlying assumption, “Everyone works under the normative principles of rationality, responsiveness, and responsibility”.
Put is simply, it means, we have assumed that an economy can work under highest order of governance; that is, where people themselves can govern the actions of theirs with highest order of moral and social responsibility. The simple it may sound (that is why I termed it as “simplistic”); however, it is very idealistic in nature.
We live in a world where everyone is loyal to themselves first, and then for others. I would say nothing wrong with it, as it is a human nature. However, if it were true, then one cannot have this kind of governance even a small group, let alone an organization or an economy. Therefore, the fault lies with the choice of wrong governance model.
I would go to an extent of holding the rating / risk assessing agencies and auditing agencies equally responsible for this debacle. The reason being, their existence is to govern the actions of assessed organizations, and if they cannot do that task diligently, they cannot justify their value to the system, and hence their existence.
This failure depicts the failure of the system, and not that of single organization. The failure of a given organization has only exposed the inadequacy of the system (to put it very mildly).
How it has happened is not important; because, it is very obvious that everyone wanted to make a kill when the going was easy. Though, they had disguised it under the phrase of “creating shareholder value”; however, fact is it was pure personal greed. Therefore, the important thing is “WHY”; that is what I have tried to cover so far.
Now, let us turn the focus on aftermath. It is visible to everyone, there is a liquidity crunch, stocks are going down, people are apprehensive of new investments, production across industries are going down….. a perfect case for recession.
I can understand the liquidity crunch, as most of the “money” is buried under those bad financial instruments, which were created to make money. However, I personally believe the swings in stock / equity market are more emotional than rational. The reason being, the “decisions” of individual investors are more based on actions on the “news” at any given point in time, than any rational assessment.
The governments across has world have realized the gravity of the situation, and have also put in place the initial corrective measures. Initial, because, those are based on “initial” assessment of the situation, and during the course may require some moderation. The reason being, as economies progress more information would get revealed, which may initiate some more actions, or moderations to earlier implemented actions.
Though it is obvious to have a fear of unknown under these kinds of situations; however, one should also make an effort to look at things rationally. The things have gone wrong, a fact no one can deny; however, it is also a fact that nations have realized this fact, and are making an effort to correct it. Obviously, it cannot be put right overnight, but then it did not happen overnight either. Therefore, I believe if all think rationally, and if corrective measures are indeed to correct the ill effects (which I sincerely believe in), and are effective to address the root cause, then we can avoid to be the victims of our wrong actions (by encouraging recession due to negative thinking).
Of course, it is my personal assessment, and with my limited knowledge and access to information, could either be lopsided or wrong. However, one thing I’m sure about is that answer lies in “why”, and not in “how”. That is, address the “why” and put a brake on rumor mills.
Saturday, September 20, 2008
Time Management - A Mystery?
The reason for this understanding is very simple, URGENCY is linked with time. That is, either we have the paucity of time, or the time to complete the URGENT task is in immediate future. What it means that either you had not planned for it, or because of short sightedness / environmental factors, we have to expedite the urgent task. In either case, this can only be done by dedicating resources to address the urgent task.
We may decide to either re-allocate the resources from current allocations, or we may dedicate spare resources (if any). The fact of the matter is, in order to complete the urgent task we need to either disturb the current allolcation or allocate additional resources. This way either we adversely impact the tasks from where the resources has been taken, or we increase the cost of allocation.
This happens because all of us operate under given constraints, and performance is optimized (at least tried to) within given constraints. Therefore, any increased demand on resources would need either a shift in the constraint boundary, or re-allocation witihn pre-defined constraints.
Big deal; re-allocation solves the problem, so what is the hitch? Well, re-allocation solves your urgent problem; however, has the potential to make other task(s) (from where the resources have been drawn) urgent. Thereby trapping us in a vicious cycle of attending to urgent tasks.
So, is there any way out? Yes, and No. Well, what I meant was that Yes, we can address those as long as those are exceptions, and No, if those become norm.
Therefore, the key is,
1) Keep your urgent tasks to minimum, if could not be donw away with completely
2) The re-allocation of resources should be judicious, and should be as per your set priorities
3) Since not everything can be controlled, therefore, communicate the impact arising out of urgency; it will help in answering the re-prioritization and adverse impact
4) Understand that no one can do all the tasks on their own, therefore, direct, guide, support, and delegate. How effective that would be, would depend on your understanding of "readiness"
5) Optimize resource allocation - as per importance / significance
6) Monitor the progress, and control the variations
7) Refine your prediction and allocation of resources by keeping in mind your "effective capacity", and not through theoretical or available capacity, and feeding back the data back into system
Now, let me develop it a little further from s/w project perspective. Many of us have an understanding that identification, definition, allocation, sequencing, execution and control of activities, is time management. In a way, it is true because this is what exactly what we saw so far in this article. However, sometimes this understanding is limited to schedule of a project alone. Still fine, as long as we understand that limited scope from a project perspective, and we operate in a wider scope.
In nutshell, it would be a mystery, as along as we spend significant amount of our time on urgent tasks rather than on important tasks.
Wednesday, September 10, 2008
Time - Is it the deciding factor in marketing?
1) Instant noodles - Easy to cook and Ready to eat
2) Ready made curries - Heat it and Eat it
3) Pain killers - Relief from pain within Minutes (or whatever the duration is)
4) Car servicing - Reliable, Same Day service with free Pick-up and drop off
5) Customer Service - Guarenteed within 30 seconds attendance of call
6) S/W Implementation - Quality, with reduced Cost and Cycle-time
7) Courier Service - Guarenteed same day delivery
.... and the list goes on.
You must have noticed, the above points have some words in bold. That is done to highlight one thing, be it product or service, the time as a differentiator makes sense when combined with the main satisfying need / requirement.
In some cases it was convenience, in some it was quality, and yet in others it was the reliability, and so forth. The time was a differentiator, because it was able to satisfy the underlying main need / requirement.
On it's own it can't survive; however, mix it with a underlying need, and you have a potent weapon in your armour. Therefore, first address the underlying need and then stress upon time factor. Can segment have any influence on time, think about it?
Sunday, June 22, 2008
(Un)Importance of Current Team Size Having as a Benchmark
More often than not any senior management role would have the following phrase as one of the desired skills;
".....should have been handling a team size of .....".
Interesting, isn't it?
I find it interesting from two perspectives, first, they want a person who would have handled a team size of given number and not managed. Second, it is given / assumed that a person who so far not has managed given number is not capable of managing that number.
I personally believe, on both counts the organizations are wrong. The reason being, if an organization fails to differentiate between handle and manage, the probability of it having an effective and satisfactory management is unfavorable. What essentially one needs is a person who can manage the people, because, only if a person is managing only then he / she,
1) would have empathy towards people,
2) would make an effort to understand their aspirations,
3) would be able to understand their competency level and allocate work,
4) would be able to understand their preparedness and mould his working style as per their preparation level,
5) would be able to communicate the importance of task / work to people.....
I mentioned it interesting, because, organizations know the difference and still use those interchangeably. Can it be a reflection of their thought process; may be.
Let's take the second part, the organization assess people as per their current capability. Nothing wrong with it, especially in lateral hires. The fault is not in thinking; as the current capability would provide some information on person's compatibility against listed requirements. Instead, the fault lies in execution.
A role may require a person to manage a team size of 10, 100, 1000 or more people; however, at any given point in time a person cannot directly manage more than 5-7 people effectively. That is, a person would have an operational structure to carry out his / her responsibility, wherein, KRA/KPA of entire population are inter linked, and work towards a common goal. If that were true, whether a perosn has managed 10, 100, 1000 or more people in past is of little relevance, as long as he / she satisfy following constraints;
1) He / She has effectively managed people in past,
2) He / She understands the importance of operational structure,
3) He / she can break down the common goal as per each operational level's work,
4) He / she understands the meaning of governance,
5) He / she has the willingness to work with more and more people,
6) Has he / she been managing, or understand the requirement of managing teams across geographies, and domains,
7) Appreciate the requirement from different social and work cultures, time zones, and languages perspective,
8) Appreciate the difference in managing vendor vs in house teams, and
9) Appreciate the different management requirements for outsource vs in house work.
Though all nine points are important for successful team leading; however, the importance of point #2 and #3 is worth mentioning.
The point #2 suggests that one should understand that one cannot do all the tasks, and not everyone can fit in any given task. That is, importance of skill, capability, work break down, and delegation. If a person knows the importance of these attributes, I believe it would be hard for him / her to miss on goal, unless the person is determined to do so :--))
The point #3 suggests that if one has understood governance as a set of processes, tools, structure, and practices to obtain targeted goals, then he / she has the capability to manage any number of people. I will not provide details on "What is Governance?", as the same has already been covered by me under same topic separately. Instead, I would like to stress on the fact that managing people is part of governance; problem starts when we take governance as a separate process / exercise.
Now, let me end this topic by asking some counter questions on this practice;
1) What is the guarantee that person's handling of people had been effective at current work?
2) Given that a person is capable, had been effective in current work, and has managed more people than required number of people; what is the guarantee that he / she would succeed at new place too?
The reason being, it is very rare that work culture of two organizations being same. It could be somewhat similar; however, there is a lot of difference in being same and similar. So, instead of harping on current team size, try to understand the person's understanding from mentioned points perspective.
Thursday, June 5, 2008
Is Customer Satisfaction a First Step in Customer Relationship Management?
In order to define and work towards creating greater “satisfaction”, we need to first understand “Who is the customer”, and “What influences satisfaction”.
It should not be very hard, as all of us, at some point in time, do act as customers. So, what are things that are satisfying, annoying, or indifferent should provide you enough clues to answer the above question, i.e. what influences satisfaction.
I personally segregate these influencers in two categories, “Internal”, and “External”. The internal sets of influencers are the tasks / processes under our control, and can provide the performance on count of “customer satisfaction”. The external set, as the name suggests, is in control of customer, and we get to see level of satisfaction by analyzing their feedback.
Therefore, a satisfaction to me can be gauged through;
Internal Indicators
a) The quality and process / project metrics
b) The management / SQA review points
c) Internal audit findings
d) The review records
e) The internal cost / financial metrics
f) Internal employee satisfaction survey
g) Number of escalations and severity
External Indicators
Though one can have subjective as well as objective questionnaire to capture the response of the customer, however, a mix of both would be the right choice, as it would provide customer an opportunity to "rank" as well as means to convey his / her feelings / observation, which would require further analysis on vendor's part. I believe following aspects should provide a suitable base for capturing the satisfaction level;
a) Product / Service Quality – Overall / Phase wise
b) Schedule Adherence (variance / span)
c) Cost Vs. Value Proposition
d) Responsiveness / Empathy
e) Accuracy of provided solution / responses
f) Resources ability / capability
g) If you were to re-execute the project, then what were the things that you would like to do differently, and how? OR
h) What are the points / factors / actions that you think could have provided much more value add to this initiative?
i) What are our two most positive and negative points, and how we could have addressed those (negative points)?
j) If some referral calls you up, what be your spontaneous feedback on us?
k) Where and how do we need to improve upon?
l) Would you like to do a repeat business with us?
These are obvious influencers, and interestingly most of those are within control of ours (as vendors). However, still customer satisfaction had been proving bane for many. Why is it so?
I personally felt that it is because of our attitude towards customers. That is, though we want them to consider us as their business partners; however, fail to reciprocate the same understanding for them. At that time we give importance to “profit margins”, and “appraisals” over “relationship” that we want to create and manage.
This dichotomy is the bane of all customer dissatisfaction, and to some extent customer relationship related problems.
Now, again have a look at the list of external indicators, you would appreciate that except for point #c, i.e. perception on cost Vs value, all others can easily be monitored and corrected internally. Interestingly, that would again be in our interests to do so; not because, it is required to improve the customer relations (though ultimately it would), but more so for our internal performance. Let’s see, how?
It is evident that if I take care of internal factors, either I improve upon cycle time, reduce costs, or increase productivity. In either case it benefits me first and then the customer. The reason being, whether I reduce the COQ, improve the performance against “First Time Right”, improve the productivity, match the schedule and effort commitments, save on escalations and resources spent on addressing those; it is me (as a vendor), who gets the benefit, and the customer satisfaction is add-on benefit. The best part, I do not have to do anything extra or specifically for the customer to increase the customer satisfaction level.
Therefore, I would go to an extent stating that first look at the internal indicators and perform on those indicators, the chances are you would have already satisfied your customer. The external indicators are more so to build a relationship, wherein, you want to contribute to the success of the customer through wider business association, and through better understanding of their other needs.
I personally believe “Customer Satisfaction” is the first step for building a customer relationship. The reason being, it would be fool-hardy to think of building a relationship with annoyed customer. How many times you have done so (building a relationship with vendors providing unsatisfactory service)?
Yes, customer relationship management is more than just customer satisfaction. It may involve, customer feedback, profiling, empathy, marketing, issue / request management, personalized service development, promotions, communication, access to information, visibility to progress made etc.; however, all of that comes after customer satisfaction. These extra parameters help you in uncovering hidden needs / reasons, to either broaden your business association or better align your services with customer needs. But, at the end of the day, those are refinements for a satisfied customer.
For example, by gathering information on additional parameters and acting in accordance with the outcome may help you broadening your business association from a single service to multiple services; however, it cannot be a substitute for getting the basics right, i.e. perform on internal indicators.
A relationship is built through demonstrable actions, and trust; which one cannot build on a foundation of unsatisfied experience.
Note: I have written this article in context of s/w industry alone.
