Management fad

Last updated

Management fad is a term used to characterize a change in philosophy or operations implemented by a business or institution. It amounts to a fad in the management culture of an institution.

Contents

The term is subjective and tends to be used in a pejorative sense, as it implies that such a change is being implemented (often by management on its employees, with little or no input from them) solely because it is (at the time) "popular" within managerial circles, and not necessarily due to any real need for organizational change. The term further implies that once the underlying philosophy is no longer "popular", it will be replaced by the newest "popular" idea, in the same manner and for the same reason as the previous idea.

Alternatively, the pejorative use of the term expresses a cynical belief that the organization desires change that would be resisted by the rank and file if presented directly, so it is dressed up in a dramatic change of management style, to remain in place only as long as it serves the underlying agenda.

Several authors have argued that new management ideas should be subject to greater critical analysis, and for the need for greater conceptual awareness of new ideas by managers. [1] Authors Leonard J. Ponzi and Michael Koenig believe that a key determinant of whether any management idea is a "management fad" is the number and timing of published articles on the idea. In their research, [2] Ponzi and Koenig argue that once an idea has been discussed for around 3–5 years, if after this time the number of articles on the idea in a given year decreases significantly (similar to the right-hand side of a bell curve), then the idea is most likely a "management fad".

Common characteristics

Management fads are often characterized by the following:

Origins

Consultants and even academics have developed new management ideas. Journalists may popularize new concepts. [3]

Like other fashions, trends in management thought may grow, decline, and recur. Judy Wajcman sees the human relations movement of the 1930s as a precursor of the later fashion of "transformational management". [4]

Examples

The following management theories and practices appeared on a 2004 list of management fashions and fads compiled by Adrian Furnham, [5] who arranged them in rough chronological order by their date of appearance, 1950s to 1990s:

Other theories and practices which observers have tagged as fads include:

See also

Related Research Articles

<span class="mw-page-title-main">Enterprise resource planning</span> Corporate task of optimizing the existing resources in a company

Enterprise resource planning (ERP) is the integrated management of main business processes, often in real-time and mediated by software and technology. ERP is usually referred to as a category of business management software—typically a suite of integrated applications—that an organization can use to collect, store, manage and interpret data from many business activities. ERP systems can be local-based or cloud-based. Cloud-based applications have grown in recent years due to information being readily available from any location with Internet access. Traditional on-premises ERP systems are now considered legacy technology.

<span class="mw-page-title-main">Team</span> Group linked in a common purpose

A team is a group of individuals working together to achieve their goal.

In software development, agile practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s), adaptive planning, evolutionary development, early delivery, continual improvement, and flexible responses to changes in requirements, capacity, and understanding of the problems to be solved. Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.

Enterprise architecture (EA) is a business function concerned with the structures and behaviors of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

Thoughtworks is a publicly owned, global technology company with 49 offices in 18 countries. It provides software design and delivery, and tools and consulting services. The company is closely associated with the movement for agile software development, and has contributed to open source products. Thoughtworks' business includes Digital Product Development Services, Digital Experience and Distributed Agile software development.

Quality management ensures that an organization, product or service consistently functions well. It has four main components: quality planning, quality assurance, quality control and quality improvement. Quality management is focused not only on product and service quality, but also on the means to achieve it. Quality management, therefore, uses quality assurance and control of processes as well as products to achieve more consistent quality. Quality control is also part of quality management. What a customer wants and is willing to pay for it, determines quality. It is a written or unwritten commitment to a known or unknown consumer in the market. Quality can be defined as how well the product performs its intended function.

<span class="mw-page-title-main">Business process re-engineering</span> Business management strategy

Business process re-engineering (BPR) is a business management strategy originally pioneered in the early 1990s, focusing on the analysis and design of workflows and business processes within an organization. BPR aims to help organizations fundamentally rethink how they do their work in order to improve customer service, cut operational costs, and become world-class competitors.

