Archive

Posts Tagged ‘technology’

Punchdrunk: projects like this need digital specialists

November 18, 2012 2 comments

 

Last week we looked at the LSE Pulse project and what had emerged since its completion. This week we do the same with Punchdrunk. I caught up with Peter Higgin, enrichment director at the immersive theatre company, whose project aimed to connect real-world and digital experiences in a performance space. He told me about the importance of having a digital specialist in a project like this, something they didn’t have the luxury of when it ran.

“Doing it again I think we’d place a digital specialist within the Punchdrunk team,” he admitted. “It would mean we could deliberately break the rules and conventions that we adhere to in the physical space when creating online experiences. We’d also be able to explore the option of creating a bespoke piece outside of Sleep No More.”

There were other lessons as well, particularly with organisation: “We would definitely restructure our scheduling and protect the time set aside for beta testing.”

But what the project did get right was the technical logistics of it all. As Peter told the Guardian back in May 2012, “The physical installation of the project saw us run over 8,000 feet of CAT-5 cable around the site, linking a 100MB internet connection to our control hub within the building with individual runs that broke out to 24 access points. This allowed us to create a network across the building to live stream sound and audio content to both live and online participants.”

The project used a mix of 10 RFID readers and 50 Bluetooth devices, as well as 10 physical portals, “which allowed participants to communicate” said Peter. “These included a poltergeist-like book that online participants could cue to flip a real book off a shelf when their participant was nearby and a typewriter that allowed online participants to type direct messages to their real-world companion.”

Happenstance: clarity is key and don’t forget the non-digital

September 30, 2012 1 comment

As part of continuing series of posts for this blog, I’ll be asking some questions of the experts behind the Digital R&D Fund to see how their answers compare and what other, perhaps smaller arts organisations can learn from…

Last time we heard from the Dero project, and what the team would have done differently had they had another chance at it – this week we ask the same questions of Katy Beale from the Happenstance project

If you could do the project again, what specific things would you do differently and why?

The programme may look deceptively simple, but actually there’s a huge amount of organising that goes into running it. From recruitment, to trouble shooting to establishing a common language and expectations across the organisations.  Even though, on paper, Site Gallery, Lighthouse and Spike Island are similar organisations, they are each very unique and had different concerns and practical issues to consider before we got going. There was a lot more preparatory work than we anticipated, but this was beneficial because it built relationships and began to get everyone to a shared understanding of what the project was about.

“We worked closely with the three organisations to place complimentary pairs of residents into each of their teams. Although we attracted great candidates and residents, for future iterations we would expand the recruitment process and make sure we were clearer about the residency roles and what sort of skills we were asking the residents to bring.

“The benefits of integrating digital technologies into the everyday working culture of the arts organisation include better internal communication, greater tolerance for risk and failure (because when technology fails, it doesn’t signal the end of the project) and a more collaborative, open culture. Something we didn’t anticipate is how much the residents changed the non-digital aspects of the host organisations: at Lighthouse, particularly, they influenced the wider team culture and this might be something we would put more emphasis on in future iterations.”

Happenstance: putting people and technology first

From what I’ve been hearing from the teams involved in and behind the Happenstance project, it’s all about the people, so when I caught up with Lighthouse’s Honor Harger about how the project was coming along, the biggest challenge she said is finding the right residents and putting them with the right arts organisation.

“Finding people who are open, sharing, have a collaborative nature, and are skilled at building trust is the most important challenge of the project,” said Honor. “Thinking hard about the recruitment process was crucial, as was ensuring we had the right arts organisations, who were prepared for the changes the residents were being invited to stimulate.”

The Happenstance project, she said, has been fortunate in that it has found six inspirational residents who have brought energy, knowledge, generosity and open minds to the organisations, and that there had been some clearly observable positive changes at Lighthouse already.

“Our residents, Natalia Buckley and James Bridle, have got us talking more openly with one another, by implementing Agile management techniques,” she said. “And this has had the immediate effect of increasing efficiency.”

“The software tool they’ve designed to help us journal and share our thoughts – Offbot – has been something of a minor revolution within the team,” she added. “It’s helped each of us develop a greater awareness of the nature of everyone’s jobs, and the uniqueness of each voice within the organisation.”

