I’m a web designer and developer whose learning to write more interesting stories and less complex code. I work for the Barbican, an arts centre in London.
Make a browser-based app for people who work at the Barbican and want to book/see available spaces in the centre.
Why? The current events system is too inaccessible for most users. It’s not intuitive to use and requires training to understand. Most users just need an easy way to view which spaces are available, and which are not.
This project has already taken 2 years to reach the first round of testing. I’m going to write a series of posts about it. This is part one.
The current events system (let's call it Filofax) does a decent job of organising events, but is now old and faces some problems:
We’re a small team, so we use Agile project management. The idea is to achieve maximum impact as quickly as possible. We break up work into very specific “tickets” and prioritise those tickets according to the goals of the project. Every 2 weeks, we assess how the project is going, and then create more tickets.
Our priority user story was “I want to easily view event data in an intuitive and useful way”. Therefore, we didn’t focus on themes such as event management/creation quite yet. Also, Filofax already provides this functionality for more advanced users.
We articulated several user stories from our initial brief, and so I began responding to these by creating wireframes in Figma.
I decided there were 3 simple steps necessary to build a view of the event data. The first one was date selection. At this stage, the user can only choose a single-day view. Ranges are not available.
Users needed to have quick entry into the app, so we implemented Office365 authentication. This is the same way we authenticate users' email or website access, so often the login happened without their knowledge.
There is also a sidebar included in the wireframes. It’s not currently included in the build but is the plan for developing app functionality. It contains potential features such as:
We had 3 ideas for useful ways to show our event data:
In Map View, live performances pulsate to denote the noise around them
Both Map and Gantt views contain several similarities:
Each view also contains navigation for:
This article is still being written. If you want to stay updated or have some suggestions, then please email email@example.com
Thanks for your message
I'll be in touch soon :)