Latest blog posts

What designers can learn from engineers

Designers are often ten steps behind engineers in the discipline of shaping and shipping software.

To build or not to build

You might hear advice that sounds contradictory: Build software earlier, or test your assumptions first. Which is right?

Breaking the Figma addiction

Yesterday I ended with the question: Does it always make sense to do Lean UX, and implement straight from wireframes?

Are we lean enough?

Today's #NaBloPoMo post is going to be less hands-on, and more philosophical. It's a reflection on yesterday's post:

Breaking down a design

Thanks to Amy Hupe, I learned that there's such a thing as National Blog Posting Month (#NaBloPoMo for short), and it starts today. So here we go with post number 1.

Learning product design

If you're learning Product Design, it can be overwhelming to know where to start and what should be in scope.

The elements of product design

Explaining product design as a stack of decisions built on top of a stack of knowledge. With apologies to Jesse James Garrett.

Work backwards

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.