Comment by smugglerFlynn

It is jobs to be done theory on steroids. If someone wants a drill, give them a hole, this kind of logic. Let users literally click “make a hole” button that would instantly make a hole in the wall, and you’ve just disrupted the whole drills market.

Or like in Harry Porter, where you don’t need cooks - food just appears from thin air and floats straight to the tables.

The problem is, jobs to be done theory is not new, and product teams that build Excel and SAP know this stuff. The reason why nobody has yet made an accounting software that is just one magic button is in the amount of user decisions that are necessary to make a “proper hole”.

This is where analogy breaks, because you are not helping to drill a hole anymore, you are helping to design a hole. And to design something you need visibility into what parameters you control, what has just changed with the latest tweak, where rough patches are that require cleanup and design rework.

In programming it just so happened that your code structure and your IDE were also your design UIs. In other areas, like Accounting, your design UI today is Excel and SAP.

Arguably a chat interface can also be a standalone design tool, just not a very user friendly one, like trying to pilot a plane through popup notifications. It works for areas where we fully give control over design to LLMs themselves, but step up into higher level designer shoes and you need proper UI/UX again, chat becomes suffocating.