The Thought Process on Processes

I have mentioned before about my fascination with proper processes. OK - I admit that sometimes I dream about processes... but wait – I digress!

For a process to work effectively, it must be developed with all the proper considerations. Yes, I can hear you thinking – he’s trying to tell me that there’s a process to design a process!

Here’s what I think you should consider when designing a process:

1. What’s the outcome you want to achieve? Working backwards from the outcome is a useful decision tool, which will help you keep the object of the task in mind at all times.
2. Who will be impacted when this process is rolled out? Those are the people you need to engage with. These people range from the do-ers to the owners of the process. By including these people in the process design, you will increase your chances that they will take ownership and champion your design after you have finished with it.
3. What is currently being done? Sorry for the platitudes, but they hold true. Don’t fix what isn’t broken. Don’t try to reinvent the wheel. Only change what is necessary, making sure you have a damn good reason to do so! 
4. How is it currently being done? Work with what you’ve got (oops – another platitude!). We don’t live in an ideal world, and (for example) even when the process owners say that they will invest in new technology, that’s often to be taken with a grain of salt. Do your research about what is a real possibility.
5. Think in binary terms where possible. A simple process is a good process. Where possible, each stage of the process should be driven to the next stage by a yes/no alternative.
6. Don’t underestimate the time it will take. Designing a process can’t be done in isolation. You will need to engage with busy people who have day jobs. Make sure you account for lag-time in your project. Also, be organised – give people deadlines to get back to you and remind them when the deadline is coming up. Another good suggestion is to use their inertia to drive behaviour - "Please get back to me with your comments by Monday. If you don't then I will assume you are happy with the current draft and I will progress on that basis."
7. Test the process before you roll it out. I know that sounds obvious, but make sure testing is comprehensive and that you factor time in for any changes that may be required as a result of testing.
8. Sew in periodic process review dates. Set regular review dates to make sure the process still works and that it is still current.

Of course, there will be other considerations depending on the type and function of the process you are developing. But I think the above is a good start to the thought process! See what I did there….?