... ok, of PDS for now - but world domination can follow.
The data and search team recently spent a day with the Web Science Institute, discussing some of the challenges facing the team as they deliver new data and search services at parliament.
As many of you will be only too familiar with, recruiting people into technical roles can be particularly challenging. Here at PDS we're dedicated to finding better ways to deal with these challenges.
Since April, I've been working as part of the Data and Search team. It's a new team so we've been figuring out what we do, what we don't do, how we work together and with other people. And we've made a fair bit of progress in identifying what's currently broken and how to fix it.
Some readers might know who we are, but I’m sure that many still don’t know. So, this post aims to answer a few existential questions about the (Corporate) Data team that you may have.
As you know, here at PDS we’re busy building a new website. As part of the discovery work the content team are doing, we recently carried out a couple of short workshops about the content management system (CMS).
Last week the Parliamentary Digital Service had the pleasure of hosting codebar.
Back in March, I was part of the House of Lords contingent at the Rapid Start event. The key theme was ‘Unlocking democracy for all’ and, in a small but significant way, our prototype delivered that aim by making it as easy for anyone to follow statutory instruments (Parliament considers around 1,000 per year) as for bills (around 20 per year).
In the different areas I’ve worked - I’m from the Commons Library, but have spent some time in the Commons Committee Office – we’ve never excelled at getting good, quick feedback from Members or their staff.
Towards the end of May we went to see Matt Jukes at the Office for National Statistics (ONS) in Newport to learn from his experience as Product Lead building the new ONS website.