On Good Will Hunting, some further thoughts

Do read Good Will Huntin’ from @fuchsiablue. It’s a terrific post in which Julie explores the loss of good will and the difficulty of trying to find it again. She also describes the importance of it as organisational currency. Good will is an elusive, highly prized thing. In all areas of life it helps us to keep going when times are tough, stay positive and go the extra mile. It’s built in any number of ways, slowly over time or quickly through a grand gesture, a moment of honesty or humility. If I think of the good will I have held for people, organisations, companies and services it’s been built from a patchwork of gestures, actions and conversations that leave you feeling warm not bitter, cared for not discounted, connected not remote. It can be lost quickly through a harsh word or a bad experience, or it can creep up slowly through a number of small disappointments which chip away at your good will. I can think of companies that won my good will quickly and squandered it lightly and customer service teams who’ve turned me around with a tone, a phrase or a simple smile.

So it must be possible as Julie says to go ‘good will huntin’ so here are some top of head thoughts about how we can do that in an organisational setting –

  • Understand where and why it was lost and learn for the future, but try to avoid dwelling on the loss, it’s painful yes but we can’t wind the clock back. Like any currency that’s dropped good will needs to be rebuilt and bolstered.
  • Listen to all positive and negative feedback from staff. Get out and about, talk to people, ask them what they’re feeling, acknowledge the challenges.
  • Find out if the standards/evaluation criteria you’re using to judge goodwill and engagement are the same criteria your staff use – if not, what’s causing that gap?
  • List 10 things you’d love to discover about your organisation if you were a new employee (even if they’re not a reality now).
  • Put yourself in their shoes and play “devil’s advocate” list the 10 least satisfying things about your organisation from an employee point of view.
  • Look for common threads which point you to the need for a new approach or a change in processes, behaviour etc. from the senior team
  • Don’t be afraid to be open, honest and radical if change is needed
  • Find ways to ask your staff regularly whether you’re meeting their expectations and what you can do to improve your performance as an individual and as a leader, weave this into everyday conversations, don’t turn it into another employee survey. Ask the question openly and listen.
  • Solicit suggestions on ways you could work collaboratively to add value to the experience of working in your organisation… What about a hackathon? Or reverse mentoring? Or an employee forum? Listen to suggestions and find ways to act on them.
  • Review your people-related policies and procedures from your employees point of view – get rid of the ones which add nothing – chuck out the chintz as @HRGem would say.
  • Identify one thing you’ve always thought was “impossible” to do but, if you could do it, would completely transform your organisation in the eyes of your staff. Find a way to do it.

I’m sure this is just scratching the surface but thanks Julie for putting a new spin on this topic. I think it’s more fundamental and basic than some of the employee engagement, motivation narratives would have you believe and can be intensely personal and contextual which makes it tricky to find a simple solution for.

I’d love to hear your thoughts on it, I’m sure we all have examples to share and learn from.

If you have to go good will hunting then the hunt is probably just the start of a long road ahead but with a positive mindset, dialogue and persistence the journey could transform things beyond all imagining…
image

NEW & EXPANDED – Corporate Earthquakes and hacking for change

Hacking often has negative connotations, the anonymous tech wizard stealing your online identity or the scurrilous journalist hacking your voicemail. In light of this it was a bit of a surprise to find myself involved in hacking in 2013. In April last year I signed up for my first hackathon – the CIPD-MIX Hackathon ‘Hacking HR to Build an Adaptability Advantage’. CIPD invited anyone interested in HR, OD and workplace issues to join this process to generate creative ideas for increasing the adaptability of our organisations. Almost 2,000 people signed up from across the globe. We were asked to consider ways in which HR could be the catalyst for increased adaptability and how, as HR practitioners, we could play a role in spearheading change in our organisations. The aim of the hackathon was to create a practical set of bold actions that could then be applied to our own and other organizations. When I signed up for the hack I had no idea what to expect. I’d heard of hacks but must confess I thought they were to do with technology, coding and software. In fact, if you look up ‘hackathon’ on Wikipedia (as I did) this is how it describes the process:

A hackathon (also known as a hack day, hackfest or codefest) is an event in which computer programmers and others involved in software development, including graphic designers, interface designers and project managers, collaborate intensively on software projects. Occasionally, there is a hardware component as well. Hackathons typically last between a day and a week. Some hackathons are intended simply for educational or social purposes, although in many cases the goal is to create usable software.

