Category: Management

Sweeping Generalizations

Right before lunch, one of my colleagues pointed out that Michael Zuckerberg, the CEO and founder of FaceBook (or the biggest rival of Bill Gates when it comes to stealing ideas!) is just 23 years old and Harvard University dropout. Right then another guy stated – “All university dropouts become rich!” Thats what sweeping generalization is all about.  I heard it for the first time when I read Edward DeBono’s , “How to have a Beautiful Mind“. These are statements in which there seems to be sufficient evidence offered to draw a conclusion, but the conclusion drawn far exceeds what the evidence supports. While it true that many rich and famous people are university dropouts but it never implies that all university dropouts make it big. Take another example, if you have worked with 2 outsourcing companies and got your fingers burnt , does it conclude that all software companies in India are bad? There is a lot of evidence that most terrorists are from Islamic nations, does it mean that all Islamic nations are terrorists? The conclusion drawn is just too exaggerating based on the evidence used. We come across these statement everyday in our lives and as managers its very important for us to understand its implications. Sweeping Generalizations are far too common and they disable open-minded thinking which is important for decision making.

Read More »

Microsoft Vs. Opensource

Which do you prefer most – Microsoft or Opensource?  As educated, rational and data-driven people, we take pride in our ability to think logically or atleast believe that our decisions are based on sound judgment. I am currently reading Malcolm Gladwell’s , Blink , which talks about the Warren Harding error. This error refers to America’s 29th president, a man so distinguished-looking that once, at a banquet, a supporter cried out, “Why, the SOB looks like a senator!” Though he radiated presidential charm, Harding was actually best at playing poker and golf, drinking and chasing women. Gladwell calls him one of the worst presidents in American history. This book is basically about snap judgments or rapid congnitions which the author refers to as “Thin Slicing” . He argues that our mind has a pattern seeking behavior, which allows our brain to get past any irrelevant stuff and “zero in” on the the stuff that really matters. This behavior has a dark side as it allows us to fall for a person’s mannerisms, appearances and this is when our rational brain succumbs to visual traps. Ram charan in his book, Know How also pointed out the potential problem of this “thin slicing”. He stated that leaders often try to look for pattern in things where none exists and this leads to erroneous judgement. This often to leads people to compare China of today to Japan of 80s or predict the success of a business or point at somebody and say – “he is going to make it big someday” In order to expose our unconscious biases towards things, psychologists at Harvard University came up with IAT. This is an acronym that stands for Implicit Association Test. IAT helps us examine two things, First, we might not always be willing to share our private attitudes with others. Second, we may not be aware of some of our own attitudes. Your results on the IAT may include both components of control and awareness. Here is what IAT has to say about this: Psychologists understand that people may not say what’s on their minds either because they are unwilling or because they are unable to do so. For example, if asked “How much do you smoke?” a smoker who smokes 4 packs a day may purposely report smoking only 2 packs a day because they are embarrassed to admit the correct number. Or, the smoker may simply not answer the question, regarding it as a private matter. (These are examples of being unwilling to report a known answer.) But it is also possible that a smoker who smokes 4 packs a day may report smoking only 2 packs because they honestly believe they only smoke about 2 packs a day. (Unknowingly giving an incorrect answer is sometimes called self-deception; this illustrates being unable to give the desired answer) So, what has IAT got to do with Microsoft vs. Opensource? The answer is – do you know if you actually have a bias towards either Microsoft or opensource? Well the take a test on Harvard website to find this out. The results may surprise you. Microsoft vs. Opensource is the current featured test on https://implicit.harvard.edu/implicit/

Read More »

There is no such thing as Microsoft vs. Apple

We often run into heated arguments within our office – some say Microsoft rules , other say Apple is the future. I try to refrain from the temptation. But, here is what I actually think: The first chapter in economics that I read, told me that Businesses makes good and services which is consumed by families, for which they have to pay businesses some money. On the other hand, families supply the resources (capital, labor) which is used businesses in return for which it has to pay interest and wages. This symbiotic relationship has existed from centuries. An extension of this logic suggests that Microsoft as an organization wants to be a company which decides how business makes money , whereas Apple wants to be a company that decides how people spend it. Thats the end of the story – The sooner we get it the better! iPod has given the greatest branding to Apple which is a consumer product whereas Windows & MsOffice (Arguably!) made MS into what it is today. I dont think Apple ever said they wanted to improve productivity or Microsoft ever said that they want to make fashionable gizmos for teens. The problem is that with excess cash and surplus managers, both of these companies sometime venture into each other domain which causes all the confusions.

