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.
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".
Management fads are often characterized by the following:
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]
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:
Software development is the process used to create software. Programming and maintaining the source code is the central step of this process, but it also includes conceiving the project, evaluating its feasibility, analyzing the business requirements, software design, testing, to release. Software engineering, in addition to development, also includes project management, employee management, and other overhead functions. Software development may be sequential, in which each step is complete before the next begins, but iterative development methods where multiple steps can be executed at once and earlier steps can be revisited have also been devised to improve flexibility, efficiency, and scheduling.
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.
The incremental build model is a method of software development where the product is designed, implemented, and tested incrementally until the product is finished. It involves both development and maintenance. The product is defined as finished when it satisfies all of its requirements. This model combines the elements of the waterfall model with the iterative philosophy of prototyping. According to the Project Management Institute, an incremental approach is an "adaptive development approach in which the deliverable is produced successively, adding functionality until the deliverable contains the necessary and sufficient capability to be considered complete."
CollabNet VersionOne is a software company founded by Tim O’Reilly, Brian Behlendorf, and Bill Portelli, headquartered in Alpharetta, Georgia, United States. CollabNet focuses on value stream management, DevOps, agile management, application lifecycle management (ALM), and enterprise version control.
An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models – typically matrices and diagrams – for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.
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.
Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
UNICOM Focal Point is a portfolio management and decision analysis tool used by the product organizations of corporations and government agencies to collect information and feedback from internal and external stakeholders on the value of applications, products, systems, technologies, capabilities, ideas, and other organizational artifacts—prioritize on which ones will provide the most value to the business, and manage the roadmap of how artifacts will be fielded, improved, or removed from the market or organization. UNICOM Focal Point is also used to manage a portfolio of projects, to understand resources used on those projects, and timelines for completion. The product is also used for pure product management—where product managers use it to gather and analyze enhancement requests from customers to decide on what features to put in a product, and develop roadmaps for future product versions.
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.
Christopher O'Malley is the president and CEO of LogRhythm an American security software company headquartered in Broomfield, Colorado.
Infrastructure as code (IaC) is the process of managing and provisioning computer data center resources through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. The IT infrastructure managed by this process comprises both physical equipment, such as bare-metal servers, as well as virtual machines, and associated configuration resources. The definitions may be in a version control system, rather than maintaining the code through manual processes. The code in the definition files may use either scripts or declarative definitions, but IaC more often employs declarative approaches.
A DevOps toolchain is a set or combination of tools that aid in the delivery, development, and management of software applications throughout the systems development life cycle, as coordinated by an organisation that uses DevOps practices.
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.
ModelOps, as defined by Gartner, "is focused primarily on the governance and lifecycle management of a wide range of operationalized artificial intelligence (AI) and decision models, including machine learning, knowledge graphs, rules, optimization, linguistic and agent-based models". "ModelOps lies at the heart of any enterprise AI strategy". It orchestrates the model lifecycles of all models in production across the entire enterprise, from putting a model into production, then evaluating and updating the resulting application according to a set of governance rules, including both technical and business key performance indicators (KPI's). It grants business domain experts the capability to evaluate AI models in production, independent of data scientists.
DevOps Research and Assessment is a team that is part of Google Cloud that engages in opinion polling of software engineers to conduct research for the DevOps movement.
Business journalists [...] participate in the creation of management fads and fashions, and provide platforms or sounding boards for the teachings [...].
[...] 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.
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.
Arguably, it was a mistake for the public sector to try to ape the transformational leadership fad that dominated some private companies.
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.
[...] yet another management fad in the style of the Tao of Leadership [...]
For a critique of the practice of branding new management ideas as fads, see
For a listicle see: