How do you make things happen? The more I think about this the more it sounds like an existential riddle.
If you make things happen in the woods at night and there’s nobody there who’s see’s you do it, does it mean that the doing it didn’t happen?
Or, what’s the sound of one hand happening?
That sort of thing. But then I think – cogito ergo sum and carry on as before.
Making things happen from within healthcare is Not Easy. Attempting to make an online infrastructure as a platform to drive innovative and collaborative online projects and applications within the world of Wellbeing and Mental Health is impossible. Well, almost.
To do it – you have too:
- get everyone (and by this I mean strategic individuals from) on board and embedded citywide as a concept – in this case: The voluntary sector, Adult Social Care, The Mental Health Trust, Service Users, Carer’s, Organisations and Other People (just regular people who don’t use or work in healthcare services)
- stop everyone on board from deciding that they are individually in charge and get them used to service design principles – pretty much by stealth
- reveal things slowly – explain how an infrastructure like an iPhone for example is great, but the app’s – that can be designed by anyone is what makes the infrastructure the really exciting bit.
- stop everyone from running off with a million idea’s that they want to start making immediately despite the money, funding and actual infrastructure not yet being in place
- make a really (really) rough kind of infrastructure (which really is a ning or a shared blog) in place and get people used to the collaborative way in which it works and continuously develops technically.
- stop some people panicking about how the world will implode at the risk of such a thing.
- write a lot of documents. A lot – Ownership agreements. A year ahead sustainable project plan with business planning forecast. Detailed service user engagement. Setting up innovating on Local Policy and Practice Advisory. Planning National Collaborative Policy Sharing. Technical Development plans. Pilot findings and recommendations. erm. Even your own Job Description. Possibly.
- go back to the (still)enthused (miraculously) people who were ready to start setting up interesting projects to make content to go on the first early prototype infrastructure. Tell them – all systems are go.
- stop justifying your existence
- then, start doing the real work of making it all work, together.
- (because this goes up to 11) start engaging everybody you can. Everyone in fact.
I am currently somewhere between 7, 8 and 9. I’m glad to be done with 6. Not that there aren’t still panickers. But its no longer my job to do the stopping of the panicking, alone.
Give it three months and my current piece of Making Things Happen will have happened. And if I do it right it will all seem so simple no one will even imagine the impossibility of how Making it all Happen actually was (is).
Except for me. And the bear. In the woods.
* as an addendum to anyone in the independent sector reading this and saying – ‘but this is an insane way of doing a startup – what madness!’ Yes. Exactly.
** as an addendum to my use of the words insane and madness. Using them here, to describe the way in which processes within health and social care directly oppose wanted innovation and entrepreneurial developments seems a very apt application. Much more so than to describe people having meaningful responses to distress.