Sandpit Pic

Photograph: Laura Sillars

Honor and the team at Lighthouse have already been looking at how to integrate the tool into wider project collaborations, and she says making technology more familiar in the arts workplace along the way will only help make arts organisations ‘digital by default’.

The Coding Club, which Natalia Buckley established, and James Bridle’s This is A Working Shop has helped demystify digital technology and coding,” says Honor. “It shows the team that technology doesn’t need to be the preserve of specialists; it’s something that all of us can get involved with and that’s been a real revelation for many of us.

“We feel inspired, empowered and motivated and wish our residents could stay on board for longer!”

Matthew Caines is a journalist currently blogging and posting updates from all eight projects involved in the Digital R&D Fund for Arts and Culture

Find out more about the Happenstance project here

Happenstance: making software and making art – the Agile manifesto

June 18, 2012 1 comment

As part of the Nesta, Arts Council and AHRC Digital R&D for Arts and Culture Fund, the Happenstance project, developed by Caper, looks to fund six technology residencies at three major UK arts organisations – Site Gallery in Sheffield, the Lighthouse in Brighton and Spike Island in Bristol.

In an extract from the Happenstance blog, Natalia Buckley explores the relationship between making art and software and experiments with a more ‘Agile’ way of working.

Generally speaking, tech companies try to get good at investigating and reflecting on their own processes – often this results in exciting ideas that challenge the traditional ways of running organisations.

At GitHub, for example, there is pride in the lack of managers – or as Ryan Tomayko puts it, the fact that “everyone at GitHub is a manager… each responsible for managing a single person: their self.”

Another example, Valve, has no formal corporate structure – everyone can pick what project they work on and the desks are furnished with wheels for setting up impromptu temporary teams. Decisions are made by getting enough supporters from across the company who want to work on the project. Their employee handbook describes exactly how it works and it’s a fascinating read.

But there is a philosophy that at first doesn’t seem quite as radical, though it appears the entire software making world is practicing it: the Agile philosophy.

I can quote the entire Agile manifesto here because it’s so short:

We are uncovering better ways of developing software by doing it and helping others do it – through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Happenstance was supposed to help consider whether the Agile philosophy of making software could be useful to arts organisations and, obviously, there are many differences between the ways in which software and art are made. The biggest difference is in the way they are funded; arts funding is mired in bureaucracy, paperwork and relies on relatively few bodies, which grant money to projects that fit within their goals and agendas.

For a while I wondered whether an Agile approach is even useful. Lighthouse is a small team working in one room – most of the work they do is about strategy, planning and managing, rather than making things.

But as I considered it more I realised that agility comes from a specific culture within the organisation and has relatively little to do with making things or technology. The idea that face-to-face conversation is the best way to convey information surely applies outside of the software-making world.

Agility comes from not fearing change or small mistakes and learning to respond to them quickly and efficiently – it’s about responding to change.

I have recently felt like I’ve gained enough trust among the team at Lighthouse to be able to propose anything and that they would at least try it out, knowing that I’ve got their best interests at heart. So I decided to give it a go, and completely banned email as a means of internal communication.

Obviously I have no way of of checking up on everyone, but judging from the feedback and the amount of work-related discussions that are happening in the office, they decided to follow it.

I’ve also introduced daily stand-up meetings where we all very briefly describe what we were working on yesterday and what we are going to be doing today. Somehow the format stuck and we even describe what we all did on our days off as well – it’s actually really nice to be always in the loop, and occasionally hear a funny weekend story.

It made me realise how much and what kinds of work everyone does – all the boring bits: catching up on emails, reviewing things and so on. So after these things were practiced for a while, what good did they do?

I find it hard to quantify it after a short period of time, partly because I don’t actually work on any of their projects, so I can’t tell whether things are easier, better, worse or without change yet.

… I will gather more feedback and then I will report on it.

Matthew Caines is a journalist currently blogging and posting updates from all eight projects involved in the Digital R&D Fund for Arts and Culture

Find out more about the Happenstance project here