Sunday, 19 February 2012

Caught Between a Rock and a Hard Place?

Matrix Management is a style of management where an individual has two reporting superiors – one Functional and the other Operational. Matrix management brings in some interesting dynamics to the work place that you wouldn’t see in the traditional organization where each person reports to one boss. With many companies going global, matrix management is more prevalent these days.
I would like to define the 2 terms for the purposes of this blog:
Functional/Line manager is a person who directly manages employees and is responsible for the administrative management of the individual as well as the functional management.  They control the compensation and evaluation of the employee. They also control the vision, strategic goals of the team.
Project/Operational managers, are responsible for directing the work of employees, but are not responsible for the administrative management of those individuals. They do not discipline the employee, promote/demote them, do salary adjustments, etc. but have inputs
Matrix Management works very well at senior levels where the Functional,Operational and their senior manager are all in synch with the same Vision, Goals and Project priorities for the team. Having been both a manager and an employee in matrix organizations, I have seen interesting, Complex Dynamic Scenarios in the work place when it is not set up right.
Think of the individual in a matrix organization whose two bosses cannot get along with each other. The two managers could push and pull the employee in different directions and make the employee work life very difficult. In such a situation, the employee can align with:
a)      The Functional manager
b)      The Project manager
c)      Do the right thing for the company and team and not align with anybody for the sake of aligning
d)      Try to align with (or appear to) both of them
e)      Take advantage of the 2 bosses and not get any work done!

Typically the Functional manager controls the compensation and evaluation of the employee. The employee can align with the Functional manager but tactically he/she has to spend most of the time working with the Project manager. Day to day activities could become a problem as the Project manager might not be supportive. The Functional manager is not aware of the employee’s accomplishments unless the manager puts in extra effort to understand and evaluate the accomplishments of the employee. Most of the time, due to the lack of good working relationship between the 2 bosses, the evaluation will be incorrect.
If the employee aligns with the Project manager, day to day activities will work fine. Since the Project manager is not responsible for the long term interests of the employee, they will not ensure that the employee morale, career aspirations are met. The Functional manager may not like the employee working well with the Project manager and could retaliate.
Employee can go about doing the right thing for the team, project and company and choose not to align with either of the bosses. But when it comes to time for promotion and bigger responsibilities, both the managers may not be supportive of the employee. They would rather support someone who is aligned to them.
The employee can try to align with both the bosses one for strategic decisions and one for tactical decision. I would think this situation could be compared to a kid with divorced parents who are pulling the kid in different directions. I believe this is not a long term solution either.
The worst case is where an employee takes advantage of the situation and does not get any work done. This is bad for the company and for everyone around.
Senior manager to both the bosses – who is responsible for the matrix organization, needs to be very aware of the dynamics and ensure that the team is fine even with the conflict between the two bosses.
The 2 bosses need to take the responsibility of ensuring that their differences do not hurt the employee or the team. The onus is on the managers, especially the Functional manager to make things right for their employee and this is the only right and ethical thing to do. But if such is not the case, I personally do not believe that any options that I have mentioned from an employee point of view will work in the long run. What do you think?

Sunday, 15 January 2012

Larger than Life Goals


