Product Designer - Government

The Product Designer (Government / Public Sector) designs digital services that a member of the public has to be able to complete - applying for a benefit or a licence, renewing a document, filing a return, booking an appointment, checking the status of a case. What makes this seat its own role is not the craft; it is the environment the craft has to survive. Accessibility and compliance are a legal floor, not a quality goal: the service must meet a statutory accessibility standard (typically [WCAG AA] and a Section-508-equivalent obligation), a plain-language mandate, and often data-protection and equality duties, or it cannot go live. The user base cannot be segmented away: it is the entire public, so the design has to hold for someone using a screen reader, on a five-year-old phone over a weak connection, reading at a low literacy level, with no email address, or filling in the form on the worst day of their life. And the work is boxed in by things a commercial designer can wish away but this one cannot - a procured contract that fixes what can be built, a legacy system of record that dictates the data and the rules, a policy that defines what the service is even allowed to do, and a mandated government design system. This is a mid-to-senior individual-contributor seat reporting to a Design Manager, running extensive research with real members of the public and designing across online and offline channels. The centre of gravity is the constraint environment, and that is what separates this seat from a commercial Product Designer (../../001_Product_Designer/). Both frame a problem, design a flow and its states, work a design system, and validate. But the commercial seat chooses a target segment, treats accessibility as a bar to hit, and optimises adoption; this seat serves everyone by law, treats accessibility and plain language as the non-negotiable floor it designs above, carries public-accountability stakes, and spends as much of its craft on the policy, legacy, and procurement constraints as on the interface. This seat also runs deep, applied research with the public but does not own the research practice - that is a UX Researcher's (../../014_UX_Researcher/) remit. And it designs the digital product inside a service; the end-to-end service blueprint across every channel, the back-office, and the policy is a Service Designer's remit, which this seat feeds and draws the seam with rather than owns. What separates great from average is designing for the person the system is most likely to fail, and treating the constraint as the material rather than the excuse. A weak designer designs the clean online path for a confident, able, connected user, meets the accessibility checklist at the end, and blames the legacy system when the service is unusable. A strong one starts from the people least served, designs the service so a screen-reader user and a person with no smartphone can both finish, writes the high-stakes moment in plain language for someone under stress, and works the legacy and policy limits into a service that still functions - or names, with evidence, the policy that has to change.