Wikipedia

Management system (open source)

Management System (Open Source) is a socio-technical system that leverages the cumulative knowledge of management practitioners and evidenced based research from the past 130 years.[1][2][3][4] The system was developed by DoD components in partnership with industry experts[5][6] and academic researchers and builds off of the US Department of Wars version 1.0 open source management system - Training Within Industry.

Management System (Open Source)
DeveloperDoD Components (Industry & Academic Partnerships)
OS familyIntegrates major elements of Toyota Production System
Source modelAttribution-ShareAlike 4.0 International (CC BY-SA 4.0)
Initial releaseJune 29, 1939; 85 years ago (1939-06-29) (Training Within Industry)
Latest releaseJune 29, 2019; 5 years ago (2019-06-29)
Repository'Management System 3.1'
Marketing target
  • Organizational Manager
  • Functional Manager
  • Program Manager
  • Team Manager
  • Individual Manager ("manage your career")

The system integrates the four organizational components of Product, Structure, Process and People. In addition, the system is based on the 4 capabilities of rapid problem solving underlying the Toyota Production System:[1]

  1. Design and Operate Work to See Problems (See Problems).
  2. Solve Problems Close in Person, Place & Time (Solve Problems).
  3. Capture and Share Knowledge from solving those problems (Share Knowledge).
  4. Managers Coach their Team in capabilities 1-3 (Managers Coach).

Derived from the original research of Steven J. Spear (Harvard Business School, Massachusetts Institute for Technology),[7] the system balances the two dimensions of high performing organizations: integrate the whole (product, structure, process & people); and increase the rate of problem solving to manage the whole (4 capabilities outlined above).[1][8]

Fundamentally, the system sets the standards of management by outlining a doctrine of rules, tactics, techniques, procedures & terms. The standards are intended to motivate change by creating a tension between the organization's "current condition" and the "ideal condition" (i.e. True North).[9]

The objective of the system is to deliver more value, in less time, at less cost relative to the competition (better, faster, cheaper).[3] For the DoD, competition is defined by the threats posed by current and potential adversaries.

Open Source (Many Names)

edit

Over the last 25 years, the US Department of Defense has leveraged evidence based research in their attempt to improve the management capability of the Department. DoD's need for change comes from an increased threat of adversaries and the requirement to improve their effectiveness and efficiency.[10] This requirement to improve effectiveness and efficiency comes from established laws for "achieving an integrated management system for business support areas within the Department of Defense" (e.g. Government Performance and Results Act of 1993 and section 904 of Public Law 110-181 of the National Defense Authorization Act 2008).

The concept of open source promotes a free exchange of ideas within the DoD community to drive creative, scientific and technological advancement. The Management System (Open Source) is a reference model that captures the underlying doctrine driving many of the DoD's efforts to improve. For example, the Chief of Naval Operations line of effort called High Velocity Learning is based on the 4 capabilities outlined above. In addition, The Distribution Management System is based on those same underlying capabilities.[6][11] Given that many programs come and go, it is important that the Department of Defense captures and shares the underlying doctrine of management that evidenced based research shows to be valid for producing high performance organizations.

Management Matters

edit

"When we take stock of the productivity gains that drive our prosperity, technology gets all the credit. In fact, management is doing a lot of the heavy lifting" (Joan Magretta, Harvard Business School).[12] A growing body of evidence based research is showing the correlation and causation of management's impact on organizational performance (productivity, growth, patents, profit, ROIC, etc.).[13][14][15][16]

The Management System (Open Source) is based on this body of research and managerial practice. The research findings is best captured by Clayton Christensen, former Kim B. Clark Professor of Business Administration at the Harvard Business School (HBS): "Management is the most noble of professions if it's practiced well. No other occupation offers as many ways to help others learn and grow, take responsibility and be recognized for achievement, and contribute to the success of a team."