But as I found out hackathons have moved on, or to be more accurate evolved. Nowadays, hacks are used increasingly outside of tech circles to support innovation and creativity in all types of areas from health services to political activism. Whilst some hacks retain a technological focus, and focus on finding digital solutions, others take a broader approach and are looking for any type of solution technological or otherwise. Some of the most exciting examples I have seen recently have been in public services. NHS Hack Days, which retain the traditional focus on technological solutions, are a great example of the use of the hackathon model for developing public services. What are we really meaning when we talk about hacking an organisation or a process? Well it’s more than simply applying a structured approach to problem solving. It’s also about adopting a certain creative mentality and mindset. It’s what Tanya Snook (aka @spydergrrl) describes as ‘playful cleverness’. I really like this depiction of hacking, she says:

When you seek, in your everyday lives, to deliberately find opportunities to be clever, ethical, to enjoy what you are doing, to seek excellence, you are hacking. Now the key here is that this behaviour is deliberate. Not a happy accident. If you aren’t acting this way deliberately, then we need to change your thinking and behaviour a little bit in order to make this your default MO.

A similar point was made by Catherine Bracey in her TEDCity talk on ‘Why good hackers make good citizens’. For me, hacking is about thinking differently as well as doing things differently. You have to tackle problems and challenges in new and alternative ways to have any hope of solving persistent problems or barriers.

What did my CIPD hackathon look like? Like most hackathons, mine included a series of short sprints. This was managed on a digital platform created by the Management Innovation eXchange and participants were supported by hackathon guides who wrote blogs, took part in hangouts and recorded videos to encourage further our thinking. Interestingly, the concept of Hackathon guides was the most controversial element of the whole process with some participants feeling it created a hierarchical structure of experts which was counter to the spirit of hacking. The hackathon process took place over a twelve week period, for NHS Hack Days it is completed in a much shorter duration. But the basic pattern is the same and you can design the hack duration to meet your needs. I’ll run through the process to give you a sense of what participation involved:

  • First, we were asked to help refine the problem, this was referred to as ‘swarming’ the problem (a lack of organisational adaptability). The 120 barriers to adaptability we came up with were then synthesized in to twelve main ‘enemies of adaptability’.
  • We were then invited to share our ‘moonshots’, descriptions of projects we thought could help to overcome the enemies we had identified.
  • Following this, we completed short mini-sprints commenting on each others ‘moonshots’ and signed up to join hack teams to work up the specific moonshots we were interested in.
  • Then we entered the main sprint. Once in teams we specced out the detail of our hacks working collaboratively in whichever way suited us. As our team was global in membership we made use of Google Drive, mural.ly and email to help share ideas and editing of the hack.
  • The lead author had responsibility for getting the hack into its final shape but it was designed to be a collaborative process from end to end.

I signed up for two hacks and was challenged to think creatively about new and old issues facing the world of work. The title of this post refers to one of those hacks, ‘Corporate Earthquakes‘ led by Alberto Blanco and co-authored by myself, Matt Frost, Stephen Remedios, Conor Moss and Guido Rubio. Our hack focused on using immersive learning techniques to empower organisations to face up to seismic change, in doing so participants gain skills and ways of working for the future which will increase organisational agility to predict, survive and build positively on unexpected change.

The CIPD hackathon created a wide-ranging set of bold, practical hacks that were shared with participants, CIPD members and published for other organizations to try. The final report is here and as you read it you can see how the ideas ranged from the creatively complex to those brilliant in their simplicity (see for example ‘Chuck Out Your Chintz’ led by Gemma Reucroft aka @HRGem). Personally, I found it a great chance to get more familiar with new thinking in HR, OD and L&D and make connections with other people working in those fields. I was exposed to range of brilliant ideas about how to increase organisational adaptability.

So why am I still excited about hackathons, what makes them different to any other form of staff or customer engagement?

I’m excited about the idea of planning an organisational hack in the not too distant future, I think this spirit of ‘playful creativity’ can be used in all shapes and sizes of workplaces to bring employees into the heart of organisational growth and development. Simply I believe hack days and hackathons are one potential antidote to clogged up systems and, more importantly, clogged up thinking (see this excellent blog from @whatsthepont for more on this) .

What I’ve found most exciting about these events is that they move beyond traditional models of public consultation and engagement to inspire people and solutions. You don’t come along to a hack just to comment, complain or have your voice heard, you come to contribute to a solution. At their heart hacks are about a collective coming-together to create progress. What’s so exciting about this model is that it thrives on collaboration and connection, bringing people together from a range of backgrounds, experiences and disciplines and it values everyone’s voice. It’s heady stuff for public engagement.

How often have you been pleasantly surprised or inspired by a colleague’s ideas? Hacking gives you a framework for capturing these ideas and then connecting people from different parts of the organisation to build solutions, grow new projects, develop new approaches. That sounds pretty engaging to me and a more inclusive, connected way to solve problems and create momentum than traditional project teams or committees.

