Category: Management

Don’t get run over by Profits

Last day, I spoke about some considerations that you must take into account while starting your business. While I am not too much a fan of grand vision and mission statements, I strongly detest the idea of being too verbose about profitability. As a young business you should not be driven by profits but you should understand what drives your profitability. First let’s attempt to understand what profit means. According to Michael Porter profits are no more than the sum of the difference between the price that customers pay for an activity and the cost of that activity. Thus, if customer is not paying for an activity then it’s non-revenue generating overhead. As a startup, you must minimize this overhead. The best way to do this is ask – “why am I doing this?”, before you add any process or demand a new report. Don’t put the cart before the horse, profitability within the business depends on certain fundamentals and you need to: 1. Drop the image of a lone warrior and focus on building a team. You’ll need to hire and retain the best people you can find. If you don’t have good talent then you will never be able to do things as effectively and efficiently. On the other side, the cost of replacement of your best people is incalculable. If you have good people then you will navigate through anything. 2. Minimize overhead. You need to ensure that maximum efforts are put in revenue generating activities. If your best people are not spending their time productively then you are not growing as fast as you should be. 3. Be crazy about customer success. You need leave a breadcrumb of successful projects and clients. If you focus on this well then, you marketing and sales will almost be on an auto-pilot for lifetime. 4. Stop competing on price. It’s not wrong to enter a matured industry without having something special (read different) to offer to the market. But, you should never differentiate yourself on price. The reasons for this demand a separate article but I would like to hint that a differentiator should not be easily copied by competitor and price could be easily cut further by an ignorant competition.

Read More »

All’s well that starts well!

There is a lot of literature around about starting your own business and growing it. The problem young companies face is that it’s often a single man who has to do everything and it’s easy to loose your priorities. The age old adage – “All’s well that ends well” does not work here, it’s important to start well! Here is a small list of things that if you can follow: Keep customer satisfaction above everything else Service business runs on referrals and reference checks. While, there are plenty of blog posts around that talk about getting even with customers or firing them, I recommend you abstain from them for a while and rather choose your customers carefully and then do everything to keep them happy. Remember that you’ll need projects that you can showcase in your portfolio and people who can give you five star feedback. Build your management team You will not be able to grow if you have to everything yourself. You need a line of leadership within your organization that can take care of entire functions and handle tough issues. A start-up is usually starved of cash and hence do get too crazy about hiring management grads. Instead hire people who are keen to learn, have a fire in their belly and are ready to grow with you. Assign them responsibilities early-on and let them do their jobs. Invest in Tools and Processes It is much easy to adopt a tool and process in a 5 people company than in a 50 people company. Thus, it is important that you sit with your team and employ tools in the areas on project management and establish key processes atleast in the areas like Project life cycle, Accounts & Invoicing and HR. There is plenty of free stuff in the market and you will realize later that your PM tool has become a goldmine of information and even a platform for information sharing. Specialize Don’t fall into the trap of trying to pick of all sort of projects regardless of price and technology. This garbage collector approach will put you in a death spiral from which you will not be able to recover from later. In the initial days it is important that you specialize in only certain type of projects. It will be easier to manage! Try looking for simmilar type of projects as the code reuse can boost your profitability as well as you can surprise the customer with a quick delivery. You must have proper management body in place before you undertake any diversification initiative. Save Cost Don’t run into renting the most plush offices that overlooks the ocean and buy expensive furniture with Aeron chairs. Remember you are startup and you are not competing with IBM. Keeping your ego in check and that will help you control your expenses. I don’t remember where I read it but I must quote and say is that being successful is not about doing things exceptionally well but it’s about making lesser mistakes.  

Read More »

Web Commuting – Walking the Talk

‘Web Commuting” is increasingly becoming omnipresent. A Citrix study showed that this is becoming increasing common amongst Americans. It read and I quote: This survey, conducted by the polling company, inc., found that 23 percent of American workers and 41 percent of small business owners regularly work from home or another offsite location Our own organization also launched a W@H (Work at home) program which allowed employees doing certain type of work to work from thier homes in case they are unable to come to office for any reason. This implies one thing for sure that with time, we will see less of our employees face-to-face. This trend makes the importance of proper communication even more important. According to experts, our non-verbal language communicates about 50% of what we really mean (voice tonality contributes 38%) while words themselves contribute a mere 7%. Thus, talking to your employee only via emails, documents or instant messenger means utilizing only about 7% of communication potential and getting only 7% information. Thus, If you not willing to travel at least once a year or devote time to provide constant feedback then it is not going to work for you. Our W@H model has matured to a level where we have employees hired for web commuting only. We see the benefits, but it has not come without time and investment.  Web Commuting can deliver outstanding cost benefits, adding the dimension of “outsourcing” makes it more lucrative. However, you must carefully plan your business processes to see if it fits your need and when you are ready, involve experts who can walk their talks  Frankly, I feel that outsourcing companies that sell “offshore staffing” as a service whereas, they do not allow remote working to their own employees, are hypocrites. They sell what they don’t believe in!