As a result, the system establishes the "practice routines" for the management profession. Evidenced based research in the field of practice shows that "practice makes permanent, so practice perfect".[17] This is echoed in Vince Lombardi's admonishment - "Practice does not make perfect. Only perfect practice makes perfect". Therefore, the Management System outlines the practice routines that enable the profession to engage in daily and "deliberate practice"[18][19] To be successful in the profession of management (as outlined by the Management System), the daily and deliberate practice routines require a manager to commit to three fundamental values: Respect for People, Continuous Improvement, and Customer First (similar to those stated in the Toyota Production System).[20]

Doctrine of Management

edit

The Management System is a doctrine that outlines the fundamental rules, with supporting tactics, techniques, procedures and terms used for the conduct of managerial work in support of the DoD component's objectives.[21] It is authoritative but requires judgment in application. Each organizational element of Product, Structure, Process and People outline the standards of management using the following construct:

  • Rule: An explicit and validated instruction governing the thinking and actions of managerial work (i.e. how to think and what to do). Validated means proven true in a given circumstance.
  • Tactic:  The employment and ordered arrangement of elements (e.g., products, structures, processes and people) in relation to each other in order to achieve an objective.  Employing a tactic may require integrating several techniques and procedures.
  • Techniques:  Effective and/or efficient methods used to perform tasks. Managers choose specific techniques based on the circumstance and objectives established.
  • Procedures:  Standard and detailed steps that prescribe how to perform specific tasks.  They consist of a series of steps in a set order that are completed in the same way, regardless of circumstance.
  • Terms:  The words and definitions used in the conduct of managerial work.

Underlying Research

edit
  • Product: The doctrine of product is heavily shaped by the research of Clayton Christensen (disruptive vs. sustaining innovation, job to be done), Michael Porter (competitive advantage for creating & capturing value) and Donald G. Reinertsen (cost of delay, the invisible product architecture).[3][2][22]
  • Structure: The doctrine of structure is heavily shaped by the research of Elliot Jaques (level of work, accountabilities & authorities) and Alfred D Chandler Jr. ("structure follows strategy").[23][24]
  • Process: The doctrine of process is heavily shaped by the research of Steven J. Spear (rules in use - decoding the DNA of Toyota).[9][25]
  • People: The doctrine of people is heavily shaped by the research of Chris Argyris (model I & II theory in use, ladder of inference, inquiry & advocacy) and Elliot Jaques (potential capability: commitment, problem solving capacity, knowledge & temperament).[4][26][27]

Underlying Management Practitioners

edit
  • Product: The advancement and application of product doctrine is best represented by Thomas Edison (phonograph, motion picture camera, practical electric light bulb) and Steve Jobs (Mac, iMac, Pixar, iPod, iTunes, iPhone, iPad).[28][29]
  • Structure: The advancement and application of structure doctrine is best represented by Andy Grove ("guy who drove the growth phase of Silicon Valley") and Hyman G. Rickover ("Father of the Nuclear Navy").[30][31]
  • Process: The advancement and application of process doctrine is best represented by Taiichi Ohno ("father of the Toyota Production System") and Henry Ford (continuous flow production).[32][33]
  • People: The advancement and application of people doctrine is best represented by all of the above management practitioners: Taiichi Ohno (adoption of Training Within Industry), Thomas Edison ("organized science and teamwork to the process of invention"), Steve Jobs (challenged people and whole industries to "Think Different"), Henry Ford (pioneer of "welfare capitalism"), Andy Grove ("training is the boss's job"...and training takes place between people..."meetings are the medium of management"), Hyman G. Rickover (his legacy of people development and technical achievement is undeniable: "United States Navy's continuing record of zero reactor accidents").

Organizational Components (Rules - TTPs)

edit

Product (Rule Statement, TTPs, Ideal Condition)

edit

Rule Statement: Prioritize and develop products (or services) that solve the customer's “job to be done” with no “cost of delay”.

  • Job to Be Done: TTP's to understand the motivation for why customers hire or fire products to help them get their job done.[34][35]
  • Market Time (Cost of Delay): TTP's to measure the time it takes to respond to market opportunities; and to prioritize development decisions by calculating the impact of time on value creation & capture.[36][37]
  • Create Value: TTP's to enable strategic choice by 1) classifying the type of product you are developing and 2) how to position it for competitive advantage.[38][39]
  • Capture Value: TTP's to capture a portion of the value you create in order to have a sustainable business model that continues to create value.[40]

