"In strategic thinking, one first seeks a clear understanding of the particular character of each element of a situation and then makes the fullest possible use of human brainpower to restructure the elements in the most advantageous way. Phenomena and events in the real word do not always fit a linear model. Hence the most reliable means of dissecting a situation into its constituent parts and reassembling then in the desired pattern is not a step-by-step methodology such as systems analysis. Rather, it is that ultimate nonlinear thinking tool, the human brain. True strategic thinking thus contrasts sharply with the conventional mechanical systems approach based on linear thinking. But it also contrasts with the approach that stakes everything on intuition, reaching conclusions without any real breakdown or analysis." (Kenichi Ohmae, "The Mind Of The Strategist", 1982)
"The obsession with methodologies in the workplace is another instance of the high-tech illusion. It stems from the belief that what really matters is the technology. [...] Whatever the technological advantage may be, it may come only at the price of a significant worsening of the team's sociology." (Tom DeMarco & Timothy Lister, "Peopleware: Productive Projects and Teams", 1987)
"The future prospects of management science will be much enhanced if (a) the diversity of issues confronting managers is accepted, (b) work on developing a rich variety of problem-solving methodologies is undertaken, and (c) we continually ask the question: 'What kind of issue can be managed with which sort of methodology?'." (Robert L Flood & Michael C Jackson, "Creative Problem Solving: Total Systems Intervention", 1991)
"An enterprise architecture can be thought of as a 'blueprint' or 'picture' which assists in the design of an enterprise. The enterprise architecture must define three things. First, what are the activities that an enterprise performs? Second, how should these activities be performed? And finally, how should the enterprise be constructed? Consequently, the architecture being developed will identify the essential processes performed by a virtual company, how the virtual company and the agile enterprises involved in the virtual company will perform these processes, and include a methodology for the rapid reconfiguration of the virtual enterprise." (William Barnett et al, "An architecture for the virtual enterprise", Systems, Man, and Cybernetics, 1994)
"Enterprise Engineering is not a single methodology, but a sophisticated synthesis of the most important and successful of today's change methods. 'Enterprise Engineering' first explains in detail all the critical disciplines (including continuous improvement, radical reinvention of business processes, enterprise redesign, and strategic visioning). It then illustrates how to custom-design the right combination of these change methods for your organization's specific needs." (James Martin, "The Great Transition, 1995)
" Project failures are not always the result of poor methodology; the problem may be poor implementation. Unrealistic objectives or poorly defined executive expectations are two common causes of poor implementation. Good methodologies do not guarantee success, but they do imply that the project will be managed correctly." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)
"EE [Enterprise Engineering] is where the business side meets IT. It is a methodology for active collaboration between business and IT during project development. When business people and IT people know how to work together, the result is faster development and higher quality." (Alan Chmura & J Mark Heumann, "Logical Data Modeling: What it is and How to do it", 2005)
"Effective project and program management involves more than strict adherence to a prescriptive methodology. Leadership skills, judgement, common sense, initiative, effective communication, negotiation skills and a broad perspective on the surrounding environment are all essential. Project and program management is a creative and collaborative process." (Peter Shergold, "Learning from Failure", 2015)
"No methodology can guarantee success. But a good methodology can provide a feedback loop for continual improvement and learning." (Ash Maurya, "Scaling Lean: Mastering the Key Metrics for Startup Growth", 2016)
"[OKRs (Objectives and Key Results): are a] management methodology that helps to ensure that the company focuses efforts on the same important issues throughout the organization." (John Doerr, "Measure what Matters", 2018)
No comments:
Post a Comment