A goal oriented process development guideline

Much of the process work I’ve been involved in over the years ends up becoming an exercise in documentation, or making everyone happy that you have incorporated their input, rather than creating the documented process that is efficient and effective. Here are a few of the often unspoken yet missed guidelines that I think are important to follow when developing any process.

  1. Construct the process that is driven by accomplishments, decisions, and goals, targeted toward the main purpose. Never forget what the process is intended to accomplish. You aren’t trying to touch every resource, unless that is your goal. Skip the work that doesn’t add value toward the goal. And be sure you understand what the goal really is.  That might be harder than it seems, but it is important to get right.
  2. Complete the steps defined to provide guidance and consistency – make sure everyone understands it, and can be successful.
  3. Keep an eye on agreements and measured management – be sure the work is defined, will be done with high assurance, and will be measured for success.
  4. Always assure the flexibility to skip unnecessary steps – creative processes get bogged down, miss deadlines, and become reworked. Development is more about risk management than repeatable procedures and steps.
  5. Create a process that is efficient, high quality, low rework, and eliminates the waste – Lean, MUDA.

 

About Rupe

Dr. Jason Rupe wants to make the world more reliable, even though he likes to break things. He received his BS (1989), and MS (1991) degrees in Industrial Engineering from Iowa State University; and his Ph.D. (1995) from Texas A&M University. He worked on research contracts at Iowa State University for CECOM on the Command & Control Communication and Information Network Analysis Tool, and conducted research on large scale systems and network modeling for Reliability, Availability, Maintainability, and Survivability (RAMS) at Texas A&M University. He has taught quality and reliability at these universities, published several papers in respected technical journals, reviewed books, and refereed publications and conference proceedings. He is a Senior Member of IEEE and of IIE. He has served as Associate Editor for IEEE Transactions on Reliability, and currently works as its Managing Editor. He has served as Vice-Chair'n for RAMS, on the program committee for DRCN, and on the committees of several other reliability conferences because free labor is always welcome. He has also served on the advisory board for IIE Solutions magazine, as an officer for IIE Quality and Reliability division, and various local chapter positions for IEEE and IIE. Jason has worked at USWEST Advanced Technologies, and has held various titles at Qwest Communications Intl., Inc, most recently as Director of the Technology Modeling Team, Qwest's Network Modeling and Operations Research group for the CTO. He has always been those companies' reliability lead. Occasionally, he can be found teaching as an Adjunct Professor at Metro State College of Denver. Jason is the Director of Operational Modeling (DOM) at Polar Star Consulting where he helps government and private industry to plan and build highly performing and reliable networks and services. He holds two patents. If you read this far, congratulations for making it to the end!
This entry was posted in Engineering Consulting, ORMS, Quality and tagged , , , , . Bookmark the permalink.

Comments are closed.