Lean software development is a translation of lean manufacturing principles and practices to the software development domain. Adapted from the Toyota Production System, it is emerging with the support of a pro-lean subculture within the agile community. Lean offers a solid conceptual framework, values and principles, as well as good practices, derived from experience, that support agile organizations.

Genba is a Japanese term meaning "the actual place". Japanese detectives call the crime scene genba, and Japanese TV reporters may refer to themselves as reporting from genba. In business, genba refers to the place where value is created; in manufacturing the genba is the factory floor. It can be any "site" such as a construction site, sales floor or where the service provider interacts directly with the customer.

The enterprise unified process (EUP) is an extended variant of the unified process and was developed by Scott W. Ambler and Larry Constantine in 2000, eventually reworked in 2005 by Ambler, John Nalbone and Michael Vizdos. EUP was originally introduced to overcome some shortages of RUP, namely the lack of production and eventual retirement of a software system. So two phases and several new disciplines were added. EUP sees software development not as a standalone activity, but embedded in the lifecycle of the system, the IT lifecycle of the enterprise and the organization/business lifecycle of the enterprise itself. It deals with software development as seen from the customer's point of view.

CollabNet VersionOne is a software firm headquartered in Alpharetta, Georgia, United States. CollabNet VersionOne products and services belong to the industry categories of value stream management, devops, agile management, application lifecycle management (ALM), and enterprise version control. These products are used by companies and government organizations to reduce the time it takes to create and release software.

James A. Highsmith III is an American software engineer and author of books in the field of software development methodology. He is the creator of Adaptive Software Development, described in his 1999 book "Adaptive Software Development", and winner of the 2000 Jolt Award, and the Stevens Award in 2005. Highsmith was one of the 17 original signatories of the Agile Manifesto, the founding document for agile software development.

Scott W. Ambler is a Canadian software engineer, consultant and author. He is an author of books about the Disciplined Agile Delivery toolkit, the Unified process, Agile software development, the Unified Modeling Language, and Capability Maturity Model (CMM) development.

Business agility refers to rapid, continuous, and systematic evolutionary adaptation and entrepreneurial innovation directed at gaining and maintaining competitive advantage. Business agility can be sustained by maintaining and adapting the goods and services offered to meet with customer demands, adjusting to the marketplace changes in a business environment, and taking advantage of available human resources.

Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; it includes testing and deploying software releases.

DevOps is a methodology in the software development and IT industry. Used as a set of practices and tools, DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle. DevOps is complementary to agile software development; several DevOps aspects came from the agile way of working.

Continuous testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate. Continuous testing was originally proposed as a way of reducing waiting time for feedback to developers by introducing development environment-triggered tests as well as more traditional developer/tester-triggered tests.

Enterprise release management (ERM) is a multi-disciplinary IT governance framework for managing software delivery and software change across multiple departments in a large organization. ERM builds upon release management and combines it with other aspects of IT management including Business-IT alignment, IT service management, IT Governance, and Configuration management. ERM places considerable emphasis on project management and IT portfolio management supporting the orchestration of people, process, and technology across multiple departments and application development teams to deliver large, highly integrated software changes within the context of an IT portfolio.

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.

DataOps is a set of practices, processes and technologies that combines an integrated and process-oriented perspective on data with automation and methods from agile software engineering to improve quality, speed, and collaboration and promote a culture of continuous improvement in the area of data analytics. While DataOps began as a set of best practices, it has now matured to become a new and independent approach to data analytics. DataOps applies to the entire data lifecycle from data preparation to reporting, and recognizes the interconnected nature of the data analytics team and information technology operations.