If you can make use of simple digital platforms for sharing the ideas and creating the hack teams all the better. Not everyone in an organisation will necessarily be up for using digital tech to manage the hack so you can either go back to basics and do it without digital tools or, even better in my book, use the process to help a wider group of staff get familiar with sharing their ideas and thoughts digitally. Now that would be a win-win situation as far as I’m concerned…

I’ll leave you with Spydergrrl’s useful list of ways you can start hacking for an agile organisation, and you can hear to her talk about these issues in this video

  • Hack yourself: Redefine barriers as a source of motivation in their own right: instead of being frustrated by “the way things are always done,” challenge yourself to do it differently this time. Use yourself as a guinea pig: Work in a way that is outside your own norm. Challenge yourself to think outside your own box. Do something that scares you. Take a risk.
  • Hack your workspace: make it suit your workstyle (art supplies, toys, blank spaces, whiteboards, room to move, a library, whatever you need). Or better yet, leave it. Grab the equipment from your desk and spontaneously hijack boardrooms for weeks at a time in order to collaborate with your team. Work from home. Work from anywhere, any time.
  • Hack communications: Stop attaching documents to emails. Find creative ways to share knowledge in your team: Do daily stand-up meetings (time them!), use chat. Use visuals to share data. In the office where I currently work, you’ll find whiteboards in common areas, win boards to celebrate team wins, libraries to share resources, outlines/ slides/ diagrams taped up in common team spaces with comment sheets so people can give feedback. We still rely too much on email, but we’re trying.
  • Hack your department: We’re not Google but we can still innovate. We can be strategically agile: we can identify trends, we can see challenges with the way things are done and change them. If the required changes seem too big and too bold, we can start small: take the opportunity to make a minor tweak to a process and see if you make an improvement: Find creative ways to use existing systems, to produce better outcomes. Take a risk. Propose your ideas: go ahead an include your bold idea in your deliverable. Even if it gets removed in the next draft, at least you planted a seed. And if it doesn’t, you may incite change.
  • Hack silos: Begin and end all projects in collaborative spaces: check them for drafts, lessons learned and other information sources to expedite your progress, ask the Twitters, Google solutions from other [organisations] in other countries. Share your learnings organization-wide at project close-out. Crowdsource plans and strategies with internal stakeholders and then test your ideas with counterparts in other organizations. Make internal collaborative tools and sites your default tabs in your web browser and use them every day.
  • Hack your training: If you need to learn a new skill and can’t get the training at work, look for free training resources, meetups or other learning opportunities. Better yet, just do it. Take on projects that stretch your skills and knowledge. Can’t get approval? Do it anyway! Help a colleague with their project in their department. Or form a working group and do it for the whole of the organization.
  • Hack your career: Figure out how to work horizontally in a vertical environment: take a job in another stream or classification to expand the depth of your knowledge. Find a project you just need to be a part of and go be a part of it.
  • Hack your perspective: Empathize with your user. Find opportunities to be the client, not just the implementer. Go sit with a program team for weeks or months to better understand the challenges they face using systems in their day-to-day work. Take an assignment and see how the other half works and lives: If you work in a program, go try out enterprise-level projects. If you work on enterprise projects, go work in a client branch to really understand how enterprise-level decisions impact internal users.
  • Hack your network. Become a reverse mentor; teach an executive to use new tools or just chat with them about the realities of working differently. Join groups that work in another discipline or area of interest. Talk to our counterparts outside the organization to find out how they are solving the same problems.
  • Hack your work. Work differently. Every day.

That’s the key for me, the best thing of all, you don’t need permission for hacking, you can start in small ways with yourself, your mindset or your workspace, your approaches – as Doug Shaw would say:

image

Let us know how it goes…

With special thanks to Andrew Jacobs and others for comments on previous drafts and the rest of my Corporate Earthquakes team.   Photo by sobczak.paul under Creative Commons Attribution licence

Corporate Earthquakes and hacking change

Back in April 2013 I found myself signing up for my first hackathon – the CIPD-MIX Hackathon, Hacking HR to Build an Adaptability Advantage.  The idea of the Hackathon was to encourage CIPD members; and anyone interested in HR, OD and workplace issues, to join together and come up with creative ideas for increasing the adaptability of organisations to a fast-changing world. When I signed up for the hack I had no idea what to expect, I’d heard of hacks but I thought they were to do with technology, coding and software. In fact if you look up ‘hackathon’ on Wikipedia (as I did) this is how it describes the process:

hackathon (also known as a hack dayhackfest or codefest) is an event in which computer programmers and others involved in software development, including graphic designers, interface designers and project managers, collaborate intensively on software projects. Occasionally, there is a hardware component as well. Hackathons typically last between a day and a week. Some hackathons are intended simply for educational or social purposes, although in many cases the goal is to create usable software.

hackathon

