Bottom up Thinking



Views of a problem from a top down perspective are always incomplete. Making sense of the world inevitably means generalisation, and the exclusion of elements considered irrelevant to the ‘big picture’. Whilst this approach has been successful in tightly coupled organisational structures, their limitations are exposed in loosely coupled, networked relationships. The Bottom up view is an aid in overcoming these limitations. In fact, it is valuable in providing a different perspective even in highly structured systems.

The bottom up design approach implies that control mechanisms are at the lowest levels, and responsibilities for actions are at the system element level. This is contrary to conventional management practice, where responsibilities for actions and consequences tend to be placed at a high level. For example, investigating a system failure in bottom up mode would look for causes at the element level, or more precisely, at their interactions. The top down mode would tend to look at the overall system, and would put ‘blam’ on the system itself and how it functions, rather than emergent properties of system element interactions.

Finally, the methodology offered for consideration in this paper is an attempt to formalise an approach using this viewpoint. Constructive criticisms are invited about it.


Previous Stage Emergent Property Problem Space System Element System Thinking 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. Beer, S. “Diagnosing the System for Organisations”. John Wiley, Chichester. (1985).Google Scholar
  2. Bertlanffy, L.von. An Outline of General System Theory. British Journal for the Philosophy of Science, vol.1, p.134–165. (1951).Google Scholar
  3. Bossomer, T., Green, D. “Patterns in the Sand: Computers, Complexity and Life”. Allen & Unwin: Sydney. (1998).Google Scholar
  4. Capra, F. “The Web of Life”. Harper Collins: London. (1996).Google Scholar
  5. Checkland, P. “Systems Thinking, Systems Practice”. John Wiley: Chichester. (1981).Google Scholar
  6. Checkland, P.B., Scholes, J. “Soft Systems Methodology in Action”. John Wiley: Chichester. (1991).Google Scholar
  7. Deacon, R. “The Silent War”. Collins Publishing: London. (1988)Google Scholar
  8. Flood, R.L., Carson, E.R. “Dealing with Complexity — second edition”. Plenum Press: New York. (1993).Google Scholar
  9. Hutchinson, W. Scoping: designing information systems to meet people’s needs, in: Matching Technology to Organisational Needs” D. Avison, D. Edgar Nevill. McGraw Hill: UK. (1998).Google Scholar
  10. Kam, E. “Surprise Attack”. Harvard University Press: Cambridge, Mass. (1988).Google Scholar
  11. Leveson, N.G. “Safeware”. Addison-Wesley: New York. (1995).Google Scholar
  12. Tsoukas, H. Organizations as Soap Bubbles: An Evolutionary Perspective on Organization Design. Sys. Pract., 6, 5, 501–515. (1993).Google Scholar
  13. Wilson, B. “Systems: Concepts, Methodologies and applications 2nd edition”. John Wiley: New York. (1990)Google Scholar

Copyright information

© Kluwer Academic Publishers 2002

Authors and Affiliations

  1. 1.Edith Cowan UniversityChurchlands

Personalised recommendations