As one of the benefits of working in large companies, I have had the opportunity to participate in Leadership Development and have come away with great insights in leadership and management. During one such leadership training, I came across the concept of BHAG – Big Hairy Audacious Goal. It is about setting visionary goals that are both strategic and emotionally compelling.
In a previous role where I was leading a large team for a large company in India, we had the opportunity to build a Hardware Chip of greater complexity than anything we had worked on before. My peers across the globe had indicated to me that few teams were capable of delivering such a chip and I would require a lot of help. I also believed that we lacked the skills in the team in certain areas and we needed to build the capability – however, I was positive that we could deliver the product. It was around this time that I took the leadership training where I was profoundly influenced by BHAGs.
This Executive Education program shared many insights and real life examples of BHAGs. A BHAG has to be meaningful, visionary, emotionally connecting to the people and should unify the efforts of the team. It has to have an impact across the whole team and affect every member in the team. The vision was to build one of the best technical teams that not only builds a chip with minimal cost and time but also to be able to replicate the same results for all future programs. With this vision in mind, my BHAG was to deliver the chip - given the history and perception of the team - beating an already aggressive schedule with minimal cost. To meet the definition of a BHAG and to get the team energized, this goal had to be something better than any other team had delivered in the company.
A good slogan helps make the BHAG a part of the daily routine. In this case we took a goal of “shipping the FIRST chip (changed)”. In chip-design, there are 2 validation (or testing in software) phases. The first phase is during the design cycle, and work is done through simulation before manufacturing the actual silicon chip. The second phase is after you have the silicon chip in hand. The idea behind the BHAG was to find all bugs during the first phase so that one doesn’t have to re-manufacture for bug fixes after the first silicon thereby saving cost and time.
A good way to start a BHAG is to get your top 10 most engaged employees. I went over my insights from the class and what I envisioned the team to be in a couple of years. We then came up with the goal of “shipping the FIRST chip” and identified 6-7 concrete items that would define the finish line. We ensured that every team member could relate to it. I then went to the next set of 20 people and went over the vision and the BHAG.  This set the momentum going. In a month the whole team was talking about and believing in “shipping the FIRST chip”.
Daily actions and decisions need to have this goal in mind. Every schedule, every milestone definition, every status tracking meeting was done with this goal in mind. This is where I have seen many leaders fail. They are excited to set the BHAG but do not follow up or follow through. You have got to eat, drink, breathe and live the BHAG every day. The team needs to feel it on a daily basis.
Three years later, we achieved the BHAG of “shipping the FIRST chip!” I am very proud of the BHAG that I set. While it took us three years to fully realize it, at the end it had given a definite sense of purpose and meaning to the team. Along the way I had found a greater meaning to my work, people, career and the industry.

Monday, 26 December 2011

Why I Continue to Work in the Technology Industry

One common question that I get asked is, “Why are you still working?”  I don’t understand that question because there is still so much more for me to accomplish and give to the technology industry.
It all started for me in high school. My high school was next to an Engineering college and I would ride my bicycle past the college every day. I always assumed I would go to the Engineering College next to my high school. This was an easy decision since there is precedence in my family with both my dad and brother having studied Engineering. I also had a good aptitude for Math and Science. 
In college, I was surprised to find that the female-to-male ratio was skewed. Although I live in a country which has a skewed gender population ratio, I still found it surprising. I come from a family where it is very much accepted to be a daughter, a wife, a mom, and a working woman at the same time. I now know that it was atypical of Indian families. When I started working, I found that the female to male ratio was again skewed across the industry and across countries. As years passed by more and more female peers dropped out (that is a topic for another blog). Their approach to problems, solutions, communication and leadership style may have been different but I still found them being very effective. Is it possible that some senior managers did not recognize this difference in approach and effectiveness?

I have had the luxury of having some of the best managers to work with who have helped me build my career. Having said that, some people have made it uncomfortable for me to work but overall it has been a positive and rewarding experience. Companies want “out-of-the-box thinkers” – the very fact that I have stayed in this industry for over 20 years and plan to continue, should make me an out-of-the-box thinker, shouldn’t it?! But at the end of the day, I still don’t see myself very different from others. I want the same things (impact, growth, recognition, job satisfaction, etc.) in my career as most other people.
With each year passing, I realize that there are so many more things to learn. Even with over 20 years, I have never done a boring repetitive job. I enjoy having ownership – whether it is a project, a product or a team. I enjoy coming up with goals that are very challenging and then convincing everybody to go after those goals. I celebrate my successes and feel sad about my failures. I enjoy working with and observing my seniors and learning from them. I enjoy hearing from my teams and not just their experiences at work but also their experiences outside of work. I enjoy spending time with the young folks in the industry and understanding them – makes me feel closer to my kids. I enjoy looking at the history of companies, products and teams.
In my twenties, when I was based in the US, I believed in the all-American dream of working hard when you are young and retiring rich early. In my early thirties I realized it is not only financial reasons that make me come to work, it is also about being part of something big and meaningful, and yes, the glory and satisfaction of doing something BIG – whether it was building the first Giga Hertz CPU or the first Indian CPU design, it was always something that I believed in and wanted to be part of.
I am in my forties now.  I would like to continue in the tech industry and keep looking for the next big thing to be a part of. My kids are grown up. For those young moms and dads who are finding it hard to do the balancing act, my only advice is to continue working; it gets easier as the kids get older. You will even find time to write a blog!
So, why do I continue to work – because this is my industry; this is one place where I can make an impact, a difference to the industry, community, company, team and to myself. Why would I not continue to be here for another 20 years? I wish though, that most of my female peers didn’t have to opt out and could reach their potential – there is so much they can give to the industry…

