Skip to main content

Interaction Designers and Content Designers – click or clash?

Posted by: and , Posted on: - Categories: Our People, Our Services
Emily Wilkinson and Colin Jones, Interaction and Content Designers - click or clashr

BPDTS’s Emily Wilkinson, Interaction Designer, and Colin Jones, Content Designer, discuss their experience working together, offering 6 tips on how to deliver brilliant work in a fast-paced environment – without pulling each other’s hair out.

How designing with policy creates better services

Posted by: , Posted on: - Categories: Our Insights, Our Services
Pete Bates

Pete Bates, a Content Designer at BPDTS, based in Newcastle, explains why designing with policy helps create better services. Part of Pete’s work is to ensure the service team with whom he works has the information they need. Asking the right questions, in a way that makes sense, improves the user journey by highlighting the essential information citizens need.

Tips on how to design good services

Posted by: , Posted on: - Categories: Our Insights, Our Services
Product Talk: Special with Lou Downe

As a core part of BPDTS's organisational culture, we’re creating an environment where learning is key to everything we do – where time spent working equals time spent learning. The BPDTS Product Talks provide an opportunity for people to learn as part of their continued personal development. In the latest Product Talk, we heard Lou Downe, former Director of Design and Service Standards for the UK Government (GDS), speak about service literacy. Keep reading to learn why good services are verbs, not nouns.

Don’t be arrogant, don’t make assumptions in user-centred design

Posted by: , Posted on: - Categories: Our Insights, Our Services
Philip Middlemass, Head of Practice, Product Design, BPDTS

If you’re involved in product design, please leave your assumptions at the door. Regardless of what role you play in the product lifecycle – a designer, front-end developer, or delivery manager, end-user research and experimentation have a role. Hypothesis driven design leads to better solutions – based on what users want, not what you think they need.