Read More »

Managing Talent

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 »

Four Type of Causes

Aristotle was one of the greatest philosophers who ever lived. I think his contribution to both science and philosophy is enormous. He described that there are four types of “causes” i.e. Material, Formal, Efficient and Final. Let me describe these causes in the following way: Let’s assume that a programmer has made a software using PHP. In the above example, PHP is the material cause because this forms the material from which the software has been made. The Formal cause is the essence or the need for fulfilling which the software has been created. The efficient cause is the act of programmer keying in PHP codes into the computer because this act actually results in the software to be created. Otherwise, the programmer can look all day at the screen and there will no software at the end of the day. The final cause of the software is the programmer itself and what he had in mind about the essence of the software. Why is this important to know? When I spent some time thinking about it, I realized that the impact is very deep. For one thing, causes leads to effects. The final cause of the software is the programmer’s interpretation (or misinterpretations). Thus, the final cause may end up producing a software which is very different from the formal cause. What if there is unity between the final cause and formal cause but the material cause is insufficient i.e. the technology used to produce the software is incapable of producing the desired application? Thus in order to meet the formal cause of any software application it is important that: The technology (or material cause) should be available or acquirable. The process and resources (efficient cause) should be available or acquirable. The understanding of the formal cause should be shared across the team members.

Read More »

Project Progress during Starting and Closing Phases

I think 80% of the project work is completed in 40% of the total time while it’s the remaining 20% that takes 60% of the time. Those of you who ever had to manage a project will notice that the it starts very slow and then it picks up speed and you see a lot of progress being made everyday but suddenly towards the end it slows down again and you feel that your team has lost the zest or they are slacking behind. But is this not expected ? if you plot the progress of the project (% of feature completed with time), you will see it takes up a S-curve as below: Let me explain why initiation and closing is slow. During Initiation Initiation refers to the starting phase of the project when you receive the notification that the project has started. It needs to be understood that unlike race-course horses, developers cannot dash out the gate at full throttle towards the finish line. They have just been allocated and they don’t even know what the project is all about. Here are some reasons which will slow down the progress during the starting phase: Team Establishment This is not about allocation of people. The team goes through a whole stage of Forming-Storming-Norming-Performing (Bruce Tuckman). This duration of this cycle depends on both the size of the team as well as diversity of domains/specialization within the project. Ambiguity in Requirements From no documentation to hundreds of pages of requirements, but I am yet to see a requirement document that is understood exactly in the same way by all people. There are multiple round of discussion between the team members and with the client during which the progress seems frozen. Tools and Environment In certain cases the project is dependent on tools and environment which is hard to duplicate in our development environment. I once remember a search engine portal project that we were doing in which our job was to make some enhancements. The current system extensively based on XPATH queries and we lost 10 days in just setting up the system on our server. In another project we are doing, the client had four different versions of the same application and the application called files (PHP includes) from multiple versions. We had to set up a team of 3 people for 7 days just to clean up the code and set it up on our servers. During Closing Closing is the abyss between when a developer says the job is complete and when you say that the job is complete. Here is what happens: Product Integration Often we have to wait for days (or weeks) for simple things like Payment Gateway info, SSL Certificate or information from 3rd party vendors on proprietory systems (web services) that the system must be intergrated with. Sometimes, server does not supports parts of codes that we have written and upgradation of server or rework of code is required. Note: CMMI required all integration requirements and environment to be planned earlier but still, if your hosting company responds to request within 5 days then what are we supposed to do? Defects As more features are added into the system, more bugs are also introduced. As the bug database takes a life of its own, there is a tendency to increase the mix of bugs to new client-valued functions being coded. The result is that the overall speed of the team is maintained but an increasing percentage of the effort is devoted toward fixing bugs or adding “bells and whistles” Enhancements Buy enhancement I am referring to all the things a developer had to do which he did not knew he will have to do when he started the project. This mostly comes in the form of – “Of course it was supposed to be there!” and with some luck we will be able to point back to requirement document and say “nope!”. The problem is that time is spent in these negotiations and discussions which would rather be spent on stabilizing the current set of features that the product already has. At the end, I remember what one client told me – “Project is like painting the wall – it’s the corners that take most of the time!”