Sunday, 11 December 2011

If Life Offers you Lemons, Make the best Lemonade

I was a panelist at a conference last year and one of the concerns from the audience was, “My manager always asks me to do unappealing jobs and I am not able to say no. Hence I always end up with those types of jobs”. Having managed large teams, I believe that there are all kinds of jobs and all of them need to get done. It is true that some jobs are considered more appealing than others by some folks. However, it is possible to make a difference with any job you have.
A few years ago, I was asked by my manager to take up a Verification Management job. I had worked on all aspects of CPU design and was interested in continuing with design. But the available job was in verification. Typically verification teams are very large teams and the management had confidence in me to pull this through. For some reason, the company had lost most of the senior verification members. It was considered a suicide mission to take over at that point in time. I was open to taking such risks and I decided to take this new challenge in my life.
As I took over the verification job, the management changed. I knew the new management was very anxious and concerned if I could pull this off.  I started the team with a handful of people and we were clearly the underdogs. The goal of the verification team is to certify the quality of the product.  Having just moved from a failed project, there was huge pressure in ensuring that this new project was successfully completed. The team morale and confidence was very low. In addition, there were multiple reasons why verification was not considered THE career choice – scope of verification, lack of process, lack of stake holder management, perception of  being a support organization, etc… - I needed to fix this as well.
I approached the verification management job just like I approached any other problem solution. I split up the problem into multiple pieces, prioritized them and started working on each of them. As I got more involved, I found that Verification Management very difficult and challenging compared to managing the design team. As a Verification Manager you have impact on the product quality, features, feature development and implementation, schedule, people management and cost. Every bug that is not found pre-manufacturing has a direct impact on cost and schedule. In CPU chip design, cost is on the order of millions of dollars and schedule impact of a quarter or more. Without going into more details and cutting straight to the results, we had a very successful product at end of the year. The quality was so good that it was productized a quarter earlier than planned. You get quality by design not by chance. The quest for quality should come from within each engineer and I had the satisfaction of having inculcated this culture.

At this point I knew that my job was only half-done. I still needed to make verification THE career choice for an engineer. I asked to continue as a verification manager for the next project too and I was given additional responsibilities of handling multiple projects.  At the end of the five year journey as a verification manager, we had completed our second product and it was as successful as the first product and again a quarter ahead of plan. The verification team had grown from a handful of people to over 100+ people and we had helped many other programs in the company in addition to our own projects. The team morale and the confidence were at its highest and I knew the team would be able to deliver to any challenges that it faced in the future.
Few months later, when we were very short of designers, I had to ask one of my best verification engineers to move to design from verification. Five years earlier he had moved to verification from design along with me.  He declined!!  He had made verification THE career choice for himself. At that point, I knew I had done my job well.
I believe in giving my best shot in everything I do – on the job, on the field, as a parent. It is what you make out of that job that matters. You need to look for new opportunities, look for the next step up, but don't forget what you already have. For those who don’t believe that they have had the opportunity, see what you can do with the current opportunity you have. It worked for me…

Sunday, 27 November 2011

Why Should a Fish Climb a Tree?

 “Everybody is a genius, but if you judge a fish on its ability to climb a tree, it will go its whole life believing it is stupid.”  This is so true. Over the years I have received feedback from my managers, parents and mentors. Some of the feedback has been very useful and some has been totally useless. 
