The Oticon Case: the Spaghetti organisation

From apppm
Revision as of 17:59, 28 September 2015 by S131882 (Talk | contribs)

Jump to: navigation, search

[[File:PerformanceDomains.png|300px | thumb| |Figure 1: Project Management Performance Domains. Cite error: Closing </ref> missing for <ref> tag, it exist different types of leadership within the program management. One of the most important are the transactional and transformational types. On the one hand, the transactional leadership focuses on the role of supervision, organisation and group performance. This type of leadership is based on the assumption that the only motivation of the worker is his own gain. Therefore, in order to improve the performance of the group is necessary some extrinsic motivation as additional salary, time off when the program is completed, potential promotion, not loose one's job, etc. On the other hand, the transformational leadership is based on a more charismatic, inspirational and intellectual leader. A leader who uses this approach intrinsically motivates and empower his employees by creating a common vision, a common goal. Any leader is neither 100 percent transactional nor transformational. Nevertheless, it can be argued that Lars Kolind was mostly transformational. The new organisation that he promoted strongly relied on the empowerment of the employees and the intrinsic motivation of those. The individuals were informed enough to understand their role in the organisation and the teams were driven by objectives. Therefore, Kolind strongly believed in the Theory Y, counting on the positive nature of people. However, it has to be say that he also applied supervision of the employees. For instance, once a year, all the employees had a meeting with their mentors to discuss their performance during the year and readjust their salaries accordingly. It should be also pointed out that the fact of creating a strong culture around the new organisation made less necessary to apply command and control techniques [book findit]

Contents

Strategy Alignment

Figure 3: Program strategy alignment

The radical change that Oticon underwent resulted in a several number of projects. Some of those had very different nature and where not interrelated at all. Hence, a perfect alignment of all of them was imperative for not making a complicated program out of a complex one[1]. In order to manage the strategy alignment of the different projects and processes, the program manager should address three different elements: the program business case, the program plan and the program roadmap and the environmental assessment. [2]. Among those aspects, the ones strongly related with leadership are the program plan. The program plan aims to clarify the organisation concept, vision, mission and benefits produced by the program [ref wiki change or book] This task was exceptionally performed by Lars Kolind, who was able to define a clear vision, under the motto Think the unthinkable, as well as a clear a mission: "help people (with impaired hearing) to live as they wish with the hearing they have". By clearly defining those two concepts and efficiently communicate them to all the stakeholders, he created a strong shared sense of direction and gave sense to the program [3]. It should also be pointed out that he also clarify the benefits of his program to the different stakeholders. For instance, when the program was launched, he send a newsletter to all the employees of the company explaining why the company needed that change and which benefits the program will produce. Some days after, a meeting with all the employees took place. It aimed to clarify all the possible doubts they could have. Anyone was obliged to go, but almost everyone went.

Stakeholder management

Stakeholder management is an important factor to take into account in every organisational change. It is necessary to identify which stakeholders will be affected and evaluate what's their degree of commitment. To facilitate the change process, the program manager must communicate a clear vision of the need of change to all the individuals affected. He must have strong leadership skills in order to set clear goals, see when is necessary the change, plan the change, monitor the change and manage the people issues along the change[4]. As it can be seen in Figure 4, the Stakeholder management can be divided in four steps: planning, identifying, engaging and management of expectations.One of the key factors of the success of the change process of Oticon was that Kolind followed those steps.

Identify Program Stakeholders

During his first years as CEO, he met several clients in order to understand their concerns and what was their idea of Oticon. Moreover, he met with internal stakeholders as managers and employees of different departments. He asked them what they thought was the vision of the company and why they think the company was in such trouble. He also figured out which ones where the relations between the different departments and what was each department exactly doing. The identification of stakeholders was done.

Engage Program Stakeholders

Then, it was necessary to plan how engage and manage the different individuals involved. At that point, the most critical point was to create a clear shared vision with all the stakeholders. Until then, the vision of the company was "leaders in hearing technology". When the change started, the vision became "helping people (with impaired hearing) to live as they wish with the hearing they have [5]. This motto and putting the new focus on the hearing care profesional instead of the end user created a clear and common vision.

Apart from the vision, another aspect to take into account while dealing with the stakeholders engagement is the communication. Within a company, several channels are used, but only one message is wanted to be transmitted. That's why is important to plan the how to transmit the message. The strategy used by Kolind was to send a newsletter titled "Think the Unthinkable" [5] explaining all the different changes he wanted to perform. Some days after, a meeting with all the employees took place. It aimed to clarify all the possible doubts they have. Anyone was obliged to go, but almost everyone went. He explained the idea and, in order to involve the employees in the process, he let them vote who wanted to be part of the project. Most of the audience respond positively. They were engaged in the change process. This commitment was crucial in further situations. For instance, due to the lack of financial resources, the company give the option to the employees to invest money in the company. The first who invested was Lars Kolind, fact that increased even more the commitment among the other employees. This strategy was embraced by Kolind other times as well. For example, as any employee of the company had an office, he didn't have neither [5].

Not only the internal stakeholder where addressed. Kolind also took care of the clients asking which where they concerns and what they were looking for in a product[5]. Those inputs were really important to decide the vision of the company and choose the new projects to develop, while they engaged the clients in the change process.

Manage stakeholders expectations

Figure 4:Transition phases in a change process

Another important aspect when managing the stakeholders is to take into account which expectations they have. If a program negatively affects a stakeholder, it is necessary to mitigate the impact in order to maintain the stakeholders involved [4]. It is important to make sure that stakeholders expectations are based on accurate information. Therefore, once more, it is important an effective communication.

In the present case, one of the biggest problems of the new organisation was to remove all the job titles. This fact created two major problems within the company.First, the resistance of the senior and middle managers.. Their expectations of loosing their benefits and power in the new organisation put them against the process. Frequently, during a change process, the stakeholders who doesn't support the change used to go through eight different stages : Shock, Anger, Denial, Depression, Acceptance of reality, Testing, consolidation and Internalisation (see Figure 4). Therefore, the task of the program manager is to contain the denial phase (e.g. not negatively affect the other stakeholders) and emotionally support the stakeholders during the depression part. Lars Kolind said: “One day a former middle manager came to me to discuss (…) he openly admitted that he didn’t know what to do for the company.” [5]. At that point, the former middle manager was entering in the depression phase. The duty of a good leader was to support him emotionally. Kolind made him see that he was not only a manager,but also once was a great specialist. That, made the middle manager decide to return to the specialist role: “He admitted that when he had been promoted to department head, the company had lost a good specialist, and gotten a bad leader in return”[ref oticon case]. In that example, we can see how Kolind was able to influence the middle manager, affecting his beliefs and attitude towards the organisation. Apart from the resistance of the middle managers, another problem arose. Some people felt frustrated because it was not possible to get promoted in the organisation. The fact of not having job titles make impossible to get promoted. The salary was fixed according to the contribution of each individual to the organisation by participating in successful projects. That extreme competitiveness made some employees not to feel comfortable. Even thought there was not a formal hierarchy, a “natural hierarchy” was created as some projects were more successful than other and some groups more productive. In that case, Kolind couldn’t do anything, as this problem was a collateral effect of the same nature of the organisation.

Implication

During his years as CEO of Oticon, Lars Kolind promoted a completely new type of organisation. The lack of hierarchy, the scarce resources and the need of fast improvements made the program extremely complex. Thus, a good leader was necessary to handle the situation and avoid the chaos. This is the fundamental contribution of that case to program management. Lars Kolind was an example of transformational leadership, leading his employees to a successful change process by inspiring and intrinsically motivating them. When he took over as the CEO, the company was running against big firms with more financial resources and more technology. The only way of being competitive was to create a fast-moving and innovative organisation. Consequently, the program needed to be fast-moving as well, resulting in less control processes and substantial delegation of power. This challenged the best practices of program management. Therefore, the success of the Spaghetti organisation can only be explained by the strong leadership its leader. From this case various things can be extrapolated to future similar cases. First of all, the fact that Kolind was able to rapidly define a clear vision and mission was one of the secrets of the success of the program. When an organisation or individual goes through a change, it is important to minimise the "non-sense stage" as usually people tend to reject what they don't understand. Second, Kolind performed really good gaining the support of the people. The fact of being completely transparent and involving employees in the process resulted in a massive commitment with the project. That improved the alignment between the individuals and the organisation. Moreover, this massive commitment solved the problem of the scarce financial resources of the company as the same employees where the ones investing in the company after Kolind invested first [footnotes 1]. Finally, it was important how the leader supported the people during the change process. He was a close leader, ready to talk with any employee and emotionally support him. That is something important during the change in order to avoid people to be depressed and negatively affect to the motivation of the whole group.

Notes

  1. You don’t lead by pointing and telling people some place to go. You lead by going to that place and making a case. —Ken Kesey

Annotated bibliography

Mark C , Bojeun (2014). Program Management Leadership. Creating succesful team dynamics. Florida: Taylor and Francis group]: This book approaches the program management from a leadership point of view. It is interesting to notice the different types of leaderships and how they can maximise the income of your program.


Hayes John (2010). The Theory and Practice of Change Management. 5rd ed. New York: PALGRAVE MACMALLIN: This book explains in detail the different aspects to consider while going through a change process. It can be useful to understand why the individuals act the way they act and how it can affect to your program.


Hans J. Thamhain and David L. WIELMON (1997). "Leadership effectiveness in program management. IEEE Transactions on engineering management. VOL. EM-24, NO3: This article reports the results of an exploratory field study of the effectiveness of different leadership styles in various project-oriented work environments.

References

  1. [Josef Oehmen, Christian Thuesen, Pedro Parraguez Ruiz and Joana Geraldi (2010). Complexity Management for Projects, Programmes, and Porfolios. An Engineering Systems Perspective. Project Management Institute. White Paper, pg 5-11]
  2. , The Role of Program Management in an Organisational Change, September, 2015
  3. [Hayes John (2010). The Theory and Practice of Change Management. 5rd ed. New York: PALGRAVE MACMALLIN, pg 167-183.]
  4. 4.0 4.1 [Project Managment Institute(2008), The Standard for Program Management, PMI Publications, 2nd ed, Pennsylvania: , pg 227-241 ]
  5. 5.0 5.1 5.2 5.3 5.4 "Lars Kolind. The second Cycle. Winning the War Against Burecracy, Wharton School Publishing.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox