In Pursuit of Workflow Breakthroughs Using “Just Enough Process Management”

  • Robert Zotti
Part of the Flexible Systems Management book series (FLEXSYS)


This chapter introduces the concept of “Just Enough Process Management” (JEPM). It is the gradual introduction and application of project and process management techniques into “low process maturity” organizations. Such organizations are less likely to have formal initiatives to monitor and manage critical work processes. Significantly, this form of process management is done by individuals at their own behest. Such efforts provide valuable incremental short-term gains and can help pave the way for significant productivity breakthroughs in the long term. This theory is explored through a case study that describes process management efforts conducted in the WebCampus Division of Stevens Institute of Technology. During the transition of WebCampus from a start-up mode to a more routine operation, essential workflow processes evolved from ad hoc procedures. The process goal for WebCampus was to leverage and improve existing cross-functional processes where possible and, in doing so, make it possible to achieve future productivity breakthroughs.


Business Process Process Improvement Business Process Management Software Process Improvement Stevens Institute 
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.


  1. Cook C (2005) Just enough project management. McGraw-Hill Companies, New YorkGoogle Scholar
  2. Hammer M, Champy J (1993) Reengineering the corporation: a manifesto for business revolution. HarperCollins, New YorkGoogle Scholar
  3. Interview with Bob Ubell (2007) Dean of Online Learning, 7 DecGoogle Scholar
  4. Kaplan RS, Norton DP (1996) The balanced scorecard: translating strategy into action. Harvard Business School Press, BostonGoogle Scholar
  5. Kotter JP (1990) What leaders really do. Harvard Business Review, Cambridge, MA. May-JuneGoogle Scholar
  6. Moore GA (2002) Crossing the chasm: marketing and selling high-tech products to mainstream customers. HarperCollins, New YorkGoogle Scholar
  7. Project Management Book of Knowledge(PMBOK) ® (2004) 3rd Edition (p. 3). The Project Management Institute®Google Scholar
  8. Reijers HA, Mansar SL (2005) Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega Int J Manage S 33:283–306CrossRefGoogle Scholar
  9. Rosemann M, deBruin T, Power B (2006) BPM maturity. In: Jeston J, Nelis J (eds) Business process management. Practical guidelines to successful implementations. Elsevier, Burlingston, MA, pp 299–315Google Scholar
  10. Rummler GA, Brache AP (1995) Improving performance: how to manage the white space on the organization chart. Jossey-Bass, San FranciscoGoogle Scholar
  11. Seacord RC, Plakosh D, Lewis GA (2003) Modernizing legacy systems: software technologies, engineering processes, and business practices. Burlingston,MA: Pearson Education, IncGoogle Scholar
  12. Stoddard DB, Jarvenpaa S (1995) Reengineering design is radical; reengineering change is not! Harvard Business Review, 18 JulyGoogle Scholar
  13. Ward RP, Fayad ME, Laitinen M (2001) Software process improvement in the small. Comm ACM 44(4):105–107 Google Scholar

Copyright information

© Springer India 2014

Authors and Affiliations

  1. 1.Stevens Institute of TechnologyHobokenUSA

Personalised recommendations