Better communication through mutual learning
How to use the mutual learning mindset and behaviours to be a better designer
Product Design & Innovation
How to use the mutual learning mindset and behaviours to be a better designer
Designers are often ten steps behind engineers in the discipline of shaping and shipping software.
You might hear advice that sounds contradictory: Build software earlier, or test your assumptions first. Which is right?
Does it _always_ make sense to do Lean UX, and implement straight from wireframes?
Am I encouraging bad practices when I talk about a workshop to break down a design into user stories to enable engineering to start?
There are certain patterns that help it go smoothly. And once it's done and the panic of 'oh gosh... where do we start?' has lifted, you can all feel really good and get cracking.
If you're learning Product Design, it can be overwhelming to know where to start and what should be in scope.
Explaining product design as a stack of decisions built on top of a stack of knowledge. With apologies to Jesse James Garrett.
Any time you’re planning, spend some time working backwards. Ask “what’s the key state I’m aiming for?”, then ask “what unlocks or enables that?”. And repeat.