Andrew Duckworth
I'm a deep thinker about product and design. Sign up for my newsletter.
Latest articles
- Service design is not mostly convincing other people to do service design
- Justifying design's impact
- When and how to move from an assumption to a hypothesis
- It's okay to start with a stakeholder's solution. Just don't stop there
- Start with the forms
- Get beyond the 'so what?'
- The role user-centred design (UCD) should play in AI development
- Get more out of design reviews
- Test often to keep your designs simple
- Why you made a bigger impact as a smaller design team
- Being clear about the shifts you need to make to get people to buy or use your service
- Growing design by letting teams experience it
- Do the design digging
- Experience-threat modelling
- Why designers design forms
- Don't underestimate being at the heart of things
- Accessibility and inclusion isn't always going to be cost neutral
- Codesign and the carnivalesque
- User stories aren't the tale for discovery
- Overcrowding the pan
- Choosing what discovery to go forward with
- Conditions for tackling problems
- Shaping design work (with STAR)
- 1 to 1s
- Don't let your design system seem complete
- Win the space to design services
- A common mistake teams make is designing for a context their users don't have
- Let your headings do the hard work
- Find a way of having presence
- A good question isn’t going to magic away a terrible policy or an unintuitive process
- Do less
- A retrospective on your retros
- Still waiting for perfect
- Making outcomes clear
- For professional users
- Document as part of your process
- Holding yourself and others to account
- Share before you solve it
- Yearnote: 2019
- Don't forget to stretch your design
- Design for real data
- Find the right words to get the job done
- Start it right
- Make it about a decision
- Let your design breathe
- Make it easier for yourself and others to work in the open
- Making your work open isn't just the final icing on the cake
- Prototyping in shorthand
- Minus interference
- You never know, you know
- Do the hard work to make it inclusive
- One thing per page
- Ask a question
- Asking the right question
- Offline services and paper forms
- Explaining a thing over saying a thing
- Trying a new format for hypotheses
- Make things obvious
- Show at your show and tell
- Questions for your questions
- Dashing dashboards
- Advice for aspiring junior UX designers
- Treat your design process like a design problem
- Kanban for interaction design
- Hypothesis driven design
- YAWYSCA or Yet Another Why You Should Code Article