Many designers in government either began, or have had extensive careers, in the private sector before joining the Civil Service. Below is a compilation of our personal experience and our observations of the differences between the 2 sectors.
From doing it all to trusting in a team
Vicky Teinaki, Senior Interaction Designer
In the private sector, I was a user experience (UX) designer, doing everything from wireframing to diary studies. However, when I switched to government I had to specialise. I started in user research and then switched to interaction design.
I had to let go of doing all parts of user-centred design, but I believe that it’s right. Given the importance of government services, all roles have best practices to follow and changes to keep up with. For example, when I was a user researcher, I had to follow rigorous recruitment practices and diligently share results. As an interaction designer, I know the nuances of using GOV.UK Design System patterns and the prototype kit.
However, being a specialist doesn’t mean working alone. A key part of the role is working with other people with complementary skills in a team. I never got to do this in the private sector, and now it’s my favourite part of the job. I love collaborating with a content designer and shaping a user-centred journey together. It’s also great to work with technical colleagues to understand the art of the possible and iterate designs based on user insights from user researchers and performance analysts.
Designing and building with accessibility in the forefront
Nikin Nagewadia, Interaction Designer
Having worked in the private sector for most of my professional career, I’ve noticed that accessibility was a major talking point at many of the organisations I’ve worked at.
Although there was a lot of interest in making a product or service accessible, when it came to prioritizing works, accessibility was low on the list in favour of projects that can lead to an immediate increase in profit margins. Whenever accessibility was prioritised, that was based out of necessity, usually to avoid any legal repercussions as that can impact an organization’s reputation and their finances.
Having been in the public sector for over a year, I can attest that accessibility is core to the design and technical implementation of a digital service. Especially since they are meant to be accessible to anyone and everyone who needs to access a government service. Accessibility doesn’t solely apply to services. There are also colleagues who advocate for accessibility by offering training and consultation sessions and being vocal when a product or service is not completely accessible.
At GDS, we have 10 design principles; our 6th design principle begins with “Accessible design is good design”. This ethos holds true, especially since our services are intended to be used by everyone no matter their capabilities.
Being part of a community
Chris Ballantine-Thomas, Senior Interaction Designer
The design community, both at GDS and across the public sector, is what I love most about working in government. I don’t know of anywhere else you can work where you can draw upon the experience of so many other designers – who are all committed to the same thing: designing better public services.
At GDS, designers work in multi-disciplinary teams where you might be the only designer. The design community gives us a space to get support and feedback from one another. We also work together to make GDS a better place to do design – things like improving our hiring processes or onboarding for new staff. These have been a great way to push my skills in directions that my day-to-day work might not offer.
We collaborate on a bigger scale across government too. There are thousands of designers in government now – and different groups get together to push forward various aspects of our craft. Whether that’s working together on new user interface (UI) components or sharing advice on how to grow more equitable design teams, we learn from each other’s work and work in the open so we can build on each other’s knowledge.
The importance of effective research
Courtney Toth, Interaction Designer
Working in the private sector, both in an agency environment and as part of in-house design teams, I found that organisations understand the importance of user needs. Still, there are challenges in empowering teams to research with users effectively.
The reality with the private sector is that financial factors will always be the biggest barrier to successful user research. This could manifest as a lack of budget or incentives to test with users. It could be not investing in research and design roles, or even favouring insights pulled from testing which represent low-cost fixes to a service rather than large, fundamental changes.
Some of the other barriers I’ve experienced in the private sector include using research to merely validate designs (to ‘tick a box’) and not having an established design community or effective way to share learnings across teams.
Having now made the shift to working in government, it’s clear that user needs drive design in the public sector. We have committed user researchers who work with designers to shape and carry out research. We work openly, share findings across teams, and user-centred design is embedded in our design principles and the Service Standard.
But most importantly, we speak to users regularly and utilise the insights we learn from them. Users will inevitably need to interact with government services. So it’s vital that we design for everyone, and that starts with understanding user needs.
Working in the open
Martin Jordan, Head of Service Design
In the public service, we are serving the public. As obvious as it may sound, we have an obligation to the people paying for what we provide via their taxes. So our task is to create the most public value for the money spent.
In my previous role in a global tech company, people prided themselves on the number of patents they had filed. In an organisation like GDS, people are instead proud of how many contributions to the Design System, a piece of guidance or a GitHub repository they have made. Similar to open-source software development, all are things shared openly with the public, the wider public sector, and governments abroad.
Through blog posts, on social media, at meet-ups and conferences, hundreds of colleagues talk openly about what they are doing, share work in progress and ask for feedback. This level of openness drew me to work at GDS. People proudly embrace the Government Design Principle ‘Make things open: it makes things better’.
And it’s not just the more senior people doing it. Design interns and junior designers are blogging, running show & tells, talking publicly, which all helps them gain confidence and develop faster. To me, that’s us living the idea of a learning organisation.
Come join us
We’re looking for mid-level and senior service designers to work on some of the toughest problems in public infrastructure, changing the way government delivers services by making them simpler and easier to use. If you’re interested in being part of the transformation, apply by Sunday, 10 March 2022.