I got sucked into a dispute yesterday between someone who had clearly spent a lot of time and effort formulating a strategy to connect people and departments working towards formulating polices for childrenâ€™s services across the local government sector. For those not familiar with how things work (or not, as the case may be) in the UK public sector, this should be recognised as a truly innovative approach â€“ i.e., establishing an environment for peer collaboration without the constraints of geographical boundaries or politics (with a small â€˜pâ€™) â€“ in other words a Community of Practice.
The poor chap had been struggling to get this initiative launched for some time, and had been knocked back by â€œthe managementâ€ who were more concerned about his use of vocabulary in the supporting documents he had produced describing what a CoP was.
I wonder why, if things look fairly simple (and thereâ€™s nothing remotely complex in developing a community of practice), we insist on building processes around it until it becomes so complex that (a) only qualified â€˜expertsâ€™ can do it properly, and (b) it can only be implemented if it is part of some corporate â€˜grand planâ€™.
I offered encouragement to the chap who was struggling against this tide of bureaucracy, but regrettably I was not empowered to make a difference for him.
This reminded me of quote I read on Euan Sempleâ€™s blog recently about innovationâ€¦..
â€Innovation becomes possible whenever and wherever the right combination of need and solution arises without being killed stone dead by processâ€.
I fear that in this instance, process has once again brutally murdered a good idea!