Read More »

Drawing your HR Map for 2008

I know its not the end of financial year as we still have one more quarter to go. It’s however very important to draw of all significant plans within the last quarter and then start making adjustment early on so that you can take on the first three quarters of the next financial year without “loosing” more time in planning. Planning for the HR is very important function in order to ensure that you have production capacity to undertake any expansion plans or support other organizational objectives. You need to sit down and answer the following questions: 1. What are new positions within the organizations that will be filled? 2. How many people will be required in what positions? 3. How will the current man-power evolve? (Think promotion and attrition!) 4. What are the new competencies that will be required? 5. What jobs would you like to remain in-house and what would you like to outsource? Once the future labor requirement and the current availability has been clearly established, the gap is action oriented target that can be handed over to the HRD (if you have one!) or in some cases you may need to draw a more detailed plan to fill those gaps. As soon as you begin to think of HR requirements, it is important to separate the qualitative issues from the quantitative issues. Let’s talk about them in more details: Quantitative Issues The quantitative issues are easiest to spot. A simple way to do this is simply calculating the ratio between number of people in the company and the current revenue and then calculating the number of people required to achieve the targeted revenue. Ofcourse, this assumes that efficiency with the organization does not change and this short process usually does the job pretty well. So, if you have 2 employees who are maintaining 40 client installations and generating $20000 every month, you simply calculate that by doing 60 client installations, you will generate revenue of $30000 and you will need one more employee. This “1” employee then needs to be hired and trained before he is actually needed for production. Qualitative Issues In a layman term these are the sort of issues that you can’t put number against and usually means that the current man-power or a part of it does not have the skills and knowledge future job requirements or in some cases you may see that the person is overqualified for the particular job. These are the sort of issues that can only be handled by Training and Restructuring. As as business owner you must realize that right people with right skills and doing the right jobs are the precondition to success. Is Outsourcing a Qualitative or Quantitative decision? Outsourcing is a quantitative decision only when same economies of scale can be achieved with an outside vendor or when it’s a strict question of changing capacity within an existing relationship. Getting this plan ready with you will allow you to look for possible outsourcing opportunities early and notify your vendor in advance about your ramp-up or ramp-down plans. However, if you ask yourself – “Can this job be done better by a specialized vendor because I want to focus on core areas?” – it becomes a qualitative decision. The core is that you must plan ahead of time about what you are going to outsource and in what volume.

Read More »
Making A Dedicated Hiring Project work!

Making A Dedicated Hiring Project work!

