Jon Plummer

I’ve long felt that the double-diamond design process was poorly explained, and my attempts to explain it to engineering-led organizations were typically met with cries of “waterfall!”

I like arguing with the agent because it reminds me of good things I already think.

Almost every 404 here is a near miss.

In 2012 we published a design framework at Belkin.

When people worry about applying AI to regulated product development, they’re usually worried about the wrong phase.

Two changes to the site today: the nav split into a leaner header and a full footer map, and side projects got a home of their own.

Care has to show up in the product, I argued last time.

If attention to detail isn’t visible in your product, it’s hard to say you care about the details.

I flubbed an interview question the other day.

Building is easy, taste is hard.

Danielle asks: Does anyone have experience doing research on design systems?

Ideas are cheap.

When a developer isn’t sure which button variant to use for a destructive action, they can ask.

In the old system, quality required specification and inspection.

There’s scuttlebutt that AI is squeezing designers out.

A product team needed to decide if and how to provide a little convenience around an API Name when their user enters a Display Name.

Last month I shipped an iOS app.

I built Monotasker to solve a specific problem: I have too many home and side projects, and it’s easy to get bogged down in the list.

These notes assume you’ve read the process documentation.

A Concept Sprint is a short, usually week-long, in-person exercise meant to accelerate high-level exploration of a new area of development, a significant problem, or a strategic initiative.

The case for human interfaces becoming obsolete is getting more sophisticated.

Last year I wrote about a first batch of “hidden” pages on this site – RSS feeds, a technologies list, the changelog, etc.