Search results

The case presents a $1+billion technology company seeking new growth through the introduction of a radically new product platform. During its first ten years, PTC Corporation grew faster than Microsoft did during the similar period of its evolution. By the late 1990s PTC was faced with intensified competition and saturation in its core markets. To maintain growth, the company introduced a completely new product platform. While PTC focused on developing and selling the product, it failed to recognize that this new product was so different from its traditional offerings that it required a new organizational structure, sales capabilities, support processes, and market strategy. The case traces the company's evolution from development and launch of Windchill through the four-year period post-launch, during which its founding CEO was forced out and the company transformed. Ultimately, Windchill became a top seller for PTC, but not until after significant internal change.

The PTC case illustrates what it means to build a new business within the context of an existing, successful firm. It can also be used to explore what it takes to accomplish a successful new product launch for a substantially new product platform. Sales and channel strategy also figures prominently in the case.

Agile software development, Knowledge workers and Lean thinking as a management system

The case lends itself to students of business management, or aspiring consultants, who have been exposed to operations management in general and Lean thinking specifically. It is an advanced case study, assuming prior knowledge in these subjects and approaches the subject matter from an organisational development point of view, rather than a pure operations point of view. It is thus well suited to an elective on operational excellence on an MBA or in executive education courses in Lean thinking

The case starts with Mark, manager of a software development team, hearing that he will have budget for two new developers who will join his team in the coming year. While the extra help could be useful, he was considering what the impact of new people would be on the productivity of the team, which he felt was already stretched. Mark continues to consider the entire development chain and how code changes were implemented to ACSESim’s (the company’s primary product) graphical user interfaces. Having recently been acquired by an American company, he was also under pressure to start to adopt some of the parent company’s systems, which would constitute a fairly disruptive, but necessary, change, particularly for future collaborations with other developers in the parent company. With two new developers, experience taught Mark that development could slow down owing to training efforts. To minimise disruption, he was wondering about how to get the new developers up-to-speed quickly and streamline their operations within a changing corporate environment. The case highlights the different mechanisms that were in place at ACSESim, including the use of issue trackers; Kanban boards; version control software; automated systems; stand-up meetings, etc. Each of these mechanisms is discussed briefly and shows the value they added to the development practices that were in place. This also allows students to understand Agile practices and what Lean thinking might mean in a knowledge work environment and then to consider what the proposed changes might mean and how they could be deployed.

To gain an understanding of how Lean and Agile principles can be applied in a software development environment and Lean knowledge work in general To consider the best way to manage new hires so that they can become productive in a Lean or Agile software development environment, whilst dealing with pressures to migrate to new systems.

Teaching notes are available for educators only. Please contact your library to gain login details or email support@emeraldinsight.com to request teaching notes.

CSS: 9: Operations and Logistics.

Lewis Byrd, a partner in the private equity firm Opportunity Capital Partners, is managing a number of interconnected issues. First, in his role as investment professional responsible for the firm's investment in a doghouse manufacturing company called Dogloo, he has to manage a relationship with an entrepreneur who has behaved in a way that has made coinvestors nervous about his skills as a CEO. The CEO, Aurelio Barretto, is a Cuban immigrant who has established a close confiding relationship with Byrd, who is an African American. Barretto has increasingly relied on Byrd to run interference for him with investors, while also providing the strategic advice that typically supports an investor-entrepreneur relationship. Another issue is that there is a potentially costly lawsuit looming involving copyright infringement by a larger, well-funded competitor in the pet products market. Byrd has to manage potentially volatile relationships while determining what's best for his firm from an investment standpoint and how best to advise Barretto to proceed. The case provides insights into the challenges in private equity investing that occur after the striking of the financial deal. The case also provides information for students about the technical and legal structure of private equity financing.

