Back to The Curious Case of Henry Modisett, with Henry Modisett.
Why Does Perplexity Refuse Design Mocks?
Henry Modisett refuses design mocks unless Perplexity really believes it will build and launch the work. A mock can open a project. It is not worth the design team's time when the company does not mean to ship it.
A mock is cheaper in hours than a built product, so an anxious organization asks for three directions and turns design into a service that draws possible outcomes. Blue-sky prompts get out of hand because they are fun for the person asking, and they kill the team's energy. The best designers want to make things people use, not visualize options for leadership.
He compares that trap to a concept car. People who love automobiles can spend a career on cars nobody drives, while another group builds the vehicle that reaches the market. He agrees that a designer who will not ship is making concept cars for a manufacturer on the way out. The picture also needs someone who understands the real constraints, or a lot is lost between the drawing and what can be built.
The Curious Case of Henry Modisett ·
From the transcript
It's cheaper in terms of man hours to make a mock. And so especially if there's a kind of an anxiety in an organization or an uncertainty, it's nice in leadership to be like, okay, let's mock up three options. Three directions. And then design becomes this sort of service organization to like visualize possible outcomes rather than, you know, a important part of the sort of strategic and launch process.
And something that I'm pretty intense about in our company is like we don't make mocks for things we're not actually going to build. Yes. Mock sort of like a starting point of a project. Interesting. Not like a, we don't like, unless we really believe this is something we're going to build and launch, like it's not worth exploring and certainly not worth my design team's time.