References

  1. Christensen, Clayton M. and Michael E. Raynor, "Why Hard-Nosed Executives Should Care About Management Theory," Harvard Business Review, Vol. 81, No. 9, Sept. 2003, pp. 66-74.
  2. Ponzi, Leonard J. and Michael Koenig, "Knowledge Management: Another Management Fad?," Information Research, Vol. 8, No. 1, Oct. 2002, paper no. 145.
  3. Clegg, Stewart; Bailey, James Russell, eds. (2008). International Encyclopedia of Organization Studies. Sage eReference. Vol. 1. Los Angeles: SAGE. ISBN   9781412915151 . Retrieved 12 August 2021. Business journalists [...] participate in the creation of management fads and fashions, and provide platforms or sounding boards for the teachings [...].
  4. Wajcman, Judy (3 May 2013). Managing Like a Man: Women and Men in Corporate Management. John Wiley & Sons (published 2013). p. 1915. ISBN   9780745668963 . Retrieved 12 August 2021. [...] participatory involvement was seen as the key characteristic of management during the Human Relations movement of the 1930s and 1940s. Even so, this precursor of the current fashion for 'transformational management' was entirely identified as a male leadership style.
  5. Furnham, Adrian, Management and Myths: Challenging Business Fads, Fallacies and Fashions, Palgrave Macmillan, Basingstoke, U.K., 2004, p. 17.
  6. See also: Levi, Daniel (28 April 2010). "Understanding Teams". Group Dynamics for Teams (3 ed.). Los Angeles: SAGE (published 2010). p. 11. ISBN   9781412977623 . Retrieved 12 August 2021. Teamwork has become a management fad with its own set of problems.
  7. The 8 Stupidest Management Fads of All Time, CBS Money
  8. "Wilson, T.D., "The Nonsense of 'Knowledge Management'," Information Research, Vol. 8, No. 1, Oct. 2002, paper no. 144". Archived from the original on 2017-12-26. Retrieved 2020-03-23.
  9. Kneuper, Ralf (24 August 2018). "Selected Current Trends in Software Processes". Software Processes and Life Cycle Models: An Introduction to Modelling, Using and Managing Agile, Plan-Driven and Hybrid Processes. Switzerland: Springer (published 2018). p. 322. ISBN   9783319988450 . Retrieved 12 August 2021. While there are some that would want to use DevOps for all types of products, applications, and organisations, others see DevOps as the latest fad that may work for small start-ups but not for any 'real' work.
  10. Bratton, John, ed. (10 February 2020). Organizational Leadership. SAGE (published 2020). ISBN   9781529715460 . Retrieved 12 August 2021. Arguably, it was a mistake for the public sector to try to ape the transformational leadership fad that dominated some private companies.
  11. Agile software development#Criticism
  12. "Enterprise Architecture Frameworks: The Fad of the Century", Svyatoslav Kotusev, British Computer Society (BCS), July 2016
  13. "A Comparison of the Top Four Enterprise Architecture Frameworks", Svyatoslav Kotusev, British Computer Society (BCS), July 2021
  14. Kotusev, Svyatoslav (2021) The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment (2nd Edition). Melbourne, Australia: SK Publishing.
  15. Furnham, Adrian (29 October 2012). "Early adopters". The Engaging Manager: The Joy of Management and Being Managed. Springer (published 2012). p. 70. ISBN   9781137273864 . Retrieved 2016-09-17. The catchphrases alone are enough to bring flooding into the memory some of the numerous time-and-money-wasting initiatives that went nowhere. Remember 'empowerment,' now replaced by 'engagement'? Remember 'thriving on chaos' and 'upside-down organizations'? [...] The change-ophile, wannabe consultant or desperate manager often embrace every new fad around.
  16. James, Geoffrey (2018-07-16). "It's Official: Open-Plan Offices Are Now the Dumbest Management Fad of All Time". Inc.com. Retrieved 2019-04-10.
  17. 1 2 James, Geoffrey (2013-05-10). "World's Worst Management Fads". Inc.com. Retrieved 2019-04-10.
  18. Cole, Mark; Higgins, John (15 August 2021). Leadership Unravelled: The Faulty Thinking Behind Modern Management. Routledge (published 2021). ISBN   9781000406849 . Retrieved 12 August 2021. [...] yet another management fad in the style of the Tao of Leadership [...]

Further reading

For a critique of the practice of branding new management ideas as fads, see

For a listicle see: