Monday, June 28, 2010

An Interview is not an Exam!

There are several important differences between an interview and an exam. First, an exam usually signifies the final stage of a process of learning. An interview, in contrast, signifies the beginning of a similar process of learning in a different setting. Secondly, preparing for an exam usually involves learning and remembering purely technical concepts, but preparing for an interview warrants much more attention to other aspects as well.

The people interviewing you are, at the end of the day, employees of the company. Therefore, in any company, the interview process is usually a mini demonstration of how the workplace is going to look like once you join, conceptually as well as contextually. The interview often brings to the table the overall management culture, the amount of creativity encouraged by the managers, the approach to problem solving, etc.

This is extremely helpful to you as a candidate for two reasons. Firstly, if you are in a position to decide between two ore more job offers, your comfort level in the interview would be a clear indication and one of the most important factors of consideration when you make your choice. Secondly, and as you may not always be in a position to choose between job offers, the mood in the interview helps to prepare yourself psychologically for the work environment you will experience once you are selected for the job.

Thus, the third key difference between an exam and an interview is that the former is usually an assessment of how much you know and remember, while the latter is a simulation to check if there would be a three-way fit between you as a future employee, the interviewer as your future manager and the company as your future employer. So remember that the creative genius in you, your systematic approach to problem solving or your personality itself could score higher in the mind of your interviewer than mere technical knowledge that you may possess!

Niranjan Srinivasan
(as written for eccgetsetgo)

Tuesday, June 08, 2010

Involvement levels & Observational biases


Any organizational change process has to start with an analysis and evaluation stage, where the resources and capabilities of the organization, or in other words the ‘system’, are analyzed and the barriers to change are identified. According to practitioners of the ‘systemic’ approach to organizational development, the analysis should not be limited to just directly focusing on areas of improvement. It involves understanding the fundamental strengths of the system and identifying opportunities to develop them and then use them to overcome the weaknesses. After evaluating the success factors, other organizational patterns and dynamics, the hypotheses are formulated. Based on these hypotheses, the key focus areas for development are identified.

A hypothesis is only a proposed explanation of an observable phenomenon. These hypotheses can be used to interpret certain dynamics, patterns and behavior of an individual, team or organization and can support the manager and consultant in his analysis. However, hypotheses are often confused with the objective truth or the reality itself. However, social reality cannot be seen in an objective way but is always constructed by the observer. The observers thus play a crucial role in formulating the hypotheses since what they express is only their own perspective. Since the formulation of hypotheses forms a vital stage in the change process, it becomes important to reduce the biases to the extent possible.

People are often biased in their observations due to a high level of involvement in issues and situations that are relatively more important to them. In other words, if two people look at the same landscape they both might see different things depending on their focus, current mood, personal situation, experience etc. A person´s position in the company, for instance, can be an influential factor on one´s social reality. A CFO might have a different focus and perception on the status of his organization than an employee or the owner of the company. Thus, in order to find the most promising solution to a problem it is useful to understand the internal models of the observers, reflect on them and build hypothesis before acting.

The relationship can be best illustrated using the figure, with the Involvement level of the observer on the vertical axis and the Extent of Biases on the horizontal axis. It is useful to understand the internal models of the observers, reflect on them and then build the hypotheses. Here we define three types of observers:

1. Primary or Resident Observers: These observers are usually the leaders, managers and employees in the organization. In general, they can be defined as those who are a direct part of the system. They have a high level of involvement in the system and largely present their own perspective of the organization, since they are directly affected by the various aspects of the system.

2. Transient Observers: This category usually represents consultants, who observe the organization and interact with the primary observers to gather their insights and perspectives about the system. They also observe aspects of the organization that are not mentioned explicitly by the primary observers and examine why these aspects are neglected. However, as they build relationships with people in the system, there is a strong tendency for the transient observers to become integrated into the system, leading to formation of perspectives. Their views and observations however are biased to a lesser extent compared to those of the primary observers due to a comparatively lower extent of involvement.

3. Remote or Distant Observers: Remote observers are those who analyze the various factors that lead to potential biases in the system and bring in a fresh perspective to the observations. The difference between a distant and transient observer is that the latter gathers information from people within the organization, i.e. the primary observers, and analyzes it. The former on the other hand is a complete outsider to the system, and ‘observes the observer’. Distant observers can help sharpen the entire process of hypotheses development.