Read More »

Debating the Organization Structure

The evening of 19th April was different at our HQ in Kolkata. There was a gathering some senior executives in the CEOs office where I ran a presentation on the proposal of restructuring the organization. The gathering also included some tehnical leads from our organization. The main idea was to get as many different views as possible. Here is a brief of that: The current organization structure In our current structure all authority and responsibilities lies with the functional heads; the structure is created by having separate departments such as Design, PHP, SEO.  This structure is not “pure devil” and it does have benefits like: It is simple and easy to understand Coordination across groups is left to the functional heads The organization overhead is low The career progression is clear Birds of a feather are flocking together Disadvantages of this structure? Coordination across departments on project that requires multiple type of specialization is poor CYA is easy, as the blame can be put on other departments. Separation of management and technical discipline is not there. No body is having the full-time job of managing projects and thinking about customer. Organizing by project teams  This will mean creating a structure that comprises of independent, self-sufficient project teams that exist autonomously within organization. This team will be assembled for a specific project under a project manager. The team will be temporary in nature and its member will be reallocated when the project is complete.  The project will be organized primarily around the project manager, and then a project team is formed. The project manager exercises direct and autonomous control over the various discipline groups and is responsible for the coordination and monitoring of the effort of the team. Benefits of this: Flexibility in allocation of resources Responsibility for project delivery lies with one person who is clearly identified Senior management is free from managing the project as there is now a full time project manager taking care of this. Thus, senior management can focus on Strategy etc. Disadvantages of this structure  Growth of individual technical skills for a team is not possible or very difficult The administrative overhead is very high in managing the resources when they are not allocated to a project Leverages exclusively on the project manager for delivery The managers may get overloaded with excess inflow of projects. The Alternative? Best of both worlds i.e. Matrix Structure In this structure the staff and resources that are required by the project manager are not permanently assigned to the project, but are obtained from a pool controlled and monitored by a functional head. People that are required to perform specific functions in a particular project are allocated as necessary and after their job is done they will be returned to the control of functional head for reassignment.  The members of the project team and their functional supervisors will have the responsibility for timely completion of allocated task within acceptable quality limits and they will report to both project manager and the functional heads.  Advantages of the creating a matrix organization  It has the benefits of both structures i.e. (current functional organization and project team structure). Allows for just-in-time allocation of resources based on problem at hand. The project personnel can retain belongingness with their functional team and still be accountable for projects as well. Allows independent growth in technology and management skills The customer relations can be better with having SPOC throughout project lifecycle Projects can be controlled better Profit margins on the project can be higher as resources having the right skills are allocated for the job instead of just having one person to do the entire thing which may require learning or rework Allows projects to be technically brilliant along with being well managed Disadvantages of the matrix organization There is a potential for conflict between functional vs. project groups. The administrative overhead is higher Increase in managerial overhead A person may be shifted across projects very frequently which may lead to insecurity. So, what’s the conclusion? Well, to be honest after hours of debate, we are yet to reach one! I will keep everybody posted on what is finally decided.

Read More »

The problems with Pricing