Ideal Condition:[36][3]

Products designed and delivered that generate:

100% Value Creation

  • Perfect Customer Satisfaction
  • 0 “Cost of Delay” (customer impact)

100% Value Capture

  • Revenue, Resources, Profits, Units
  • 0 “Cost of Delay” (organization impact)

Structure (Rule Statement, TTPs, Ideal Condition)

edit

Rule Statement: Structure the role relationships (vertical and functional) to solve problems that deliver products of value.[41]

  • Takt Time (Problems): TTP's to determine the demand on the structure to meet the “expected scope & frequency of problems” to manage the cross-functional flow of product (think Andon system).[1][42]
  • Role Alignment: TTP's to establish the vertical and functional groupings of work to meet the demand of problem solving.[4]
  • Role Relationship: TTP's to define authorities and accountabilities required for effective vertical and cross-functional role relationships.[43][44]
  • Role Responsibilities: TTP's to define the specific role responsibilities (how & what).[4][45]

Ideal Condition:[4]

Roles aligned and structured for:

  • Clear Communication
  • Perfect Information
  • Effective Decision Making
  • Disciplined Problem Solving
  • Clear Accountabilities & Authorities

Process (Rule Statement, TTPs, Ideal Condition)

edit

Rule Statement: Develop the process to deliver “just in time” (right product, right qty, right time, right cost).

  • Takt Time (Product): TTP's to set the pace of production to match pace of customer demand (net available time / customer demand).[42][46]
  • One Piece Flow: TTP's to produce and move one product at a time (or in small batches) continuously across processing steps.[7][47]
  • Level Pull: TTP's to level the type & quantity of production over a fixed period of time; and a pull method of production control where downstream activities signal their needs to upstream activities.[48][49]
  • Standard Work: TTP's to define current best method for performing an activity (standard sequence, standard WIP and standard time).[9][50]

Ideal Condition:[1]

Process that produce and deliver the product:

  • On-demand (actual customer pull)
  • No waiting (0 lead-time)
  • Zero Defect
  • Perfect Safety (physical, emotional, professional)
  • No Waste (over production, over processing, transport, inventory, movement, waiting, rework/defect)

People (Rule Statement, TTPs, Ideal Condition)

edit

Rule Statement: Develop and deliver capable people “just in time” (right role, right qty, right time).

  • Takt Time (People): TTP's to set the pace of developing capable people to match the pace of demand (roles to be filled).[42][51]
  • Assess the People: TTP's to assess the applied capability of people in their current role and potential capability for their future role.[43]
  • Develop the People: TTP's to develop the capability of people for their current role (coaching) and for future roles (mentoring).[52]
  • Source the People: TTP's to source people capable of being developed to fill current and future roles (outlined in “role responsibility”).[4]

Ideal Condition:[43]

Process that develops and delivers people capable for the role:

  • Commitment to the role
  • Problem solving capacity
  • Knowledge and Abilities
  • Positive Temperament (no minus T)

Limitations

edit