In practice however, the three levels of observations could be done by one person or by a team by merely acknowledging the diverse perspectives that stem from different levels of involvement in the system.

It is natural for people to have diverse perspectives. We need to bear in mind that the goal in this case is not to single out the best among the different perspectives but rather to disclose the hidden and most important aspects in the organization, which require attention. We must treasure the perspectives of all three categories of observers and actively use them to formulate better hypotheses and hence focus on the right areas for organizational development.

Niranjan Srinivasan (along with Mag. Christine Wawra begin_of_the_skype_highlighting     end_of_the_skype_highlighting)

The authors are practicing consultants at Doujak Corporate Development - www.doujak.eu - dealing with Change Management & Strategy Implementation

For more details, feel free to contact me at ninja.srini@gmail.com

The P-R Framework for Teams



The PR framework shows Academic Performance of teams on the vertical axis and Professional Relationship among team members on the horizontal axis. The four-quadrant framework is represented in the figure.

Quadrant 1 – High-High: Teams in this quadrant score high on both academic performance and professional relationship. These teams are effective in weeding out minor differences in view of the main driver of unity, which is the final goal (36% of respondents). This is the ideal quadrant for a team to be located in. Teams in this category would require minimum training spend and can be assigned more complex projects to enhance the overall productivity and profitability of the organization. Some members from these teams could be redistributed to teams in other quadrants to enhance their performance.

Quadrant 2 – Low-High: In this quadrant, the team members have a good understanding between each other, but score very low on academic performance. One of the main drivers of unity in such teams is homogeneity (36%); the presence of sub-groups is negligible, since the team members gel well with each other. The team here is seen as an immediate support system almost 60% of the time. However, the issue is that the team may not be technically sound to deal with complex problems. The team could potentially operate in a “zeal too often” mode, where the members are having fun but performance levels drop considerably. This could also lead to a lack of motivation to deliver the best results. This makes this quadrant the trickiest to deal with, since the team members are in harmony with each other and would resist any form change. Creating sub-groups or restructuring these teams with technical experts or swaps could lead to a lack of fit and may hence worsen the situation. The ideal way to enhance productivity and performance would be by improving specific skill-sets of existing members of the team through technical training.

Quadrant 3 – Low-Low: Almost sure-shot candidates for relationship discord and performance failure, teams in this quadrant need immediate attention and a complete revamp. There is a high incidence of Unconscious Sub-groupism in such teams (77%). The main reason for this is that members in the team may not be in the best of terms with each other, leading to selective avoidance of certain members in the team, resulting in an unconscious formation of sub-groups. It has also been observed that the main driver for unity in such teams is the presence of external competition (50%). The team is never the first support system (~28% of the time). Team members often look outside the teams for support and motivation to perform. The challenge is to try to move these teams to either of the adjacent quadrants – improve professional relationship or academic performance. This would involve get the members to understand each others’ differences, subordinate their goals to the team goal, thereby arriving at a ‘common’. Improving one may often be easier than the other depending on the environment and the composition of the team. In a professional environment, it may sometimes become necessary to restructure the team to counter its weakness – include a technical expert or swap members from another team to improve dynamics.

Quadrant 4 – High-Low: Teams in this quadrant score high in academic performance, but low in professional relationship. These teams show high levels of capability and end up performing against odds, coping with bad team member dynamics and hence high levels of unconscious subgroupism. As in teams in the 3rd quadrant, the main driver of unity in these teams is also external competition (56%) and the team is seldom the first support system. In such teams, it may be alright to maintain the status quo for short-term projects. In the long term, there may be two approaches depending on the degree of discord in terms of the professional relationship between the members. In situations where it may be difficult to bring the team members together to arrive at a ‘common’, it may make more sense to introduce some level of conscious sub-groupism – where the team is split explicitly into smaller groups with sufficient functional expertise, but people who can work better with each other.

This framework works best when conducted at an ex-post, i.e. after the teams have worked on projects for a couple of months. Suggesting the most optimum team composition ex-ante is highly dependent on the nature of the projects and the environment in which the teams operate. This could be done based on personality analysis & psychometric tests conducted on the team members before they are allocated to a team. Further research is being conducted to extend the framework to help address the bigger issue of resource allocation in companies.

Niranjan Srinivasan (along with Ashish Khushal Dharamshi, Indian School of Business, Class of '10)
For more details, please contact me at ninja.srini@gmail.com