This case describes how eight entrepreneurs discover different opportunities for new businesses to exploit a single technological invention. The case focuses on the process of entrepreneurial discovery and its implications for the creation of new firms. Many of the teaching materials on entrepreneurship assume that entrepreneurs have already discovered an opportunity. While these materials provide useful information about the process of creating new enterprises, they miss the crucial first step in the entrepreneurial process: identifying an opportunity. The case illustrates the theoretical concept of the role of information in the discovery of entrepreneurial opportunities. It can be used in a class on entrepreneurship or management of technology.

Strategic decision making, strategic alternatives.

This case is suitable for undergraduate and postgraduate business and management, MBA programs; the case could be used in strategic management, strategic analysis methods, change management courses.

This case illustrates how Storm, a small innovation company located in the city of Novosibirsk, Russia, tackled the problem of future development. The company was set up in 1992 by young scientists to produce equipment for automatic process control systems in power engineering. All the engineering solutions were based on the developments of the company's founders. Currently Storm is the regional leader in creating engineering complexes for power generating companies. However, because of the drastic changes in the business environment and increased market competition, the company faced the challenge of further development. The company's management and owners saw the further development prospects and risks differently. Three strategic alternatives are available and the company is required to choose one of them, substantiating the choice made.

After completing the case study assignment, learners should be able to: state the strategic problems of small business development; identify the challenges of the external environment for company development; apply the tools of strategic analysis for evaluation of the company's market position; analyze the company's internal strengths and weaknesses; and elaborate and evaluate strategic alternatives for the company's growth.

Teaching notes are available – consult your librarian for access.

The application of activity based costing (ABC); calculating the cost of a CNC Process using ABC; designing a pricing strategy.

The case can be used in the following courses: MBA program with specialisation in finance (to teach students the application of costing in services sector); MBA program in general management (to highlight the concept of activity based costing and its application); and under an elective course on management control systems in MBA programs (to highlight the strategy to determine price effectively).

The case highlights the application of activity based costing in arriving at cost and finally leading to development of price to be charged by KK Metals. The company wishes to compute the activity based cost of CNC process and develop the selling price for 194 precision turning services scientifically as opposed to the present strategy of being a price taker, largely on the basis of what essentially is prevalent in the local market within which KK Metals operates. The case gives an insight to numerous control variables that the management can consider while pricing its services.

The case can be used to understand management concepts such as ABC, pricing and the role of efficiency in business processes. It can be used to: teach complexities involved in identifying activity driver(s) in case of ABC as far as application to service sector is concerned; help understand the use of costing as an effective tool in pricing strategy of the company; and help students realize the significance of inputs used for calculating per hour cost.

Teaching notes are available. Consult your librarian for access.

Pebble Technology Corporation (Pebble) was an early entrant into the smartwatch industry. Pebble’s Founder, Eric Migicovsky, began thinking about creating a smartwatch in 2008 while still an undergraduate engineering student. After selling about 1,500 prototype watches, he was accepted into Silicon Valley’s prestigious Y Combinator business start-up program. Finding it difficult to attract investors, Migicovsky launched a crowdfunding campaign that raised a record-breaking $10.27m on Kickstarter. The case concludes shortly after Apple’s unveiling of its soon-to-be-released Apple Watch. The case provides an opportunity to evaluate Pebble’s various strategic options at the time of Apple’s announcement.

The authors observed over 30 h of video and audio recordings of speeches, interviews and other events involving Pebble’s founder, other Pebble executives, investors and competitors. These recordings are all publicly available. Whenever possible, the authors also reviewed the Twitter feeds, Facebook sites and personal websites of Pebble’s top executives over time. Similarly, the authors followed Pebble’s official website, corporate blog and Kickstarter campaign websites. The authors also drew from numerous media reports. Due to the public nature of the data, no company release is provided nor has any information been disguised in any way.

The case is designed for both undergraduate and graduate students for courses in strategic management.

