I’ve been using the Flow Engines principles a lot since late August, when it arose from the Culture Mapping blog project. It’s certainly the most developed, fully realised tool that came out of that burst of work.
Anyway, I used it last week to write a general guide for people to run field trips. I’m not going to detail out below the stuff under the bonnet, as that’d be a bit dull, but save to say it uses the three steps (Consequences, Environment, Embodiment) reinforced inside each other as before.
Why share it? Well, I love a good field trip. But I don’t think people do them enough. So I thought it’d be good to put it up here, as it might be useful to others, but also so that people can add thoughts and ideas on how to improve it.
FIELD TRIPS: GETTING OUT, LOOKING AROUND, WRAPPING UP
A good field trip is something that everyone in any sort of business can get a lot from. Think of yourselves as giant, rechargeable ideas batteries; a field trip provides more good input to replace the output of looking down and typing (which, let’s be honest, we all do too much of).
A field trip doesn’t need to be planned meticulously (though you can if you wish), but you should have a plan in mind to at least give yourself something to deviate from should you need to.
This quick guide will help you write out a plan, and make sure the people you’re leading out have an interesting, useful time.
Step 1 – Getting out
When you have a location in mind to go to, don’t just say “we’re going to xxxx…”, make sure you have a short, focussed explanation in mind of what you want people to learn from going out.
“We’re going to the Science Museum, to learn more about how scientists and inventors discover new ideas.”
“We’re going to Trafalgar Square, to see what happens when you take people out of their natural environments”
To get people to come along, make an invitation that has the location and the reason clearly explained. You can just send an email, or you can be more creative if you wish. What often works well is setting up a little fiction for the trip out; let’s pretend we’re another group of people, or let’s assume that the world is different in this particular way.
Step 2 – Looking around
You don’t have to have been to the location before yourself, but it’s useful. If you haven’t, you should make it clear to the people you’re taking; “we” are going on an exploration. Invite them to be complicit in the discovery of what’s there.
But you should definitely have a good idea of what might be there, from using the internet, or intel from other people who have been.
Once you’re all there, you’re playing two roles.
Firstly, you’re scouting around, looking for the sorts of things that you suspected may be useful. If you spot things, invite others over to see, and think back to the reason you outlined for coming in the first place in order to ask questions?
“What’s interesting about the way Watt discovered a new idea here?”
“How can we tell who are the tourists here? What are they doing that others aren’t?”
Secondly, you’re bringing up the rear, just checking around to make sure that people are happy and comfortable discovering new things for themselves. As you have different conversations with different people who’re on the field trip, try to cross-pollinate thoughts and discoveries – “oh, David was just talking about that with Gillian, you should catch up with them and talk about it”.
Step 3 – Wrapping up
Finally, at the end of the trip, make sure you have time to all sit together and discuss what you’ve all found, in relation to what you set up to explore.
Having a way to write a communal set of notes around the table is really useful; it locks in the learning of the trip, and will help people remember for future use. I usually use Artefact Cards for this, of course, but whatever you want to use is fine. It needs to be in the middle of the table between you all though, to prompt discussion.
If you go somewhere with a gift shop, for instance, you can get everyone to buy a thing that represents what you’ve learned from the trip, and get everyone to explain their object.
There you go then, hope it’s useful. As always, builds and critiques most welcome.