Skip to main content

In Conversation with Ben Holloway, Head of Data and Navy Applications

Posted by: , Posted on: - Categories: Navy Digital

Ben Holloway, the head of Data and Navy Applications was asked to join the judging panel for the first pan-Defence Hackathon at RAF Henlow. Eighty people from the RAF, Army, Navy, Reserves and Civil Service worked together in cross-functional teams throughout the week to find solutions to MOD-wide problem sets.

Enabled by Astra and delivered by Appivate, Digital Academy and Navy Digital, the Defence Hackathon builds on the success of the RAF Hackathon held in 2021. Extending the Hackathon across the MOD enables the identification of talented individuals in any profession who have a technical skillset that will benefit Defence Cyber and Digital.

The Defence Hackathon is an opportunity to promote professional career paths within Defence and generates a sustainable network for both professional and non-professional developers to collaborate across the MOD, while valuing their skills and providing a future for our people in a technically-evolving world.

Ben provides his thoughts on the event below.

What did you expect of this year’s Hackathon?

I was privileged be one of the judges for the final, alongside senior Digital reps from other TLBs and the Chief of the Air Staff. This was the first one I’ve attended, as such, I didn’t really have too many expectations around it. Teams were given criteria such as technical feasibility, business value and then executed their idea over a strict 2-day window. 

What impressed you most?

The fact that these were a complete mix of backgrounds, from the very senior to the very junior, who had come together to build something in only 2 days.  There must have been 150 people there, either as competitors or as part of the support team. 

Talking to the teams themselves, they were almost inappropriately enthusiastic and very diverse. It was great to see a genuine mix of backgrounds, ranks, gender, ethnicity, experiences and specialisations, both military and civilian. Not that you could see much of this at first glance – the only uniform was a hoodie with no clue as to rank. There was also no hierarchy, everyone had an equal voice, their value was judged solely on what they said or did.  

The winning team developed something special. They’d chosen to attack the sustainability and environmental challenge and developed an app which used open-source thermal satellite imagery, overlaid on maps and integrated with data from smart meters, to show which buildings on a military establishment were energy inefficient. 

This allowed users to then conduct analytics on the data (which they’d also built tools for) and get a sense for how much money or carbon footprint they might save by doing something like installing energy saving light bulbs.

I left the Hackathon enthusiastic about what I’d seen. There were 6 Navy people represented in the teams from a mix of places, some had worked in digital before, whereas some didn’t know such jobs existed and had entered because of a personal passion. 2 of them were between jobs, on holdover, and as such one of them has subsequently joined us here in DNA. 

What will you do differently at the next one?

I’ll attend some of the earlier days.  The start of the week included upskilling sessions from industry partners like Apple, Digi2al and VMWare.  They would have been pretty good, I think.

How much upskilling was required of the participants, or did they need to have the skills before they went?

My understanding was that everyone had dabbled beforehand, but not all of them were deeply technical.  There were people who attended as Delivery Managers, User Researchers and Business Analysts alongside the technical team members who did the physical development activity. They had fantastic ideas born of their individual experiences over the course of their careers and they had the skills and aptitude to do something about them. In addition, they all had a passion and aptitude for digital as the common leveller.

What attracted the new member of staff to join DNA whilst they were there?

The guy we’ve acquired is a holdover officer who really wanted to employ the skills he had to offer meaningful output to the RN.  Whilst he’s waiting for a permanent place on his professional training course, why would he not want to work in the RN’s Software House?!  We will take his skills and put them to good use whilst also structuring a programme of experience so that he leaves with more than he had when he joined. 

DNA could become a good place for more holdover personnel to join us. They could come and learn agile, including how to work in Jira and act as a Scrum Master. Learn some credible digital skills, maybe even how to build something which might make their lives easier in future jobs. There are loads of development opportunities out there, we simply need to help people find them. 

What links were evident to DNA/Navy Digital's existing portfolio?

We’ve been thinking for a while that there’s potential to offer more mobile products than simply MyNAVY / MyRAF.  These are absolute flagship products, but there’s so much more which could be done.  The only problem has been that with only about 5% of the Navy having MOD phones or iPads, people needed to want to download them onto their personal phones.  Any such products needed to be absolutely focussed on making the users’ life better or easier.  

For example, one Hackathon team had developed an IOS app which published a QR code to the Apple Wallet which in turn could be used to grant access to an establishment and had developed the whole approval workflow to go alongside it – potentially great for temporary visitors to a naval base, such as for a homecoming. Another team had developed an app which allowed you to report potential security incidents from your phone, use the camera to take a photo and the location services to drop a pin. These alerts then went to a central dashboard where a user triaged them, could task others to respond and could issue push notifications to users in the vicinity to keep them updated. Whilst this was a great use case, it could also have been used for literally anything – building defect reporting, parcel notifications from the mail room, etc.

The Hackathon has really opened my eyes to what could be offered and has resulted in some follow-on conversations about where this might go.

What cross pollination would be possible between industry, education, and defence?

Good question – I think it’s fair to say that nothing is off the table, but that we’re not much more advanced than that.  Cross pollination is always challenging within the MOD’s security requirements, but we’ve now got Hack4Defence which turns academia onto the Defence problems as well as the internal Defence Hackathon.  Is there something which could join the two…?  Maybe…!  Either way, DNA will continue to try and work with both Industry and the Education sector to develop people, skills and products which better the Navy, both today and set conditions for success in the future. 

Sharing and comments

Share this page

Leave a comment

We only ask for your email address so we know you're a real person

By submitting a comment you understand it may be published on this public website. Please read our privacy notice to see how the GOV.UK blogging platform handles your information.