PDS does a lot of stuff. As our user research team is relatively small, we need to prioritise what work we focus our attention on. We also need to find other ways of supporting the rest of the work done by PDS.
Start with user needs
Laurence Grinyer talks about the common misconception that design is only about aesthetics.
We recently completed an intranet discovery project. A team of people from PDS worked together to understand the user needs of the Parliamentary intranet.
As part of the work we’re doing on the new website, we’re testing the beta pages with our users. During this testing, we’ve seen some unexpected behaviour from users.
Laurence Favager talks about his career move from journalist restricted by deadlines, to PDS content designer free to iterate.
We're making our content work harder by making it easier to understand. To borrow a phrase from the experts on plain English – this isn't about dumbing down, it's about opening up.
The Parliamentary Archives stores more than four million records and are the oldest Parliamentary archive in the world. They recently started working on a transformation project and are planning on building a new website, which is where we come in.
User needs are mentioned a lot in PDS. In this post, I explain my understanding of user needs, what starting with user needs means, and how PDS does this.
The Digital Development team in PDS has rapidly expanded, and there are a lot of new faces. Feedback from our last away day showed that staff wanted to get to know colleagues. With this purpose in mind we decided to get everyone together to do some user research.
Our user researchers use collaborative analysis workshops to share the findings of research with stakeholders. In this post, Steve Bromley, explains what those workshops are and why we use them.