LukeW | Digital Product Design + Strategy

As AI can agents tackle more work, we naturally assign more work to them.

Just about every chat-based AI application kicks things off with a question.

Last year, I walked through the evolution of AI products to date starting with AI models behind the scenes and ending with an assertion that "the inevitable next step is for AI models to collaborate and interact to get things done."

Big AI models like ChatGPT and Claude get all the attention, but the continually increasing amount of fast, low cost models means today's software can embed little bits of intelligence anywhere they're needed.

The Ask LukeW feature on my Web site has been answering people's product design questions using my writings, talks, images, and videos for over three years.

A few years ago I wrote about the upcoming shift from canvas-centric image and video editing tools to object-centric ones.

Large scale AI models can produce an innumerable variety of output (text, images, code).

There's a growing sentiment that AI lets you do everyone else's job: designers picking up Claude Code, developers spinning up Figma Make.

Today, AI tools are mostly solo sports.

With AI, anyone on a team can generate mockups in minutes.

About a hundred senior designers and leaders from AI labs, big tech companies, and startups got together in San Francisco last week for the Design Futures Assembly.

The designer/developer handoff has been with us for years.

I recently sat down with Mark Swaine on the UX Institute podcast to talk about where interfaces are heading, what's changing for designers, and why most of the software we use today is still kind of crappy.

There's lots of ways to build a website.

There's a question that never goes away in design: should designers code?