This is a nice and easy framework to use when you find yourself needing to do a quick service discovery to find out some basic details about a service and how it can be transformed. The point at which you might want to use this is right at the start of your digital work, when […]
A while ago I shared a post with a template showing how you can take a capability-based approach to picking technology by focusing on user needs. There has been a fair bit of interest in it since it was published, so I thought it might be useful to run a short online workshop running through […]
A pidgin language is a simplified language, usually used for trade, that allows people who can’t communicate in their native language to nonetheless work together. User stories act like this. We don’t expect customers or users to view the system the same way that programmers do; stories act as a pidgin language where both sides can agree enough to work together effectively.
Acceptance criteria (ACs) are a key part of user stories. They set the boundaries of what should be achieved - telling the developer when to stop, the QA how to test, and the product owner what to expect. Because they’re used by technical and non-technical people, ACs must use simple language and be non-implementation specific. This post looks at why we changed our approach to ACs on GOV.UK Verify and the effect it has had on the team.
Personas are a great place to start with user centred design, particularly if the whole practice is new to your organisation. This is because they can provide a quick and cheap way of ensuring your project puts the different types of user at the heart of your service design process. Personas are fictional representations of […]
Something that I have found helps an awful lot is having a simple way to match identified user needs with the technology capabilities needed to meet them. It helps in two main ways: by encouraging people to consider the user needs they are trying to meet before thinking about technology solutions (always tempting, but dangerous!) […]
User stories are the strongest way you can capture requirements for your digital service and are another key component in taking a user centric approach to design. Rather than the old way of doing things, of producing a specification document outlining every single feature that a product needs to have, user stories focus on the […]