The Process Engineering Hammer

Process is a wonderful thing.  In moderation.  At its best, process helps answers the question: If you don't have time to do it right, when will you have time to do it over?  At its worst, process can stifle company growth and innovation. 

 How many times have you seen this happen in a company?  Early on, it's all hands on deck; just get it done.  After a while, as the company grows and gets more complex, disasters start happening due to everybody doing things on the fly.  A meeting is held: processes are needed to ensure that the recent disasters don't happen again.  A group of people that are interested in process get together and start putting out task lists, checkpoints and documentation requirements.  And. Business. Slows. Down.  New ideas that used to take weeks to develop suddenly take months.  The best thinkers are spending more time filling out forms than thinking. 

 This is not good process.  I've seen it happen in all different kinds of businesses and organizations. It's part of the cyclical nature of centralized control and de-centralized decision-making that companies go through during their lifecycle.  But it doesn't have to be this way.

 Great process is a balance between rigor and adaptability, planning and working, documenting and doing.  Use process when necessary and appropriate.  Allow improvisation and judgment when possible.  Keep any process to the minimum necessary to accomplish the goals; anything beyond that is just a waste of time.  In short: develop processes with a light touch.

 Properly done, process can actually save time and increase innovation.  Process that forces groups to do some short, rigorous thinking about the end-to-end project and its risk factors can help weed out half-baked ideas. Or pull the plug on an idea that looked good initially but starts to prove to be a waste of time, thus releasing the team to work on more promising ideas.  It can also help ensure that a job is done right, saving rework time. 

 So, who should be in charge of process development?  Be careful of enthusiasts. To paraphrase an old saying: when you have a process engineering hammer, all the world is a nail.  In fact, I've always felt that the best person to lead process development is someone that is good at it, but doesn't really like it.

 If you have any questions about this article or process development, or would like to talk about how to develop processes that enable and energize your business, contact me at 617-855-5439 or jmarcos@complexityclarified.com.

Visit Complexity:Clarified

Very good. "Be careful of enthusiasts". Very good indeed.

Like
Reply

Well said John. Look forward to the next installment!

Like
Reply

Great topic with valuable insights that are on the mark. Process is a necessary evil, but should not, necessarily be evil.

Like
Reply

To view or add a comment, sign in

More articles by John Marcos

  • Agile: Revolution or Evolution?

    Agile represents a change for traditional development shops, but is it a revolution or an evolution? While Agile feels…

    8 Comments
  • Mastering Risk: How to Use Risk in Strategic Decision-Making

    Here's the easy part: risk is everywhere - even a decision to not take any risks is risky. Now the hard part: how to…

  • How to Talk to I.T.

    Slowly, with lots of TLAs (three letter acronyms). The key to talking with IT is to first understand a bit about…

  • Finding a Great (Banking) Relationship

    Part I: Treasury Services. Treasury is simple, right? It's the mechanics of money in and money out, and it all…

    1 Comment
  • Computers: the Good, the Bad & the Ugly

    Computers can do amazing things, but in fact, they're only good at a few things. Of course, the things that they're…

  • NPV and DCF and WACC, Oh My!

    Net Present Value explained. Which would you prefer someone to give you: one dollar today or a dollar a year from now?…

    1 Comment

Others also viewed

Explore content categories