StatusCake

Hello Lamp Post – The Gamification of a City

downtime

The UK city of Bristol will play host later this month to a new digital project which allows members of the public to interact with and talk to objects all around them.

The project is the brainchild of the research and design studio PAN, and it’s their “Hello Lamp Post” that has won the first ever Watershed Arts Venue’s Playable City Award.  The awards were launched by the venue and the council alongside universities and tech businesses to find ways in which the city could be explored by its residents, known as Bristolians, and visitors to the city in a more game-like fashion.

The creators say that the aim of their Hello Lamp Post project is to:

“invite [city-dwellers] to try a new way of communicating… to slow down, reflect and give themselves permission to play.”

Bristol residents will be able to interact with urban, everyday street furniture – such as lamp posts, post boxes and bus stops.  These objects already have a unique code on them, so that the local council can identify an object when it needs fixing, but these codes are now used as IDs for the objects – you simply text the object’s ID to wake it up, and it will start talking to you.

When you wake an object it you start a conversation with it, answering questions about your surrounding and what you can see.  When someone else comes along and speaks to that same object they’ll learn more about people that have been there before and what they’ve seen and said.  The more people that interact with the objects, the more that stories of the hidden lives of Bristol’s residents will be opened up.

The Hello Lamp Post project runs in Bristol from July 19th through to September 8th 2013.

James Barnes, StatusCake.com 

Share this

More from StatusCake

A Notification List Is Not a Team

3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years

Alert Noise Isn’t an Accident — It’s a Design Decision

3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.

The Incident Checklist: Reducing Cognitive Load When It Matters Most

4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already

When Things Go Wrong, Systems Should Help Humans — Not Fight Them

3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,

When AI Speeds Up Change, Knowing First Becomes the Constraint

5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things

Make Your Engineering Processes Resilient. Not Your Opinions About AI

4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development.  For some teams, it’s an obvious productivity multiplier.  For others, it’s viewed with suspicion.  A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.