Any of us who have ever placed a formal bid for a project must have come across absurd prices from competitors that defy common sense. After observing this for a while, it is typical that the organization leaves its own pricing principles and attempt to cut-down or increase its prices. So how should organizations price themselves? Economics tells us that prices are determined by the dynamic equilibrium of Demand and Supply so that at the equilibrium price the demand and the supply are equal to each other.  In simple English it means, if all you are not pricing high then all your employees should be working on paying projects and it you are pricing too high then you will not have paying projects. On the other hand, if you are unable to keep with the number of projects and the HR department has to work overtime then may be its time to increase your prices. But, the big fat books on Marketing tell us that pricing should be done based on the perceived value of goods or service and not on its actual value. Thus, even if it costs $250 to make an iPod, it can be sold at $600 and this is how business consultants can demand for such insane prices and we pay them gladly! The sad truth is that most of the time organizations don’t know how to price themselves. Too often prices are determined by the internal cost structures on the company or prevalent market prices rather than “value” or “demand-supply”. The most common logic is – “we will 4 months on the project and with 2 persons working on, it will cost us X amount of dollars so let’s quote 1.5X for the project” or, “every body is selling it at $400 – $500, lets price it within this range only” For an average organization that is locked in a bidding scenario, it the option to either under-price or over-price. Under-pricing is used either as an “account penetration” or “staying in business” strategy. Many times, companies under-price because they just don’t know what to quote. An organization whose sales people are busy placing 50 odd bids on places like Elance etc , really don’t have the time (or may be even the knowledge) to correctly evaluate each project. This is also true for organizations that has under-staffed its sales department. They bid low in order to get the job and within few weeks (or even days) or execution, they realize that the job cannot be completed within the price and they will have to accept losses on the project. In this case the organization simply decides to accept the loss and learn the lesson or it decides to throw in the towel. In former case, this still means that corners are cut, scope is reduced, quality is ignored and the customer suffers. This is because an under-bidding organization is more focused in minimizing its losses than satisfying its customers. Over-Pricing is the other side of the same coin. If a project is over-priced then there are only two possible outcomes i.e. either the organization will win the business or it will not win the business. If it is not winning the business then it will either adjust its prices or it will go out of business. However, winning an overpriced project poses its own set of problems.  How will the organization allocate budget for an overpriced project? If it expects Y% profit then allocation of (100-Y)% as the project’s budget will lead to excessive project budget which will give an false impression regarding the project’s team performance. On the other hand, if it decides to allocate the normal budget as project’s budget (given it knows what the normal budget is!) then it will lead to abnormal or excessive profits which will sooner or later drive more competition into business and create a pricing pressure. Thus, in order to sustain the business and maintain the “elegance”, a lot more thought needs to be given on pricing. It is very important to first determine and then monitor the parameters based on which you are deciding how to price yourself better. Please note that “Better” does not means “Higher”!

Read More »

Its a Problem not a Risk

Risk Management is a fundamental discipline for any planning process. Risk is defined as a possibility of a loss and has a probability associated against it. As a manager, it is important to continuously monitor risks and take actions to mitigate them. Dr. Robert Charette said that risk management is not about future decisions but, future of present decisions. The process to identify risks starts the beginning of the planning process itself. All the participants brainstorm to find out all the possible risks that may affect their plans. Then a monetary value is put against the risk which represents the amount of loss that will incur if the event actually occurs and finally, a percentage value is put against the risk item that represents the probability of the risk actually occurring. The impact of the risk is calculated as a product of probability and loss amount. This gives managers a way to prioritize risks and manage them effectively. For risks that can adversely impact our plans, it is also important to write up a contingency plan i.e. what will we do if this risk occurs. Decision making under a scenario of chaos is normally not as effective. I think the biggest benefit of risk planning is that it helps us in executing a pre-planned action at the time of chaos. This is because the action has been planned thoughtfully before the risk has actually occurred and hence the element of urgency does not cloud the judgment. For example, a data centre might consider fire as a risk to its facility and servers. Now, unless a plan has been drawn up earlier that tell the superintendent on duty about what to do in case of a fire, it will be difficult to take the “right action” or take “all the actions” that might be required to protect the facility and data in case there is fire. Too often within the planning process, people write down known issues as risks. Known issues are problems and not risks. For example, if you know that your organization does not have the skills to deliver the project then it’s a problem – not risk! You have to deal with it right away. A problem is a risk that has already been realized. They have a 100% probability.  The only reason someone wants to put a known problem as a risk is because they don’t want to deal with it right away. It’s same as saying – “OK! I know we cannot deliver this project but let’s put this down as a risk as we will deal with it later. Let’s focus on getting the SOW signed now”. This is wrong! Problems must be dealt with as soon as the identified and Risks can only be dealt with once they are occurred. In a nutshell, Risks always deal with future events and not present while whatever is known right now is a problem and not a risk. Thus as a customer, if  you ever come across a risk management plan where problems are listed as risks then you should be aware and ask your vendor to address them right away i.e. before the plan is approved.

Read More »

Why build open-source software?