After completion of the case study, the students will be able to understand the importance of being culturally savvy when working in a culturally diverse environment and managing people from different cultures; critically reflect on the risks resulting from the absence of a clear direction from the company’s top management regarding unifying corporate values and a diversity policy for cooperation across cultures; be aware of best practices in implementing diversity management (DM) initiatives in the company; and learn that changes in the strategic orientation (i.e. focus on automation projects) must be cascaded down to hard elements of structures, processes and systems, as well as to soft elements of skills, staff and management style.

The Kuwaiti branch of a Japanese corporation specialising in control systems and instruments, Rising Sun IT, hired a German professional, Alex, to handle the increasing demand for automation from customers. This recruitment followed several unsuccessful attempts by the company to deliver more advanced automation solutions. Recognising the need to adapt to Kuwaiti customer requirements or risk losing market share, Japanese management understood the importance of transforming their engineering staff. Failure to achieve this next automation step would result in a steady decline in market share and ultimately impact the company’s survival. However, Alex, who was supposed to lead automation projects, was confronted with opposition from the Indian engineering staff and managers. He was not able to find common ground with the staff and perceived issues such as lack of communication, delays in work schedules, missed deadlines and high levels of absenteeism, as a sign of low work morale. Although he tried to increase the awareness of his supervisor and other managers by informing them repeatedly about the problems regarding employee behaviours, his interventions went unheard. He felt ousted by his fellow colleagues and the other employees. Besides, from Alex’s point of view, the Japanese top management did not provide clear directions to the staff and explicit support to Alex in his efforts. This case study highlights three dimensions of Alex’s problem with establishing and maintaining working relationships with other people in the company:▪ Alex’s cultural “blindness” and ignorance of differences in work behaviours that ultimately led to his inability to build solid and trustful relationships with other employees. The case study demonstrates Germany’s performance-oriented and individual-centric culture versus India’s family- and community-oriented culture and the Japanese employees’ strongly hierarchical and company loyalty-oriented culture.▪ Lack of support from the Japanese top management to Alex, which is connected with a wider problem of the lack of a systematic strategic approach to managing a culturally diverse workforce. The case study pinpoints the rhetoric–reality gap in DM in the company, where the diversity, equity and inclusion programme and corporate values were applied only formally and had little attention from the leaders as well as non-managerial employees.▪ Employee resistance to change: The lack of positive communication from the top management level in the company regarding automation projects and the lack of support for Alex’s mission in the company resulted in steady resistance to executing projects, which endangered the company’s survival in the market. Also, one part of Alex’s problem with building a working relationship with the Indian engineering staff was based on the fact that others perceived him as the automation “change agent” – an advocate and catalyst of an undesirable change connected with adverse consequences on employment in the Indian community.

This case is intended for discussion in undergraduate management and business study programmes.

Teaching notes are available for educators only.

CSS 6: Human resource management.

This case is about Kija Kim, a Korean born founder and CEO of Harvard Design and Mapping Inc. (HDM). Founded in 1988, HDM is a cutting-edge GIS firm with $5 million in revenue and 35 employees in their Cambridge, MA and Washington D.C. offices. Through Kija Kim's leadership, HDM has become a significant niche player in homeland security and disaster relief. The case ends in fall 2005 just after HDM provided Hurricane Katrina mapping support, and Kija is nominated for the SBA Small Business Person of the Year. This case explores the intersection between cultural heritage, leadership effectiveness and organizational behavior. It particularly notes Kija's ability to turn her immigrant female minority status into a business advantage. This strength coupled with her ethos of care and ability to network in all walks of her life contributes to her distinctive and integrated leadership style. Definitions of leadership success and implications for decision making are also highlighted.

In mid-1992, Christine Olsen, the chief financial officer (CFO) of this large CAD/CAM equipment manufacturer, must decide on the magnitude of the firm's dividend payout. A subsidiary question is whether the firm should embark on a campaign of corporate-image advertising and change its corporate name to reflect its new outlook. The case serves as an omnibus review of the many practical aspects of the dividend decision, including (1) signaling effects, (2) clientele effects, and (3) finance and investment implications of increasing dividend payout.