On this page
Questions you could ask me
Astutech won a competitive tender to design and develop the Norfolk Fire Service website around 2004–2005. We delivered the service and continued supporting and developing it for several years.
The website combined public information with fire-safety education, interactive games and a live incident feed. It was a substantial public-service project with very different audiences and a practical responsibility to make important information accessible.
Making public information useful
A fire service communicates with very different audiences.
Some people are looking for general advice. Others need information about local activity. Children and families may respond better to interactive educational material than to conventional guidance.
The site needed to accommodate these requirements within a coherent experience.
I was closely involved in designing the front-end and much of the underlying engineering, working with my team on the resulting service.
Our responsibility didn’t end with the initial implementation.
We continued supporting and developing the website over several years, gaining a practical understanding of the organisation and the particular needs of emergency-services communication.
That experience became valuable later.
Another opportunity
Around 2012, I competed for a separate contract involving the Norfolk Resilience Forum.
This was a different kind of organisation and project, bringing together representatives of several emergency services and other agencies.
The proposal involved a website and mobile application.
I attended a presentation to a panel of approximately a dozen senior representatives, including personnel from the police, fire, ambulance and Coastguard services.
I knew there were other bidders.
As I waited, I saw one of my competitors leaving with display boards and a considerable amount of presentation equipment.
I had chosen a different approach.
Putting the idea in their hands
Rather than relying entirely on slides and explanations, I had prepared a prototype of the proposed mobile application.
The demonstration was a realistic interface prototype, not the finished application. It let the panel experience the proposed design directly before we built the working service.
I asked the people around the table to take out their phones and load it.
Suddenly, the discussion was no longer limited to what an application might look like.
They could see the interface, hold it in their hands and experience the proposed direction for themselves.
A prototype can make a difficult conversation much more concrete.
People who may have different technical backgrounds can respond to something they can see and explore. They can form opinions about the proposed experience without first having to understand the engineering behind it.
That was the purpose of bringing the prototype.
The result
I received a telephone call on my journey home informing me that I’d won the contract.
Our established Fire Service work showed that we could deliver and maintain a relevant public-facing system. The prototype made the next proposal tangible. Together, they gave the panel something concrete to assess.
It illustrated the experience I wanted to create, rather than requiring the panel to reconstruct that experience from a specification.
The delivered Norfolk Prepared platform
After the tender, the work became a functioning service. The delivered Norfolk Prepared solution comprised mobile applications for iOS and Android and a responsive website. A central content management system allowed the Forum to publish emergency information to both channels from one source.
The applications also provided preparedness guidance, quizzes for adults and children, and an I’m Safe facility for letting contacts know that someone was safe following an incident. Astutech’s archived case study describes delivery on time and within budget, followed by maintenance and support. It also preserves customer feedback attributed to Jayde Robinson, then Norfolk Resilience Forum Business Manager.
Those accounts are contemporary project and customer records. They should not be confused with an independent evaluation. The separate Norfolk Prepared case study examines the delivered system and its architecture in greater detail.
What the two projects demonstrate
I tend to think of these contracts together because they illustrate two related aspects of engineering work.
The first is the importance of delivery.
Winning a contract is only the beginning. Building a service, supporting it and developing a reputation for dependable work matter over time.
The second is the importance of communicating a design clearly.
A technically capable solution can still be difficult to explain, especially when several organisations and professional disciplines are represented in the same room.
Sometimes a document is the appropriate way to communicate.
Sometimes a diagram is enough.
And sometimes the most effective thing you can do is put the proposed experience directly into someone’s hands.
A working relationship is built through delivery. An idea becomes easier to support when people can see what it means.
Those two principles have served me well.
Project context
Topic: Emergency services
Explore further
Further reading is listed below.