Field of Dreams

Helen Walker

Helen Walker has worked in the field of educational technology for over 25 years – obviously, she doesn’t look old enough to have done so. She is now a joint owner of Purify Technology, a company which helps organisations to ensure that their technology works, is adopted and has impact. She runs Purify with Dave Prior-Jones (who has a better business brain than her) and Akin Fadipe (a solution architect and all-round good egg).

Website: www.purify-tech.co.uk

Email This email address is being protected from spambots. You need JavaScript enabled to view it.

Build it – but they won’t necessarily come.

I love ‘Field of Dreams’. For those of you that don’t know the film, Kevin Costner plays Ray, an Iowa farmer who hears a mysterious voice in his cornfield saying, "If you build it, he will come." He interprets this as an instruction to build a baseball diamond (what else?) and, once it’s complete, he is visited by the ghosts of the 1919 Chicago White Sox. If you haven’t watched it, don’t let this synopsis put you off – it really is a brilliant film.

Not sure about its marketing and implementation message though: build it and they will come. Maybe this works in the spiritual realm, but in the more prosaic world of IT, we can build it but it definitely doesn’t mean that they will come. Or use it. Or read the instructions. Or thank you for all of your hard work in building the thing in the first place.

I was at a BESA LearnED event recently and one of the brilliant panellists advised us to yes, have failures and learn from them, but not to Tweet about them. Sod that. Let’s share failure. Here’s one of my big ones from back in 2015. Back then, one of the projects I was attempting to breathe some life into/resuscitate was an online forum for nominated ‘Digital Leaders’ from a number of schools within a multi-academy trust. The forum was established to support these DLs in the roll-out of new technologies, software and curricula within their schools by providing them with the facility to share experiences, resources and ideas.

I met with them in Manchester in the summer and we spent two days together, discussing and plotting e-learning initiatives, and developing and extending their plans for the delivery of the Computing curriculum. During those few days, I introduced the forum to them and we began to use it as a collaboration space: resources were shared, conversations were started and plans were hatched. All left enthused and promising to keep in touch via the forum. And then... well, very little. A few more posts dripped through and then there was silence. Partly, this was due to the summer break but my attempts to reinvigorate this digital space following that first meeting failed.

field dreams 2

Why? Well, in this instance, we/I hadn’t created an effective community. I took a ‘field of dreams’ approach to the development of the forum: ‘build it and they will come’. Unfortunately, creating a space, providing a tool, or setting up brilliant systems does not encourage presence, participation, or adoption. In this particular instance, I had provided no ‘rules of engagement’: participation was informal, voluntary and unstructured. I had not effectively designed, directed, and informed the transaction:

‘One of the difficulties with early computer conferencing was sustaining participation and high levels of discourse (Gunawardena 1991; Hiltz and Turoff 1993). Low levels of interest and participation were rooted in a lack of structure and focus resulting from an excessively ‘democratic’ approach. While there must be full and open participation, for a purposeful educational experience there is an inherent need for an architect and facilitator to design, direct, and inform the transaction.’ (Garrison and Anderson, 2003, p.29*)

field dreams 3

Many of us will have experienced ‘low levels of interest and participation’ when it comes to introducing new IT kit or systems. There may be cupboards of shame in your schools where dusty visualisers or tablets sit untouched, or expensive software that was used for a few months by a couple of enthusiastic members of staff but which was gradually forgotten. The reasons for the failure will be subtly different in all instances but, at root, failure of adoption is down to the fact that we can’t just build it, we need to give reasons for them to come and – more importantly – to stay and use it. Garrison and Anderson perceptively identify the need for directed, designed action within community educational experiences. We also need to structure and focus implementation and adoption activities, designing, directing and informing the change.

Some key principles include:

  • Understanding why you’re making the change and what your success criteria are. The reasons for change should be clear and specific. For example, if you’re considering adopting Microsoft Teams because it will ‘improving communication’, that’s great but what does that mean? What are the problems with how you communicate now? How will Teams help? Which specific communications and workflows will you use Teams and the wider Office 365 ecosystem for – and how? What will your communication architecture look like?

  • Executive level engagement. If your leaders aren’t on board, you might as well pack up and go home. You need a sponsor - an advocate/cheerleader/big flag-waving fan - at senior level. In Field of Dreams Ray (Costner) believed in the voices, he had a vision, he made it work. But he made it work because he owned the farm and could make the decision to cut down the corn to make way for the baseball field.

  • Champions, digital leaders, pilot users. Call them what you will, it’s vital that you trial the tech with a smaller group before you roll out at scale. There are so many benefits to this: problems are addressed on a small scale before they become a big issue, models for best practice can be established, and you’re also developing, through this process, a team of in-house experts who will be able to provide peer support with adoption once the wider roll out happens.

  • Baby steps, don’t boil the ocean and other clichés. Whichever well-worn adage works for you, heed it. So many tools can do so much and it’s tempting to try and achieve a lot as you can as quickly as you can. But start small and stay focused: granular, stepped changes are the way forward.

  • WII FM(?) As the brilliant Susan Hanley has pointed out, many of our internal radios are tuned to WII FM – ‘What’s In It For Me’. It’s vital that you make the case for change clear to individuals: how will they benefit? How will the tech improve things for them? When explaining this, you should focus on scenarios not services. So, rather than, ‘Teams will make it easier for you to work together’, be explicit about the specific ways that it will: ‘So, Janet, you know how frustrating it is when there are multiple versions of a document in our library drive? Well, let me introduce you to SharePoint and versioning…’

So, have a plan, get buy-in, test it, sell the message and, importantly keep assessing the impact of the change you’ve implemented. Adoption is never ‘finished’ – unlike a baseball field – but hopefully, if you build the solution and the process well, they will come.

Want to receive cutting-edge insights from leading educators each week? Sign up to our Community Update and be part of the action!

In order to make our website better for you, we use cookies!

Some firefox users may experience missing content, to fix this, click the shield in the top left and "disable tracking protection"