"All models are wrong, but some are useful", George E. P. Box. Business research has the potential of falling victim to what Phil Rosenzweig outlines in his book "The Halo Effect" (a book that criticizes pseudoscientific tendencies in the explanation of business performance). The Management System (Open Source) states that it leverages evidenced based research, but in reality, all research can fall victim to some of the below effects.[53]

  1. The Halo Effect: the cognitive bias in which the perception of one quality is contaminated by a more readily available quality (for example good-looking people being rated as more intelligent).In the context of business, observers think they are making judgements of a company's customer-focus, quality of leadership or other virtues, but their judgement is contaminated by indicators of company performance such as share price or profitability. Correlations of, for example, customer-focus with business success then become meaningless, because success was the basis for the measure of customer focus.
  2. The Delusion of Correlation and Causality: mistakenly thinking that correlation is causation.
  3. The Delusion of Single Explanations: arguments that factor X improves performance by 40% and factor Y improves by another 40%, so both at once will result in an 80% improvement. The fallacy is that X and Y might be very strongly correlated. E.g. X might improve performance by causing Y.
  4. The Delusion of Connecting the Winning Dots: looking only at successful companies and finding their common features, without comparing them against unsuccessful companies.
  5. The Delusion of Rigorous Research: Some authors boast of the amount of data that they have collected, as though that in itself made the conclusions of the research valid.
  6. The Delusion of Lasting Success: the "secrets of success" books imply that lasting success is achievable, if only managers will follow their recommended approach. Rosenzweig argues that truly lasting success (outperforming the market for more than a generation) never happens in business.
  7. The Delusion of Absolute Performance: market performance is down to what competitors do as well as what the company itself does. A company can do everything right and yet still fall behind.
  8. The Delusion of the Wrong End of the Stick: getting cause the wrong way round. E.g. successful companies have a Corporate Social Responsibility policy. Should we infer that CSR contributes to success, or that profitable companies have money to spend on CSR?
  9. The Delusion of Organisational Physics: the idea that business performance is non-chaotically determined by discoverable factors, so that there are rules for success out there if only we can find them.

References