But as I found out, the approach has moved on, or to be more accurate evolved. See this write up in advance of an event last year in NYC for a great review of the many and varied ways the hacking mentality is being used.  Nowadays, hacks and hackathons are used increasingly outside of tech circles to support innovation and creativity in a range of fields and disciplines. Some of the most exciting examples I have seen recently have been in the public sector, whilst some events have a specific technology focus, aiming to find digital solutions to persistent problems, others take a more inclusive approach and are simply looking for any type of solution to overcome challenges. In the UK a great example is the use of NHS Hack Days, the most recent was run in January in Cardiff and you can read more about the event here.

Like Chris Bolton, who writes the ever-informative What’s the Pont blog , I believe hack days and hackathons are a potential antidote to clogged up systems and clogged up thinking. What I’ve found most exciting about these events is that they move beyond traditional models of public consultation and engagement to inspire people and solutions. You don’t come along to a hack just to comment, complain or have your voice heard, you come to contribute to a solution. And at their heart hacks are about a collective coming-together to create solutions for the future. Invariably, at the end of a hackathon a number of hacks are selected as ‘winners’ and supported in some way (either through funding or corporate/organisational support) to ensure that the ideas come to be realised.

Like most hackathons, mine included a series of short sprints during which we were asked to first help refine the problem (see The enemies of adaptability for a summary of the issues identified during the initial sprint) and then to come up with mini-hacks (short descriptions of our ideas about what could help to overcome the problems identified), participants were then encourage to comment on the hacks and sign up to join hacks they were interested in working on. This was all managed on a simple digital platform created by the Management Innovation eXchange  (who run global hacks tackling a variety of issues). Usually then teams begin work on speccing out the detail of their solutions, working collaboratively in whichever way suits the team. Ours, like many others, was global in membership so we made use of Google Drive and email to help share ideas and editing of the hack. The lead author has the responsibility for getting the hack into its final shape but it’s designed to be a collaborative process from end to end. For the CIPD hackathon this process took place over a three month period, for the NHS Hack Day it was completed in a much shorter duration. But the basic pattern is the same.

What’s so exciting about this model is that it thrives on collaboration and connection, bringing people together from a range of backgrounds, experiences and disciplines and it values everyone’s voice. This is heady stuff for public engagement. For me the CIPD hackathon was a chance to get more familiar with the new thinking in HR, OD and L&D and make connections with other people working in those fields. It did all of that for me, I was exposed to range of brilliant ideas about how to increase organisational adaptability. I signed up for two hacks and was challenged to think creatively about new and old issues facing the world of work. The final hackathon report is here and as you read it you can see how the ideas ranged from the creatively complex to those brilliant in their simplicity (see for example Chuck Out Your Chintz led by Gemma Reucroft aka @HRGem).

So why write about this now after all these months? Two reasons, Firstly I’m excited about the idea of planning an organisational hack in the not too distant future, I think the model is ripe for use in all sorts of workplaces to bring employees into the heart of organisational improvement. How often have you been pleasantly surprised by a colleague’s ideas for tackling a problem or issue? Hacking gives you a framework for capturing these ideas and then connecting people from different parts of the organisation to build solutions. That sounds pretty engaging to me and a more democratic way to solve problems than traditional project teams or committees. Don’t get me wrong to implement change you need plans and milestones and organisation but in the early stages when you’re trying to identify what’s going wrong, or not as well as it should be, why wouldn’t you want to have the widest discussion possible and get everyone involved? And if you’re looking for creative thinking and novel solutions why wouldn’t you want to hear from as many people as possible?  If you can make use of simple platforms for sharing the ideas and creating the hack teams all the better. But not everyone in an organisation will necessarily be up for using digital tech to manage the hack so you can either go back to basics and do it without digital tools or, even better in my book, use the process to help a wider group of staff get familiar with sharing ideas and thoughts digitally, Now that would be a win-win situation as far as I’m concerned.

My second reason for blogging about this now is that a refined version of our CIPD hack ‘Corporate Earthquakes‘  led by Alberto Blanco and co-authored by myself, Matt FrostStephen Remedios, Conor Moss  and Guido Rubio Amestoy has been chosen as a finalist for the Management Innovation eXchange (MIX) Digital Freedom Challenge. The Digital Freedom Challenge team evaluated contributions from hackers around the world , in their words ‘looking for depth, boldness, originality, thoroughness, and the ability to inspire and instruct’.  Our hack focuses on using immersive learning techniques to empower organisations to face up to seismic change, in doing so participants gain skills and ways of working for the future which will increase organisational agility to predict, survive and build positively on unexpected change. We’re very proud that our hack has been selected but in order to make it even better we need people to comment on the hack and give us their thoughts. And time is short so please do have a read of the hack and add your comments, we’d love to hear from you. I’m sure the other finalists would be interested in your thoughts too, see it’s never too late to get involved in a hackathon!