What incentive does a commercial organization have to build an open-source software? Why will a programmer spend time and effort in contributing to any open-source product? These are some questions that we tend to avoid. We are an open-source web development company. Each day of our company is spent working with PHP/MySQL/Apache and Linux. These are all very powerful open-source products. We generate revenue by creating application based on these platform or co-opting them in commercial projects or by customizing an open-source product to individual business needs. But, what is the economic benefit for the programmers who created these applications or extend them continuously? I recently came across an article from Harvard Business School – Working Knowledge that answered some on these questions. Benefit to a ProgrammerA programmer will volunteer for a project only when they see a “net benefit” in doing so. “Net benefit” consists both of monetary benefits (immediate benefits) and non-monetary benefits (or delayed benefits). Monetary benefits are easy to visualize if the programmer is working on a commercial project. It will normally include things like Salary and Bonuses. Non-monetary benefits the author says, consists of improved chances of receiving future job offers, shares in commercial open-source, access to venture capital and ego gratification (my personal favorite). The group of programmers working on an open-source also share very strong alumni relationship with each other and will be available to help in future. In a commercially created program, outsiders can’t really tell who did what. Open source is different. As Lerner and Tirole write, “Outsiders are able to see not only what the contribution of each individual was and whether that component ‘worked,’ but also whether the task was hard, if the problem was addressed in a clever way, whether the code can be useful for other  programming tasks in the future,” and so on. Thus, a programmer can prove that he is competent and his career prospect greatly increases. The commercial world will offer an opportunity only when capability and credential have already been established, whereas the open-source world offers an opportunity to establish that credibility in the first place. The full working paper can be accessed from here. It seems that all that notion of altruistic programmer is not entirely true and it simply may be a gateway to enter into the commercial world.

Read More »

Talent Management

What does Jack Welch (The legendary CEO of GE) and McKinsey have in common when it comes to managing talent? Both of them seem to agree on the same thing when it comes to managing talent within an organization. In order to build a great company you need to employ great people. What actually are A , B and C graders ? “A” grade employees are people that deliver beyond what they are expected to deliver. Look at your best designer, best programmer, best sales guy, best support technician or, look at the best people with the same level (i.e. having same designation), your best manager, your best project lead. – they are the “A” graders within your company. The people whom you truly consider your assets! “B” grade employee are people who are consistent performers. They don’t do exceptional things but they are fairly consistent at what they are doing. According to Jack Welch – “They are on the fence” “C” grade employees are poor performers who either cannot deliver results or require too much pushing. Why can’t you hire “A” Grader directly? The problem is that there is no sure shot technique that will guarantee that you will have all the “A” class guys working for you. There are not many of them around! Even if you can come up with an objective shortlisting process that can help identify a super-performer from an average-performer, meeting the numbers will be quite a challenge – specially if your company is growing at 100% every year. If you think that everybody who works for you is an “A” grade gut then you have simply not raised the bar high enough. The good news is that hiring “B” grade performers is not that difficult and as it turns out, it is a better strategy too. There are following possibilities with a guy who is at “B” grade: He will turn out to be a “A” grader (Tiger within Sheep’s skin!) They will remain “B” graders They will actually turn out to be “C” graders There is a real competition out there for hiring talent. McKinsey says that this “war for talent” requires a new way of thinking for attracting and retaining quality talent:   The Old Way The New Way Talent Mindset HR is responsible for people management. All managers – starting with the CEO – are accountable for strengthening their talent pool. Employee Value Proposition We provide good pay and benefits. We shape our company, even our strategy, to appeal to talented people. Recruiting Recruiting is like purchasing. Recruiting is like marketing. Growing Leaders We think development happens in training programs. We fuel development through stretch jobs, coaching, and mentoring. Differentiation We treat everyone the same, and like to think that everyone is equally capable. We affirm all our people, but invest differentially in our A, B, and C player So you are in a safe position as long as you have a process to recognize and reward the “A” grade people, attract, train and upgrade the “B” grade people and most importantly, identify and get rid of “C” grade employees. Why getting rid of “C” grade people is important? There are a lot of reasons why you should get rid of poor performers: 1. You stand for what you tolerate. If you tolerate incompetence then you and your organization stands for it. 2. There is lot of effort required in converting “C” graders to “B” grade. At the same time remember that your “A” graders and “B” graders are spending their time on “C” graders. It’s like throwing an olympic swimmer into a pool with weights tied to his waist and then expecting him to win the race. I firmly believe that the results will be much better if a “A” grade employee spends time on “B” grade than on “C” grade. How to avoid hiring “C” graders? I think “C” graders are terrible at recruiting. If you believe, that a person is below average (either within the organization or amongst peers) then that worst thing that you can do is let them hire other employees. So, you should only allow your best and brightest people to select future employees of the organization. Remember, no one can hire someone better than himself. So, while “A” graders will hire “B” graders, “B” and “C” graders will hire even more “C” graders. Let’s begin the new year by cleaning up some deadwood. Shall we!?

Read More »
MENU
CONTACT US

Let’s connect!

Loading form…

CONTACT US

Let’s connect!

    Privacy Policy.

    Almost there!

    Download the report

      Privacy Policy.