FIVE THINGS WE HAVE LEARNED ABOUT COLLABORATIVE WORKING
PLEASE DOWNLOAD THE ARTICLE FOR THE FULL VERSION, INCLUDING IMAGE(S) AND FOOTNOTES
In Sutton, we are proud of our legacy of collaborative working. From a unique community safety partnership with the Metropolitan Police (8 years old and counting…) to the launch last year of a shared ICT service with the Royal Borough of Kingston-upon-Thames and a shared legal service with three London boroughs, we feel we are getting better at delivering projects of this nature.
At the beginning of 2014, Sutton, Kingston, Richmond and Merton councils were awarded £485,000 for further shared services work under the Transition Challenge Award, so we must be doing something right.
That is not to say we are perfect by any means. However, with shared arrangements of different types moving into double figures and two more in the pipeline, we felt it was time to take stock and review some of the lessons we have learnt. Below are five key concepts that might help you:
1. Beware the Tower of Babel
Share a language. A shared service means different things to different people. Organisationally, we found it helpful to map out the shared arrangements we have in place and to categorise them. This is set out in the Resource vs Speed Pyramid on the next page.
This exercise was more of an art than a science, however it has helped clarity of thinking when embarking on initial discussions.
I would recommend doing a similar exercise with potential partners in the early stages of a collaborative project and to be prepared to negotiate on terminology as your partners may have different views.
The value comes from a shared language for the project as it helps discussions and the formulation of a vision.
2. It’s a change programme Jim, but not as we know it
It is easy to treat collaborative projects as change programmes; they share a number of similarities. However, the biggest difference is that you are dealing with multiple organisational cultures – and usually political aspirations. This adds a complexity unlike an internal transformation programme and it should be recognised, managed and, crucially, seen for what it is, a risk if left unchecked but an opportunity for delivering better outcomes if that diversity is channelled and ideas are genuinely shared.
3. Use PRINCE2
A project management approach is essential, however collaborative working occurs in a less controllable environment.
We have found that dedicated project management and project support helps ensure success. These posts do not need to be externally sourced but they do need to be committed to the project.
We also suggest having a minimum of a project sponsor chairing an executive board for strategic decisions (and elected member engagement), along with a project board with clear project assurance from the respective partners.
Having workstreams for (at least) communications, workforce development and finance are also no-brainers and you will need to think about ongoing governance of the service from the beginning.
Above all, be comfortable with the fact that all shared services work moves you in to an uncontrolled environment and that this offers opportunities.
4. If it ain’t broke, it still might need fixing and it might have been broke all along
Don’t be precious about your existing organisational practice.
Learn from others and use these projects as chances to take stock and see what is happening elsewhere.
The way you do things now might be fine but everyone can improve and this is a perfect time to consider how. Furthermore, be proud of what you do well and share it – with humility!
Communication works for those who work at it
Everyone talks about the importance of communicating during projects, particularly where they involve organisational change but who can say they have done it really well?
Too often this is the part of a project that has the best of intentions behind it at the outset but loses focus as work progresses.
Good communications need expertise, planning, resource and senior management commitment. For a shared services project, all publicity is rarely good publicity!