edit
  1. ^ a b c d e Spear, Steven J. (2009). Chasing the rabbit : how market leaders outdistance the competition and how great companies can catch up and win. McGraw-Hill. ISBN 978-0-07-164151-7. OCLC 285255407.
  2. ^ a b Christensen, Clayton (2016). The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail. Harvard Business Review Press. ISBN 978-1-63369-178-0. OCLC 911172216.
  3. ^ a b c d Porter, Michael E. (2014). Competitive Strategy: Techniques for Analyzing Industries and Competitors. Free Press. ISBN 978-1-4165-9035-4. OCLC 893101158.
  4. ^ a b c d e f Jaques, Elliott, editor. (5 July 2017). Requisite Organization: A Total System for Effective Managerial Organization and Managerial Leadership for the 21st Century. Routledge. ISBN 978-1-351-55132-8. OCLC 994220939. {{cite book}}: |last= has generic name (help)CS1 maint: multiple names: authors list (link)
  5. ^ "Sources Sought: Management System for DoD component".
  6. ^ a b Defense Industry Daily staff. "Industry Partner to help DoD". Defense Industry Daily.
  7. ^ a b Spear, Steven J. "The Essence of Just In Time". Production Planning & Control: The Management of Operations. 13, 2002 - Issue 8. doi:10.1080/0953728031000057307. S2CID 110452138.
  8. ^ "Designing Products and Processes".
  9. ^ a b c Spear, Steven J (September–October 1999). "Decoding the DNA of the Toyota Production System". Harvard Business Review.
  10. ^ "DoD Agency Strategic Plan" (PDF).
  11. ^ "Management System at DLA".
  12. ^ Magretta, Joan. (2014). What management is. Free Press. ISBN 978-0-7432-4224-0. OCLC 893122625.
  13. ^ "Management Matters Most for Corporate Performance". June 2019. doi:10.13007/744. S2CID 242842030. {{cite journal}}: Cite journal requires |journal= (help)
  14. ^ Bloom, Nicholas; Reenen, John Van; Brynjolfsson, Erik (2017-04-19). "Good Management Predicts a Firm's Success Better Than IT, R&D, or Even Employee Skills". Harvard Business Review. ISSN 0017-8012. Retrieved 2020-03-23.
  15. ^ "Why management matters for productivity | McKinsey". www.mckinsey.com. Retrieved 2020-03-23.
  16. ^ "Other researchers' work – World Management Survey". Retrieved 2020-03-23.
  17. ^ Ericsson, K. Anders; Prietula, Michael J.; Cokely, Edward T. (2007-07-01). "The Making of an Expert". Harvard Business Review. No. July–August 2007. ISSN 0017-8012. Retrieved 2020-03-24.
  18. ^ Colvin, Geoffrey, author, narrator., Talent is overrated : what really separates world-class performers from everybody else, ISBN 978-0-593-17235-3, OCLC 1128992519 {{citation}}: |last= has generic name (help)CS1 maint: multiple names: authors list (link)
  19. ^ "Practice Doesn't Make Perfect; Perfect Practice Makes Perfect". Scientific Bulletin of Naval Academy. 19 (2). 2016-12-15. doi:10.21279/1454-864x-16-i2-065. ISSN 2392-8956.
  20. ^ "The Toyota Way: our values and way of working". www.toyota-europe.com. Retrieved 2020-03-24.
  21. ^ "What is Army Doctrine". 22 March 2016.
  22. ^ Christensen, Clayton M., author. (21 October 2016). The innovator's prescription : a disruptive solution for health care. McGraw-Hill Education. ISBN 978-1-259-86086-7. OCLC 950637388. {{cite book}}: |last= has generic name (help)CS1 maint: multiple names: authors list (link)
  23. ^ Chandler, Alfred Dupont, 1918-2007. (2013). Strategy and structure : chapters in the history of the industrial enterprise. Martino Publ. ISBN 978-1-61427-508-4. OCLC 897495577.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  24. ^ Jaques, Elliot. (1982). The form of time. Crane-Russak. ISBN 0-8448-1394-X. OCLC 797221444.
  25. ^ Spear, Steven. (2017). Fast discovery : the imperative for high velocity learning by everyone, about everything, all of the time. Health Foundation. ISBN 978-1-906461-87-4. OCLC 994682016.
  26. ^ Argyris, Chris, 1923 - 2013, VerfasserIn. Integrating the individual and the organization. ISBN 978-1-351-51217-6. OCLC 1015834129. {{cite book}}: |last= has generic name (help)CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  27. ^ Argyris, Chris (2004-03-25). Reasons and Rationalizations. Oxford University Press. doi:10.1093/acprof:oso/9780199268078.001.0001. ISBN 978-0-19-926807-8.
  28. ^ Brooks, William; Frow, George L. (2001), "Edison, Thomas", Oxford Music Online, Oxford University Press, doi:10.1093/gmo/9781561592630.article.08549
  29. ^ Jobs, Steve, 1955-2011. (2011). I, Steve : Steve Jobs in his own words. Hardie Grant. ISBN 978-1-74270-358-9. OCLC 759584923.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  30. ^ Grove, Andrew S., author. High output management. OCLC 949269580. {{cite book}}: |last= has generic name (help)CS1 maint: multiple names: authors list (link)
  31. ^ Duncan, Francis (February 2000). Rickover, Hyman George (1900-1986), nuclear engineer and naval officer. American National Biography Online. Oxford University Press. doi:10.1093/anb/9780198606697.article.1301389.
  32. ^ Ford, Henry, 1863-1947. (2019). My life and work. OCLC 1104208330.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  33. ^ Ohno, Taiichi; Bodek, Norman (2019-12-17). Toyota Production System. doi:10.4324/9780429273018. ISBN 9780429273018.
  34. ^ Christensen, Clayton M. Hall, Taddy Dillon, Karen Duncan, David S. Pruden, John., Competing Against Luck : The Story of Innovation and Customer Choice., ISBN 1-4417-3978-5, OCLC 957652628{{citation}}: CS1 maint: multiple names: authors list (link)
  35. ^ Chris Spiek and Bob Moesta, with Ervin Fowlkes (2014). Jobs-to-be-Done The Handbook: Practical Techniques for Improving your Application of Jobs-to-be-Done. [Middletown, Delaware]. ISBN 978-1-4993-3923-9. OCLC 957571178.{{cite book}}: CS1 maint: location missing publisher (link)
  36. ^ a b Reinertsen, Donald (2009). The Principles of Product Development Flow. Redondo Beach, CA 90277: Celeritas Publishing. ISBN 9781935401001.{{cite book}}: CS1 maint: location (link)
  37. ^ "Cost of Delay". Black Swan Farming.
  38. ^ Christensen, Clayton (2013). The Innovator's Solution: Creating and Sustaining Successful Growth. Perseus Book LLC (Ingram). ISBN 978-1-4221-9658-8. OCLC 1024281603.
  39. ^ Porter, Michael (1996). "What is Strategy?". Harvard Business Review. November–December 1996.
  40. ^ Osterwalder, Alexander (2010). Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers. Pigneur, Yves,, Clark, Tim, 1956-, Smith, Alan (Designer). Hoboken, New Jersey: John Wiley & Sons Inc. ISBN 978-0-470-87641-1. OCLC 648031756.
  41. ^ Spear, Steven J (1999). THE TOYOTA PRODUCTION SYSTEM: AN EXAMPLE OF MANAGING COMPLEX SOCIAL/TECHNICAL SYSTEMS 5 RULES FOR DESIGNING, OPERATING, AND IMPROVING ACTIVITIES, ACTIVITY-CONNECTIONS, AND FLOW-PATHS. HARVARD UNIVERSITY GRADUATE SCHOOL OF BUSINESS ADMINISTRATION George F. Baker Foundation.
  42. ^ a b c Ōhno, Taiichi (1988). Toyota Production System: Beyond Large-Scale Production. CRC Press Taylor & Francis Group. pp. Boca Raton, FL 33487. ISBN 978-1-000-05648-8. OCLC 1140155660.
  43. ^ a b c Jaques, Elliott (1994). Human capability: A Study of Individual Potential and its Application. Falls Church, VA: Cason Hall & Co. ISBN 978-0962107078.
  44. ^ Capelle, Ronald G. (2013). Optimizing Organization Design: A Proven Approach to Enhance Financial Performance, Customer Satisfaction and Employee Engagement. Jossey-Bass, a Wiley brand. ISBN 978-1118763735.
  45. ^ Stephen D. Clement & Christopher R. Clement (2013). It's All about Work. Organizing Your Company to Get Work Done. Organizational Design Inc. ISBN 978-0988639607.
  46. ^ Liker, Jeffrey K. (2013). Toyota way : 14 management principles from the world's greatest manufacturer. McGraw-Hill. ISBN 978-0-07-139231-0. OCLC 868002276.
  47. ^ Liker, Jeffrey K. (2007). Toyota talent : developing your people the Toyota way. McGraw-Hill. ISBN 978-0-07-150994-7. OCLC 290489200.
  48. ^ Jeffrey Liker, David Meier (2006). The Toyota Way Fieldbook: A Practical Guide for Implementing Toyota's 4Ps. McGraw-Hill. ISBN 978-0071448932.
  49. ^ Locher, Drew. (2011). Lean office and service simplified : the definitive how-to guide. CRC Press/Taylor & Francis Group. ISBN 978-1-4398-2031-5. OCLC 713843790.
  50. ^ Lean Production Simplified, Second Edition. 2007-03-02. doi:10.1201/b17932. ISBN 9781439852545.
  51. ^ Womack, James S. Jones, Daniel T. Roos, Daniel. (2007). The Machine that changed the world. Simon & Schuster. ISBN 978-1-84737-055-6. OCLC 966108262.{{cite book}}: CS1 maint: multiple names: authors list (link)
  52. ^ Liker, Jeffrey K. Meier, David P. (2007), Toyota Talent: Developing your People the Toyota Way, McGraw-Hill, ISBN 978-0-07-147745-1, OCLC 481275535{{citation}}: CS1 maint: multiple names: authors list (link)
  53. ^ Rosenzweig, Philip M. (2014). The halo effect ... and the eight other business delusions that deceive managers. Free Press. ISBN 978-1-4767-8403-8. OCLC 896890481.


edit
Retrieved from "https://en.wikipedia.org/w/index.php?title=Management_system_(open_source)&oldid=1180225853"