Steve Bromley has written about who our website is for and why it's important to be realistic about who our audiences are.
Start with user needs
We’ve just finished the alpha phase of improving Parliament's online visitor information, where we did rapid prototyping and testing. Here's what we learned.
Steve Bromley has learned a lot by making mistakes. In this post, he explores some of the challenges teams face that prevent useful research from happening and what techniques he's used to overcome them.
George Lamb recently worked with the House of Commons Library to help them with a new product they hope to release later in the year.
Jack Craig has blogged about the choices we made when choosing our new typeface for the beta website.
This is part one of a series on the people team’s recent alpha on members' activity. User researcher, Marttiina Gilchrist, shares the process and practices that were used to get the team immersed in research and understanding the users.
We recently blogged about creating a new guide to procedure for MPs. John Newton has written about what it was like being part of the product team from a content perspective.
When people think about user research, their image is often of our research lab. Steve Bromley explores the attraction to usability testing in a lab, but also explaind how we decide on the research method used.
We recently launched an online process for petitioning against a hybrid bill after receiving hundreds of paper petitions against a recent bill. Sarah Purssell has blogged about why this was a good opportunity to develop this as a digital service.
We're building a new website and rather than redesigning the entire website at once, we’re creating little bits of it in iterative steps. You'll probably hear us calling this 'agile' and 'iterative' design. Laurence Grinyer explains what agile working looks like in Parliament.