One of the most important roles of a manager is to give the right feedback at the right time. I have seen managers giving feedback only when they are forced due to company policy, say at the annual review. I like to get feedback from a person who is observing me on a daily basis and giving me pointers. Pointing out how to make things better with the right examples and right time would make feedback very useful. I have had my “A-ha” moments with feedback given this way.
The feedback has to be meaningful to the employee.  The idea of giving feedback is to help your employees improve themselves. Calling names such as “Bully” or “Stupid” do not give any insight to the employee unless good examples are given. Even worse is when the feedback is contradictory. As an employee getting such feedback, you are left wondering what your manager meant.
A common mistake that I have seen managers make (I am also guilty of this and I see parents making it too) is to try to make their employee someone they are not – making them fit to a preset mold. This brings me to the starting point of this blog – why do we make the fish climb a tree? Why do we try to turn the fish into a monkey? Even if it tried its whole life, it would not excel. Instead, if we believed that each of our employees is a genius and brings a special value to the team and then make full use of their talents, the team will benefit.
I learnt this the hard way when my son was 4 years old. Wanting to make him a math genius, I signed him up for Kumon classes which emphasizes learning math through repetitive activities. I learnt that it is impossible to make my son do repetitive jobs. He is good at math but he cannot learn it the Kumon way. Each person has an inherent personality and talent. I have had to be very creative in recognizing and bringing out his talents.
One piece of feedback I have recently received  is that my English is bad. At 40+ years of age, it is going to be very difficult to fix this. I agree that my English isn’t the best, but the bigger question is - is it good enough? I seem to be able to connect to hundreds of people with the language I have. One of the best speakers I know mixes languages almost every other sentence but boy, is she a good speaker!! She kept the 400 people crowd engrossed in her speech. One of the authors I like is Chetan Bhagat. He has very vibrant characters in his stories – he mentions that his language is not technically the best and would never win a Bookers award but his books sell.
As a manager, as a parent you need to get the best out of people. Focus on enhancing people’s positive points. Reiterating what they are incapable of doing is not going to achieve results. If you notice that the feedback to your employee is the same year after year, probably the feedback is not being meaningful to the employee. Make a fish flip and do a somersault in the water but don’t make it a clumsy tree climber. Don’t make the fish think it is stupid because it is a clumsy tree climber. Make it believe it is a great swimmer and can do even better.

Sunday, 13 November 2011

Contagious Leadership

Microprocessor design was a passion that began in college and has stayed with me even after 23-24 years. In our 3rd year of Engineering, I was introduced to the 8085 Intel microprocessor as part of the curriculum. Professor V. was very friendly and gave the students a lot of room to try out the different experiments and projects. I was enamored by the Architecture, Assembly level language and the SDK kit that we could do all our experiments on. I literally spent my 3rd and 4th year in the microprocessor lab. I was hooked on CPUs and microprocessors.  I ended up taking many architecture courses in my graduate school and many more after I joined work.
When I was about 2 years into my career, I got a job at IBM in the CPU design team.  The team was very large and we were working on a CPU that was at least 4x in performance compared to the best performing CPU available in the market at that time. I was very excited to have landed a job in a CPU design team and finally I had my dream job.

Few months into my job at IBM is when I met the Mr. R, our design manager of the project . He was a very good people manager and he would walk into people’s offices, sit down with them and have casual talks. He made it so comfortable, that I could talk to him very openly. Here was a senior manager who led a 200+ people team – not just any team, a hardcore CPU design team, took the time to talk to a junior person like me and would discuss issues that I am facing.  This is when I decided that I wanted to be a design manager – not just any design manager but one like Mr. R. who could lead a cutting edge technology team and also relate to the people.
This is what I mean by contagious leadership. You just want to be like them. This was how the journey began for me; this is how I set my goals. These goals drove me through all the difficult times of work-life balance and kept me going through 20+ years of my career. Simple efforts by leaders make a big impression on people.  The leaders probably do not realize the impact they have but it takes people through a long way.
I met many more leaders that I want to emulate post IBM. It reminds me of the Jungle Book song “I wanna be like you. I wanna talk like you. Walk like you, too. You'll see it's true. Someone like me. Can learn to be
Over time, your goals do change.  I have moved on from the CPU design teams. But, what has remained constant is that I want to have positive impact on others. I want to be a contagious leader too...

Who am I and Why do I want to Blog

I am putting this site together to jot down my thoughts and learn from others. I want to make blogging a way to make the tech industry a close knit community. I think it is wonderful that people share their thoughts and one can learn many things from bloggers all over the world.
I have been in the hardware industry for over 20 years and have now recently started working on software products also. I went to graduate school at Georgia Tech and worked in multiple companies (most of them global) as an individual contributor, technical lead, architect, and as a manager of large organizations (100+). I have worked in some of the largest computer companies and small companies. I have worked in US and in India and equally appreciate both the cultures.
I have had the most interesting experiences – some great successes, some dismal failures. I have met the most interesting people, most humane people and some difficult people!  I have met some of my best friends here.  I have had many wonderful managers and mentors that have helped me grow and learn a lot over the past 20 years.  I am going to share and question some insights and observations.
I am married to a techie for over 20 years. We have two lovely boys. I learn a lot about people management by parenting my kids and handling my husband. I take with me a lot of learning from my work to home and vice-versa.
This is my industry, this is what I chose, and it’s my home away from home. I want to make it a better place for us and our future generations.