Even though distance, communication barriers, lack of local knowledge and geopolitical factors create significant risks, the economies of Offshore outsourcing are numerous and significant. However, to make these economies work for you, you should keep in mind the following few very important points: Project Scope – Clarity and Understandability Project Scope is the most important part of the project. The success or otherwise of your project largely depends on how clearly the developer has stepped into your shoes and understood the project scope, the purpose of his actions and the consequences thereof. It is advisable that your initial efforts should mostly go in making sure that your words are being understood clearly and correctly. If you find any deflection, you should right away contact either the Project Manager or the Account Manager and get a meeting scheduled with the developer, where the relevant issues are discussed in an open and constructive manner. The importance of clear communication should never be discounted at this stage and everything should be put in black and white as far as possible. Manage The Project Developers are mainly concerned with developing and not with project management. Someone needs to manage the project and that’s your job in a dedicated hiring project. You should not treat the project as the Developer’s responsibility alone, but should also understand yours as well, which includes the following: Make sure the Developer’s interpreted your description the way you intended. Make sure the Developer delivers what you asked for. You need to set expectations and inspect the Developer’s work to make sure it meets your needs and quality standards. If something turns out to be much harder than expected, or does not work out exactly as planned, you might need to decide which of several paths the project should take, after consulting the developer with regards to their feasibility. Again, Developers do not know the intimate details of your business, your users, etc. An old expression says you only have the right to expect what you inspect. You have to be involved in the project to make sure it delivers what you need. Finally, it is your project! You have the final say about what the project is. Share Your Vision With The Developer After hiring a developer, most people answer the developer’s questions about the project and assume that if he doesn’t ask a question about a particular part of the project, everything must be OK. What they did miss are all the assumptions: Assumptions made when writing the project description Assumptions the developer made when he read the description One problem is that we tend to write from our own perspective, not even realizing the assumptions we make. But the fact remains that you know your business inside and out, but your content developer probably won’t know anything about it. So to avoid this issue, one should take the following precautions: Be very clear and concise in your project description. Keep it brief and focused. Adding more words often just adds chances for different interpretations. Ask the developer some probing questions about the most important parts of the project. You will very likely discover some assumptions that you or the developer are making. Get some interesting or useful work output from the developer as early as possible. Use Instant Messaging for Communicating at the initial stages Instant Messaging makes remote workers feel as if they’re in the office. It’s faster and more intimate than email and allows you to track and transcribe exchanges. It’s also best for immediate feedback, quick question-and-answer exchanges and other important discussions. Again, only important matters be discussed over the messenger during the project period or before the beginning an important phase of the project. Have regular goal-oriented communication sessions scheduled with the developer and the project manager. However, it is always recommended that you send your suggestions, ideas and views through email, as you can be express yourself in a much better and free way and discuss the same over IMs. On a personal level, you must try and gain certain information about the Developers. For example, send across an e-card to wish him on his birthday or on his marriage anniversary. It is similar to treating him like an employee in your own office. This will motivate him and make him feel like a part of your family, after all, he is working for you as your employee! Proper Expectation Setting This is the most common mistake people new to software projects make. Unreasonable expectations lead to despair and failure. Most of us just give away a few general ideas about what we want, then sit back and wait for the finished product. Result: unsatisfactory projects. You need to put time and effort into managing the project to get exactly what you want. Hiring a developer is not “fire and forget” methodology. To succeed, you need to be involved in the process. You must be prepared, determined, and flexible. You should first ask the developer to work on at least one small project you want to be done. This allows you to learn the ropes on a project you fully understand. It also frees your time for other more important or more profitable tasks! Understanding The Cultural & Language Differences Most of us believe that there’s no need to be concerned with culture or language differences that exists during outsourcing. But we must understand that cultural differences can appear in any function. Acceptable user interfaces may have a different look and feel from one society to another. Colors and sentence structure may differ just enough to draw the user’s attention. When business processes are outsourced, cultural differences are even more pronounced. For example, the way the developers answer your queries, how they interpret the complaints of irate customers, and how they try to add humor to the conversation may all be driven or affected by local culture. For example, a message that is written by a well-intentioned customer to his client in

Read More »

Focus improvement at the level that matters

Organizations need to continuously improve themselves, not for capturing more market share but for maintaining the current share that it holds. However, most of the improvement efforts tend to focus on levels that are not directly contributing to creation and delivery of products and services. I don’t blame people for this, but if you are trying to improve too much without actually impacting the way the work is getting done then you will achieve too little. If you don’t see the link, then try to think your organizations performance as a summation of performance of all individuals within it. This chart will probably help you think: ∑ Individual’s performance = Performance of the Team ∑ Team’s performance = Performance of Department ∑ Department’s performance = Performance of Organization Now given the above relationship, look at what you need to do to improve the organization: To Improve the Organization => Improve Departments To Improve the Departments => Improve Teams To Improve the Teams => Improve Individuals Thus, before wasting a single dollar on any silver bullet solution, the most important questions to ask is – “Will it improve the way the individuals works?”. If you can’t say yes, then it ain’t worth doing it and on the other hand the smallest change that can improve the way an individual works, is worth doing right away.

Read More »

Timing your start-up

A quick tip for budding entrepreneurs: If your business starts at the right time, you can extract maximum growth by getting ready when the industry segment gets the peak demand. I strongly suggest that a new business should be started during the “low-tide”, i.e. when markets are not doing well and industry sentiments are not positive. It helps in many ways: 1. You can get the best talent available in the industry due to lay off by major players. 2. You will not have major competition and you can prepare your competitive edge “in hiding” to give surprise to your competitors. 3. Tough times results in innovation. It is highly probable that your company will have the “innovation” advantage as you try to come up the adversities of a low-lying market. This innovation can become a catalyst when the markets are strong and can become the deciding factor. 4. You can concentrate in building the right processes, measurements, quality control systems and genetic-composition of your company which will result in its rapid growth when the right time comes. 5. Your expenses will be lower in building the fundamental framework for the company. It is well known that markets have both the ups and downs. I feel “downs” should be well utilized to prepare the company for taking maximum advantage of the “ups”. It makes much more business sense and also keep your spirits up! Note: It is important to be patient. It is very important to know that you are preparing for the “good days” and, it is most important to know that you should not blow up all your money, since capital is another thing that you need to scale up your company fast when the right time comes.  

Read More »
MENU
CONTACT US

Let’s connect!

Loading form…

CONTACT US

Let’s connect!

    Privacy Policy.

    Almost there!

    Download the report

      Privacy Policy.